Currently, I would consider this point to be RECOMMENDED, rather than REQUIRED.<div><br></div><div>At some point down the line, I would love to incorporate more documentation-related guidelines, just to move more Themes in the direction of best practices and WordPress documentation/coding standards; but for now, I just point out things like that, and recommend the developer follow the WordPress documentation standard.</div>
<div><br></div><div>Chip<br><br><div class="gmail_quote">On Sat, Oct 15, 2011 at 11:03 AM, Kirk Wight <span dir="ltr"><<a href="mailto:kwight@kwight.ca">kwight@kwight.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
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>_______________________________________________<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>