Notes

Thing with WordPress nowadays is that we’ve now got blocks, reusable blocks, custom blocks, and block patterns, but also block styles, block variations, block templates, (theme) templates, and template parts. And they’re different things. (Also, [custom] text formats, block transforms, theme.json and block.json, server-side rendering, hybrid themes, and more.) And I haven’t even looked at React/JSX, yet.

Been playing with WordPress’s Full-Site Editor some more, especially the core “theme” (or “post”) blocks that are rendered server-side. Has allowed me to add not just microformats, but additional “social icons” (like Mastodon’s), too.

That explains! (I’ve been experiencing some issues with child themes, and was looking for a way to instead use the Site Editor only.)

[D]evelopers and users are expecting to be able to create this type of template in the new Site Editor. This is a reasonable expectation. Unfortunately, the feature is not complete yet and not included in WordPress 6.0.

More FSE fun! Once a block theme is active, the “old” Customizer is notoriously hard to find.

Got to experience this first-hand because the default Twenty Twenty-Two theme does not style “Classic Block” blockquotes the way it styles “Quote Block” blockquotes, and I needed to add a bit of CSS somewhere to get that fixed.

More FSE fun! (I’m doing this experimenting on a different blog of mine, mind you.)

My theme (Twenty Twenty-Two) uses the Post Date block in just its two “single” templates. I’m adding support for microformats, however, and thus want date blocks on all home, archive, and search pages—have that dt-published class on all my posts, right?

So, the default date format’s F j, Y. Fine for English, but this blog’s in Dutch. (And while the date format’s correct (i.e., j F Y) in the overall blog settings, the Post Date block does not pick this up … Which means hand-editing some six template files it is.

Of course, since I’m overriding the default Post Date block anyway, I could totally make this smarter, but then I might spoil things for anyone else that would like to experiment off of my child theme.

Quick reminder: WordPress has had (limited) microformats support since just about forever. The new “block” (FSE) themes, like Twenty Twenty-Two, not so much. This is a regression.

WordPress respects the hAtom microformat. Therefore every post has an .hentry class added to it to respect the specification.

Somewhat inspired by https://www.zylstra.org/blog/2022/09/wordpressindieweb-as-the-os-of-the-open-social-web/, I did some experimenting with WordPress’s new Full Site Editor. The result is this, still very hacky, Twenty Twenty-Two child theme. https://github.com/janboddez/tt2-mf2

Hoping to update my “IndieWeb plugin” with basic block support. Fixing core would be even better.

Either way, themes will need to update, too.

I just realized that Jetpack’s Markdown module (and thus “my” Easy Markdown plugin) supports Markdown Extra. And I can thus add inline link classes using the {.u-bookmark-of} format.

The one downside is, the unparsed Markdown is what I end up automatically crossposting to Mastodon. Usually, that’s fine: I want backticks, underlines, and so on to show; they convey meaning. For links, though, I think a URL only is much more readable.

The Kanban bit looks interesting.

Bookmarked https://developer.wordpress.org/block-editor/reference-guides/block-api/block-patterns/.

Bookmarked https://codemirror.net/.

And, after yesterday’s Webmention package, a basic IndieAuth package for Laravel.

Been toying with Laravel a bit more. Decided to split off some Webmention functionality into a package of its own, https://github.com/janboddez/laravel-webmention. There’s two classes here that matter, one for receiving (Http\Controllers\WebmentionController), and one for sending (WebmentionSender). Hoping to add a parser of sorts later, and some CLI/Artisan commands.

I forgot to do (or rather, show) the short URL thing.