Gutenberg Editor: Giving it a fair go.

There’s been a lot of talk around the latest release of WordPress, primarily due to the integration of the Gutenberg editor that has been packaged with the update. Understandably, many WordPress users are unwilling or not yet ready to adopt this new editor as standard practice due to theme incompatibility or instability. Releasing the update right before the 2018 Christmas holidays didn’t exactly make the lives of many developers (particularly those managing multiple instances) easy, but for the most part it was effectively managed with a few precautions in place.

Well, it’s now 2019 and my team have since updated all of our client sites to V5.0.3 with little to no impact. With that said, most – if not all – are using the Classic Editor Plugin as default until we are able to test our builds with the new editor. Luckily, WordPress have announced they will be supporting Classic Editor until at least 2022, which gives us plenty of time to test drive our sites on the upgraded core.

Not one to jump on the ‘change is bad’ bandwagon, I have decided to give the Gutenberg editor a fair go by building my new personal website for 2019 using only the new editor and WordPress’ standard Twenty Nineteen theme. And you know what? So far, so good. Granted, I will primarily be using this site for writing and documenting processes, but it’s nice to experience the full WordPress 5.0+ experience without all of the clutter and bloat that comes along with more sophisticated builds.

I’ve always been a big fan of clean, minimal design with a focus on content and accessibility, and I have to admit that WordPress have certainly upped their game with this new theme. I’m very much looking forward to putting it to the test.

Here we go…


Comments

Leave a Reply

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