Absolutely, we can definitely add this as a "RECOMMENDED" item ... it will most likely be a reviewer's eye-on approach for the foreseeable future, too.<br>It would be good practice to insure the documentation is readily available (inline) especially as we approach the derivative themes issues.<br>
<br>We can leave it to Simon and Otto for sorting out how to add it to the Theme-Checks but it strikes me as something much too arbitrary to "conditionally" check.<br><br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote">On Sat, Oct 15, 2011 at 12:17 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hey, if you think that it's time to move in that direction, I'm all for it! :)<div><br></div><div>I generally do list @package/@subpackage as *recommended* in my reviews now anyway, when I see Themes using @package: WordPress. But if we want to begin formalizing it, that's great.</div>
<div><br></div><div>But I do see this as RECOMMENDED, for the foreseeable future.</div><div><br></div><font color="#888888"><div>Chip</div></font><div><div></div><div class="h5"><div><br><div class="gmail_quote">On Sat, Oct 15, 2011 at 11:15 AM, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Although we have no say over how Plugins and their guidelines are created and implemented it does strike me as a good idea to follow suit on items that make sense; in this case I would agree the Theme guidelines should be making similar references to how the theme's inline documentation (i.e.: phpDocs) is written, more for some sort of consistent approach than anything else.<br>
<br>This is something that can be put forward as part of the "new" v3.3 guidelines: Documentation Recommendations (and Requirements, as applicable).<br><br><br clear="all">Cais.<br>
<br><br><div class="gmail_quote"><div>On Sat, Oct 15, 2011 at 12:03 PM, Kirk Wight <span dir="ltr"><<a href="mailto:kwight@kwight.ca" target="_blank">kwight@kwight.ca</a>></span> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
Are we allowing "@package WordPress" references in theme DocBlocks?<div><br></div><div>I found <a href="http://lists.wordpress.org/pipermail/theme-reviewers/2010-November/003118.html" target="_blank">one list reference</a> questioning the practice based on plugin guidelines, but available themes such as Duster and Coraline still have them. Should they be accepted?</div>
<br></div>_______________________________________________<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></blockquote></div><br>
<br>_______________________________________________<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></blockquote></div><br></div>
</div></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>