I just need to vent for a moment.

The #1 thing a blog post editor should do is make sure you NEVER LOSE WORK... and the sooner I can find time to satisfy my obsessive dedication to never 404ing URLs while switching to a static generator, the better.

WordPress deserves an *award* for how readily it destroys your work.

Try to edit a table or a definition list in the raw HTML for lack of visual access to a desired feature and oops your manual tag-balancing? It garbles everything up on switching to the WYSIWYG view to preview your work without pushing it public.

Misunderstand what the buttons on the "Invalid HTML. What do you want to do?" popup mean? There's no Undo so you better hit Reload instead of Save.

Want to edit stuff naturally in the new Blocks editor? Good luck. The interaction between cursor motion and selection means that trying to select a paragraph of scratch text without reaching for the mouse will snap the selection to the entire block, including text outside your intended span.

I just *lost* a big edit to an old list post because, for reasons I can't even fathom, switching from TinyMCE to raw HTML reverted it to the saved version.

Wanna save? Better make sure you didn't leave the tab open too long or it'll get stuck on that "Saving" message that replaces the "Save Draft" button.

Wanna use the preview function but have your browser set to only allow new windows/tabs to be opened by an explicit middle-click or context-menu choice? Too bad. The Preview button can't be middle-clicked.

When I remember, I've taken to editing my blog posts by switching to HTML mode, copying them into Vim, and only copying them back once I think they're ready.

...actually, that's a lot longer than I expected, so I think I'll tweak it a bit and post it to my blog.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves. A STEM-oriented instance.

No hate, No censorship. Be kind, be respectful

We federate with all servers: we don't block any servers.