sitesmithlisted

# sitesmith A website is not done when the code compiles, and it is not done when the checks pass. The checks are a floor. It is done when it has the fourteen things in [v2/00-done.md](v2/00-done.md), and has been rendered, looked at, measured and corrected. **Read [v2/](v2/README.md). That is the skill.** The pipeline it follows is declared once, in [PIPELINE.json](PIPELINE.json) — which is also what the command vocabulary and the provider packages are generated from. `references/` is the upstream material this descends from, kept for attribution and not read during a build. **Progressive disclosure is mandatory.** What is always in context is this file, the sixty core rules, and one mode file. Everything else is read at its step and put down again. A routine task must never pull the whole rule set or the 1.4 MB of data into context. --- ## 1. Route Two questions, in this order. **Which mode is this page?** Route per page, not per project — a shop's About page is marketing and its order admin is product UI. One design system across all of them. | Mode | The visitor is | Open | | --- | --- | --- | | **M** Marketing | Deciding whether to care. Company sites, services, launches, portfolios, editorial. | [v2/modes/marketing.md](v2/modes/marketing.md) | | **E** E-commerce | Deciding whether to buy, and from whom. Listings, product pages, checkout. | [v2/modes/ecommerce.md](v2/modes/ecommerce.md) | | **P** Product UI | Already committed, and now working. Dashboards, admin,