Dollie Editor SDK guide
Core Concepts Overview
Learn the small set of contracts that power the editor, renderer, catalogs, and Copilot
Dollie Editor stays coherent by using the same concepts everywhere.
| Concept | Responsibility |
|---|---|
| Page | Stores an ordered definition of the content |
| Section | Provides one top-level React page region |
| Field | Describes an editable prop |
| Slot | Reserves a Field for an Element |
| Element | Supplies a swappable visual or dynamic unit |
| Catalog | Defines the content available to people and Copilots |
| Template | Provides a ready-made Page |
| Document | Wraps a Page with identity, revision, metadata, and capabilities |
| Transport | Connects the editor to host-owned persistence and services |
The central relationship
Catalog
├── Sections
│ └── Fields
│ └── Slots
│ └── Elements
└── Templates
Page
└── ordered Section references + props
The Catalog describes what can be used. The Page records what was chosen.
Why the model is structured
Structured Page data gives every interface the same boundaries:
- the editor shows the right controls;
- the renderer resolves known components;
- validation rejects unknown content;
- the Copilot sees valid ids and fields;
- persistence stores portable JSON;
- migrations can preserve old pages.
There is no separate “AI page format” or “visual-editor format.”