I would say these would be best practices for the most part, although I would
like to get 'namespace' and 'textdomain' both as strongly recommended to be the theme
slug into the guidelines.<br>
<br><br>Cais<br><br><div class="gmail_quote">On Wed, Oct 20, 2010 at 12:00 PM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Wed, Oct 20, 2010 at 10:47 AM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
> Or, are these better left to "best practices", and left out of the<br>
> Guidelines?<br>
<br>
</div>Yeah. That. For any case you can come up with, somebody will be able<br>
to come up with a reason to do it a different way.<br>
<br>
Generally, the single options entry of a serialized array is best...<br>
except when it's not. ;)<br>
<div class="im"><br>
> On a related note: should we formalize the suggested function nomenclature<br>
> (Theme slug as unique function-name prefix)?<br>
<br>
</div>Should be in a recommended, I'd say. Or best practice. Or whatever you<br>
want to call it. But yeah, the theme-slug should be your prefix, and<br>
everything that should be "unique" to the theme should be prefixed. Or<br>
in a class-as-namespace structure.<br>
<font color="#888888"><br>
-Otto<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>
</font></blockquote></div><br>