In reply to Seth Goldstein.

I am doing pretty much the same thing on my site. I enjoy using Gutenberg for blog posts a lot more than the Divi Builder, though obviously for page building purposes Divi is the best choice right now.

In the future, I am hoping Divi and the other page builder plugins end up re-basing themselves off of Gutenberg so they can take advantage of the block APIs. That would mean you could potentially use the Divi Slider module (now a block) on a page using the normal Gutenberg editor (actually, the block could be split off into its own plugin entirely), or use Gutenberg blocks from core WordPress and plugins directly in the Divi Builder. Sections, Rows, and Columns could become blocks on the technical side, and perhaps you would finally be able to nest sections and columns in Divi. (Though I would hope that would come anyway regardless of Gutenberg integration.)

Extending off of Gutenberg would also mean switching to another builder plugin like Beaver Builder could be a lot easier in the future, since the blocks could be separate from the builder and of course, disabling Divi would not leave shortcodes everywhere since it would be using the Gutenberg HTML comments as delimiters instead.

I imagine that in the long-run, page builder plugins would end up being split up into several smaller plugins:

- plugins that simply replace the visual user interface of Gutenberg with an alternative UI
- plugins that extend Gutenberg with additional functionality (selective sync, advanced color picker, text color options visible on every block, copy-paste styles from one block to another)
- plugins that add blocks to Gutenberg like sliders, CTAs, advanced rows and columns, accordions, and so on

This would be really nice as it would mean you could pick and choose the functionality you wanted and not get locked in to a single monolithic plugin that bundles large amounts of functionality. I hope that is the direction that Divi will end up heading in the future.