Avada And Gutenberg, Important Info On Publishing Content
By now most people will have heard of the WordPress Gutenberg Project, coming to WordPress 5.0. According to Automattic, one of the driving forces behind the development of WordPress - the world's leading CMS, Gutenberg is a new publishing experience for WordPress. The "Try Gutenberg" callout is already appearing in user dashboards as of WordPress 4.9.8.
Avada And Gutenberg - Continued Compatibility Progress
Here at ThemeFusion HQ, we constantly strive to evolve Fusion Builder, by adding new features and dynamic solutions to supercharge your workflow. We have big plans for Fusion Builder in the coming months and years, and as a team, we are excited to deliver these updates to our wonderful customers.
While Fusion Builder continues to set new benchmarks for usability and and functionality, we are also aware, that the WordPress core development team likewise is hard at work to improve the default editing experience of WordPress. The classic editor has come a long way, but it is time for an improved WordPress native post editing experience. This is why the new Gutenberg editor will be released with WordPress 5.0. The new WP editor is still positioned as a beta plugin and has not matured enough to make it into core, but eventually it will be merged in.
Our team will stay on top of the Gutenberg development cycle as it develops to ensure that Avada users get the best out of WordPress and Avada.
Avada 5.7 Gutenberg Additions
We know that our user-base prefers the power and convenience of Fusion Builder to create and edit their page and post content, but we also believe that we should make it easier for everyone to try out Gutenberg and to use it side by side with the Avada Fusion Builder. For this reason, we have added several small helpers to Avada 5.7. Please note the 4 images below.
- The default "Add New" button will open the the usual post edit screen with Fusion Builder if it is enabled for that post type, and Fusion Builder Auto Activation is activated. You can now choose between Fusion Builder, Gutenberg or Classic Editor from a dropdown list when you add a new page, post etc., which makes it easy to get the editing experience you prefer.
- The default edit link on existing content opens the classic editing experience in whatever form you created, or last saved it in (Text Editor, Visual Editor, Fusion Builder). If Fusion Builder Auto Activation is activated, the edit screen will always be loaded with Fusion Builder. To open content in the Gutenberg editor, you need to choose the Gutenberg Editor link.
- If you choose to edit with Gutenberg, there is now an "Edit with Fusion Builder" button in the top panel of the Gutenberg Editor, which helps you to switch to Fusion Builder.
- Also, in the Gutenberg Editor, there is now the Fusion Element Generator button, which allows you to add Fusion Builder elements into Gutenberg Classic Blocks.
The WordPress 4.9.8 Test Gutenberg Callout
The new Gutenberg editor is in form of a plugin, until it is merged into the WordPress Core for version 5.0, for which currently there is no exact ETA. This plugin is under development and intended for testing and feedback purposes, allowing the core WP and the Gutenberg team to gather more data and feedback on how Gutenberg functions and interacts with users installs in the wild.
You can choose to install the Gutenberg plugin and try out the new editor, but you are by no means forced to do so. If you don't want to test it at this time, there is no further action you have to take. Whether you choose to ignore or test the Gutenberg editor, this dashboard callout stands as official notification that Gutenberg will be merged into WordPress core.
There is also an option to install the Classic Editor plugin. Don't panic, you don't have to do this. This is just a proof for the fact that WP is going to support the classic editor, even if Gutenberg will be merged into WP core in the future.
Is Gutenberg Ready To Use?
The new callout box to try out Gutenberg is simply introduced to get as many users to try the new editor. It has progressed quite a bit in the last few months, which is why the WP core and the Gutenberg team decided to add this callout now. At the same time, there is a significant amount of debate regarding the desire and readiness for Gutenberg to be pushed out to the entire WordPress community.
One of the most recent Git items from the WP core team is to alert users that even if using the Classic Editor, editing Gutenberg content can create havoc within the content and lead to content loss. The same stands true if you edit existing content, using the Gutenberg editor. So, there are still several compatibility issues to overcome.
So, the current state of Gutenberg could be summarized as ready to test but not ready to use (on production sites).
How Does This Affect Me?
Once you have updated to WordPress 4.9.8, the WP dashboard callout gives you these choices:
Choosing To Install And Try The Gutenberg Editor
The goal behind the WP 4.9.8 Gutenberg inclusion is to demo and garner feedback for the new editor. The moment you install and then activate the Gutenberg editor, you will be presented with a new post demo showcasing the editor:
The goal of this new editor is to make adding rich content to WordPress simple and enjoyable. This whole post is composed of pieces of content—somewhat similar to LEGO bricks—that you can move around and interact with. If you save or publish the Gutenberg demo post, in the WP Dashboard >> Posts screen you will see the Gutenberg post clearly identified (only whilst Gutenberg is active):
It must be noted that editing a Gutenberg post is not interchangeable with the either the Classic editor or any premium theme content builder, and, vice versa.
In the WP Dashboard >> Posts screen, if you elect to edit the saved Gutenberg post with the Classic editor you will be presented with the following in WP Text edit mode and this in WP Visual edit mode. If you elect to edit the saved Gutenberg post with the Gutenberg editor you will be presented with the following edit mode.
Choosing To Install The Classic Editor
As per the WordPress Dashboard prompt, "Not Quite Ready?", the new editor will be enabled by default in the next major release of WordPress. If you’re not sure how compatible your current themes and plugins are, we’ve got you covered. Install the Classic Editor plugin to keep using the current editor until you’re ready to make the switch.
Installing the Classic Editor plugin enables the WordPress classic editor and the old-style Edit Post screen layout (TinyMCE, meta boxes, etc.)
What Will Happen If I Do Not Install Either Editor Plugin?
In short, nothing. If you do not want to try and test the new Gutenberg editor then no further action is required right now.
As a team, here at ThemeFusion HQ we are closely following development cycle and progress of Gutenberg. As has and always be the case, we are dedicated to delivering the best working experience to everyone who uses our product, with any new version of WordPress and/or for the release of Gutenberg. We will also be releasing up to the minute documentation for anything that Avada users need to be aware of for anything Gutenberg.
It is difficult to make predictions about Gutenberg specifically, far too much of it is still unclear, not implemented or not even discussed with the wider WordPress community contributing to the project.
Change is often enough difficult for many and that is understandable. We believe that WordPress as a CMS and the WordPress community as a whole will emerge out of this transition stronger, polished and ready for the next 25 years of innovative and market-share dominating progress. For now, with many seemingly divided by this new direction WordPress is embarking on, the following is clear: