Skip to main content
On a site running Divi, WPOS builds real Divi pages. Give it a design and it can assemble the page from that design’s own code, or build it again in native Divi modules. Its widgets show up in the Divi Builder like any other module.
The Preferred page builder setting in Settings offers Gutenberg and Elementor. On a Divi site, say in the chat that you want the page built in Divi.

​
Two ways to build a Divi page

From the design's own code

Give WPOS a design, such as a Stitch artboard, and it assembles the page from the design’s exported HTML and CSS instead of redrawing it, so the result matches the design.

In native Divi modules

Ask for the page in native Divi modules and it builds one you can edit module by module in the Divi Builder.
In the video, WPOS does both from one Stitch artboard:
  • It copies the design’s images into the media library first, because the original image links would expire.
  • It fixes what WordPress and Divi change on save, such as extra paragraph tags, stripped form fields, and Divi styles overriding the design’s own.
  • Before the native rebuild, it says which parts of the design have no native Divi equivalent, and builds the native version on its own page instead of replacing the one that already works.

​
WPOS widgets in Divi

  • Native Divi modules. Every WPOS widget is registered as a Divi module, on both Divi 4 (classic, shortcode-based pages) and Divi 5 (block-based pages).
  • In the Visual Builder. On Divi 4, add and edit WPOS modules in the Visual Builder like any other module.
  • Same output everywhere. A widget renders the same HTML on Divi 4 and Divi 5, and the same widget also works in Gutenberg and Elementor.

Page builders

How WPOS works across page builders, with no lock-in.

Gutenberg

Build with core blocks and reuse sections as widgets.