The following changes to the Theme Review Guidelines are being issued for public review and comment. All comments and feedback are welcome and encouraged.
The changes will be finalized when or shortly after WordPress 3.1 is released, and will be made effective one month after the release date of WordPress 3.1.
New WordPress 3.1 Features
The following guidelines will be implemented for new features introduced in WordPress 3.1:
- Post Formats
- Themes may optionally to support Post Formats.
- Themes may optionally implement layout and/or style changes for any, all, or none of the standard Post Format types.
- Unless an extension API is implemented in core, Themes are required not to implement a custom extension for Post Format types (e.g. “hacking” the core Post Format type list to add custom types, such as “code”).
- Custom Post Type Index Pages: if Themes include Custom Post Type Index Pages, they are required to provide Theme documentation to explain their usage
- Admin Bar: Themes should be aware of any potential aesthetic impact of the Admin Bar
Previous “Draft” Guidelines
The following guidelines revisions, previously listed as “draft”, are now final:
- Site Information Template Tags: the correct template tags must now be used where appropriate (home_url(), site_url()
- WordPress-generated CSS classes: definitions for .sticky and .bypostauthor are now required
- Guidelines for optional additional footer credit links
Other Changes to Guidelines
The following changes will also be made to the Guidelines:
- License Header Tags:
- Themes are required to add License: and License URI: header tags to style.css
- Translation and Custom Theme Function/Option Names:
- Themes are required to use theme-slug as the Theme’s translation namespace, and as a prefix for all custom Theme functions and options
- Theme Documentation:
- Themes are recommended to include a readme.txt file, using Plugin readme.txt markdown.
- In lieu of a readme.txt file, Themes are recommended to include a changelog, indicating version-to-version Theme changes.
- Themes are required not to use TimThumb solely as a replacement for core Post Thumbnail functionality.
- Any use of TimThumb outside of this requirement will be evaluated on a case-by-case basis.
- Up-Sell Themes:
- Up-sell Themes may be subjected to more rigorous or additional Theme-Review requirements, at the discretion of the Theme Review Team
- Themes are recommended not to implement custom favicon functionality.
- If implemented, favicon functionality is required to be opt-in, and disabled by default.
- If implemented, favicon functionality is required to support user-defined favicon images