A focused vocabulary for clear communication

Clodsite pages are assembled from typed components. Each component owns its schema, template, and styles. Agents choose from the catalog; validators make sure the plan stays inside the supported vocabulary.

This is less flexible than arbitrary HTML by design. Constraints make plans easier to generate, review, test, and render consistently.

The component catalog today

Component Purpose
prose Headings, paragraphs, lists, links, tables, quotes, and code using GitHub Flavored Markdown
media-section One image paired with prose in a constrained responsive layout
gallery A responsive image grid with alt text and optional captions
mailto-form A zero-backend form that opens the visitor's email client
resend-form Server-backed email delivery with validation and optional Turnstile protection

Assets live with each site. Themes and shared infrastructure live with Clodsite. Building one site does not modify another.

The whole site lifecycle

Clodsite does more than emit HTML.

Capability What it provides
Validate A strict, inspectable contract before work begins
Build Script-generated templates and an Eleventy static site
Preview A local site for review before deployment
Deploy A Cloudflare Pages project and production URL
Protect Resend secrets and optional managed Turnstile widgets
Connect Custom-domain association and DNS automation
Observe Local and deployed site status in one view
Remove Explicit teardown of Pages projects and deployment history

Proven on real projects

Clodsite grew out of building small, real websites where the same pattern kept appearing: a little work required interpretation, while most of the build and deployment work should have been repeatable.

Each project expands the vocabulary while keeping the build contract understandable.