The agent builds it
Most CMSs are built for a person clicking. Shio is built for a coding agent:
Claude Code, Cursor, or anything that speaks MCP, and the curator stays in the loop
as the curator, not the typist. The instance describes itself in one call
(a manifest of every capability plus a context pack of the site as it stands), so an
agent does not spend a session exploring before it can write. Content is addressed by
path, not by id: post:<site>/<friendly-url>, folder:<site>/<name-chain>,
site:<name>, and a site's home page is post:<site>/.
Writes are a small, deterministic vocabulary. A batch is transactional, a
desired-state document is planned before it is applied (--dry-run first, always),
serialization is byte-identical run to run, and a 4xx never just says no: it carries
fix, allowed, didYouMean and an example. For authoring, files beat APIs,
project a site to disk and an agent's cheapest tools (Edit, Write, Grep) work
on it directly, with a per-field three-way merge so a curator's console edit is never
overwritten by a push. When a change lands, the agent verifies it without asking a
anyone to look: content lint, route proof, render digest.
MCP Server
Drive Viglet Shio from Claude Code, Cursor or any MCP client: POST /mcp, twelve tools, six resources, four prompts, and the Claude Code plugin.
The Agent Surface (REST)
/api/v2/agent/**: one call to discover the instance, addressed reads, an atomic op vocabulary, desired-state apply, and a verification loop that needs nobody to look.
Content as Files
Project a Shio site to disk as Markdown and edit it with ordinary tools: the tree layout, sidecars, assets, and the three-way merge that protects a curator's edit.
The shio CLI
@viglet/shio, the shio command: scaffold a site, sync content and post types both ways, verify, replicate an existing site, and gate a pipeline on drift.
Blueprints
Appliable starting points: a blueprint installs a content model, a folder tree, sample pages and a front end in one call, with a plan you can read first.
Pages, Layouts & Regions
How Viglet Shio composes a page: Handlebars templates over Page Layouts, Regions and Themes, the helper set, sections, preview and public delivery.
Design Tokens (DTCG)
Viglet Shio reads W3C Design Tokens (DTCG) on a Theme and compiles them to CSS custom properties, so a restyle is a reviewable field edit instead of a stylesheet rewrite.
Replication
Point Shio at a site that already exists: capture it, propose what could become editable content, convert it, and serve it, in fidelity or authorable mode.
Token Economy
What a call to Viglet Shio costs in tokens, the budgets enforced in CI, how to spend less, and the benchmark the project holds itself to.