Documentation

A reading order

The four setup guides are written to be read in sequence, and each one assumes the one before it. If you are installing today, this is the shortest path to a site that can be left running.

Getting started first, because it ends with an article on the screen and everything after it is easier to judge once you have seen one. It is deliberately manual: you press a button, one draft appears, nothing publishes.

AI providers next, once you know whether the first draft was good enough. This is where the choice of model, the fallback order and the cost of a failed attempt are explained, and where you decide whether to stay on a free tier.

Run ceilings before anything runs without you watching it. An agent chooses its own next step, so the only thing that reliably stops one is a limit set from outside. Read this before scheduling, not after a surprising invoice.

Approvals and undo last, and only if you want a person between a draft and the site. The safety net underneath it works whether or not you turn approvals on: every change is recorded before it happens.

The knowledgebase is a different kind of writing and does not need to be read in order. It covers how AI assistants choose what to cite, which is a subject that outlives any one plugin.

If something here is wrong

Documentation drifts from software, and ours is not exempt. If a screen does not match what a page describes, tell us and we will fix the page rather than explaining the discrepancy away.

For anything account-related, billing or licence questions included, contact support is faster than the docs.