[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:20 chipbennett]:
 > Replying to [comment:19 littlefyr]:
 > >
 > > 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.
 > >
 >
 > The key thing to remember - and I remember the epiphany way back when
 Post Formats were first introduced - is that the feature is not a custom
 ''content'' (i.e. ''post'') type, but rather a custom ''taxonomy'', for a
 given ''content'' (i.e. ''post'') type.

 This is a confusing distinction given that a taxonomy is already a concept
 in WP. If post formats are the same ''sort'' of thing as a category or
 tag, then it should should '''be''' the same sort of thing. And in that
 case, we can ask the same sorts of questions you ask below about tags and
 categories.

 But if you mean in an abstract sense, then the collections of Post Types
 within a particular WP installation forms a taxonomy as well. ''That''
 understanding does not impart any further information IMHO.

 > A blog post (i.e. the content type) can have different kinds of
 information. How that information gets entered and stored is really what
 needs to be fleshed out and standardized.

 The ''kinds'' of information that something has is what ''defines'' a
 type. How that information is arrived at is neither here nor there. "how
 that information gets entered" is a UI question and the Rest API already
 means one can create whatever UI one might want invalidating any such
 fleshing and standardization.

 > For a post with the Link post format, does the user enter the link as
 the Post Title, or the Post Content - or maybe as post meta data? Is the
 link entered as a raw URL, or does it have a link title for constructing a
 fully formed HTML link? Does a post with the Link post format also allow
 for descriptive content?
 >
 > Does a post with the Aside post format have a Post Title?

 How is it that this is ''necessarily'' a Post, and not a different Type
 altogether? What possible reason would I have not to create a custom post
 type ''except'' to hack around the fact that you cannot (easily) mix the
 multiple post types in a list of "latest posts" (where post is 'things I
 wrote', not Post), for example.

 > I think those things can be answered with the feature remaining in core.
 Others may disagree.

 I think the question is whether or not the thing currently known as "post
 format" should be an abstract concept within WP Core for which specific
 instances may live either within or without the Core (just as post types
 are an abstract concept that is defined in the WP Core that also includes
 two specific instances... Page and Post, and myriad custom instances exist
 outside the Core) '''OR''' should it be a fixed way of doing things
 defined only within the WP Core

 There is a further issue. A Post '''is''' a specific Post Type. The
 definition and behaviour of Formats ought to be done within the context of
 defining a Post Type, and not as a special case.

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