Somewhat inspired by, I did some experimenting with WordPress’s new Full Site Editor. The result is this, still very hacky, Twenty Twenty-Two child theme.


Tried to do “Björk” instead. Did not work out, got Site Editor errors. Might be my server, haven’t tried elsewhere.

Also, most of the template modifications are just “better” defaults, from an “IndieWeb” point of view.

For the most part (overriding core post blocks), this really could be a plugin. In fact, adding the `h-entry` class to the single post template is really the only thing that has to be done in a (child) theme. Except … on single post pages, we could … use `body_class()` instead.

Might potentially screw up some pages, but one could argue that’s up to the user and their theme/setup.

This actually may be what I was looking for. Will we one day get a single “IndieWeb” plugin to rule them all?


Added the microformats bits to my “IndieWeb” plugin and switched back to plain TT2, and … it works!

Then tried another theme. No dice. Or, rather, this new theme does not, by default, display summaries on things like archive pages.

So the typical microformats parser is going to make some assumptions there.

But, if you edited the relevant templates using the Full Site Editor, you could totally make it work!

To get the most reliable results, a dedicated (child) theme is the way to go.

I’ve restructured things a bit a little while ago, so that most of what this little plugin does, can be disabled, too.

I do think I should have notes just use `post_tag`, though, rather than a new “note tag” taxonomy.

And rename the plugin. Like, once the CPTs are configurable, too. Like, some folks might prefer (just) post formats, or something. As long as the microformats are there, none of that matters (except maybe for feeds to decide if they should display a title or not).

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!