WordPress 5.0 is just about to land and with it, they will bring an entirely new editing experience. Everyone in the CMS world is buzzing because of the Gutenberg editor. This new software has been rebuilt for media-rich pages and posts whilst still maintaining a level of flexibility through their new ‘blocks’.
It’s replaced one of the most central aspects of WordPress backend and overhauled central ways of how CMS works. Although the plugin has been available for around a year now, a lot has changed since its first release.
Over the years, individual updates have brought with it, significant shifts and along with it, significant opinions. The 4.9 ‘Tipton’ update enabled users to schedule design changes in the WordPress customiser so they can go live at later dates, just like post drafts. And WordPress 4.8 brought with it an array of widget updates including three dedicated media widgets that no longer have to be manually uploaded.
However, these aren’t really “game-changers”. They’re more of an incremental change. But WordPress 5.0… WordPress 5.0 will be less incremental, more innovative, instrumental, intelligent… you get the gist.
Developers use meta boxes to add more information to the posts. Sometimes, it’s not just the content, but also settings and arbitrary data. It’s been reported that with the current user interface, there is no place for meta boxes; but they should think of it as though they’ve been pushed into a different position.
And why would we want to get rid of Page Builder? It’s useful. Developers can build general templates which clients can easily create pages and edit content without deterring from current layout/designs. Page builders allow the client/user to easily move elements around as they’re fully customisable. Gutenberg overrules all current page builders, which for some isn’t good news.
However, with Gutenberg, you won’t need to know HTML, or be able to write shortcodes, increasing personalisation capability. You can control the front end and the backend of a website entirely from a single console, and similar to working with HubSpot, what you see is what you get. For non-developers who are building their own website, this will make navigating WordPress a whole lot easier.
But that doesn’t necessarily mean that if you’re not a developer you should be building a website. Without basic UX knowledge, your site might still look a little basic and because Gutenberg focuses on the content, not on custom fields, the meaning of custom fields becomes a bit blurred. Some popular plugins such as WooCommerce might not work because of this. Although Yoast SEO foresaw this and has it covered.
Plus, there’s an innate possibility that Gutenberg will break a lot of things when it’s merged. The effect of this will be especially felt by those that are building and running the site for others, such as digital agencies and the IT team. Though in a roundabout way, this will hopefully raise the barrier for developers to keep their plugins up to date and render those which are non-functional, non-functional.