Theme Review Team » 3.4https://make.wordpress.org/themes
Reviewing WordPress ThemesMon, 02 Mar 2015 21:22:06 +0000en-UShourly1http://wordpress.org/?v=4.2-alpha-31603Proposed WordPress 3.4 Guidelines Revisionshttps://make.wordpress.org/themes/2012/05/08/proposed-wordpress-3-4-guidelines-revisions/
https://make.wordpress.org/themes/2012/05/08/proposed-wordpress-3-4-guidelines-revisions/#commentsTue, 08 May 2012 15:21:39 +0000http://make.wordpress.org/themes/?p=915As we near the final release of WordPress 3.4, it is time to begin discussion and finalization of the related changes to the Theme Review Guidelines. Below are the proposed changes. Please discuss in the comments. We’ll do our best to keep this proposed list updated based on discussions in the comments.

New WordPress 3.4 Functionality

Custom Headers/Backgrounds

New and deprecated functions are already covered by existing Guidelines. Themes may OPTIONALLY provide backward-compatibility with pre-3.4 handling of custom backgrounds and headers

Child Themes

Child Themes will formally be allowed to be submitted for inclusion in the Theme repository.

Child Themes are REQUIRED to use an approved Theme as a Template (i.e. as the Parent Theme)

Child Themes are REQUIRED to demonstrate sufficient difference from the Parent Theme to warrant inclusion

New Guidelines (REQUIRED)

If implementing a site logo, Themes are REQUIRED to provide user-configuration of the logo via the core custom header feature. (Exception: if incorporating both a site logo and custom header, the custom header is required to support the core custom header feature, and the custom logo is then required to be implemented via custom Theme option.)

Function Parameters, Filters, and Action Hooks

Themes are REQUIRED to use function parameters, filters, and action hooks where appropriate in order to modify content, rather than hard-coding:

Clarifications

Clarifications to existing guidelines being enforced:

Presentation vs Functionality

Themes are REQUIRED to function as stand-alone code. Themes may OPTIONALLY integrate support for third-party Plugins; however, Themes are REQUIRED to degrade gracefully and to function fully and properly without any such Plugins active.

Feedback

What else should be included? What should be revised? Let us know in the comments.

]]>https://make.wordpress.org/themes/2012/05/08/proposed-wordpress-3-4-guidelines-revisions/feed/58I’ve updated wp themes com to use WordPress…https://make.wordpress.org/themes/2012/04/23/ive-updated-wp-themes-com-to-use-wordpress/
https://make.wordpress.org/themes/2012/04/23/ive-updated-wp-themes-com-to-use-wordpress/#commentsMon, 23 Apr 2012 16:29:13 +0000http://make.wordpress.org/themes/2012/04/23/ive-updated-wp-themes-com-to-use-wordpress/I’ve updated wp-themes.com to use WordPress 3.4, that way I could fix #WP20514. This could potentially reveal themes that are broken in 3.4, so keep an eye out. I will be watching the error logs.
]]>https://make.wordpress.org/themes/2012/04/23/ive-updated-wp-themes-com-to-use-wordpress/feed/1Updating Custom Backgrounds and Custom Headers for WordPress 3.4https://make.wordpress.org/themes/2012/04/06/updating-custom-backgrounds-and-custom-headers-for-wordpress-3-4/
https://make.wordpress.org/themes/2012/04/06/updating-custom-backgrounds-and-custom-headers-for-wordpress-3-4/#commentsFri, 06 Apr 2012 14:58:24 +0000http://make.wordpress.org/themes/?p=847When WordPress 3.4 is released, the old implementation methods for custom backgrounds and custom image headers via add_custom_background() and add_custom_image_header() will be deprecated, in favor of a much simpler – and much more powerful – implementation method, using add_theme_support(). Here’s how to update your existing Themes to use the new implementation.

Custom Backgrounds

Old method:

add_custom_background();

New method:

add_theme_support( 'custom-background' );

(Admit it: that was easy, wasn’t it?)

Now for the fun part: add_theme_support( 'custom-background', $args ). What’s that: $args, you say? Yes! This method accepts an arguments array. Here are the defaults:

You may notice that the arguments array also includes the same callbacks that have always been available for custom image header implementation, so you also have more control over the front-end style definitions as well as the admin display.

As you can see from the defaults array, this new implementation adds some new functionality: flexible headers. See Amy Hendrix’s excellent write-up for more information on this feature.

]]>https://make.wordpress.org/themes/2012/04/06/updating-custom-backgrounds-and-custom-headers-for-wordpress-3-4/feed/37Heads Up To Developers: WordPress 3.4 is in Betahttps://make.wordpress.org/themes/2012/04/05/heads-up-to-developers-wordpress-3-4-is-in-beta/
https://make.wordpress.org/themes/2012/04/05/heads-up-to-developers-wordpress-3-4-is-in-beta/#commentsThu, 05 Apr 2012 13:24:54 +0000http://make.wordpress.org/themes/?p=843See the post on the wpdevel site:

Here’s some of what’s new:

Theme Customizer with Previewer

Flexible Custom Header Sizes

Selecting Custom Header and Background Images from Media Library

Better experience searching for and choosing a theme

And some of the under-the-hood changes:

New XML-RPC API for external and mobile applications

New API for registering theme support for custom headers and backgrounds

Performance improvements to WP_Query by splitting the query (Please test!)

Performance and API improvements when working with lists of installed themes

Support for installing child themes from the WordPress Themes Directory

Note: there are changes in WordPress 3.4 that will impact Themes, and the Theme Review guidelines. Now is the time to switch your development environments over to the beta version, and start hammering on the changes. (And if you find any bugs, report them!) Soon, the Theme Review Team will begin discussions regarding changes to the Guidelines. If you are interested in participating in those discussions, please beta-test now, and keep your eye on this site, and on the Theme-Reviewers mail-list.