A content-first CMS: content is the first-class citizen, and outputs are how it leaves the system — the same authored content can leave as an HTML page, a JSON record, or a fragment, each through a renderer its content type declares.
These chapters are for people building with Accent — site builders and developers. For the design system the CMS renders through, see Mark Design. The boundary test: does the page still make sense with no CMS, as plain HTML off a CDN? Then it is Mark Design's page.
Sites, assets, content types, the identity triple, and why a page is a view rather than a table.
The reusable field registry, data type vs editor, field sets and namespaces, options vs content.
Creating templates, directories and identity — the document shell a page renders through.
Where authored content lands, and what a template owns around it.
require(), include(), cms.partial() — and the editor and API lanes.
The `cms` object every template renders with — the asset, queries over the site, outputs as values.
Outputs, the Content renderer (None · Layout · Partial), and delegation.
Sections are content types: data-accent-content, data-zone, data-label.
Entity routes, the composition verb, and JSON delivery.
Theme packages, follow vs fork, and how a site binds one.
The Manage Site surfaces, slugs and titles, folders, the page panel.
The agent lane over the same API a person uses.
Accent UI — the admin’s finished skin: stock Bootstrap markup, one control height, colour as state.
The system components — one anatomy, one home, rendered everywhere it applies.