Getting started
How do I get started with BetterCMS?
You create a workspace, pick a template or start from an empty content model, then invite the people who will publish. Everything runs in the browser. No local install and no build pipeline stand between you and a first page on a real URL, because the editor, the content model and hosting are parts of one product rather than three decisions.
If a site already exists somewhere else, start with the Migrator instead of a template. It maps an existing schema onto BetterCMS collections and brings entries and assets across with it.
The order to do it in
Workspace first, then a project, then the content model, then people, then the domain. The workspace carries billing, members and roles. The project carries one site: its model, its pages, its collections, its media and its domains. Getting those two the right way round matters, because members are added once at the workspace and reused across every project under it, while each project gets its own Site plan.
The domain comes last on purpose. A project publishes to a working URL before any DNS is touched, so waiting on a registrar never blocks the first page.
Pick the starting point that fits
There are three, and they are genuinely different amounts of work. A template is the fastest: the model and the pages arrive together and you replace the words. An empty content model is right when a designer has already drawn the site, because the model should describe that design rather than bend to a template. A migration is right when a site already exists somewhere else, and it starts in the Migrator rather than in a template.
Teams that pick a template and then try to reshape it into a model they had already designed do the work twice. If the design exists, start from the schema builder.
Settle who can publish before you invite
Roles are easier to set than to walk back. A workspace where everyone was made an admin on day one is a workspace where nobody knows who approved what by month three, and the audit log records a lot of admins.
The cheap version of this decision is two lines: who is allowed to publish, and who has to approve first. Every Workspace member costs the same $15 a month whatever their role, so there is no cheaper tier to put an approver on. Settle the names first and the bill follows.
Also in getting started
Still have a question left
Thirty minutes with the product team, and a straight answer.