Coming in WordPress 3.6: Post Formats UI Improvements/Changes

See the make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. post here:

WordPress 3.6: the Post Formats UI feature

If anyone has any particular input into the what/how of improvements/changes to or standardization of Post Formats, please contribute there.

We’ll do our best to stay on top of any proposed changes, so that we can give as much advance notice as possible to Theme developers, for anything that would impact Theme development or the Theme Review guidelines.

#3-6, #guidelines, #post-formats

Based on current feedback, a slight revi…

Based on current feedback, a slight revision has been made to the upcoming WordPress 3.1 release-related changes to the Theme Review Guidelines.

In short: in order to ensure UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. consistency and full Theme-to-Theme portability of Post Format types for users switching among Themes in the repository, repository-hosted Themes will be required to add support for Post Formats, and to support all Post Format types.

Note that support does not mean the same thing as implement. Basically, repository-hosted Themes will need to add one line to the functions.php file, and that’s it. This one line will provide users with the Post Format UI (the metaboxMetabox A post metabox is a draggable box shown on the post editing screen. Its purpose is to allow the user to select or enter information in addition to the main post content. This information should be related to the post in some way. on the Edit Post screen). Any front-end Post Format-related changes to Themes remain entirely optional.

#3-1, #guidelines, #post-formats