<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>I found this troublesome to a very large degree on some themes where
overrides couldn’t happen directly in the child theme because of load order so
the theme had an override box in the theme options to compensate but shaking my
head about it; it feels totally doing-it-wrong.</DIV>
<DIV> </DIV>
<DIV>I’ve even seen one theme where they had ANOTHER style-override.css file
meta tag in the header.php that happens after the wp_head execution where advise
people to use that to place their overrides in.</DIV>
<DIV> </DIV>
<DIV>Then plugins like jetpacks edit-css module and my theme companion; you can
never be sure if the override will happen after their wp_head injection of their
overrides; ugh it’s just a mess when theme developers do that.</DIV>
<DIV> </DIV>
<DIV>..pure headache /agree</DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">
<DIV style="FONT: 10pt tahoma">
<DIV><FONT size=3 face=Calibri></FONT> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=weavertheme@gmail.com
href="mailto:weavertheme@gmail.com">Weaver Theme</A> </DIV>
<DIV><B>Sent:</B> Wednesday, July 16, 2014 12:26 PM</DIV>
<DIV><B>To:</B> <A title=theme-reviewers@lists.wordpress.org
href="mailto:theme-reviewers@lists.wordpress.org">Discussion list for WordPress
theme reviewers.</A> </DIV>
<DIV><B>Subject:</B> [theme-reviewers] Best Practice Question:
style.css</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style="FONT-STYLE: normal; DISPLAY: inline; FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: small; FONT-WEIGHT: normal; TEXT-DECORATION: none">
<DIV dir=ltr>
<DIV>
<DIV>
<DIV>
<DIV>I've been looking at some themes lately, and have noticed what may be a
trend in how style.css is handled.<BR><BR></DIV>A number of themes, including
Responsive, for example, are providing an "empty" style.css with just the header
info needed to work with WP, while providing the actual style in a style file
buried in some subdirectory. One loads the "real" style first, followed by the
standard style.css (to get child themes)<BR><BR></DIV>I can see both positives
and negatives with this. <BR><BR>It makes it a little harder for users to mess
with it directly.<BR></DIV>It allows a theme to more easily load one of several
style sheets depending on options, perhaps.<BR></DIV>
<DIV>It simplifies creation of child themes in that they don't have to @import
the parent stylesheet (if they know the parent is using this
practice.)<BR><BR></DIV>
<DIV>The main disadvantage I see is that a child theme can't do a total style
replacement by NOT @importing the parent.<BR><BR><BR></DIV>
<DIV>Any thoughts on this? It seems there should be some guidelines on and
"empty" style.css and putting the theme style elsewhere. It really does affect
how child themes deal with the parent style.css.<BR><BR>Bruce
Wampler.<BR></DIV></DIV>
<P>
<HR>
_______________________________________________<BR>theme-reviewers mailing
list<BR>theme-reviewers@lists.wordpress.org<BR>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<BR></DIV></DIV></DIV></BODY></HTML>