How it works

A site, and the machinery behind it.

Pages are made of blocks. Blocks carry your brand tokens. Everything a visitor does, an enquiry, a booking or an order, becomes a record you can find later.

A barista working behind the espresso machine, the street door open onto wet cobbles
09:12 · enquiryNew enquiryvalidated and stored
The order of things

Four steps, and none of them is a migration.

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

01Make an account

Sign up on the platform. You get a site with a home page, a navigation partial, a footer and a not-found page already in it.

02Set the brand

Three colours generate the whole token scale: headings, body, muted, borders, the inverse band, and readable text on your accent. Fonts are slots you bind to roles.

03Change anything

Drag elements onto the canvas, or edit text in place. Each node carries desktop, tablet and mobile styling, plus hover and focus.

04Publish, then point a domain at it

Pages are drafts until you say otherwise. The domain is the last step, on purpose: a site in progress should not be reachable.

A print workshop with paper hanging to dry beside a flatbed press under a lamp
A published page is finished HTML, rendered on the server
Two languages, one site

Write it once. Serve it twice.

Translation here is an overlay keyed to the text itself, not a second copy of every page. Edit an English sentence and its Dutch counterpart stays attached to it.

ServingYour default language serves unprefixed. Every other enabled language serves under its code, so this page is also at /nl/how-it-works.
NavigationThe language switcher renders plain anchors to the current page in each language, so it works with no JavaScript at all.
Getting startedMissing strings can be machine-translated in bounded batches, marked as machine, and never overwriting a human edit.

One thing worth knowing before you plan URLs: slugs themselves are not translated. The Dutch version of /how-it-works is /nl/how-it-works, not a Dutch word. That is the current behaviour, and this site runs on it.

Publishing

What happens when you press publish.

The page is rendered on the server, so what a visitor and a search engine receive is finished HTML.

Page visibilitydraft or published, per page
Revisionsevery save keeps the previous tree
Schedulinga page can be given a date to go live on
Sitemapgenerated for the site, including entry URLs per language
Faviconsone upload generates the set browsers ask for
Runtime on the pagea ~3 KB script, not a front-end framework
Start

Make the first page today.

Everything above is reversible. Pages stay drafts, and the domain is the last thing you attach.