create-ailk 0.8.0 → 0.10.0

package/site-templates/minimalism-site/TEMPLATE-MANIFEST.md

@@ -1,458 +0,0 @@
-# Template manifest — `minimalism-site`
-
-> The second Pro template (#5589) — a reports-first site whose home is a **nine-slide scroll-snap deck**, shaped after the reference captured in `docs/research/bondcap-capture/`. Structure and design are the reference; **the copy is not** — every line here is placeholder English of the same shape and length. Generated file: the regions between `<!-- generated:begin <id> -->` and `<!-- generated:end -->` are produced by `scripts/build-template-manifest.mjs --template minimalism-site` from the composed layer stack (this tree → its required modules → `_base` → the always-copied overlay), each roster row's MDX `sections[]`, and `component-catalog.json`. Everything outside the markers is written by hand.
-
-| Field                  | Value                                                                                                                                                                            |
-| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Template               | `minimalism-site`                                                                                                                                                                |
-| Level                  | Pro (derived from `requires` — `scheduling` and `signal-collectors` are paid; never declared)                                                                                    |
-| `requires`             | `[marketing, scheduling, signal-collectors]` — **no `docs-blog`**, which is what makes this a sibling of `marketing-site` rather than `marketing-site` plus a module (#5618 D2)  |
-| `extends`              | `_base` — lineage only, never level                                                                                                                                              |
-| Delivery               | licence-checked module bundle (#5441); never in the Free tarball                                                                                                                 |
-| Sample content posture | every sample report, service and flow in the demo is **public** and **placeholder**                                                                                              |
-| Reference              | `docs/research/bondcap-capture/{home.behavior.md,home.snapshot.yml,repro/}` — panel shapes and the rescued section reproduction. No reference copy and no reference asset ships. |
-
-## 1. Chrome
-
-This template's chrome is the `minimalism` design's (#6638), not a `layout` block of its own; it was the first non-default chrome (#5612). The deck is the reason: a nine-panel scroll-snap home with a revealed brand mark has no room for a nav row, an announcement bar or a four-column footer.
-
-| Piece               | Value                                                                                                                                                                                                         |
-| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Nav                 | `mark-only` — **no nav items render**. The revealed brand mark plus the right-hand controls are the only header chrome. Every page a reader reaches, they reach from a slide action or the footer bottom bar. |
-| Footer              | `centered` — the slide-9 bottom bar: Privacy · Terms · FAQ, the social row, the theme toggle and the locale switcher.                                                                                         |
-| Announcement banner | off. The cookie-consent banner is unaffected — it is not an announcement.                                                                                                                                     |
-| Home                | `deck` — the locale-root route mounts `MarketingShell` with `snap="mandatory"` + `deckHero` (#5612 D3 / #5426 D7). Every other route renders normally.                                                        |
-
-### Layout knobs (#5612)
-
-The `minimalism` design's knobs (#6638) — the template declares no `layout` block of its own; `design: minimalism` supplies these through `DESIGN_LAYOUTS`, resolved with `resolveSiteChrome(layout, design)`, defaults filled. Any shape that names this design gets the same chrome.
-
-<!-- generated:begin layout -->
-
-| Knob                 | Value       |
-| -------------------- | ----------- |
-| `nav`                | `mark-only` |
-| `footer`             | `centered`  |
-| `announcementBanner` | `false`     |
-| `home`               | `deck`      |
-
-<!-- generated:end -->
-
-### Theme (locked)
-
-The template's `theme:` block as `_site.mdx` declares it — the shape knobs and the colour overlay. Generated, so a change to a locked template's look is a red `manifest:check`, not a silent drift (starter-template contract R3.5).
-
-<!-- generated:begin theme -->
-
-| Setting                  | Value      |
-| ------------------------ | ---------- |
-| `corners`                | `square`   |
-| `eyebrowCase`            | `sentence` |
-| `placeholders`           | `fill`     |
-| `checkmarks`             | `plain`    |
-| `colors.light.bg`        | `#ffffff`  |
-| `colors.light.bgMuted`   | `#ffffff`  |
-| `colors.light.surface`   | `#ffffff`  |
-| `colors.light.border`    | `#000000`  |
-| `colors.light.text`      | `#000000`  |
-| `colors.light.textMuted` | `#333333`  |
-| `colors.light.primary`   | `#000000`  |
-| `colors.light.primaryFg` | `#ffffff`  |
-| `colors.light.accent`    | `#000000`  |
-| `colors.dark.bg`         | `#000000`  |
-| `colors.dark.bgMuted`    | `#000000`  |
-| `colors.dark.surface`    | `#000000`  |
-| `colors.dark.border`     | `#ffffff`  |
-| `colors.dark.text`       | `#ffffff`  |
-| `colors.dark.textMuted`  | `#cccccc`  |
-| `colors.dark.primary`    | `#ffffff`  |
-| `colors.dark.primaryFg`  | `#000000`  |
-| `colors.dark.accent`     | `#ffffff`  |
-
-<!-- generated:end -->
-
-## 2. The home deck — nine slides
-
-`layout.home: "deck"` makes every direct section child of `home.mdx` one full-viewport snap target, in order. The mark is hidden on slide 1 (the deck-hero landing state) and revealed from slide 2 on.
-
-| #   | Slide             | Section                                                        | Ground                   | Action                                                                                                    |
-| --- | ----------------- | -------------------------------------------------------------- | ------------------------ | --------------------------------------------------------------------------------------------------------- |
-| 1   | Landing           | `hero` (`backdrop`)                                            | gradient band + backdrop | `{Primary CTA} →` → `/reports`, centered; 44px scroll cue. _No mark — but see the Nav-wiring note below._ |
-| 2   | Tagline           | `content-block` (`align: center`, `fill: viewport`)            | light                    | — (_the mark reveals here once #5697 lands_)                                                              |
-| 3   | Our community     | `logoCloud` (`actions`)                                        | light                    | `Refer someone →` → `/referral`, bottom-centered at 44px                                                  |
-| 4   | Reports headline  | `content-block` (`align: center`, `fill: viewport`)            | light                    | —                                                                                                         |
-| 5   | Special reports   | `reports-list` (`list`, `tone: on-dark`)                       | dark (`gradient-dark`)   | four dated titles → `/reports/<slug>`                                                                     |
-| 6   | Favorites         | `reports-list` (`list`, `tone: on-dark`)                       | dark (`gradient-dark`)   | year-only titles → `/reports/<slug>`                                                                      |
-| 7   | Services headline | `content-block` (`align: center`, `fill: viewport`)            | light                    | `Hire me →` → `/meet`                                                                                     |
-| 8   | Partners          | `team` (`with-large-images`, `hoverReveal`, `phoneColumns: 2`) | light                    | `About us →` → `/about`, bottom-centered at 44px                                                          |
-| 9   | Closing           | `cta` (`minimal`)                                              | light                    | `Contact me →` → `/contact`, centered                                                                     |
-
-### How the deck honours the site principle
-
-Sam's site principle for this template — _every slide's action sits at the bottom, centered, at 44px or larger; grids are 2-up on a phone_ — is held by bounded section props, never by a `className` override or hand-rolled markup in a template (`.claude/rules/frontend.md` § Chrome Composes Blocks). #5691 landed the seven the deck was missing and this tree sets all seven; the composition of every slide is unchanged from the table above.
-
-| Prop                                        | Owner                                    | Slides that set it | What it does here                                                                                                                                                                                      |
-| ------------------------------------------- | ---------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `hero.backdrop`                             | `packages/ui/src/sections/Hero.tsx`      | 1                  | paints `assets/hero-backdrop.svg` (installed at `/hero-backdrop.svg`) full-bleed behind the copy. A distinct slot from `image`, which counts as a stacked reveal — so the 44px scroll cue survives it. |
-| `content-block.align`                       | `.../ContentBlock.tsx`                   | 2, 4, 7            | centers the headline cluster, the body and the CTA row, through `SectionHeader`'s own `align` prop                                                                                                     |
-| `content-block.fill`                        | `.../ContentBlock.tsx`                   | 2, 4, 7            | the copy centers in the middle of the full-viewport snap panel instead of sitting at its top                                                                                                           |
-| `logoCloud.actions`                         | `.../LogoCloud.tsx`                      | 3                  | one bottom-centered action at the 44px floor beneath the strip (the #5622 `stair-steps` footer placement)                                                                                              |
-| `team.actions`                              | `.../Team.tsx`                           | 8                  | the same row beneath the member wall                                                                                                                                                                   |
-| `'gradient-dark'` on `SectionSurfaceSchema` | `packages/validation/…/page-sections.ts` | 5, 6               | the dark ground `tone: "on-dark"` (#5562, shipped **for** this template) was always meant to sit on. `SectionFrameBand` has carried the band itself since 2026-08-29.                                  |
-| `CardGrid.phoneColumns`                     | `packages/ui/src/panels/CardGrid.tsx`    | 8                  | the six-tile wall is two-up at 390 rather than overflowing the snap panel one tile at a time                                                                                                           |
-
-Two notes on the last row. `CardGrid`'s 1-up-below-`md` ramp stays the system-wide default — the recorded #2803 fix, since an `sm` step made every phone 2-up-cramped — and `phoneColumns: 2` is the opt-in Sam disposed on 2026-09-16 for this deck and the client decks built from it; nothing else in the repo sets it. And slide 8 is the only deck slide that reaches `CardGrid` at all: slide 3's logo strip is a reflowing flex row with no column count, and `reports-list`'s `list` variant has no grid — so one knob on one slide satisfies the whole principle.
-
-### The Nav wiring — #5697, and not this template's to fix
-
-The deck's brand-mark story is the other half of `layout.home: "deck"`, and it is not wired. `apps/web/app/[locale]/layout.tsx` forwards `snap` and `deckHero` to `MarketingShell` but forwards neither `sticky` nor `deckMorph` to `Nav`, so today the lockup is pushed out of view by the first snap and the morph hooks the #5426 CSS keys off are never in the document. A template declares layout; it cannot forward a prop in an app's layout file. Filed as **#5697**, with both states photographed (`home-*` vs `home-wired-*` under `docs/design-evidence/5589/`).
-
-One thing #5697 also settles: #5589's text says slide 1 shows "no visible logo", while what #5426 D4 ships is a cross-fade — wordmark on the landing slide, mark from slide 2 on. The mark's absence from slide 1 holds either way.
-
-## 3. Pages
-
-One `page=<route>` region per roster row, generated from the seed file the composed layer stack lands for that route.
-
-`/`:
-
-<!-- generated:begin page=/ -->
-
-| #   | Section                                                            | Component      | Copy (first line)                                                      |
-| --- | ------------------------------------------------------------------ | -------------- | ---------------------------------------------------------------------- |
-| 1   | `hero` (centered · surface=gradient-brand · fill=viewport · 1 CTA) | `Hero`         | Your Company                                                           |
-| 2   | `content-block` (narrow · align=center · fill=viewport)            | `ContentBlock` | A working partnership with the teams building {what your market needs… |
-| 3   | `logoCloud` (layout=grid · logos ×3 · 1 CTA)                       | `LogoCloud`    | Our community                                                          |
-| 4   | `content-block` (narrow · align=center · fill=viewport)            | `ContentBlock` | Research on {your field}, and on where the next decade of it is going  |
-| 5   | `reports-list` (list · surface=gradient-dark · tone=on-dark)       | `ReportsList`  | Special reports                                                        |
-| 6   | `reports-list` (list · surface=gradient-dark · tone=on-dark)       | `ReportsList`  | Favorites                                                              |
-| 7   | `content-block` (narrow · align=center · fill=viewport · 1 CTA)    | `ContentBlock` | Trusted work for the people who carry {the outcome you deliver}        |
-| 8   | `team` (with-large-images · members ×6 · 1 CTA)                    | `Team`         | Partners                                                               |
-| 9   | `cta` (minimal · 1 CTA)                                            | `CTA`          | Your Company                                                           |
-
-<!-- generated:end -->
-
-`/reports`:
-
-<!-- generated:begin page=/reports -->
-
-| #   | Section                               | Component     | Copy (first line)                           |
-| --- | ------------------------------------- | ------------- | ------------------------------------------- |
-| 1   | `hero` (centered · eyebrow "Reports") | `Hero`        | Research on {your field}, published in full |
-| 2   | `reports-list` (cards)                | `ReportsList` |                                             |
-| 3   | `cta` (minimal · 1 CTA)               | `CTA`         | Want the next one as it lands?              |
-
-<!-- generated:end -->
-
-`/about`:
-
-<!-- generated:begin page=/about -->
-
-| #   | Section                                    | Component      | Copy (first line)                                                      |
-| --- | ------------------------------------------ | -------------- | ---------------------------------------------------------------------- |
-| 1   | `content-block` (narrow · eyebrow "About") | `ContentBlock` | We work with a small number of {the people you serve}, for a long time |
-| 2   | `team` (with-large-images · members ×6)    | `Team`         | Partners                                                               |
-| 3   | `cta` (minimal · 2 CTAs)                   | `CTA`          | Work with us                                                           |
-
-<!-- generated:end -->
-
-`/services`:
-
-<!-- generated:begin page=/services -->
-
-| #   | Section                                | Component | Copy (first line)           |
-| --- | -------------------------------------- | --------- | --------------------------- |
-| 1   | `hero` (centered · eyebrow "Services") | `Hero`    | Three ways to work together |
-| 2   | `items` (columns=3 · items ×3)         | `Items`   | Engagements                 |
-| 3   | `cta` (minimal · 1 CTA)                | `CTA`     | Not sure which one?         |
-
-<!-- generated:end -->
-
-`/services/[slug]`:
-
-<!-- generated:begin page=/services/[slug] -->
-
-_Detail route over `content/en/Service/` — 3 seed pages: `first-engagement.mdx`, `second-engagement.mdx`, `third-engagement.mdx`._
-<!-- generated:end -->
-
-`/contact`:
-
-<!-- generated:begin page=/contact -->
-
-| #   | Section                               | Component | Copy (first line)             |
-| --- | ------------------------------------- | --------- | ----------------------------- |
-| 1   | `hero` (centered · eyebrow "Contact") | `Hero`    | Say what you are trying to do |
-| 2   | `cta` (minimal · 1 CTA)               | `CTA`     | Would a call be faster?       |
-
-<!-- generated:end -->
-
-`/referral`:
-
-<!-- generated:begin page=/referral -->
-
-| #   | Section                                                        | Component    | Copy (first line)                        |
-| --- | -------------------------------------------------------------- | ------------ | ---------------------------------------- |
-| 1   | `hero` (centered · eyebrow "Referrals" · checklist ×3 · 1 CTA) | `Hero`       | Know someone who should be on this list? |
-| 2   | `stair-steps` (tiles ×3)                                       | `StairSteps` | Three steps, about a minute              |
-| 3   | `cta` (minimal · 1 CTA)                                        | `CTA`        | Make an introduction                     |
-
-<!-- generated:end -->
-
-`/faq`:
-
-<!-- generated:begin page=/faq -->
-
-| #   | Section                                                       | Component | Copy (first line)      |
-| --- | ------------------------------------------------------------- | --------- | ---------------------- |
-| 1   | `faq` (centered · items ×5 · supportLink · initialOpen first) | `FAQ`     | Questions              |
-| 2   | `cta` (minimal · 1 CTA)                                       | `CTA`     | Still have a question? |
-
-<!-- generated:end -->
-
-`/glossary`, `/newsletter` (base-layer seeds every starter carries, #6658 D5):
-
-<!-- generated:begin page=/glossary -->
-
-| #   | Section                             | Component       | Copy (first line)                            |
-| --- | ----------------------------------- | --------------- | -------------------------------------------- |
-| 1   | `hero` (eyebrow "Glossary" · 1 CTA) | `Hero`          | {Glossary: the terms your customers look up} |
-| 2   | `glossary-index` (columns)          | `GlossaryIndex` | {Terms, A to Z}                              |
-
-<!-- generated:end -->
-
-<!-- generated:begin page=/newsletter -->
-
-| #   | Section                               | Component    | Copy (first line)                                |
-| --- | ------------------------------------- | ------------ | ------------------------------------------------ |
-| 1   | `hero` (eyebrow "Newsletter" · 1 CTA) | `Hero`       | {Newsletter: what subscribers get and how often} |
-| 2   | `newsletter`                          | `Newsletter` | Subscribe                                        |
-| 3   | `faq` (expanded · items ×3)           | `FAQ`        | FAQs                                             |
-
-<!-- generated:end -->
-
-`/book-a-call` (this template's own override of the base seed — the call to action opens the `/meet` booker the scheduling module supplies, not `/contact`):
-
-<!-- generated:begin page=/book-a-call -->
-
-| #   | Section                                | Component | Copy (first line)                          |
-| --- | -------------------------------------- | --------- | ------------------------------------------ |
-| 1   | `hero` (eyebrow "Book a call" · 1 CTA) | `Hero`    | {Book a call: what a visitor gets from it} |
-| 2   | `items` (columns=3 · items ×3)         | `Items`   | What happens on the call?                  |
-
-<!-- generated:end -->
-
-`/privacy`:
-
-<!-- generated:begin page=/privacy -->
-
-| #   | Section                             | Component         | Copy (first line) |
-| --- | ----------------------------------- | ----------------- | ----------------- |
-| 1   | `document-chassis` (layout=article) | `DocumentChassis` | Privacy Policy    |
-
-<!-- generated:end -->
-
-`/terms`:
-
-<!-- generated:begin page=/terms -->
-
-| #   | Section                             | Component         | Copy (first line) |
-| --- | ----------------------------------- | ----------------- | ----------------- |
-| 1   | `document-chassis` (layout=article) | `DocumentChassis` | Terms of Service  |
-
-<!-- generated:end -->
-
-`/purchase-policy`:
-
-<!-- generated:begin page=/purchase-policy -->
-
-| #   | Section                             | Component         | Copy (first line) |
-| --- | ----------------------------------- | ----------------- | ----------------- |
-| 1   | `document-chassis` (layout=article) | `DocumentChassis` | Purchase Policy   |
-
-<!-- generated:end -->
-
-`/meet`:
-
-<!-- generated:begin page=/meet -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/meet/[slug]`:
-
-<!-- generated:begin page=/meet/[slug] -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/meet/confirmed`:
-
-<!-- generated:begin page=/meet/confirmed -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/appointments`:
-
-<!-- generated:begin page=/appointments -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/flows/[slug]`:
-
-<!-- generated:begin page=/flows/[slug] -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/flows/[slug]/start`:
-
-<!-- generated:begin page=/flows/[slug]/start -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/flows/[slug]/results/[payload]`:
-
-<!-- generated:begin page=/flows/[slug]/results/[payload] -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/reports/[slug]`:
-
-<!-- generated:begin page=/reports/[slug] -->
-
-_Detail route over `content/en/ReportPage/` — 4 seed pages: `annual-letter-2024.mdx`, `field-notes-2023.mdx`, `platform-shift-2025.mdx`, `state-of-the-market-2026.mdx`._
-<!-- generated:end -->
-
-The signal-collectors bundle's sample pages — the project listing, two projects and three thank-you pages — are this template's own roster rows (#6646), so the roster lists every page the scaffold installs.
-
-<!-- generated:begin page=/projects -->
-
-| #   | Section                        | Component | Copy (first line)          |
-| --- | ------------------------------ | --------- | -------------------------- |
-| 1   | `hero` (centered)              | `Hero`    | Projects                   |
-| 2   | `items` (columns=2 · items ×2) | `Items`   | Selected engagements       |
-| 3   | `cta` (2 CTAs)                 | `CTA`     | Have a project like these? |
-
-<!-- generated:end -->
-
-<!-- generated:begin page=/projects/[slug] -->
-
-_Detail route over `content/en/Project/` — 2 seed pages: `fit-check-funnel.mdx`, `launch-site-in-fourteen-days.mdx`._
-<!-- generated:end -->
-
-<!-- generated:begin page=/thanks/[slug] -->
-
-_Detail route over `content/en/ThankYouPage/` — 3 seed pages: `apply.mdx`, `contact.mdx`, `newsletter.mdx`._
-<!-- generated:end -->
-
-### 3a. Differences from the organization-service shape roster
-
-This template is the `organization-service` shape (`shape: organization-service`) rendered in the `minimalism` design (`design: minimalism`). Since #6757 that shape carries its own standard roster (fifteen rows: `HomePage`, `AboutPage`, `ServicesList`, `Service`, `ContactPage`, `FAQPage`, `GlossaryList`, `NewsletterSignup`, `BookCall`, `PrivacyPage`, `TermsPage`, `PurchasePolicyPage`, `BlogList`, `PortfolioList`, `PortfolioItem`) — its own deviations from the raw `derive-roster.py` derivation are recorded in `site-templates/shapes/organization-service/TEMPLATE-MANIFEST.md` § 3a, not repeated here. This template's differences are additions and drops from THAT roster only:
-
-| Row dropped                       | Why                                                                                                                                                                                                         |
-| --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `PortfolioList` · `PortfolioItem` | the reports are the proof, not a portfolio (§ 2)                                                                                                                                                            |
-| `BlogList`                        | the `/blog` teaser upsells Pro and Fumadocs; a Pro alias does not carry an upsell to its own level (`marketing-site` and `saas-product` already drop the same row, #6753 D4, for the same reason of degree) |
-
-| Row added                                                                                   | Why                                                                                                                                                                        |
-| ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `/reports`                                                                                  | the site is reports-first: the deck's landing CTA and slides 5–6 lead here, and it indexes the `signal-collectors` reader at `/reports/<slug>` (§ 2)                       |
-| `/referral`                                                                                 | the referral magnet — the pitch and what a referrer gets, opening the `referral` flow (§ 6); slide 3's action leads here. Both rows are `LandingPage` slugs, not new types |
-| the three signal-collectors sample rows (`/projects`, `/projects/[slug]`, `/thanks/[slug]`) | the module's own sample content this template declares as its own rows (#6646)                                                                                             |
-
-Every kept row of the shape roster (`HomePage`, `AboutPage`, `ServicesList`, `Service`, `ContactPage`, `FAQPage`, `GlossaryList`, `NewsletterSignup`, `BookCall`, `PrivacyPage`, `TermsPage`, `PurchasePolicyPage`) is unchanged: this template's own `/about`, `/contact` and `/book-a-call` seeds override the shared ones (its `/book-a-call` seed points at the `/meet` booker), and the rest ride the shared layers exactly as the shape roster declares them.
-
-## 4. Roster, as the registry declares it
-
-`minimalism-site` composes the `organization-service` shape roster plus the § 3a differences: the deck replaces the document-scroll home, and `/how-it-works`, the product page (`/software/product`), `/pricing` and `/sign-in` are not pages this site has. The roster is what the template IS, so an unrostered page has neither a route directory nor its seed: `scaffold()` installs a `_base` or overlay seed only for a row that names it (#6646), so `content/en/Pricing/pricing.mdx` does not land. The merged roster, as the registry composes it:
-
-<!-- generated:begin roster -->
-
-```
-minimalism-site:
-  requires: [marketing, scheduling, signal-collectors]
-  categories: [real-estate, technology, legal]
-  shape: organization-service
-  design: minimalism
-  roster:
-    - { route: "/",                               kind: page, content: ["content/en/HomePage/home.mdx"] }
-    - { route: "/reports",                        kind: page, content: ["content/en/LandingPage/reports.mdx"] }
-    - { route: "/about",                          kind: page, content: ["content/en/AboutPage/about.mdx"] }
-    - { route: "/services",                       kind: page, content: ["content/en/ServicesList/services.mdx"] }
-    - { route: "/services/[slug]",                kind: page, contentDir: "content/en/Service" }
-    - { route: "/contact",                        kind: page, content: ["content/en/ContactPage/contact.mdx"] }
-    - { route: "/referral",                       kind: page, content: ["content/en/LandingPage/referral.mdx"] }
-    - { route: "/faq",                            kind: page, content: ["content/en/FAQPage/faq.mdx"] }
-    - { route: "/glossary",                       kind: page, content: ["content/en/GlossaryList/glossary.mdx"] }
-    - { route: "/newsletter",                     kind: page, content: ["content/en/NewsletterSignup/newsletter.mdx"] }
-    - { route: "/book-a-call",                    kind: page, content: ["content/en/BookCall/book-call.mdx"] }
-    - { route: "/privacy",                        kind: page, content: ["content/en/PrivacyPage/privacy.mdx"] }
-    - { route: "/terms",                          kind: page, content: ["content/en/TermsPage/terms.mdx"] }
-    - { route: "/purchase-policy",                kind: page, content: ["content/en/PurchasePolicyPage/purchase-policy.mdx"] }
-    - { route: "/projects",                       kind: page, content: ["content/en/ProjectsList/projects.mdx"] }
-    - { route: "/projects/[slug]",                kind: page, contentDir: "content/en/Project" }
-    - { route: "/thanks/[slug]",                  kind: page, contentDir: "content/en/ThankYouPage" }
-    - { route: "/meet",                           kind: route }
-    - { route: "/meet/[slug]",                    kind: route }
-    - { route: "/meet/confirmed",                 kind: route }
-    - { route: "/appointments",                   kind: route }
-    - { route: "/flows/[slug]",                   kind: route }
-    - { route: "/flows/[slug]/start",             kind: route }
-    - { route: "/flows/[slug]/results/[payload]", kind: route }
-    - { route: "/reports/[slug]",                 kind: page, contentDir: "content/en/ReportPage" }
-```
-
-<!-- generated:end -->
-
-By source:
-
-```
-template:           / · /reports · /about · /services · /services/<slug> · /contact
-                    /referral · /faq · /privacy · /terms
-scheduling:         /meet · /meet/<slug> · /meet/confirmed
-signal-collectors:  /flows/<slug> · /flows/<slug>/start · /flows/<slug>/results/<payload>
-                    /reports/<slug>                                    (#5562)
-```
-
-`/reports` and `/referral` carry no `GATEABLE_SURFACES` entry and need none: both are single-segment `LandingPage` slugs served by the generic `[slug]` route (#5469 D2), the same mechanism Free's `/how-it-works` uses. The three module-less surfaces this roster enables are `privacy`, `services` and `terms`.
-
-## 5. Renaming `/about`
-
-Many sites want this page at `/partners`, `/team`, `/family` or `/company`. That is a ROUTE rename in the customer's scaffold, never a content move and never something the template does for them — `AboutPage` is a content type in the schema registry, not a URL.
-
-1. Keep `content/en/AboutPage/`.
-2. `git mv "apps/web/app/[locale]/about" "apps/web/app/[locale]/partners"`.
-3. Update the one footer label that names it (`messages/<locale>.json`).
-
-Once #5572's routes map ships in the scaffold this collapses to one row: the `/about` row's `route`, plus a `legacyRoutes` entry so the old path 301s. The `postInstall` message says the same thing to the buyer.
-
-## 6. The referral request
-
-`/referral` is the magnet — the pitch and what a referrer gets. Its bottom action opens the REQUEST, which is a `signal-collectors` flow: `flows/referral.flow.json` in this tree installs to `database/flows/referral.flow.json` and is served at `/flows/referral/start` (`InstrumentCapturePage`). One field step (name, email, who and why), then a `message` step that confirms inline.
-
-The issue named the path `/referral/request`. That path has no `ROUTES` row and no route directory, so serving it would mean shipping a `page.tsx` into every scaffold for one template's page — which a template may never do. **The lead's `source` is `flow:referral`**, not the bare `referral`: `flow-engine.ts` composes it as `` `flow:${slug}` `` for every flow, and that is not a template-level knob. Recorded on #5589 for Sam; his call supersedes.
-
-## 7. Component inventory
-
-Every component the roster rows' seed content composes today (generated):
-
-<!-- generated:begin inventory -->
-
-| Tier     | Used by this template                                                                                                                             |
-| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Shell    | `MarketingShell`                                                                                                                                  |
-| Chrome   | `Nav`, `Footer`, `Banner` (+ `BannerConsentIsland`, `BannerDismissIsland`)                                                                        |
-| Sections | `ContentBlock`, `CTA`, `DocumentChassis`, `FAQ`, `GlossaryIndex`, `Hero`, `Items`, `LogoCloud`, `Newsletter`, `ReportsList`, `StairSteps`, `Team` |
-
-<!-- generated:end -->
-
-## 8. Known gaps this manifest depends on
-
-| Gap                                                                 | Issue      |
-| ------------------------------------------------------------------- | ---------- |
-| The deck's Nav wiring (`sticky` + `deckMorph` under `home: "deck"`) | #5697      |
-| `/about` rename as one routes-map row                               | #5572      |
-| The Pro demo host `minimalism-site.ailaunchkit.ai` — provisioning   | #5589 body |

package/site-templates/minimalism-site/ailk-template.json

@@ -1,23 +0,0 @@
-{
-  "name": "minimalism-site",
-  "requires": ["marketing", "scheduling", "signal-collectors"],
-  "extends": "_base",
-  "$comment": "The second Pro template (#5589) — the reports-first, scroll-snap deck site. NOT marketing-site plus a module: requires omits docs-blog, so this template and marketing-site are siblings under _base (#5618 D2), never a lineage. Composed base → modules → template: /privacy and /terms arrive with the _base layer this extends (its unrostered /pricing seed does not install, #6646); /meet, /meet/<slug> and /meet/confirmed with the scheduling bundle; the /flows/* routes, the /reports/<slug> reader route and the sample report PDF at apps/web/public/reports/sample-report.pdf with the signal-collectors bundle; the Free contact/faq/about compositions with the overlay, which this template's own /about, /contact and /faq files then override; the overlay's other seeds (/use-cases, the /software/product page, the /blog teaser) are unrostered here and do not install (#6646). This tree holds ONLY its own compositions, its placeholder copy and its generated placeholder assets. layout (nav mark-only, footer centered, announcementBanner off, home deck) is the minimalism design's, supplied by DESIGN_LAYOUTS from the TEMPLATE_MANIFESTS entry's design field (#6638), not declared here — the code registry is authoritative for a template create-ailk ships, and a block here would be a second authority for one fact. installMap: bundle-relative source -> scaffold-relative destination; the stager reads only installMap/postInstall/patches. Unmapped content/en/** lands at the scaffold root's content/, exactly as marketing-site-free's does.",
-  "installMap": {
-    "provenance.json": ".ailk-template.json",
-    "TEMPLATE-MANIFEST.json": ".ailk-site-manifest.json",
-    "assets/hero-backdrop.svg": "apps/web/public/hero-backdrop.svg",
-    "assets/wordmark-placeholder.svg": "apps/web/public/wordmark-placeholder.svg",
-    "assets/logo-placeholder-1.svg": "apps/web/public/logo-placeholder-1.svg",
-    "assets/logo-placeholder-2.svg": "apps/web/public/logo-placeholder-2.svg",
-    "assets/logo-placeholder-3.svg": "apps/web/public/logo-placeholder-3.svg",
-    "assets/avatar-placeholder-1.svg": "apps/web/public/avatar-placeholder-1.svg",
-    "assets/avatar-placeholder-2.svg": "apps/web/public/avatar-placeholder-2.svg",
-    "assets/avatar-placeholder-3.svg": "apps/web/public/avatar-placeholder-3.svg",
-    "assets/avatar-placeholder-4.svg": "apps/web/public/avatar-placeholder-4.svg",
-    "assets/avatar-placeholder-5.svg": "apps/web/public/avatar-placeholder-5.svg",
-    "assets/avatar-placeholder-6.svg": "apps/web/public/avatar-placeholder-6.svg",
-    "flows/referral.flow.json": "database/flows/referral.flow.json"
-  },
-  "postInstall": "Template minimalism-site installed. The home page is a NINE-SLIDE SCROLL-SNAP DECK (content/en/HomePage/home.mdx): one full-viewport panel per section, the brand mark hidden on slide 1 and revealed from slide 2 on, no nav items, and the footer bottom bar carrying Privacy, Terms, FAQ, the social row, the theme toggle and the locale switcher. Its module pages arrived with their bundles: the booker at /meet from scheduling, the report reader at /reports/<slug> and the flow routes from signal-collectors; /privacy, /terms, /glossary and /newsletter came with the base layer, and /book-a-call is this template's own override of the base seed, its call to action opening the /meet booker. This template adds the deck, /reports, /about, /services (+ three samples), /contact, /faq, /referral, four sample reports and the referral flow at /flows/referral/start. RENAMING /about: many sites want /partners, /team, /family or /company instead. That is a route rename in YOUR scaffold, never a content move - keep content/en/AboutPage/ (AboutPage is a schema type, not a URL), rename the route directory (git mv 'apps/web/app/[locale]/about' 'apps/web/app/[locale]/partners'), and update the one footer label that names it (messages/<locale>.json). Once the routes map ships in the scaffold it is one row: the /about row's route plus a legacyRoutes entry so the old path 301s. EVERY line of copy, all four sample reports, the three logo placeholders, the six portrait placeholders, the wordmark lockup on slide 1 and the hero backdrop are placeholders - replace them before you launch."
-}

package/site-templates/minimalism-site/content/en/AboutPage/about.mdx

@@ -1,110 +0,0 @@
----
-type: "AboutPage"
-slug: "about"
-title: "About"
-description: "The people behind {your company}. Placeholder copy and placeholder portraits — replace both before you launch."
-sections:
-  [
-    {
-      "id": "intro",
-      "type": "content-block",
-      "data":
-        {
-          "variant": "narrow",
-          "eyebrow": "About",
-          "headline": "We work with a small number of {the people you serve}, for a long time",
-          "body": "{Two or three sentences on how the practice started, what it does now, and what it refuses to do. Keep the paragraph short — this page is read standing up.}",
-        },
-    },
-    {
-      "id": "partners",
-      "type": "team",
-      "data":
-        {
-          "headline": "Partners",
-          "variant": "with-large-images",
-          "hoverReveal": true,
-          "largePhotos": true,
-          "members":
-            [
-              {
-                "name": "{Name One}",
-                "role": "{Role}",
-                "bio": "{One line on what this person does here.}",
-                "avatar":
-                  { "src": "/avatar-placeholder-1.svg", "alt": "{Name One}" },
-              },
-              {
-                "name": "{Name Two}",
-                "role": "{Role}",
-                "bio": "{One line on what this person does here.}",
-                "avatar":
-                  { "src": "/avatar-placeholder-2.svg", "alt": "{Name Two}" },
-              },
-              {
-                "name": "{Name Three}",
-                "role": "{Role}",
-                "bio": "{One line on what this person does here.}",
-                "avatar":
-                  { "src": "/avatar-placeholder-3.svg", "alt": "{Name Three}" },
-              },
-              {
-                "name": "{Name Four}",
-                "role": "{Role}",
-                "bio": "{One line on what this person does here.}",
-                "avatar":
-                  { "src": "/avatar-placeholder-4.svg", "alt": "{Name Four}" },
-              },
-              {
-                "name": "{Name Five}",
-                "role": "{Role}",
-                "bio": "{One line on what this person does here.}",
-                "avatar":
-                  { "src": "/avatar-placeholder-5.svg", "alt": "{Name Five}" },
-              },
-              {
-                "name": "{Name Six}",
-                "role": "{Role}",
-                "bio": "{One line on what this person does here.}",
-                "avatar":
-                  { "src": "/avatar-placeholder-6.svg", "alt": "{Name Six}" },
-              },
-            ],
-        },
-    },
-    {
-      "id": "closing",
-      "type": "cta",
-      "data":
-        {
-          "variant": "minimal",
-          "headline": "Work with us",
-          "primaryCta": { "label": "Hire me →", "href": "/meet" },
-          "secondaryCta":
-            {
-              "label": "Contact me →",
-              "href": "/contact",
-              "variant": "outline",
-            },
-        },
-    },
-  ]
----
-
-{/\*
-RENAMING THIS PAGE. A site whose partners page should read `/partners`,
-`/team`, `/family` or `/company` renames it in two moves, both in the
-scaffold, neither of them here:
-
-    1. `git mv content/en/AboutPage content/en/<NewType>` is NOT one of them —
-       `AboutPage` is a content TYPE in the schema registry, not a URL. Keep the
-       directory. Rename the ROUTE:
-       `git mv "apps/web/app/[locale]/about" "apps/web/app/[locale]/partners"`.
-    2. Point the renamed route at the same content and update the one nav/footer
-       label that names it (`apps/web/lib/nav-config.ts`, `messages/<locale>.json`).
-
-Once #5572's routes map lands in the scaffold this collapses to ONE row —
-the `/about` row's `route` (and its `legacyRoutes` entry, so the old path
-301s). Documented, never implemented here: a template declares pages, it does
-not move a customer's routes for them.
-\*/}