Documentation

Two paths through this. If you are setting up a site for a business, read the first three. If you are building for someone else, read all five.

1 · Install

Two files and one command. What you need, what happens on first boot, and how to put it behind a domain.

2 · Run your site

The dashboard: content, the visual canvas, the assistant, history and undo — and what each is for.

3 · Make things happen

Confirm a booking when the deposit lands, text the customer when it is confirmed — and try it before it is real.

4 · Build with it

The spec as files, fcms, the API, and the MCP server for agents.

Reference

Every field type, every block, every operator — generated from the schema, so it cannot describe a version that does not exist.

5 · Keep it running

Backups and restores, upgrades, and what to do when something is wrong.

The one idea

Everything else follows from this: your site is a spec — one declarative document describing content types, pages, logic, access and integrations. It is not a database of settings and it is not code.

Every way of changing your site edits that same document, through the same validation and the same history:

forms · canvas · assistant · fcms · MCP
│
▼
the site spec
│
validate → describe → confirm if destructive → apply with an inverse
│
▼
your site, and one undoable history

So a change made by an agent at 2am and a change you make on your phone are the same kind of thing, appear in the same list, and undo the same way.