<div dir="ltr">I'm neither for nor against an "empty" style.css (from a guidelines point of view) ... but if it's a matter of over-writing the "buried" stylesheet why not just (copy and paste, then) dequeue it and carry on?<div>
<br></div><div>Link: <a href="http://codex.wordpress.org/Function_Reference/wp_dequeue_style">http://codex.wordpress.org/Function_Reference/wp_dequeue_style</a></div></div><div class="gmail_extra"><br clear="all"><div>Edward Caissie<br>
aka Cais.</div>
<br><br><div class="gmail_quote">On Wed, Jul 16, 2014 at 3:36 PM, Emil Uzelac <span dir="ltr"><<a href="mailto:emil@uzelac.me" target="_blank">emil@uzelac.me</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Empties are ugly and not really needed. </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">
This is what I do for my clients:</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default"><div class="gmail_default"><font face="arial, helvetica, sans-serif"> // Parent theme style.</font></div>
<div class="gmail_default"><font face="arial, helvetica, sans-serif"><span style="white-space:pre-wrap"> </span>wp_enqueue_style( 'my-style', get_template_directory_uri() . '/style.css', array(), null );</font></div>
<div class="gmail_default"><span style="white-space:pre-wrap"><font face="arial, helvetica, sans-serif"> </font></span></div><div class="gmail_default"><font face="arial, helvetica, sans-serif"><span style="white-space:pre-wrap"> </span>// Child theme style.<span style="white-space:pre-wrap"> </span></font></div>
<div class="gmail_default"><font face="arial, helvetica, sans-serif"> if ( is_child_theme() ) {</font></div><div class="gmail_default"><font face="arial, helvetica, sans-serif"><span style="white-space:pre-wrap"> </span>wp_enqueue_style( 'my-child-style', get_stylesheet_uri(), array(), null );</font></div>
<div class="gmail_default"><font face="arial, helvetica, sans-serif"><span style="white-space:pre-wrap"> </span>}</font></div></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div>
<div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Parent style.css remains at the usual place and when child is active it will add it's own stylesheet :)</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">
<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">And of course no @imports either ;)</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Wed, Jul 16, 2014 at 2:26 PM, Weaver Theme <span dir="ltr"><<a href="mailto:weavertheme@gmail.com" target="_blank">weavertheme@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><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>
<br></div></div><div class="">_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></div></blockquote></div><br></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>