I really like the 3-tier approach, especially the second tier option.<br><br>Communicating before the initial review a better definition of what is expected may help speed up the process of the actual review itself.<br><br>
<br>Cais<br><br><div class="gmail_quote">On Tue, Jul 13, 2010 at 4:52 PM, Lance Willett <span dir="ltr"><<a href="mailto:nanobar@gmail.com">nanobar@gmail.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;">
>> Good afternoon, Theme Reviewers!<br>
<div class="im">>> Please take a look here:<br>
</div><div class="im">>> <a href="http://codex.wordpress.org/Theme_Development_Checklist_Draft" target="_blank">http://codex.wordpress.org/Theme_Development_Checklist_Draft</a><br>
>><br>
</div><div class="im">>> These are the draft theme development checklist and review criteria. Please<br>
</div>>> take a look and comment. Once we're all agreed on the guidelines, I'll<br>
<div class="im">>> generate WXR and SQL files to accompany the revised guidelines.<br>
<br>
</div>Thanks for your work on this, Chip. I'll be working on this as much as<br>
I can this week.<br>
<br>
I don't think an SQL version is necessary, just the WXR to import into<br>
a test install.<br>
<div class="im"><br>
>> Everything should be retained from the current TDC, and I've updated the<br>
>> required file structure and supported functions/features through WordPress<br>
>> version 3.0.<br>
<br>
</div>Let's clarify the purpose of the checklist.<br>
<br>
1. Is it only to show what is required to submit a theme to the directory?<br>
2. Or is it also for theme developers in general?<br>
<br>
For option one, the purpose would be "What are basic items I need to<br>
check off before I get my theme submitted?"<br>
<br>
Option two is a list that can be used by web designers wanting to make<br>
a rock-solid theme -- perhaps for a client site or for personal use --<br>
*and* by theme developers wanting to create rock-solid<br>
publicly-released themes.<br>
<br>
An example of this distinction is the license requirement. That should<br>
be required for directory submissions, but not for a theme developer<br>
that is creating a theme for a client project.<br>
<br>
Should we consider doing a tiered checklist in three pages?<br>
<br>
1. Theme Coding Standards<br>
An updated version of the current theme development checklist aimed at<br>
all theme developers listing the standards that every WordPress<br>
theme--including themes that will never be publicly released--should<br>
abide by.<br>
<br>
2. Theme Directory Standards<br>
A new checklist that specifically states the requirements for<br>
submitting a theme to the WordPress.org directory (then edit<br>
<a href="http://wordpress.org/extend/themes/upload/" target="_blank">http://wordpress.org/extend/themes/upload/</a> to point to this page).<br>
<br>
3. Theme Unit Tests<br>
A simpler version of the current test data with some useful updates.<br>
<br>
Thoughts?<br>
<font color="#888888"><br>
--<br>
Lance Willett | Automattic Theme Wrangler<br>
</font><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>