<p>I think the plugin link should be included in the guidelines themselves, under best practices.</p>
<p>Just my 2p</p>
<div class="gmail_quote">On May 28, 2012 11:53 PM, "Doug Stewart" <<a href="mailto:zamoose@gmail.com">zamoose@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Right, but not all theme devs think "Oh, I should join TRT" and thus<br>
miss out on that info. I think this is one of those cases and thus we<br>
ought to think about adding a link, prominently, to the submission<br>
process.<br>
<br>
On Mon, May 28, 2012 at 5:36 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>> wrote:<br>
> There used to be a "resources" section on the Theme Review Codex page, but<br>
> it has since been moved elsewhere. The Theme Review page is intended to be<br>
> the Guidelines, and *only* the Guidelines.<br>
><br>
> That said: if you follow through to the Theme Unit Tests Codex page, you'll<br>
> see a link to How To Join WPTRT:<br>
><br>
> Read How To Join WPTRT, and follow all test-environment setup instructions<br>
><br>
><br>
> The setup instructions on How To Join WPTRT includes a step to install Theme<br>
> Check. :)<br>
><br>
> Chip<br>
><br>
> On Mon, May 28, 2012 at 12:01 PM, Doug Stewart <<a href="mailto:zamoose@gmail.com">zamoose@gmail.com</a>> wrote:<br>
>><br>
>> On Mon, May 28, 2012 at 10:30 AM, Central Victorian Irish Association<br>
>> <<a href="mailto:info@cvia.com.au">info@cvia.com.au</a>> wrote:<br>
>> > Well,<br>
>> > Kind of pointless trying to argue the point isn't it? Especially, from<br>
>> > what<br>
>> > you tell me, your own theme (twentyten) is not compliant but yet<br>
>> > released<br>
>> > with WordPress.<br>
>> > But never mind, my frustration only comes from my passion to make a<br>
>> > contribution to Open Source and not towards those who do not have that<br>
>> > passion.<br>
>> > I will fix the "Recommended" issues and resubmit it. I won't be holding<br>
>> > my<br>
>> > breath though.<br>
>> ><br>
>> > Have a good day.<br>
>> > Dan<br>
>> ><br>
>><br>
>> Dan:<br>
>> Did you run your theme through the Theme Check plugin by any chance?<br>
>><br>
>> Theme review team:<br>
>> I note that the submission page and the Codex articles don't seem to<br>
>> call out the Theme Check plugin as an excellent way to avoid these<br>
>> sorts of developer frustrations. Is there a particular reason we avoid<br>
>> pushing this valuable tool so as to save theme devs a few headaches?<br>
>><br>
>> --<br>
>> -Doug<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>
><br>
><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>
<br>
<br>
<br>
--<br>
-Doug<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>
</blockquote></div>