[wp-trac] [WordPress Trac] #32844: Remove Post Formats and make them an optional plugin like Links

[WordPress Trac]

#32844: Remove Post Formats and make them an optional plugin like Links
--------------------------+------------------------------
 Reporter:  mor10         |       Owner:
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Post Formats  |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by littlefyr):

 Replying to [comment:15 TomHarrigan]:
 > Replying to [comment:11 chipbennett]:
 > > I support completing the implementation of Post Formats in core,
 versus removing Post Formats from core.
 >
 > What would complete the implementation? Part of the issue with Post
 Formats is that most are unsure of what its supposed to be.
 >
 > Another large part of the issue in all cases I've encountered is that
 the feature is inherently crippled in that it's not extendable. We love WP
 for its flexibility, but having a feature with no wiggle room inhibits its
 growth and success. I understand that the reasoning in the beginning was
 for standardization and to allow more portability between themes, but at
 this point it's clear that that path wasn't successful. Not every use case
 fits cleanly into the pre-defined formats.

 Agreed. Probably the most compelling use case for Post Format is one where
 I have a serial collection (ie Posts) of things but on any given day I'll
 want to have a different thing and that thing is distinguished not by its
 style, but by its content.

 By way of example, let's pretend I have enough free time to keep up a blog
 where I regularly review WP plugins, themes, and also JQuery plugins and
 NPM modules. Now many of the entries in my blog are going to be about what
 I had for lunch, but when I review something, I'm going to want to have
 links to the Git repo, the WP page, a taxon for its license (for
 searching) and so on.

 I ''could'' make these reviews into a simple custom post type, but if I
 want to make a list of all my serial content, I'd have to make two queries
 and combine and sort them. And I'd have to do some similar jiggery pokery
 to have a single common set of categories.

 At least that's what I recall from the last time I looked at something
 like this. I seem to recall thinking it wasn't going to be easy so what's
 the point.

 If it is trivial to have a custom post type that meshes seamlessly with
 posts, then ''this ticket has already been completed'', you need only to
 distribute each of the current post formats as a plugin of its own.

 If not, that would seem to me to be the fully baked implementation. A Post
 Type Format (lets keep it generalized) that seamlessly integrates with its
 host post type (polymorphism for Post Types).  Let a post type define the
 values it needs (classname, excerpt, title, body, featureImage), and let
 the Post Type Format (through filters/actions as appropriate) supply those
 values from its data, or fall back to the post type's default.

 This puts the  ''bulk'' of the responsibility for displaying the post
 format on the creator of the format, and strikes me as being sufficiently
 flexible to cover past and future uses for post types.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/32844#comment:19>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform