Start here
Glossary
Plain-language definitions of the terms used in the CMS and these guides.
Content and identity
| Term | Meaning |
|---|---|
| Resource | A stable record such as a page, post, template, shared section, menu, brand, settings record, term or author profile. Its identity stays the same across edits. |
| Content type | A registered definition of fields and behaviour for entries. Posts and Pages are the protected defaults; administrators can create custom types and manage retired types separately. |
| Slug | The URL-friendly identifier used in a public route. It is not the same as the entry’s display title or immutable resource ID. |
| Taxonomy / term | A classification system, such as Categories or Tags, and one item within it. A post can refer to terms. |
| Author profile / person | An author profile supplies public attribution. A person is a login account with a role. They can be linked but are separate records. |
| Media asset | An uploaded image or supported document plus metadata. Content references its stable ID; the file bytes live in managed media storage. |
Sources: Core content contracts; Registered content definitions; Database schema.
Editing and publication
| Term | Meaning |
|---|---|
| Revision / snapshot | An immutable saved version of a resource’s content and layout. |
| Working revision | The current editable version. Saving makes a new revision and moves this pointer. |
| Published revision | The version selected for publication. It can differ from the working revision. |
| Public / Private | Visibility choices. A private item may have a published revision without being exposed as an anonymous public page. |
| Pinned revision | The specific saved version attached to a review, schedule or preview. Later edits do not silently replace it. |
| Preview | An authenticated, permission-checked rendering selected by a preview token that can include specified draft revisions. Possessing the link alone does not grant anonymous access or publish the draft. |
| Dependency | Another record required by content, for example a referenced shared section, menu or media asset. Publication checks these relationships. |
| Conflict | A rejected change because the expected version no longer matches current state, often after another editor saves or publishes. |
| Restore | Recover an older revision as working content. This does not automatically publish it. |
Sources: Core content contracts; Revision and publication workflow.
Website design
| Term | Meaning |
|---|---|
| Composition | A saved arrangement of visual blocks and their settings. A page’s own composition overrides inherited template design, even when it is empty. |
| Puck | The visual-editor library used for the block canvas and component property controls. |
| Template | A reusable layout selected for a page, content type or public route context. |
| ContentBody | A dynamic block that renders the current entry’s rich-text body inside a composition. |
| Shared section | A separately managed design resource used by reference in multiple places. A copied set of blocks no longer has that shared link. |
| QueryLoop | The Content collection block. It selects eligible published entries by content-type key with a limit of 1–24 and an optional heading; its card presentation is defined in code. |
| Brand tokens | The supported identity, color, font and logo values stored by Brand & theme. Spacing and many component colors remain defined in the stylesheet rather than editable brand tokens. |
Sources: Visual component configuration; Public rendering data resolution; Supported brand token controls; Public component styles and theme limits.
Setup and operations
| Term | Meaning |
|---|---|
| Web process / worker | The web process handles requests. The separate worker handles queued and scheduled background work. |
| PostgreSQL / Drizzle | PostgreSQL stores the CMS data. Drizzle provides typed database access and migration tooling. |
| Migration | A controlled database-schema update run with the deployment’s migration role. |
| API scope | An action allowed by a particular integration token, intersected with its owner’s current permissions. |
| Idempotency key | A request identifier used to recognize a retried operation and avoid applying it twice. |
| SMTP / Mailpit | SMTP sends account emails. Mailpit is the local mail-capture service for development and testing. |
| Backup / export | A full recovery backup includes the database and media files. The content JSON export is a smaller portability package. |
| RPO / RTO | Recovery point objective describes acceptable data loss in time. Recovery time objective describes acceptable restoration time. Targets require tested operational procedures. |
Sources: Operational terminology and recovery; Deployment services.