[theme-reviewers] Theme Review Codex Page: Addressing Recent Feedback

Otto otto at ottodestruct.com
Thu Aug 26 20:37:19 UTC 2010

Looking at it now. Random order thoughts follow:

XHTML is dead, we should allow for the fact that many newer themes are
going to be HTML 5. I have personally switched to it exclusively. Note
that the core can produce acceptable HTML 5 just fine. BTW, "profile"
is not supported in the head tag for an HTML 5 document.

Widgets are only necessary if the theme has a sidebar. Not all themes do.

Automatic feed links may be undesirable in some custom purpose themes,
or if the theme incorporates its own special types of feeds (using
add_feed or similar). Possible examples: photoblog, podcasting
specific theme, comic strip oriented theme.

Ditto comments, not all special purpose themes need necesarily support this.


On Thu, Aug 26, 2010 at 2:30 PM, Chip Bennett <chip at chipbennett.net> wrote:
> Good afternoon, all!
> I have started making an attempt to incorporate recent feedback and
> constructive criticism into the Theme Review Codex page:
> 1) "Last Updated" line added
> 2) Separated Functionality from Tags and Hooks
> 3) Under Functionality, indicated which functionality is required and
> recommended, and tied relevant function calls/xrefs to functionality
> 4) Under Functionality, for recommended functionality, indicated that
> functionality is not required, but if implemented, must support WordPress
> core functionality
> 5) Under Tags and Hooks, separated template-part tags
> (get_header/get_footer/get_sidebar/etc.) from other tags and hooks
> 6) Under Tags and Hooks, indicated that template files
> (header/footer/sidebar/etc), if incorporated in the Theme, must be called
> using the correct template tag.
> 7) Replaced "must" and "should" throughout with "required", to avoid
> confusion. All Guidelines should now read as "required", "recommended", or
> "optional".
> I made a few changes yesterday, too:
> 1) Added all missing Codex xrefs
> 2) Added links to Log Deprecated Notices plugin, Debogger plugin, and W3C
> validator (XHTML, CSS, and Unicorn) under Guidelines/Code Quality
> 3) Added emphasis to statement instructing developer to ensure Theme meets
> Guidelines and is tested using Theme Unit Tests prior to submission
> 4) Updated the Resources links and Codex xrefs
> Hopefully, these changes will address much of the feedback we have received
> recently.
> Please take a look, to make sure I didn't screw anything up, or put in any
> incorrect/inaccurate information.
> (My next step will be to start looking at the cross-referenced functions,
> tags, hooks, etc., and see if any of that can be improved upon in the name
> of helping to educate Theme developers regarding their necessity and proper
> use. Unless we can find a good way to incorporate such information into the
> Theme Review page in a manner that does not detract from conveying the
> existing information, I intend to put any such information on the
> cross-referenced Codex pages themselves.)
> Thanks,
> Chip
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers

More information about the theme-reviewers mailing list