Many Divi users are already asking the question "Will Divi and Gutenberg be compatible? ». The most curious among them have already installed the test version of Gutenberg on a website using Divi and have already noticed that there were no conflicts. However, the cohabitation of the two page builders was not a model of perfect integration...
Edit from December 6, 2018: this article was written this summer, when Gutenberg was just a plugin at the time. Since version 5 of WordPress was released today, a lot has changed! We are currently at version 3.18 of Divi which I have tested for you. I invite you to read this article.
The developers of ElegantThemes are already working on the issue since the Gutengerg editor has been officially announced to be part of the future major WordPress update.
It's official since yesterday, with the release of Divi Builder 2.11 and Divi 3.11 => Divi and Gutenberg are now "compatible".
What is Gutenberg?
In the WordPress community, everyone has been talking about it for quite some time now!!!
Gutenberg is the future WordPress publishing editor that will be integrated with the release of WordPress 5.0.
If you use Divi, the new editor will look familiar: Gutenberg offers "blocks " while Divi offers "modules", but the system remains the same...
And if you use Divi, chances are you won't find Gutengerg very User Friendly, to say the least!
If you haven't tried it yet, you can already install Gutenberg which is available as a pluginfor now. Then, in the next version of WordPress, Gutenberg will be integrated in its core. The idea is to start getting familiar with this new interface, but especially to give time to developers to create addons and lots of new types of blocks.
When will WordPress 5.0 be released?
Don't worry, WordPress 5.0 & Gutenberg won't be released tomorrow, but the deadline is coming up!!!
The team of contributors and developers of the WordPress project have been working hard for months to release a new version! But you can imagine that this new version will integrate a new feature and that it can be very risky!
In short, you still have a few months to go: WordPress 5.0 should be out by the end of 2018, but nothing has been officially announced yet.
Divi and Gutenberg: the before and after
This update of the Divi Builder doesn't seem to have changed much, but if you have Gutenberg installed in parallel, you will be able to appreciate these changes:
1 - Switching from post editing
The new version of Divi (and the Divi Builder) now allows you to easily switch between Gutenberg and the Divi Builder. This may seem like a simple option, but it wasn't available before Divi supported Gutenberg.
So, just as you can switch between the classic WordPress editor and the Divi Builder, you can do the same between Divi and Gutenberg.
2 - Choose your editor when creating posts
Again, this option was not available. Now, by clicking on the drop-down menu, the "Divi" option has been added.
3 - Choose your editor from the list of posts
When you want to edit an existing post from your list of pages or articles, you can also choose to edit with Divi.
When you hover the mouse over the post you want to edit, the option "Edit with Divi Builder option appears.
4 - Will the cohabitation between Divi and Gutenberg remain like this?
Apparently NOT. This is just the first important step that ElegantThemes has taken to prepare the new version of WordPress. By the way, Nick Roach - the head of the company - announced it himself:
We want you to know that this is just the first step, and we have a lot of great ideas on how we can better integrate the next publishing editor. As the new editor continues to evolve and we get closer to the release of WordPress 5.0, we hope to release additional updates that will further enhance your page building experience.
What if you don't want to use Gutenberg?
As you can see, Gutenberg is currently in beta and is not yet part of WordPress. It is only available as a standalone plugin. If you don't want to use it now, you don't have to do anything but know that when WordPress 5.0 is released, Gutenberg will become the default editor.
If you're worried about the changes that the new version of WordPress will bring and you're not ready to get started with the new interface, you can install the Classic Editor plugin. This will allow you to keep the old WordPress publishing editor.
Gutenberg has already been talked about (too much)! I never wrote an article about it because I don't like predictions and as long as nothing is done, I wait and see...
I have tested Gutenberg several times and I even integrated it in my training program when I train my students to WordPress.
For almost a year, I've been suggesting to my students to discover Gutenberg so that they won't be lost when WordPress 5.0 is released... And the opinions are clear: Gutenberg is unanimously accepted, but in the wrong way: nobody has opted for this page builder and won't do so... for the moment anyway!
I understand that everyone needs to modernize and that WordPress needs to offer an embedded solution to create layouts that are a bit more complex than those done with the classic editor. I also understand that WordPress couldn't leave this crucial part to third-party developers, while Wix and company already have drag and drop solutions. This evolution is normal and should be beneficial in a more or less near future.
Still, with the best developers in the world at Automattic, I expected a much more UX, drag and drop and even front-end tool. I suppose that these developments will come...
Some people are worried and even question the future of the companies creating themes and page builders...
But honestly, I'm sure that the heads of WordPress have taken into account the users but also the developers of plugins and themes whose economy is based on publishing within the CMS (I'm talking about Divi, Elementor, Visual Composer and company!). Without forgetting all the websites made by freelancers or web agencies and that will not "explode" overnight ...
There is a whole ecosystem that revolves around WordPress and it would be madness to hide it...