What you are describing should be fine ... just make sure you document it well; more for the end-user than anything else.<br><br>The upload script / Theme Check should not see any major difference; and, the Theme reviewers should be comfortable enough to read the CSS imports to find what they may need to look at more closely.<br>
<br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote">On Sun, Jul 10, 2011 at 5:13 AM, Tony Crockford <span dir="ltr"><<a href="mailto:tonyc@boldfish.co.uk">tonyc@boldfish.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 9 Jul 2011, at 19:27, Chip Bennett wrote:<br>
><br>
> AFAIK, the only naming "conventions" are those that impact template files - i.e. not using "reserved" names for template files, and using page-{template}.php for custom Page templates.<br>
><br>
> Beyond that, I don't think anything exists, and like Cais, I don't think anything *needs* to exist.<br>
<br>
</div>That's good news then.<br>
<br>
On a similar note, is there anything that prevents me from not having my CSS in style.css - i.e. *having* an empty(ish) style.css, but using CSS loaded from a different folder in my theme?<br>
<br>
By way of explanation, I'm just building up to theme-building and making sure that my preferred way of working won't have to change.<br>
<div><div></div><div class="h5">_______________________________________________<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>
</div></div></blockquote></div><br>