The Gutenberg WordPress editor is a page builder in its beta testing phase and is expected to become an integral part of the WordPress core, anytime soon. Gutenberg is a pseudo name given to the upcoming Admin interface of WordPress. If the rumors are to be believed then, the full throttle version of the editor would be released with the WordPress 5.0. The core functionality is the addition of content blocks, which would be rolled out to all existing and the up-to-date WordPress sites.
It is considered as a revolutionary change in the WordPress framework. The need for this editor emerged as the current or prior visual editors are rigid in the sense that they are dependent in utilizing quite a lot of HTML work and shortcodes in order to make things work for the user.
Goal of Gutenberg Editor:
The ultimate goal of Gutenberg is to make things easier both for the advanced and new users of the WordPress tool. Their design team is actively involved in enhancing the user interface, visual design and the overall user experience, along with the ease of using the required components within the framework.
The idea this time is to make use of blocks and these blocks would eventually replace the need of using the custom HTML or the shortcodes. In more technical terms, the inclusion of the said editor would replace the need of the TinyMCE which at the moment is the default editor of WordPress. The user with the new change would move forward in developing their WordPress websites while building the easy-to-use content layouts and not just go on with writing the articles. This is one of the many changes, but surely one of the most significant as well. Furthermore, the editor seek to enhance the usability features of WordPress and would tend to diminish the concept that the users of the platform would require any supplementary plugins for the sake of managing things, just as simple as the layouts.
Understanding Gutenberg Blocks in Detail:
Block here refers to an abstract term which is employed for explaining the different units of markup, which, when composed together would lead to content or a full layout of a webpage. The concept of blocks would do the work similar to that of the custom HTML, shortcodes and the embedded discovery, but in a much convenient manner, and that too, forming a consistent single API and excellent user experience.
As an example, consider generating an image in your post using a block. In order to define such a block, you need to employ the lorempixel.com service, which gives you freedom in selecting a category and you would prefer in giving this as a useful option when you are editing such a post in WordPress. The ideal workflow in the platform for adding an image would ask you to first insert a block, where it would be shown in a kind of an empty state. You would have the option for selecting your preferred category from the dropdown. Once, the selection is confirmed, then you will see the image’s preview, right next to the dropdown that you used for the selection. At this point, you might think that adding controls, while in the content’s edit mode would lead the published post not to be the same as you desired, due to the expected markup inclusion. It means, that you would obviously does not want your webpage viewers to see any dropdown, while browsing your published content. This is what that lead as one of the foremost requirements in the urge of explaining a block.
You as a developer are prompted to give solutions both for the content to be shown in the editor and what exactly you would like to be published for the webpage visitors. In order to remove any chances of redundancy, you should go on with the sharing of the common behaviors by the virtue of splitting up the code in the form of components.
What’s Next, When Gutenberg Arrives?
A lot of people have confusions that what exactly would happen when Gutenberg arrives. Things are coming for your convenience and processes would be a lot more streamlined with backward compatibility as well. The following are some of the points that would help your queries in this regard:
- If you are concerned about your shortcodes and widgets then there is no need to worry about. They would function just as they are doing now. The novice editor would look to offer some innovative methods for the sake of interacting with your webpage’s existing elements. With the deployment of the editable blocks for supporting these elements, you will be having an excellent control over the user experience or the visual display of the content and that too, with no need of knowing any kind of code.
- It wouldn’t replace you plugins, at least not in the initial phase. The WordPress developers are working out ways for customization and would hand over, after the initial release is rolled out to the commercial users. The approach here with this new editor is to help users with no need of piling on any huge count of the plugins, in order to support any form of the backend functionality or the webpage layouts.
- In case you are considering about the fate of your page builder plugin specifically, then this is the thing which is still not confirmed. Remember, Gutenberg is only an editor and not actually a page builder. The webpages which as of now uses shortcodes and HTML/ widgets etc. does have the power of employing them, as needed. Customization, as discussed above is expected much later, and this is where the elements of the page builder plugin would see quite a few conflicts and perhaps some chances of dual functionality as well.
- You will have the power to use the normal WYSIWYG editor post Gutenberg release. This is true initially as according to some authentic sources (WPEngine), WordPress would offer the option of reverting to the older editor, if required However, in the best interest of the users, WordPress expect users to go Gutenberg way, once it is deployed in the market after its commercial release. Support for the older editor would be stopped once Gutenberg is entrusted as the best editor option.
- You will have the option of using your theme templates just in the same manner as you are doing it now. Gutenberg would allow you to make a theme template selection through its right hand side selection options. The developers will have the freedom of releasing their own templates right now with the Gutenberg model in mind, while thinking about different types of the design blocks which the potential users could employ in order to fill it up with their content.
The Expected Release and the Planning Required:
We just have the WordPress 4.9.4 installed in our systems and the WordPress 5.0 is just a few months, or probably weeks away. As WordPress is highly trusted by many for developing their webpages, so there is a kind of uncertainty related to the upcoming release and what they could expect or do best to prepare themselves. Much has been said above about the expectations and you can feel much better by knowing the following crucial details that will help you plan or at least get to know about the actual scenario:
- The existing webpages of your site would get converted into Gutenberg through the access of the ‘Classic’ block. These are the blocks which would then exist and they would be displayed just as they are being displayed now and that too with no manual effort required in preserving them.
- In case, you are editing any existing webpage or may be a post and something very unusual happens, then you have the option of using the segmented backup system of W Engine which would securely restore all your temporarily lost or affected content.
- For the legacy editor lover, the Classic Editor Plugin could be easily downloaded in order to help you revert back to your prior editor.
Conclusively, Gutenberg is touted as a very exciting option, especially for its security, diversity, uniformity and offering user with an excellent user experience. As a best practice, it is highly recommended by WordPress experts to create a backup of your existing stuff first before any migrations or updates. Give it a test, learn new things and then go on with its live usage for creating, organizing and maintaining your actual webpage.