I talked directly to the Developer of the integrations.
There’s an easy way to do this. Let me explain it.
Custom row modes (like the integration rows) pre-pack the row structure for a particular type of content, while you can always reproduce (almost) the same thing by using any row type.
All you need, is to use appropriate ID and Class attributes.
For example, the content row mode of DIVI uses following structure (high-level):
- <div id="et-main-area">
— <div id="main-content">
———— content here
So you can use any row type from layouts.
For example "Cells extend to full width" ==> which expands to full page width.
Then you can apply the "et-main-area" ID to the row, while you can apply the "main-content" ID to the content cell (used in the row).
This outputs (almost) the same structure, BUT, you may need to apply some extra CSS (to look it exactly the same).
To summarise:
- For full-width row, you can use any row other than the custom row mode, but you need to use the appropriate structure (i.e. IDs, classes)
- Or you use the specific DIVI row type (to wich BTW you can also add your Custom CSS if wished)
As far as the future updates are concerned:
This is going to change the almost same way, I mentioned above.
Means, we are going to less rely on custom row modes and cells (as much as possible).
So you can understand the real power of Layouts and we can help reducing such confusions.
We will try to make the Integrations as simple as possible without any Custom Content, by adequately updating the GUI and the Cell Types and the possibilities you have with them.
The integration is for the DIVI Theme, so yes, you need that Theme.