Skip to content

Integrations overview

Octa Editor does not store field or SEO data itself. It reads and writes through whatever plugin owns that data, and folds the result into the same document.

When a supported plugin is active, its data appears in the document automatically.

If none are installed, those parts of the document are simply omitted. Nothing needs configuring.

An exported document carries a read-only _meta.providers block that names the active field and SEO plugins. This matters for SEO, where template variable syntax differs between plugins. Read _meta.providers.seo from a pattern export before writing SEO values.

The provider model is pluggable. Developers can swap the field or SEO adapter with a filter.

  • octa_editor_fields_provider replaces the custom-fields adapter.
  • octa_editor_seo_provider replaces the SEO adapter.

This is how you add support for a field or SEO plugin that is not built in. See Hooks and filters.