Page builders (not supported)

Octa Editor does not support page builders. Elementor, Divi, Beaver Builder, WPBakery, and similar tools do not store their layout in post_content. They keep it in their own post meta, for example Elementor’s _elementor_data, as a private structure that only the builder understands.

Builder layouts are never touched

The document schema only writes keys it recognizes, which are the core post fields, taxonomies, the ACF fields object, and the seo object. A page builder’s layout meta is not part of that schema, so Octa Editor never reads or writes it. Editing a builder page through Octa Editor cannot corrupt its layout, because the layout data is out of scope by design.

The reverse is also true. You cannot edit a builder layout through Octa Editor. There is no way to change a widget, section, or design element built with Elementor or Divi from the document.

What you can still edit

A page built with a page builder is still a normal post, so its standard fields remain editable. You can change the title, status, slug, dates, parent, and taxonomies, and you can write ACF fields and seo values on it. Only the visual layout is off-limits.

Some builders also mirror a copy of their output into post_content. Writing content on such a page has no visible effect, because the builder renders from its own meta and ignores post_content.

Why there is no support

Page builder layouts are deeply nested, builder-specific structures with unique element IDs, and they carry side effects such as cached CSS that a direct write would leave stale. They do not map onto a portable, field-addressable document, which is the model Octa Editor is built around. Supporting them safely would require a separate, builder-specific adapter for little practical gain, so it is intentionally out of scope.