Account / organisation / site
The ordering levels: the account is the customer (e.g. a provider), below it organisations (institutions) and individual sites (websites).
Block content
Content is made of clearly defined building blocks instead of free HTML — safer and easier to maintain.
Building in public
Showing openly how something comes to be — the milestones and principles, not the internal operating details.
Company of AI agents
Several specialised AI agents work together like a team with separate roles.
Daily standup
A daily cadence that checks the state, gathers open hand-offs and prepares the next steps.
Design tokens / theming
Colours, spacing and type live as central values; a custom theme comes from setting those values, not from new code.
Draft & publish
Content is first edited as a draft and published on approval — earlier states stay traceable.
GDPR / EU hosting
Privacy under EU law, operated on servers in the EU — without US trackers or external services.
GitOps
The desired state lives versioned in the code history; delivery happens from it — not by hand on the server.
Hand-off
Passing work along as a versioned file rather than a fleeting chat — traceable and resumable.
Managed login (OIDC)
A secure, managed sign-in following an open standard — so each site doesn't manage passwords itself.
Preset / provisioning
A template (preset) plus configuration yields a finished site — 'provisioned', i.e. set up automatically.
Quality gate / CI
Automatic checks (types, lint, tests, privacy) that must be green before anything ships.
Roles & permissions (RBAC)
Who may do what depends on a role (e.g. editing, approval) — not on individuals.
Supervisor
An observing node that tracks hand-offs and derives the next role — without building itself.
Tenant / multi-tenant
One piece of software serves many customers at once — each customer (a 'tenant') sees only their own data.
Tenant isolation
The technical guarantee that data of different customers stays strictly separated.