A small print workshop, press and flat files, no one in the room
Docs

The manual, written by
the people who built it.

Twelve areas, in the order you will meet them. Every page says what the thing does, what it needs, and the one mistake people make with it.

How it reads

Written for the person doing it.

Not a reference dump. Each page opens with what you are trying to achieve and closes with the thing that goes wrong first.

A ceramicist trimming a bowl on the wheel by a studio window
How to read a page

What it does. What it needs.
What goes wrong first.

Every page in the manual has the same three parts, in the same order, so you can skip to the one you came for.

What it doesOne paragraph, in the words you would use to describe it to somebody else.
What it needsThe thing that has to exist before it works. A resource behind a service, a payment provider behind a shop.
What goes wrongThe mistake people actually make, written out, with the fix.
The manual

Twelve areas.
In this order.

You can stop after any of them. A site with one page and a working contact form is a finished thing.

01

Your first site

An account, three colours, a layout, a page. The domain is the last step, on purpose.
02

The design system

Tokens for colour, space, type and radius. Change the brand and every block that referenced a token follows.
03

Blocks and the library

Thirty five elements, three breakpoints, hover and focus, and a library for the sections you want to reuse.
04

Forms

Fields on the page, rules checked twice, files, spam screening, and where a submission actually goes.
05

Bookings

The three modes, the resource each one needs, weekly availability, exceptions, pricing rules and the lifecycle.
06

Tickets

Events, occurrences, tiers, allocations, and check in at the door.
07

Selling online

Products, the cart, hosted checkout, and how a digital file is delivered after payment clears.
08

Articles and content

Content types, entries, the listing repeater and the detail template they render into.
09

Two languages

The translation overlay, locale prefixed URLs, per language slugs, and the switcher.
10

Statistics and consent

How a visitor is counted without a cookie, what is kept, and when the banner is still worth having.
11

Agents and MCP

Issue a token, connect a client, and the full tool roster with the arguments each one takes.
12

Publishing

Drafts, revisions, scheduling, the sitemap, favicons, and attaching your own domain.
A maker's workbench in a design store, tools and samples under a street window at dusk
The tool reference

Every tool, every argument,
generated from the server.

The agent reference is produced from the live tool registry rather than written by hand, so it cannot drift from what the server actually accepts.

Start here

Three ways in,
depending on who you are.

Most people need the first one. The third is for anybody wiring a client or an agent to the platform.

Never built a siteStart with Your first site and stop after the contact form. Come back when you need a calendar.
Moving an existing siteRead Publishing first. Attach the domain last, so the old site keeps serving until the new one is ready.
Building with an agentIssue a token, read Agents and MCP, and take a screenshot of everything you write.
Quickstart

Three lines,
and a site exists.

The agent route, for anybody who would rather type than click. The same three calls the editor makes.

create-website spaceId, name, langset-brand-profile primary, secondary, surfaceappend-blocks-to-page pageId, blocksEvery write is validated first, and refused whole if anything in it fails.
First site · Design system · Blocks · Forms · Bookings · Tickets · Selling · Content · Languages · Statistics · MCP · PublishingFirst site · Design system · Blocks · Forms · Bookings · Tickets · Selling · Content · Languages · Statistics · MCP · Publishing
Start

Read one page, then build the thing.

The docs are shorter than the average onboarding video and you can search them.

Hands repairing a linen garment by needle and thread