Went ahead and updated to 5.0. And immediately hit a "No update required" bug, had to shell in and disable the cache. Great testing, Automattttttic.
Took a look at Twenty Nineteen theme, but even after completely customizing the CSS, it was screwing with my layout in unpleasant ways. In 2019, blog columns are 640px wide, instead of 840px in Twenty Sixteen! Nope. So updated 2016, restored my Fake Emoji Fuck Off, more custom CSS, and things are back to normal.
I'm ignoring Gutenberg for now, but Jetpack's got a Markdown block, so that may usable someday.
Am I really better off with this giant pile of junk, instead of going back to blosxom or some other static generator? I could write my own in a week. Well, I would miss media management. Automatic reposting to Mastodon and Twitters; I could script that myself, too, but Twitter's hostility to APIs means I'd be constantly fixing it or cutting off Twitter. So I'll stick with this for now.
Comments are closed.
Mentions
Micro.blog views on Gutenberg
@bradenslen If Gutenberg Breaks my Blog Where to Move?
@nitinkhanna thoughts on WordPress 5 and Gutenberg
@arush nails accessibility here & here
@ross not “an operating system for the web” but dreamweaver
@mdhughes sticking to classic Like this:Like Loading...
With WordPress 5.0 Gutenberg now launched, I think I will wait until the dust settles a little bit. I’m not encouraged by Matt’s State of the Word talk, in which he said ‘get deeper into Javascript’. I’d rather not actually. Most of the few plugins I use haven’t been updated to WP5 yet, and some of its authors write how Gutenberg breaks them. Also there’s still some bugs being ironed out. For now I’ll stick with WP4, until I see more confident reviews. Currently, searches for WP alternatives, calling WP’s new course Dreamweaver, quirks, and bugs, do not inspire that confidence. And already earlier this year there was the discussion of the total lack of accessibility efforts.