I tend to agree, which is why the Guidelines are as detailed as they are.<div><br></div><div>But, that level of detail has led to complaints. So, I'm wondering if there is a reasonable way to balance concerns?</div><div>
<br></div><div>I like your suggestion. It definitely keeps everything together on one page - and helps us summarize the main points/goals that we're trying to accomplish with the Guidelines.</div><div><br></div><div>Chip<br>
<br><div class="gmail_quote">On Wed, Oct 20, 2010 at 3:51 PM, Marty Martin <span dir="ltr"><<a href="mailto:m@seoserpent.com">m@seoserpent.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I think a bulleted sidebar box or a list at the top of the original page with #anchor links or something like that is best rather than a second page, because if you/we implement the simplified list, then in my opinion designers won't look at the expanded list and it'll increase problems for reviewers. I could be completely wrong, but that was my gut reaction.<div>
<br>Marty<br><br><div class="gmail_quote"><div><div></div><div class="h5">On Wed, Oct 20, 2010 at 4:49 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</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></div><div class="h5">
All,<div><br></div><div>In order to address the complaint that the Theme Review Guidelines are overly complex, and too long/difficult to read, what would everything think of creating two versions:</div><div><ol><li>Simplified Guidelines, that list just the requirements</li>
<li>Expanded Guidelines, that go into specific details (listing specific features/functions/implementations/etc.)</li></ol></div><div>I'm not really sold on this approach (two pages are more difficult to maintain than one, single page), but I can see the benefit of a shorter, less-detailed list of the existing Guidelines. To wit:</div>
<div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div>Code Quality</div></div><div><div><ul><li>Themes are required not to have any notices, warnings, errors; or use of deprecated functions.</li>
<li>Themes are required to utilize current recognized version(s) of (X)HTML and CSS.</li><li>Themes are required to generate no JavaScript errors</li><li>Themes are required to have a valid HTML document HEAD</li></ul></div>
</div><div><div>Functionality</div></div><div><div><ul><li>Theme is required to incorporate the following WordPress core functionality:</li><ul><li>Automatic Feed Links</li><li>Comments</li><li>Widgets</li></ul><li>Theme is recommended to incorporate the following WordPress core functionality, but is not required to do so. However, if incorporated, functionality must support the core WordPress implementation:</li>
<ul><li>Navigation Menus</li><li>Post Thumbnails</li><li>Custom Header</li><li>Custom Background</li><li>Visual Editor CSS</li></ul></ul></div></div><div><div>Template Tags and Hooks</div></div><div><div><ul><li>All template tags and hooks used in a Theme are required to be implemented properly, including incorporation of required template tags and hooks where appropriate.</li>
</ul></div></div><div><div>Including Files</div></div><div><div><ul><li>If incorporated into the Theme, standard template files are required to be called using the correct template tag.</li><li>If incorporated into the Theme, custom template files are required to be called properly.</li>
<li>Themes are required to include all template files called within the Theme, rather than relying upon legacy Theme support.</li></ul></div></div><div><div>Site Information</div></div><div><div><ul><li>If incorporated into the Theme, site information is required to be called using the correct template tag.</li>
</ul></div></div><div><div>WordPress-Defined CSS Classes</div></div><div><div><ul><li>Themes are required to support WordPress-defined CSS classes</li></ul></div></div><div><div>Theme Template Files</div></div><div><div>
<ul>
<li>Theme is required to include all template files, as specified.</li></ul></div></div><div><div>Licensing</div></div><div><div><ul><li>Themes are required to be 100% GPL-licensed, or use a GPL-compatible license.</li></ul>
</div></div><div><div>Theme Name</div></div><div><div><ul><li>Themes are required to adhere to Theme Name Guidelines</li></ul></div></div><div><div>Credit Links</div></div><div><div><ul><li>Themes are required to adhere to guidelines for appropriate credit links</li>
</ul></div></div><div><div>Theme Unit Tests</div></div><div><div><ul><li>The Theme must meet all the requirements of the Theme Unit Test.</li></ul></div></div></blockquote><div>(Or something along these lines. I culled this very quickly from the existing Codex page.)</div>
<div><br></div><div>Thoughts?</div><div><br></div><font color="#888888"><div>Chip</div><div><br></div>
</font><br></div></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></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>