Post formats is going to be a major win for 3.6. It’s one of those features that has so much potential, but it really falls short in usability and honestly we haven’t really taken the time to truly show what it can do. We’re going to re-think the admin (and super admin) UI User interface for post formats, similar to what Alex King did with his WordPress Post Formats Admin UI plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. The goal is to make post formats much more user friendly and then show them off with the 2013 theme.
We’ve chosen @helen as lead for this project. Helen has done some amazing stuff customizing the post screen for various projects, and we’re glad to be able to leverage that for core Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
Anyone interested in helping with this feature, please comment to let us know. The 3.6 schedule is considerably shorter than the 3.5 schedule was, so we really need to get moving on things as quickly as possible.
The current list of post formats is on the Codex page: https://codex.wordpress.org/Post_Formats
- aside – Typically styled without a title. Similar to a Facebook status update.
- chat – A chat transcript.
- gallery – A gallery of images.
- link – A link to another site.
- image – A single image.
- quote – A quotation.
- status – A short status update, usually limited to 140 characters. Similar to a Twitter status update.
- video – A single video.
- Edit: audio has also been added as our final post type.
There has been suggestion of an “audio” format, which makes sense given the other multimedia posts. Another one recently suggested to me was a “code” format, which I could get behind.
I know we changed “photo” to “image” to be more generic, but I’m thinking we should change it back, and define a gallery as a gallery of photos. Not that you couldn’t use images there as well, but our target here is photos in particular, I’d imagine.
We need to make sure we get these right the first time, so if you have a suggestion, you should weigh in. I’ll be sending a link to this post out to a number of theme developers to hear their insights based on their experiences.
As a reminder, the main focus of this feature is portability and standardization, thus, custom formats are not being supported by the API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.. (For more, see Mark’s post and the comments.)
Post Format UI User interface and saving is in core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Themes announce their support of various formats like so:
add_theme_support( 'post-formats', array( 'aside', 'gallery' ) );
The UI looks like this, right now:
That UI only shows up if your theme supports it. By default, only Posts support it, but you can add support to other post types like so:
add_post_type_support( $post_type, 'post-formats' );
Twenty Ten has support for the “gallery” and “aside” post formats (it retains its backwards compat support of the special “Asides” and “Gallery” categories).
Post Format is shown on the post listing screen:
That was done very quickly, and I’m soliciting feedback for how that should be conveyed. Head over to the ticket.