Browse documentation
CMS and dynamic pages
Model structured content, create collections, and bind entries into dynamic routes.
Model content before layout
A collection defines the fields and validation rules shared by a type of content. Entries hold draft and published values against a versioned collection schema.
Choose field names that describe meaning rather than presentation. For example, use customerQuote instead of grayItalicText so the content can survive a redesign.
Create dynamic routes
A dynamic page connects a route pattern to a collection. Each published entry resolves to a stable path using its slug and the site route graph.
Bindings connect element properties to collection fields. Publishing validates the referenced collection, schema version, entry state, and route before producing artifacts.
/customers/{slug}
/resources/{category}/{slug}
/team/{slug}Publish content safely
Draft entries are visible in authenticated preview but are excluded from production releases. Publish an entry when its required fields, route, media, and references are complete.
Schema changes should remain backward compatible while published pages still depend on older fields. Review affected bindings before removing or changing a field type.
Still need help?
Find recovery guidance or contact the DevAssistant team.