WordPress Logo

ma.tt – Happy birthday from Bielefeld


I do love your idea to encourage people blogging for your birthday.

You probably do not remember me, but we do have a history. We met at BarCamp / WordCamp Jena, Germany in 2009. At the night before the event, we had a short discussion about your heritage. I told you – due to the mullenweg.com website and that Heepen is part of Bielefeld now, that your ancestors were born in my hometown.

WordCamp Jena. Matt Mullenweg plus Olaf and Nick Bohle in the Background
Matt Mullenweg, Olaf from wpde.org and me…

But that is old stuff. I also gave up my request, that you publish your photos of the above mentioned event.

Let’s focus on today and my favorite WordPress topic: Post formats. Regarding the State of the Word 2022, you answered a question of mine:

Q9. WordPress introduced and pushed “post formats” with the 2014 theme. Regarding the development in the Twitterverse, what are your thoughts on the post format asides? And what do you think of post formats in a block editor world?

A9. Currently, post formats are in a stable state; they are still supported and usable, but there are no real plans to foster adoption or add additional functionality around them. There are no plans to focus on them during the remaining phases of the Gutenberg project, but if there were a group of motivated contributors who wanted to spend some time on post formats, we would welcome those contributions!

2022 State of the Word Q&A

In regard to my question, I have to admit that my website has also changed during the last year. First of all, I got rid of the perfect classic Uku theme by Elmastudio and changed to FSE and TT4. Doing this conversion, I realized that I have to get rid of a patch that I considered to be a plugin. Thanks, to @Nacin and @markjaquith.

With this patch, I was able to have 3 WordPress taxonomies:

/type/* (* defined by post formats, incl. standard if patch is installed)

Three taxonomies mean three ways of classification. Categories and Tags are both content related. Type can be format related.

So nowadays, when I write a post, I have an issue. First, I use categories and tags as normal as I could. Second, I select the post format and add an associated tag (e.g. post format Image vs. tag Bild. Unfortunately, I do hate the fact of using tags for content classification and format classification. Why? We all learned to separate HTML and CSS, so why don’t we stop mixing classifications or as Germans would say it: Gesetz der Ordnung – Rules of Order.

On the other hand and this is really important to me, I do not want standard post templates/patterns depending on the post format. @photomatt, what I wish for is the following:

  • Adding Post Formats as a fourth taxonomy to the query block
  • Adding Post Formats to the html-template hierarchy, so that, for example, a single post marked with post format „image“ shows a featured image on the archive pages, but no featured image on the actual post, since the image is the main content of the single post.
  • Rename Post Formats to Standard Post Types (vs. Custom Post Types) and add all of them to core.

But okay, enough of my wishes. Matt, I have to say thank you. Thank you for making publishing easier for me.

PS: If there is a WordCamp in Bielefeld, would you join us? Where the streets have no your name? Directly translated: Millpath.