WordPress 5.0 has been released and the top feature was the redo of the WordPress editor, the one known as Gutenberg.
If you expected some drama, deep reflections or other thoughts around it, I’m passing on that.
If you came to the post expecting a tutorial, or demo, sorry to disappoint you. At least this time. But if you peruse the web, you will likely find countless of them out there.
Recently I asked someone who wasn’t neck-deep in the community how they defined the new editor. They said, simply:
It lets us create posts and pages using block.
That was it. No more, no less.
WordCamp US 2018 in Nashville
The new WordPress editor, as you may know, was released the day before the biggest WordPress event of the year, WordCamp US. Supposedly everyone was full of tension and stress, so it was predicted that the whole event would reflect this. Well, I didn’t see it. Maybe it was because I had other stuff to talk about. In any case, it was an awesome event as usual, and I’ll leave this post void of drama.
Gutenberg and BobWP
What you may have noted, is that I purposely avoided the word Gutenberg. I know the name is fraught with tension in some places, but let’s call it what it is.
Since around here, we spend almost all of our time in WordPress writing, editing, tweaking and repurposing content, it affects our workflow quite a bit. I imagine I spend more time in the editor than the majority of WordPress users.
So what are our plans?
When Will I Update?
Unlike almost all past major updates I have lived through over my 11 years working with WordPress, this will be the first one I won’t switch over to immediately after the release. I’m weighing it all carefully this time around. I will likely update when 5.0.1 comes out.
When Will I Start Using Gutenberg?
That is the million dollar question. Because of the time I do spend in the editor, I’m not jumping on the bandwagon anytime real soon. I will test it first in staging (maybe sooner than later) and when I do update, I will probably install the classic editor plugin.
Because I have been creating posts for years and years in the editor I’ve been using. And there is not only a learning curve for myself, but, also, in a fast-paced environment like ours, with new content being pushed out daily, I must consider how it will affect our deadlines and workflow.
I use a lot of graphics in posts. I also use other channels, such as audio and video. I need to get a feel for how best to make this all work for me. In other words, I need to find that sweet spot and make the switch when I’m good and ready.
Why Did I Wait?
You might be asking “So Bob, why didn’t you spend more time conquering that learning curve during beta?” I guess I’m just not a beta kind of guy. Sure I played with it a bit. But before I am ready to tackle it, I want it to be in final form, not a beta version. When it comes to tech, I’m not the best guinea pig.
So in the Meantime…
This does not mean I’m planning on learning this through osmosis. I will have it all set up on a test site and teach myself, as I have taught others in the past.
I will also create, write and edit posts to experience it myself and work out the kinks.
This may soon or I make just take my sweet time.
No matter, I do believe that this is the future of WordPress. I’m excited about it and anxious to see how it grows. What little grumbles or frustrations I may have along the way will be mine to own. So I am welcoming the new editor with open arms and open mind.
In fact, as I ponder on it more and see what it has to offer, I think, even in the beginning, I will be able to do some very cool stuff.
It’s time to move on, learn new stuff and watch as WordPress continues to grow and innovate.
An audio option for this post.