Dapper Roadmap

This is the plan for making Dapper the best tool for people who want to build static websites quickly with an AI assistant, and publish them wherever they like.

The idea

Describe the site you want to your AI assistant; Dapper makes it real, keeps it correct, and publishes it wherever you like.

Dapper doesn't contain an AI and never charges for one. It works with the assistant a person already uses (Claude, ChatGPT, Cursor, or anything that speaks MCP or can run a command), and gives that assistant what it needs to do good work safely: clear conventions, guardrails, checks that explain what is wrong, and a fast loop from edit to preview to publish.

Principles

  1. You own everything. A site is plain files: Markdown, HTML, YAML and CSS. No database, no account, no lock-in. Any host that serves files works.
  2. Safe by default. Content is never run as code. AI changes are checked against schemas before they're written, and dapper check must pass before a deploy.
  3. Explain, don't just fail. Every error names the file, says what is wrong, and is available as JSON, so an assistant can fix it without help.
  4. Bring your own AI. Dapper meets assistants where they are: MCP for assistants that support it, AGENTS.md for coding agents, --json for scripts.
  5. Small and durable. Dapper has run since 2002. New features earn their place, and a site built today should still build in ten years.

Who it's for

What a session looks like

  1. Install Dapper in one line (single file, Homebrew or Docker).
  2. dapper init --template business (or a theme from a git URL).
  3. Ask your assistant: "Make this the site for my bakery. Here are our hours, and here's our menu." It reads AGENTS.md (or uses Dapper's MCP tools), writes pages that match the schemas, and runs dapper check.
  4. dapper serve shows the site; the browser reloads as the assistant edits.
  5. dapper deploy publishes only what changed, to S3, GitHub Pages or any host.
  6. Months later: "Post Saturday's event recap with these photos." The assistant knows how, because the project explains itself.

What 1.0 has

Safe content, front matter schemas, data files, pagination, category and tag pages, a sitemap, an Atom feed, SEO and structured data tags, Markdown copies and llms.txt, Pagefind search, dapper check --json, the MCP server, clean output, live reload, the blog starter, and installs as a single file, a Docker image and a Homebrew formula. 1.0 also makes assistants good at Dapper from the first minute, gives people good looking starting points, and makes publishing one command:

What 1.10 adds

Images (sizes, responsive copies, WebP, lazy loading), components in Markdown (callouts, details, galleries, videos, buttons, figures, maps, and components of your own), drafts and scheduled posts, accessibility and SEO checks in dapper check, and dapper import from WordPress, Jekyll, Hugo and Medium.

Next

The biggest gap left is making Dapper easy to hand to an AI assistant: to set up, to see what it changed, and to undo.

Working with AI assistants

Quality and content

Later

Not planned

How releases are made

Each release keeps the bar set by 1.0: every feature has tests that fail without it, the retired markbenson.io site still builds the same, dapper check passes on every starter, the README is updated and its examples are built before they're documented, and CI passes on Perl 5.10 to 5.40, the single file and the Docker image.