The homepage used to describe the templates. Now it shows them: two rows of real sites drifting in opposite directions, pulled live from the editor's own catalog, so the wall is never out of date with what you'd actually get.

Click any tile to open that template in the editor.

Archival now speaks MCP, so an assistant can author a site end to end without a checkout, a local toolchain, or a copy of the CLI. It writes the object files and templates, builds them against a pinned archival binary on our side, and hands back a preview URL you can look at and react to.

Build errors come back as tool output, which means the assistant can fix its own templates instead of handing you a broken site.

See Building with Claude for setup.

Add the schema comment to the top of your archival_objects.toml:

#:schema https://archival.dev/schemas/archival_objects.schema.json

Your editor will complete field types, flag a definition that can't build, and explain the reserved keys inline. The same schemas are in the SchemaStore catalog, so most editors pick them up with no comment at all.