I’ve known for some time that WordPress, the content management software this blog uses, has been encouraging folks like me to stop using its “classic” user interface and start using blocks.
Blocks, it seems, are the best thing since sliced bread. They’re the bee’s knees and the snail’s eyebrows.
Blocks make creating rich content easy as falling off a log. They’ll inspire me to create new pages in a flash.
Although apparently I don’t need Adobe Flash to make blocks work.
Which is just as well, since I wasn’t planning on using Flash media.
At any rate, I kept putting off using WordPress blocks. Previous experiences suggested that anything that wonderful and stupendous, that easy-to-use and likely to make my life so much easier — would be far more trouble than it was worth.
So I kept putting off what I suspected would be a steep, as in near-vertical, learning curve.
Then I realized that WordPress had been warning folks like me that their classic user interface would be supported until 2022. And that it was high time for me to start climbing that curve.
So far, I’ve been pleasantly surprised. And have found a pretty good how-2 tutorial page.
- “How to Use the WordPress Block Editor (Gutenberg Tutorial)” Editorial Staff, wpbeginner.com (last updated June 28, 2021)
I’ve also learned that the Block Editor, the way I’m using it at any rate, won’t show rich content that I’ve created: if the rich content isn’t quite what the Block Editor expected.
There are less anthropomorphic ways of saying that, but I figure you know what I mean.
For me, so far, this week has been good news. And will almost certainly give me more opportunities for practicing patience.
Looking back, I’ve been paying more attention to the technical side of blogging this year. And that’s another topic.
- “I’m Back! — So are Comments and ‘Likes’”
(May 6, 2022 ) - “I’ll be Back, or, Resolving Technical Issues (Maybe)”
(May 3, 2022) - “Norbert Nerdly Rides Again: Keyboard Concerns”
(April 2, 2022) - “Brain Defogging, Technical Issues, and Me”
(March 22, 2022) - “Comments, Technical Difficulties and Other Frustrations”
(March 12, 2022)
