[theme-reviewers] input from theme reviewers - top do's and don'ts

[Kirk Wight]

Hello all theme reviewers,

I'll be giving a presentation at our next WordPress dev meetup (Montreal)
about theme review; the process in general, and code requirements/best
practices for a successful submission. While I obviously won't be speaking
officially for the TRT, I'd like some input from you all regarding some
content. Any appropriate examples with your comments would be greatly
appreciated too!


Top three do's for getting your theme accepted:

   - Make sure your theme meets all of the requirements. ALL of them. If
   you're unsure about a requirement, don't submit it and hope for the best -
   ask on the mailing list and do it correctly before submitting.
   - Develop with WP_DEBUG true, and with the Theme Check, Log Deprecated
   Notices, and Debug Bar plugins activated.
   - Subscribe to the theme-reviewers mailing list, as well as the TRT P2
   site to stay up-to-date.


Top three don'ts for getting your theme rejected:

   - Don't try to "game the system": coding around issues rather than
   solving them, spammy links, base64_decode, submitting under different
   profiles
   - Don't be abusive or threatening
   - Don't be vague about licensing; all themes in the theme repo must be
   100% GPL-compatible, and explicitly declared so (this includes all code and
   binaries, such as images and icons)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120125/e2db4e9d/attachment.htm>