Guides
Home / Documentation / CMS
CMS features layer structured content on top of the same site document the editor uses. Collections define schemas; dynamic pages bind routes to those schemas; submissions land in your workspace.
A collection is a typed set of entries (fields, validation, and optional presets such as blog or directory). Create collections in the dashboard, then attach them to pages that should render one entry per URL.
Dynamic pages pair a route pattern with a collection. Index content lives in normal page blocks; detail layouts can include template-only sections that bind to entry fields. The API exposes the same structures under site pages with dynamic metadata.
Per-page SEO for CMS detail URLs can use seoMapping with placeholders such as {{fieldId}} so titles and descriptions track entry data. See the API reference data models for exact fields.
Form blocks post to hosted endpoints; submission storage and exports follow your plan. Visitor traffic to POST /api/forms/submit counts toward limits described in pricing.