Documentation

Everything this site publishes about how lazysite works, and which question each page answers.

Who this is for

Anyone who runs a lazysite site, an AI agent working on one, or someone working on the engine itself. The pages are grouped by who reads them, then by theme: start in your own section.

This manual is the engine's. It serves on every site, upgrades refresh it, and a page the site puts at the same path overrides it - see The /docs manual.

Setting up and running a site: the operator

Giving an AI assistant access

Onboard an AI agent
The operator's side of granting a partner access: the account, its permissions, and watching and revoking it.
Connect an AI assistant
Adding the site to Claude.ai, ChatGPT, Claude Desktop, Claude Code or another MCP client, step by step, and how a client connects and authenticates.

Installing and configuring

Installation
Installing and upgrading.
Configuration
lazysite.conf, nav and extensions.
Manager
The manager interface.
Reference
Keys, variables and file locations.
Troubleshooting and migrating
When something does not behave.

Accounts and access

Authentication
Accounts, groups, capabilities and the access model.
Behind an identity provider
Letting a proxy in front of the site sign visitors in, what the provider's groups may do, and a Caddy and Authentik example.

Content

Authoring
Writing content.
Front matter
Every front-matter key a page may carry.
Advanced authoring
The richer authoring constructs.
Remote content
Pulling content from elsewhere.
API and raw mode
The control API, and serving a page as an artifact rather than a document.

Look

Layouts and themes
How layouts and themes are structured.

Forms, data and connections

Forms
Defining forms, field types, validation, limits, and reading what they collect.
Form helpers
The delivery handlers a form can bind to.
SMTP configuration
Mail delivery for forms.
Data tables
Declaring a table, putting records in it, and reading them on a page.
Connectors
A credentialed destination forms and callers send site data through, and where the answer is kept.
The Odoo extension
Running named Odoo operations from pages, forms, the schedule and agents, and what bounds each.
Payment
The x402 payment flow.
Installing a site as an app
Making a site, or one section of it, installable on a phone as a progressive web app, and what the device keeps.

Working on a site: an AI agent

If you are an AI partner connecting over MCP or the control API, read the briefings first. They are written for you, and they answer most of what the tool surface alone will not. The operator's pages above are the reference behind them.

Connecting

Connect an AI assistant
Endpoints, connection modes and authentication: how a client reaches the site, exchanges its pairing key and presents its token.
AI connector - tools reference
Capabilities and denied paths, and every tool the connector exposes.
AI briefing - publishing
The onboarding brief, the path mapping, WebDAV, the control API actions, briefs, ownership and cache behaviour.

Building and writing

AI briefing - building sites
Read before creating or restructuring pages. How content, layout and theme stay separate, what not to do, and the one sanctioned pattern for live data.
AI briefing - content authoring
Front matter, Markdown, URLs, and the content rules.
AI briefing - field practice
One agent's field notes from real sites, a companion to the briefings.

Look

AI briefing - layouts and themes
Layouts, themes, and the token vocabulary.

Configuration and data

AI briefing - configuration
Site configuration keys and what they change.
AI briefing - data tables
Declaring tables, loading records, and rendering them - for an assistant.
AI briefing - visitor analytics
How to read the analytics payload and answer questions about traffic.

Bringing in an outside source

Integrations
How an agent brings an external design, document or export into a site.
Figma
Building or restyling a site from a Figma design.

Working on the engine: a developer

AI briefing - development
Working on the engine itself.
Development
The local development server, build tools, and troubleshooting.

A note on capabilities

A capability map answers what has this account been granted. It does not answer what can lazysite do - these pages answer that. If a tool is not offered to you, the usual reason is that the capability has not been granted, not that the feature does not exist. Ask the operator.