Concepts
The platform model behind every interface — how websites, objects, permissions, design documents, locales, and files fit together.
The admin panel, MCP, and the REST API are three views of the same model. These pages describe that model once, so the interface pages can stay short.
- Websites and publishing — preview mode, subscriptions, domains, and public URLs.
- The object model — object types, fields, entries, relations, and restore.
- Permissions — public access, platform roles, website user roles, and conditions.
- The design model — design documents, blocks, revisions, and publish timing.
- Locales and translation — the three locale ideas and how not to mix them.
- Files and assets — the library, directories, uploads, and CDN URLs.
One model, three interfaces
A change made in the editor, through MCP, or through the API lands in the same tables and the same revision history. There is no separate agent data store, which is why an agent can pick up exactly where a person left off.
Where to go next
- New to the platform: Getting started.
- Choosing an interface: Interfaces.
- Looking for a specific screen: Admin panel.