Creativity in front. Reliability behind it.

Most AI website tools ask the model to keep making decisions all the way through the build. Clodsite draws a line.

The customer and agent decide what the site should say, how it should be organized, and which supported components express the message. That work produces a human-readable YAML document. Clodsite then executes the approved document without inventing new content or layout.

1. Collaborate

Start wherever the useful information already lives:

• A conversation
• A product brief
• Existing web copy
• Repository documentation
• Images and screenshots
• A hand-written build plan

The agent gathers context, asks questions, proposes structure, and drafts content. This is the right place for interpretation and judgment.

2. Review the contract

The result is $SITES_DIR/<site-name>/build-plan.yaml.

slug: example
name: Example Site
style: bold
pages:
  - id: home
    title: Home
    components:
      - type: prose
        markdown: |
          # A clear message
          The final, reviewable copy lives here.

The plan is ordinary text. Read it, edit it, diff it, commit it, or generate it with another tool. Validation rejects unknown components and malformed configuration before a build begins.

3. Compile the site

The build pipeline is fully scripted:

validate plan
    ↓
write site data
    ↓
apply theme + component styles
    ↓
render page and Function templates
    ↓
build with Eleventy

A valid plan produces the same site without another round of inference. Generated templates and output stay isolated per site.

4. Put it online

Clodsite can preview locally or deploy directly to Cloudflare Pages. It can provision form secrets, configure Turnstile, connect a custom domain, show deployment status, and tear a project down when its job is done.

SITE_NAME=example bash scripts/build-deploy.sh

The pipeline is also callable through MCP, so a designer agent can discover the component vocabulary, submit a build plan, and receive a deployed URL.