Getting started
What does a BetterCMS project contain?
A project holds one site: its content model, its pages, its collections, its media and its domains. Each project has its own Site plan. A workspace holds several projects, and members, billing and roles sit on the workspace. A team running one marketing site and one docs site keeps them as two projects under one workspace, with a Site plan for each and its people paid for once.
Project or workspace, and why it matters
The project holds everything about one site: the content model, the pages, the collections, the media library and the domains. The workspace holds everything about the people and the money: members, roles, billing and the AI budget.
The practical consequence is that people are paid for once. Somebody who works across three projects is one member, not three, because the membership belongs to the workspace. Each project still carries its own Site plan.
When two projects beat one
Split when the two sites want different content models. A marketing site and a developer docs site are the common case: the docs site wants versioned articles and a navigation tree, the marketing site wants landing pages and case studies, and forcing both into one model gives you a model that fits neither.
Do not split for a microsite that shares the marketing model. That is a folder and a domain, not a project.
What travels with a project
A project can move between workspaces, and it takes its content, its model and its domains with it. What it does not take is the old plan: it resets to the receiving workspace, so a transfer never carries a price into an account that did not agree to it.
This is the mechanism agencies use. Build in your own workspace, hand the project to the client when it is finished, and the client pays for it from then on.
Also in getting started
Still have a question left
Thirty minutes with the product team, and a straight answer.