Start from a template
Blog, Case studies, Team, FAQ or Custom. Every field can be renamed, removed or added.
Set up a collection once. Writers add items and publish them, and the live site shows them right away. No build, no waiting, no second system.
Blog, Case studies, Team, FAQ or Custom. Every field can be renamed, removed or added.
Publish puts an item on the live site. Pages read the site's database on every request.
It lives in the site's own database and leaves with the site in an export.
An item saves a moment after you stop typing. Publish is a separate step, and every version can be brought back.
Rich text with headings, lists, quotes and links. Write and Preview show the text the way the site will.
Write, publish and restoreHistory lists versions as you edit and publish. Restore one and the current version stays in the history.
A collection with Pages on gets a list page and a template for each item. People who only write get a simpler editor.
A list with search, filters and sorting, and a template for each item. Both are files in your site you can restyle.
Collection pagesContent editors and clients see pages and their SEO, collections and forms. Design, layout and the agent stay with you.
The client content editorNo. Publish puts an item on the live site. Pages read the site's database on every request, so a published item shows up without a build.
Anything you repeat: blog posts, case studies, team members, questions and answers. Start from Blog, Case studies, Team, FAQ or Custom, then rename, remove or add fields.
In the site's own database. It belongs to the site, so an export carries the content, uploaded media and form submissions along with the code.
Yes. Content editors and clients get pages and their SEO, collections and forms. Design, layout and the agent stay with you.
Yes. History lists versions as you edit and publish. Restoring one keeps the current version in the history.
Same design, rebuilt as real code, with a CMS the whole team can use.