Premium plugin
Schema is not included in the standard Redactor package. It ships as part of the Editorial Suite — purchase the suite on the pricing page (with Redactor, or later from your account), then download the package and enable the schema plugin.
Schema is Redactor for structured content — articles, landing blocks, and CMS entries that must follow a fixed shape. Authors do not get an empty page; they get labeled sections: headline, cover image, tags, body, and whatever else your schema defines.
Content is edited visually but stored and exported as structured data (type, meta, sections) ready for a headless CMS or custom backend. That is the difference between “HTML soup” and content you can validate, query, and render in multiple channels.
Empty schema — labeled sections are ready (headline, cover, tags, body, and so on), but no content has been entered yet. Authors see the document shape before they start writing.
Same schema after it is filled — fields hold real values, and the body uses normal Redactor blocks inside the structure your CMS expects.
Schema definition, fields, and JSON export: Schema plugin.
What authors see#
Sections with purpose. Each region has a label — Headline, Cover, Body — so the form of the document is obvious. Required fields and generated values (for example an author line) keep the structure honest without turning the UI into a cold form builder.
Familiar editing inside constraints. Body sections still use Redactor blocks. Images and inputs use the field types your schema allows. Authors stay productive; they just cannot accidentally invent a layout your CMS cannot store.
JSON in, JSON out. Load a document from your API as schema JSON; save the same shape back. HTML is a rendering concern, not the source of truth.
When Schema shines#
Use it when Redactor is the authoring UI for a CMS, not a free-form notepad: marketing sites with fixed page types, editorial systems with required metadata, or any product where the backend owns the content model.
Note: Schema mode is not combined with Versions or Email — those products own a different document model.