One compiler, a growing vocabulary
Clodsite already carries a focused site from an approved plan to a custom domain, with goal-oriented components, metadata, sharing previews, and small commerce in place. What's next deepens the message and the way people refine it — without ever giving up the small, reviewable contract at the center.
Recently shipped
- Goal-oriented components — heroes, feature grids, key facts, quotes, calls to action, and resource cards
- FAQ/disclosure sections for common questions
- A warm editorial theme, alongside minimal, professional, and bold
- Small-commerce — Stripe checkout, fulfillment, and personalized products
- Metadata, sharing previews, structured data, and response headers
- Agent-facing documentation for both site authoring and tool development
1. Grow the vocabulary without growing the language
The next architectural step keeps the core language small and lets a site extend it by selecting versioned component libraries — so an agent only ever reasons about the vocabulary a given site actually needs. Today's built-in components become the standard library, selected automatically; you reach for more only when you need it.
This first step is deliberately local: libraries resolved from your own project, with no remote code. A shared registry, a marketplace, and paid libraries are open questions for later — not commitments, and gated on a real trust model.
2. Make refinement a first-class workflow
A governed preview-and-revise loop will accept feedback from conversation, screenshots, and specific communication goals. It will propose a reviewable build-plan diff and rebuild only after approval.
3. Make routing honest and intentional
Generated not-found pages will let unknown URLs return a real 404. Explicit redirects will preserve useful old links with deliberate 301 responses instead of sending every unknown path to the home page.
Further out
Clodsite is also exploring generalized Cloudflare Pages Functions and secrets, authenticated MCP over HTTP, and installable packaging.
Bigger ambitions — managed multi-customer hosting, agency and autonomous-agent workflows — depend first on real isolation between tenants. We name that honestly and build it before the futures that need it.
The long arc is a portable website format with many authoring experiences and one dependable compiler.
Contributing to Clodsite
Clodsite is also built to be worked on by agents. The project now separates current operating guidance from historical design records, so a development agent can tell which documents define today's behavior and which explain how the project got here.
Agents changing Clodsite should start with docs/agent-development.md. It maps the source tree, names the compiler boundary, lists the verification commands, and explains when to update current docs, roadmap items, or dated design records.
Agents using Clodsite to build sites should start somewhere else: docs/agent-authoring.md and components/CATALOG.md. That split matters. The public site contract and the tool-development workflow are related, but they are not the same job.