May one day port some of the tricks I’m using to “greatly” simplify my “WordPress IndieWeb experience” to an add-on plugin, or a theme, or both. Or at least better document how I do things like set titles (yet “hide” them on the front end) for notes, to make for a more convenient back-end browsing experience. As an alternative to Post Kinds, perhaps, and existing themes. (And then make the whole thing Gutenberg-compatible. 😬)
Always said I much preferred my Laravel setup over proper WordPress, because of all the control I’ve got over the front-end markup, but my web host has sort of made things much more difficult to maintain. And fully custom code’s way harder “to share to the world,” too. And I’ve been way overthinking things—what’s new?
Too bad this got closed. Being able to easily add a class name, like `u-bookmark-of` is a pretty big deal. https://github.com/WordPress/gutenberg/issues/13368 (It's why I stick with the classic editor's HTML view, typically.) But we'll find a way.
Thing is, how many “assumptions”—all filterable, of course—do I bake into such a plugin, and what do I leave for end-users to configure? Thinking of having the defaults be mostly the way I do things, yet allowing users to fairly simply ignore them. That way, most folks wouldn’t have to touch a thing, and those who are used to tinkering can keep doing so. (Regardless, I’ll be open-sourcing my theme tweaks and site-specific plugins, too, for inspiration.)
@jan I mean, you could create a plugin that registers some microformatted blocks, but that seems like a bit much. Too bad they didn't consider the esoteric use-case of adding ✨ classes ✨
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!