WordPress Blocks

WordPress 5 introduced an entirely new editor, Gutenburg.  I knew it was coming, but had not really paid attention.  So when I updated DarkerView to WordPress 5 I was unprepared for what was coming.

The new Gutenburg editor introduced with WordPress 5
The new Gutenburg editor in WordPress 5

Oh *#$@!  This is different.

Blocks?  What are blocks?  Everything is blocks? I think I get it, it makes sense, the concept is straightforward… The trouble is in the details of actually doing anything useful, learning what icon to press, how to arrange things.  There should be a way to do this, but where is it?

Now that I have had some time with it, and watched a couple training videos, I think I am getting the idea.  At least I have been able to produce new posts without struggling.

The new editor is truly more powerful, more of a desktop publishing editor than a simple blogging editor.  With Gutenburg the power of WordPress to produce professional websites is dramatically improved.

I wonder what new users will think of when they encounter the editor.  Gutenburg dramatically steepens the learning curve necessary before using WordPress.  It is possible to use the classic editor, but only within a block.  A more explicit way to use the classic editor may be a good idea.

The only real effect on DarkerView right now will be a modest increase in the time it takes me to write a post, there are more keys to press and a few more mouse clicks to get the job done.  There will be no real change in the appearance or function of the blog, at least for now.

Author: Andrew

An electrical engineer, amateur astronomer, and diver, living and working on the island of Hawaiʻi.

3 thoughts on “WordPress Blocks”

  1. I’m sticking with the Classic Editor. I’ve been testing the new blocks editor the past year for many months and it’s a pain to format things at this time when moving things around due to the constraints of the blocks. I’ll eventually move in due time but I see no rush.

Leave a Reply

Your email address will not be published. Required fields are marked *