[theme-reviewers] input from theme reviewers - top do's and don'ts
Kirk Wight
kwight at kwight.ca
Thu Jan 26 01:30:27 UTC 2012
Yep, already using those, thanks for posting them :)
On 25 January 2012 20:12, Chip Bennett <chip at chipbennett.net> wrote:
> Er, that link might not work :)
>
> http://www.slideshare.net/chipbennett
>
> Chip
>
>
> On Wed, Jan 25, 2012 at 7:11 PM, Chip Bennett <chip at chipbennett.net>wrote:
>
>> I think those will make great presentation points, Kirk!
>>
>> If it will be helpful, feel free to use anything you need from my WC
>> presentations (all of which, so far, involve Theme development and review):
>> http://www.slideshare.net/chipbennett/edit_my_uploads
>>
>> What kinds of examples/code/comments are you looking for?
>>
>> Chip
>>
>> On Wed, Jan 25, 2012 at 7:03 PM, Kirk Wight <kwight at kwight.ca> wrote:
>>
>>> 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)
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> theme-reviewers mailing list
>>> theme-reviewers at lists.wordpress.org
>>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>>
>>>
>>
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120125/ec178ca5/attachment.htm>
More information about the theme-reviewers
mailing list