Roadmap

Scope discipline

Clodsite v1 does one thing: take a technical user from zero to a live static site in five commands. Every feature request that came up during development was evaluated against that definition. If it didn't belong in v1, it went into the roadmap with a one-line rationale — not silently implemented, not silently dropped. The result is a tool that does its job reliably, with a clear surface area and a clean upgrade path.

v2 and beyond

The following were deferred from v1. For the full rationale on each, see ROADMAP.md.

• Multi-site workspaces — v1 is single-site by design; workspace management adds state complexity that doesn't belong in the MVP
• Installable skill packaging — distributing Clodsite as an installable Superpowers plugin is the right end state, but packaging requires a stable v1 first
• /modify — post-build edits to an existing site; requires a diff-aware build layer
• /teardown — tear down a Pages project and clean local artifacts; low priority until multi-site is real
• Custom domain automation — DNS provisioning via the Cloudflare API; deferred because it requires zone access, which is a broader permission scope than Pages-only
• Free-form interview — unstructured intake that Claude synthesizes into a spec; v1 uses a fixed ten-question form for predictability
• Contact form — submittable form with backend handling; v1 uses mailto: links only
• Ecommerce — out of scope for a static site generator in its first version
• Blog, calendar, and gallery page types — dynamic content patterns that need a data layer or CMS integration