Glossary
Every page of this documentation uses the term in the first column. The code sometimes calls the same thing by another name, shown in the third column so you can match what you read here to what you see in code. The words in the last column are not used on these pages.
The product is written BOLDCMS, in capitals. Package, command and domain names keep their own
lowercase spelling, such as @boldcms/astro or boldcms design check.
| Term | Meaning | Code name | Do not use |
|---|---|---|---|
| Project | One website and everything it owns: its content, its settings and its domain. The admin lists projects under Projects. | tenant | tenant |
| Design | How a site looks and the markup it draws. A project wears one design at a time. | design | skin, renderer |
| Direction | A starting point for a new site, picked from the catalog: a design with sample pages and content. | direction | |
| Page | A page of the site, with its own address, built from sections. | pages | |
| Section | One part of a page: a block placed on it and filled with content. The admin lists a page's sections in order, under Sections. | an entry of layout | |
| Block | A kind of section, such as a hero, a call to action or a form. Each block has its own fields. | block, blockType | |
| Collection | A list of entries of one kind, such as blog posts, services or team members. | a collection slug, such as blog | |
| Module | A feature that can be switched on or off for a project, together with its collections and blocks: blog, team, FAQ, testimonials, services, branches, portfolio, logos. | enabledModules | |
| The admin | The web interface where a project's content is edited. | /admin | |
| The engine | The Astro integration a design is built on. It answers every route of a site, loads the page from the CMS and hands it to the design's components. | @boldcms/astro | |
| The contract | What a design is written against, and the check that decides whether a design is compatible with it. | @boldcms/contract, design.json | |
| Design check | The local command that renders a design over the contract's fixtures at the widths it declares, and reports ok, warn or refuse. | boldcms design check | |
| Publish | Making a draft the version visitors see. Content goes live by publishing, without a deploy. | _status: 'published' | |
| Draft | The saved state of a page, blog post or service that visitors do not see yet. Edits go to the draft, and a live page keeps showing its published version until the draft is published. | _status: 'draft' | |
| Version | A saved earlier state of a page, blog post or service, with its time and what changed. A version can be restored as the draft. | versions | |
| Deploy | Putting a new build of a site's code live. A new design version reaches a site through a deploy; content does not need one. | deploy | |
| MCP | The Model Context Protocol: the open protocol through which an AI agent reads and writes a project's content. | the cms_* tools | |
| Agent | An AI assistant that works on a project for you through MCP. | ||
| Delivery API | The HTTP API a site reads its project's content from, at https://cms-production.boldcms.dev. | /api/routing/resolve | |
| Access token | The credential a request to the delivery API carries. Each project has its own, and it decides which project a request reads. | accessToken, BearerAuth | SDK token |