It's been a little over six months since I wrote my first post in Gutenberg (and it was about Gutenberg). In that time, I've published 18 posts using Gutenberg. It still has ways to go before I think it's going to be great, but it's continuously solving my needs on this site. When I originally posted my comments, I posted a mix of ideas, bugs, oooh-moment features, and reactions. Some of them are worth revisiting:
It’s pretty. And Fast. I never thought of the post editor as being slow, but there is something about Gutenberg that makes it feel fast.
This is still true! Overall I’m still impressed with how fast things feel. And as some of the clutter pieces have been removed, it’s gotten even prettier.
There are a lot of rough edges. It’s hard to know what is a bug, what is intentional, what just hasn’t been done yet, and what hasn’t been thought of.
It is becoming clearer what is a bug (and they still exist), what needs another riff, and what is just new to me.
The default state is likely my favorite “Distraction Free Writing” implementation in WordPress yet. I’m simultaneously able to focus on my content, and yet I have all the tools I need for writing. I don’t yet have all the tools I need for content creation.
Creating content in Gutenberg has only gotten better.
I need to take my hands off my keyboard more than usual. Adding a paragraph after a list isn’t easy to do with just a keyboard.
It’s more keyboard friendly, but still has steps to go before I can really not use my keyboard.
And now for some new thoughts:
- I like the direction Gutenberg continues to head in, but there are a number of edges that continue appearing rough. Some of those are the micro-interactions that continue to be iterated on, while others are the result of bugs (copy and paste right now is rough).
- Developing software in the open is hard. I'm continuously impressed with the Gutenberg team's ability to take and turn it constructive.
- Once better documentation is in place, I think we will start being at a point that we can consider when Gutenberg is merged into Core. I view the lack of great documentation as being a blocker for that discussion. Until it's easy for plugin developers to support Gutenberg, they can't build much and until things are built, it's hard to figure out when Gutenberg is ready to ship.
- I think the documentation is going to need to tackle things from multiple points of view:
- How to use all the various extension points.
- How to create automated tests
- Advice on making decisions/Philosophy of what extension points to use (I'm hoping some designers write this)
- I'd like to see some iteration around the taxonomies in the sidebar. In part to make custom taxonomies easier and in part to see if there are ways to make it easier.
- I'm going to be building something for production in February and am seriously considering building it in Gutenberg so it's more future proof.
- This post was the first time I needed to use the classic text block. Blockquotes and paragraphs inside list items might be an edge case, or perhaps the list block is too rigid.
I'm going to try and remember to post more thoughts on Gutenberg in another six months. I think it will be in WordPress core by then, but I'm not sure if 5.0 will have been released. For others that have been using Gutenberg for a while, how has your opinion changed?