Avada, WordPress, And Gutenberg. An Ode To Progress

Avada, WordPress, And Gutenberg. An Ode To Progress

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 worlds leading CMS, Gutenberg is a new publishing experience for WordPress.

WordPress 4.9.8 is scheduled for release at the end of July, bringing with it the “Try Gutenberg” callout that will appear in all user dashboards.

WordPress Gutenberg Dashboard Call Out

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).

I Use A WordPress Theme, How Does This Affect Me?

Once you have updated to WordPress 4.9.8, the WP dashboard callout gives you these choices:

  • Option to install the new Gutenberg editor plugin, or

  • Option to install the Classic Editor plugin (which is not needed), or

  • You can choose to ignore installing either for now.

You should not edit any existing Fusion Builder generated page/post content with the Gutenberg editor and vice versa, as they are not interchangeable. We advise against testing this on a live site.

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. *This only applies whilst Gutenberg is a separate plugin. Once Gutenberg is built into the core of WordPress, you will need to install the Classic Editor plugin in order to disable Gutenberg.

In Summary

As a team, here at ThemeFusion HQ we are closely following the development cycle and progress of Gutenberg. As has and always will 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:

  • Progress and change is always a positive thing, how else will we all continue to evolve and stay ahead of the curve

  • Developers have to rethink the way features are built and implemented
  • Users brand new to WordPress will appreciate the new editing experience
  • Regular users will to some extent have to familiarize themselves with the new editor

“There is nothing noble in being superior to your fellow man; true nobility is being superior to your former self.”
Ernest Hemingway

By |2018-11-05T15:48:15+00:00August 2nd, 2018|Gutenberg|


  1. whuang99 August 3, 2018 at 11:20 pm

    Just need further clarity. With 5.0 the “new editor will be enabled by default in the next major release of WordPress” according to the call out. I interpret this to mean that they will not force Gutenberg on us (yet) and Classic will remain, at least in this version.

    They’re not exactly saying Classic will always be around for users who don’t ever want to use Gutenberg or are using themes that may never be able to seamlessly convert content to Gutenberg.

    • Michael August 8, 2018 at 9:05 am

      Hi @whuang99. Yes, the Classic editor will be available to activate instead for the foreseeable future. Exactly how long that will be is anyone’s guess, the Gutenberg team are not very clear in terms of their overall plans/roadmap. As for us and our team, we are monitoring this all very closely to ensure that we stay ahead of the curve as we always have when it comes to WordPress and the wider industry.

  2. pagemonroe August 4, 2018 at 5:32 pm

    Thank you for your updates and commitment to your users. Your updates in regards to Gutenberg have brought a lot of peace knowing that you are on top of this massive change. As a business owner who’s company lives and dies off of wordpress development. I know that I’m in good hands with the themefusion team! You guys rock!

    • Michael August 5, 2018 at 3:49 pm

      Hi there. Thank you so much for sharing this, it not only motivates and encourages us, it validates everything. Our team, all of us, love what we do and who we do it for and we are so incredibly excited for what lies ahead in the years to come. Gutenberg will mean some change for anyone in the WordPress community, not just theme developers, however, we do feel it is a positive change for the overall WordPress ecosytem roadmap. Thank you kindly

  3. emgwebsites August 8, 2018 at 1:14 pm

    I use Avada on client builds and have for years ‚Äď thus have been navigated thru numerous changes by ThemeFusion and have no reason to worry about this upcoming change. Thanks again for all the dedication, as there is much value packed into Avada and I, for one, have never regretted the choice to rely on it.

    • Michael August 9, 2018 at 3:28 pm

      Thank you very much for sharing this and we are grateful to have you as a part of the Avada family! The best is still to come ūüôā <3

  4. migstf August 8, 2018 at 5:34 pm

    Unless I’m missing something obvious, there’s no way to use Fusion Builder for pages, if Gutenberg is active?

    • Michael August 17, 2018 at 9:14 am

      For now that is correct. Editing pages created with either is not interchangeable, yet and that is why WordPress includes the classic editor plugin

  5. Ter747474 December 4, 2018 at 4:19 pm

    The WP 5.0 is just around the corner. I am in no hurry to update but I have to ask, how things are going in the relationship with Avada and Gutenberg? Are things looking rosy or is there a storm coming up in the horizon?

    • maximusmedia December 6, 2018 at 5:51 am

      Hey! If you have already updated to Avada 5.7.2, you are good to update to WP 5.0 once it is released and will be able to work with Avada and Fusion Builder just like you are used to. There is no special recommendation from us to update to WP 5.0, because a lot of people in the community expect that WP 5.0.1 won’t be far off. So, it might be more convenient to wait.

      Also, moving forward, we’ll always make sure that you can work with Avada in the same smooth way that you are used to.

Leave A Comment

Recent Posts

Recent Tweets

For privacy reasons Twitter needs your permission to be loaded. For more details, please see our Privacy Policy.
I Accept