Roadmap: what is missing, what comes next

Missing today

• Proof from more than one site. The proof page shows one.
• A standard way to count enquiries. Analytics is optional today: the interview offers a cookieless tool, and nothing sets up a conversion to count.
• A lock on publishing. The tests run by default, but a person can still publish a build that failed. The test gate says where.
• A one-line install. Today you clone the repository and run a script.
• Import. There is no route for bringing an existing site in.
• Forms. A site can have one small server function for a form, but there is no dedicated forms skill and no bundled test that submits one.
• Tested support beyond Claude Code. The guides for Codex and Antigravity exist; neither has been tested from start to finish.

Next, in this order

1. A standard way to count enquiries. Cookieless analytics with one conversion event set up by default, so arrivals can be tied to enquiries.
2. Checks that go deeper and cannot be skipped. A check for leftover template slots in the finished pages. Required checks on the publishing branch, so a failing build cannot go live. Deeper checks on the message of a page.
3. An easier install. A plugin package, a listing where people look for skills, and one command that starts a project.
4. Import of an existing site. Bring a site you already have under the same tests.
5. Forms. A dedicated skill for contact forms, with a bundled test that submits one.

Later, perhaps

• A pipeline for regular posts.
• Starting from a screenshot or a design file.
• A few worked example sites to look at.

Out, on purpose

• A visual editor. You work with your assistant in plain language.
• Shops and accounts. An app builder serves you better there.
• Hosting by us. Your site stays on hosting you control.

If one of these is what you need, the alternatives page says which kind of tool fits. To argue for a change of order, open an issue on GitHub.