create-ailk 0.6.0 → 0.7.0

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

@@ -14,7 +14,7 @@
 
 ## 1. Chrome
 
-This template is the first to declare a non-default `layout` block (#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.
+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                                                                                                                                                                                                         |
 | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -25,7 +25,7 @@ This template is the first to declare a non-default `layout` block (#5612). The
 
 ### Layout knobs (#5612)
 
-The template's `layout` block — resolved with `resolveSiteChrome`, defaults filled.
+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 -->
 
@@ -38,6 +38,39 @@ The template's `layout` block — resolved with `resolveSiteChrome`, defaults fi
 
 <!-- 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.
@@ -84,17 +117,17 @@ One `page=<route>` region per roster row, generated from the seed file the compo
 
 <!-- generated:begin page=/ -->
 
-| #   | Section                                         | Component      | Copy (first line)                                                      |
-| --- | ----------------------------------------------- | -------------- | ---------------------------------------------------------------------- |
-| 1   | `hero` (centered · 1 CTA)                       | `Hero`         | Your Company                                                           |
-| 2   | `content-block` (narrow)                        | `ContentBlock` | A working partnership with the teams building {what your market needs… |
-| 3   | `logoCloud` (logos ×3 · 1 CTA)                  | `LogoCloud`    | Our community                                                          |
-| 4   | `content-block` (narrow)                        | `ContentBlock` | Research on {your field}, and on where the next decade of it is going  |
-| 5   | `reports-list` (list)                           | `ReportsList`  | Special reports                                                        |
-| 6   | `reports-list` (list)                           | `ReportsList`  | Favorites                                                              |
-| 7   | `content-block` (narrow · 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                                                           |
+| #   | 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 -->
 
@@ -129,7 +162,7 @@ One `page=<route>` region per roster row, generated from the seed file the compo
 | #   | Section                                | Component | Copy (first line)           |
 | --- | -------------------------------------- | --------- | --------------------------- |
 | 1   | `hero` (centered · eyebrow "Services") | `Hero`    | Three ways to work together |
-| 2   | `items` (items ×3)                     | `Items`   | Engagements                 |
+| 2   | `items` (columns=3 · items ×3)         | `Items`   | Engagements                 |
 | 3   | `cta` (minimal · 1 CTA)                | `CTA`     | Not sure which one?         |
 
 <!-- generated:end -->
@@ -138,18 +171,17 @@ One `page=<route>` region per roster row, generated from the seed file the compo
 
 <!-- generated:begin page=/services/[slug] -->
 
-_Code route — no content, no sections._
+_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   | `contact-form` (card · fields ×3)     | `ContactForm` | Name · Email · What are you trying to do? |
-| 3   | `cta` (minimal · 1 CTA)               | `CTA`         | Would a call be faster?                   |
+| #   | 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 -->
 
@@ -176,13 +208,45 @@ _Code route — no content, no sections._
 
 <!-- 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` (eyebrow "PLACEHOLDER — REPLACE BEFORE LAUNCH") | `DocumentChassis` | Privacy Policy    |
+| #   | Section                             | Component         | Copy (first line) |
+| --- | ----------------------------------- | ----------------- | ----------------- |
+| 1   | `document-chassis` (layout=article) | `DocumentChassis` | Privacy Policy    |
 
 <!-- generated:end -->
 
@@ -190,9 +254,19 @@ _Code route — no content, no sections._
 
 <!-- generated:begin page=/terms -->
 
-| #   | Section                                                            | Component         | Copy (first line) |
-| --- | ------------------------------------------------------------------ | ----------------- | ----------------- |
-| 1   | `document-chassis` (eyebrow "PLACEHOLDER — REPLACE BEFORE LAUNCH") | `DocumentChassis` | Terms of Service  |
+| #   | 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 -->
 
@@ -249,12 +323,63 @@ _Code route — no content, no sections._
 
 <!-- generated:begin page=/reports/[slug] -->
 
-_Code route — no content, no sections._
+_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. Deviations from the standard roster (recorded, #6638)
+
+This template is the `organization-service` shape (`shape: organization-service`) rendered in the `minimalism` design (`design: minimalism`). The standard page set for that shape (`derive-roster.py` —
+`entityType=organization · offeringType=services · primaryGoal=generate-leads · scale=global`,
+`mainEntity: Organization`, 33 rows) is the baseline; the design adds no rows of its own —
+the deck home, the mark-only nav and the centered footer are layout, not pages. What this
+roster keeps from the standard set: `HomePage`, `AboutPage`, `ContactPage`, `FAQPage`,
+`PrivacyPage`, `TermsPage`, `ServicesList`, `Service`, and — since #6658, which gives every
+starter these three whatever its shape (`docs/decisions/starter-roster-page-set.md` D4, D7) —
+`GlossaryList`, `NewsletterSignup` and `BookCall` (its `/book-a-call` seed is this template's
+own, pointing at the `/meet` booker).
+
+| 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 |
+
+| Standard row omitted                         | Why                                                                                                          |
+| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
+| `TeamList` · `TeamMember` (entity spine)     | the partners are one `team` slide on the deck and the `/about` page (§ 2, § 5), not a directory              |
+| `CareersList` · `JobPosting` (entity spine)  | not a hiring site; nothing to seed                                                                           |
+| `PartnersList` · `Partner` (entity spine)    | the partner/community strip is a `logoCloud` slide on the deck, not a page                                   |
+| `ProjectsList` · `Project` (offering branch) | the proof is the reports, not a project portfolio                                                            |
+| `Pricing` (offering branch)                  | engagements are booked, not priced on the page; `/pricing` is unrostered, so its seed does not install (§ 4) |
+
+The lead-generation tier (CaseStudies, Testimonials, Clients, UseCases, Events, Downloads) and
+the Resources content system (ResourcesHub, ResourceDetail, HowTo, Whitepaper) are the
+goal-driven default a site prunes; the reports stand in for them here.
+
 ## 4. Roster, as the registry declares it
 
-`minimalism-site` is the one declared template that does not reuse `TEMPLATE_BASE_ROSTER`: the deck replaces the document-scroll home, and `/how-it-works`, `/features`, `/pricing` and `/sign-in` are not pages this site has. `/pricing`'s absence is not a missing file — the `_base` layer still lands `content/en/Pricing/pricing.mdx`; the roster is what the template IS, so an unrostered page simply has no route directory copied. The merged roster, as the registry composes it:
+`minimalism-site` is the one declared template that does not reuse `TEMPLATE_BASE_ROSTER`: 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 -->
 
@@ -262,25 +387,34 @@ _Code route — no content, no sections._
 minimalism-site:
   requires: [marketing, scheduling, signal-collectors]
   categories: [real-estate, technology, legal]
+  shape: organization-service
+  design: minimalism
   roster:
-    - { route: "/",                               content: ["content/en/HomePage/home.mdx"] }
-    - { route: "/reports",                        content: ["content/en/LandingPage/reports.mdx"] }
-    - { route: "/about",                          content: ["content/en/AboutPage/about.mdx"] }
-    - { route: "/services",                       content: ["content/en/ServicesList/services.mdx"] }
-    - { route: "/services/[slug]" }
-    - { route: "/contact",                        content: ["content/en/ContactPage/contact.mdx"] }
-    - { route: "/referral",                       content: ["content/en/LandingPage/referral.mdx"] }
-    - { route: "/faq",                            content: ["content/en/FAQPage/faq.mdx"] }
-    - { route: "/privacy",                        content: ["content/en/PrivacyPage/privacy.mdx"] }
-    - { route: "/terms",                          content: ["content/en/TermsPage/terms.mdx"] }
-    - { route: "/meet" }
-    - { route: "/meet/[slug]" }
-    - { route: "/meet/confirmed" }
-    - { route: "/appointments" }
-    - { route: "/flows/[slug]" }
-    - { route: "/flows/[slug]/start" }
-    - { route: "/flows/[slug]/results/[payload]" }
-    - { route: "/reports/[slug]" }
+    - { 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 -->
@@ -319,11 +453,11 @@ 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 | `ContactForm`, `ContentBlock`, `CTA`, `DocumentChassis`, `FAQ`, `Hero`, `Items`, `LogoCloud`, `ReportsList`, `StairSteps`, `Team` |
+| 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 -->
 

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

@@ -2,9 +2,10 @@
   "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: /pricing (unrostered), /privacy and /terms arrive with the _base layer this extends; /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; /how-it-works, /features, /sign-in and the Free contact/faq/about compositions with the always-copied overlay, which this template's own /about, /contact and /faq files then override. 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 declared on the TEMPLATE_MANIFESTS entry, not here — the code registry is authoritative for a template create-ailk ships, and a duplicate 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.",
+  "$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",
@@ -18,5 +19,5 @@
     "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 and /terms came with the base layer. 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."
+  "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/BookCall/book-call.mdx

@@ -0,0 +1,53 @@
+---
+type: "BookCall"
+slug: "book-call"
+title: "{Book a call: what a visitor gets from it}"
+description: "{One sentence on who the call is for and what they leave with}"
+placeholder: true
+schema:
+  mainEntity:
+    "@type": "Offer"
+    name: "{Your call name}"
+    price: 0
+    priceCurrency: "USD"
+sections:
+  [
+    {
+      "id": "hero",
+      "type": "hero",
+      "data":
+        {
+          "eyebrow": "Book a call",
+          "headline": "{Book a call: what a visitor gets from it}",
+          "subheadline": "{One sentence on who the call is for and what they leave with}",
+          "primaryCta": { "label": "Book a time", "href": "/meet" },
+        },
+    },
+    {
+      "id": "what-happens-on-the-call",
+      "type": "items",
+      "data":
+        {
+          "headline": "What happens on the call?",
+          "columns": 3,
+          "items":
+            [
+              {
+                "title": "{The first thing you cover}",
+                "description": "{One or two sentences on what the visitor learns or decides here}",
+              },
+              {
+                "title": "{The second thing you cover}",
+                "description": "{One or two sentences on what the visitor learns or decides here}",
+              },
+              {
+                "title": "{The next step you agree}",
+                "description": "{One or two sentences on what happens after the call}",
+              },
+            ],
+        },
+    },
+  ]
+---
+
+{/* Rendered from frontmatter `sections[]` by the /book-a-call route. This template carries the scheduling module, so the call to action opens the /meet booker. It overrides the base layer's copy, which points at /contact. The `schema:` Offer is the page's JSON-LD main entity — a free call. Placeholder copy — replace every {brace} with your own words before you launch. */}

package/site-templates/minimalism-site/content/en/ContactPage/contact.mdx

@@ -16,41 +16,6 @@ sections:
           "subheadline": "{One line on what happens after you send this, and how long it takes.}",
         },
     },
-    {
-      "id": "contact-form",
-      "type": "contact-form",
-      "data":
-        {
-          "variant": "card",
-          "source": "contact",
-          "fields":
-            [
-              {
-                "name": "name",
-                "label": "Name",
-                "type": "text",
-                "required": true,
-              },
-              {
-                "name": "email",
-                "label": "Email",
-                "type": "email",
-                "required": true,
-              },
-              {
-                "name": "message",
-                "label": "What are you trying to do?",
-                "type": "textarea",
-                "required": true,
-              },
-            ],
-          "submitLabel": "Send →",
-          "consentText": "I accept the Terms",
-          "consentLink": { "label": "Terms", "href": "/terms" },
-          "successMessage": "Thank you — your message is in. You will hear back within {time amount}.",
-          "action": "/v1/leads/submit",
-        },
-    },
     {
       "id": "closing",
       "type": "cta",
@@ -64,5 +29,6 @@ sections:
   ]
 ---
 
-{/_ The form posts to the site's own API (`/v1/leads/submit`) and confirms
-inline — no redirect, no thank-you page. Placeholder copy. _/}
+{/_ The /contact route mounts the page's one contact surface — the guided
+intake, with its fallback form — which posts to the site's own API
+(`/v1/leads/submit`) and confirms inline. Placeholder copy. _/}

package/site-templates/minimalism-site/content/en/PurchasePolicyPage/purchase-policy.mdx

@@ -0,0 +1,124 @@
+---
+type: "PurchasePolicyPage"
+slug: "purchase-policy"
+title: "Purchase Policy"
+description: "How cancellations, reschedules and refunds work for bookings made on this site. Placeholder policy — replace every section before you launch."
+placeholder: true
+sections:
+  [
+    {
+      "id": "purchase-policy-document",
+      "type": "document-chassis",
+      "data":
+        {
+          "headline": "Purchase Policy",
+          "layout": "article",
+          "updated": "Last updated {Month Day, Year}",
+          "navGroupLabel": "Contents",
+          "sections":
+            [
+              {
+                "id": "cancellation",
+                "heading": "Cancellation",
+                "blocks":
+                  [
+                    {
+                      "kind": "paragraph",
+                      "text": "This page is starter content that shipped with your site. It is not a purchase policy, it makes no commitment on behalf of Your Company, and it is not legal advice. Replace every section with the policy you actually operate, and have someone qualified read it before you publish.",
+                    },
+                    {
+                      "kind": "paragraph",
+                      "text": "This section explains how cancellations and reschedules work for bookings made on this site. The headings are the ones a customer and an agent both look for, so keep them and fill in your own terms.",
+                    },
+                  ],
+                "subsections":
+                  [
+                    {
+                      "id": "notice",
+                      "heading": "How much notice is required",
+                      "blocks":
+                        [
+                          {
+                            "kind": "paragraph",
+                            "text": "State the notice period in hours before the appointment, and say how it is measured. A customer reading at midnight should be able to work out, without arithmetic you have not shown them, whether they are still inside it.",
+                          },
+                        ],
+                    },
+                    {
+                      "id": "how-to-cancel",
+                      "heading": "How to cancel or reschedule",
+                      "blocks":
+                        [
+                          {
+                            "kind": "paragraph",
+                            "text": "Give one route to cancel and one to reschedule, and say whether a reschedule inside the notice period counts as a cancellation. If a booking confirmation carries a self-service link, name it here.",
+                          },
+                        ],
+                    },
+                    {
+                      "id": "fees",
+                      "heading": "Late cancellations and no-shows",
+                      "blocks":
+                        [
+                          {
+                            "kind": "paragraph",
+                            "text": "Say what a late cancellation costs and what a no-show costs, as a figure or a share of the booking, and when each is charged. If you hold a deposit, say what happens to it in each case.",
+                          },
+                        ],
+                    },
+                    {
+                      "id": "our-cancellations",
+                      "heading": "If we cancel",
+                      "blocks":
+                        [
+                          {
+                            "kind": "paragraph",
+                            "text": "Set out what a customer gets if you cancel or move an appointment — a full refund, a rebooking, or both — and how quickly you tell them. A policy that only binds one side reads as one.",
+                          },
+                        ],
+                    },
+                    {
+                      "id": "exceptions",
+                      "heading": "Exceptions",
+                      "blocks":
+                        [
+                          {
+                            "kind": "paragraph",
+                            "text": "Name the circumstances in which you waive a fee — illness, bereavement, severe weather — and say what you need from the customer to apply the waiver. Vague discretion is worse for you than a short written list.",
+                          },
+                        ],
+                    },
+                  ],
+              },
+              {
+                "id": "refunds",
+                "heading": "Refunds",
+                "blocks":
+                  [
+                    {
+                      "kind": "paragraph",
+                      "text": "Say what a customer gets back after a cancellation — the booking price, the deposit, or both, and how long the refund takes to reach the payment method it came from. If you offer store credit or a rebooking instead, describe when each applies.",
+                    },
+                  ],
+                "subsections":
+                  [
+                    {
+                      "id": "questions",
+                      "heading": "Questions about a refund",
+                      "blocks":
+                        [
+                          {
+                            "kind": "paragraph",
+                            "text": "Point to the one place a customer should write, and say roughly how quickly you answer. A policy nobody can ask a question about is a policy that generates disputes.",
+                          },
+                        ],
+                    },
+                  ],
+              },
+            ],
+        },
+    },
+  ]
+---
+
+{/* Rendered from frontmatter `sections[]`; the MDX body is not read by the section-catalog renderer. Service shape (#6646): cancellation and refunds — this template's override of the `_base` product-shape seed. The JSON-LD — a WebPage, wrapping a MerchantReturnPolicy when a returns section is present — is emitted by `buildPurchasePolicyPage` (#6646), not hand-rolled here. */}