create-ailk 0.6.0 → 0.7.0

package/dist/template-manifest.js

@@ -1,5 +1,44 @@
 import { classifyModules } from "./lib/module-tier.js";
 import { MODULE_SLICES, normalizeModules, } from "./module-architecture.js";
+/**
+ * The closed **shape** enum (starter-template contract § The three axes,
+ * operator-disposed 2026-09-24) — `<primary node>-<offering node>` in
+ * schema.org terms, kebab-cased. Declared beside `TemplateManifest`, the same
+ * pattern `ModuleName` uses in `parse-args.ts`: a `readonly [...] as const`
+ * array plus its derived literal-union type, so an unrecognized value fails
+ * type-check rather than a runtime validation.
+ */
+export const STARTER_SHAPES = [
+    "organization-product",
+    "organization-service",
+    "local-business-service",
+    "local-business-product",
+    "person-service",
+];
+/**
+ * The closed **design** enum (same contract section) — the look applied to
+ * any shape; orthogonal to it by construction.
+ */
+export const STARTER_DESIGNS = ["standard", "minimalism"];
+/**
+ * Each design's layout knobs (#6638) — the part of a design that is chrome,
+ * so a template names `design:` instead of re-typing a `layout` block, and any
+ * shape can wear any design. `resolveSiteChrome(layout, design)` reads it:
+ * an explicit `TemplateManifest.layout` wins field by field, then this, then
+ * `DEFAULT_SITE_CHROME`. `standard` declares nothing — it IS the defaults, so
+ * spelling them out here would be a second copy of them to drift. A plain
+ * object, not a file: this module touches no disk. The design's documented
+ * look lives in `site-templates/designs/<design>/DESIGN.md`.
+ */
+export const DESIGN_LAYOUTS = {
+    standard: {},
+    minimalism: {
+        nav: "mark-only",
+        footer: "centered",
+        announcementBanner: false,
+        home: "deck",
+    },
+};
 /**
  * The base layer's directory under `site-templates/` (#5618 D1) — the seed
  * files every template reaches by declaring `extends`, installed by
@@ -12,6 +51,16 @@ import { MODULE_SLICES, normalizeModules, } from "./module-architecture.js";
  * the directory-scanning tests key their skip on.
  */
 export const BASE_LAYER_DIR = "_base";
+/**
+ * Whether a merged roster declares one scaffold-relative content file
+ * (#6646 D1): named by a row's `content`, or under a row's `contentDir`.
+ * The one predicate the scaffold's per-row install and the manifest
+ * generator's install-diff both read, so the two cannot disagree.
+ */
+export function rosterDeclares(roster, path) {
+    return roster.some((row) => (row.content ?? []).includes(path) ||
+        (row.contentDir !== undefined && path.startsWith(`${row.contentDir}/`)));
+}
 /** Thrown on an undeclared template name or a route claimed twice. Mirrors `SurfaceError`'s shape. */
 export class TemplateError extends Error {
     constructor(message) {
@@ -20,32 +69,62 @@ export class TemplateError extends Error {
     }
 }
 /**
- * The ten rows every declared template brings itself — one declared page set,
- * whichever mechanism scaffolds each (the Free manifest § 3, #5469 D4).
+ * The three pages every starter carries whatever its shape (#6658 D5,
+ * `docs/decisions/starter-roster-page-set.md` D4/D7): a glossary, a newsletter
+ * signup and a book-a-call page. Each is a module-less `GATEABLE_SURFACES`
+ * entry the roster enables, with its seed in `_base`. A template carrying the
+ * scheduling module overrides `BookCall/book-call.mdx` in its own tree, so the
+ * call to action opens `/meet` rather than `/contact`.
+ */
+const SHAPE_INDEPENDENT_ROWS = [
+    { route: "/glossary", content: ["content/en/GlossaryList/glossary.mdx"] },
+    {
+        route: "/newsletter",
+        content: ["content/en/NewsletterSignup/newsletter.mdx"],
+    },
+    { route: "/book-a-call", content: ["content/en/BookCall/book-call.mdx"] },
+];
+/**
+ * The rows every `organization-product` template brings itself — one declared
+ * page set, whichever layer carries each seed. Re-derived by #6658 from the
+ * standard (`derive-roster.py --entity-type software --offering-type software
+ * --primary-goal convert --scale global`, the `--shape organization-product`
+ * equivalent), edited only by the deviations the Free manifest's § 3a records
+ * with their reasons. With a template named, `scaffold()` keeps a `_base` or
+ * overlay seed only when a merged roster row names it (#6646 D1): the roster
+ * decides what installs, and the manifest generator's `--check` proves it.
+ *
+ * Two layers, one roster:
  *
- * Two mechanisms, one roster:
+ *   - `/`, `/software/[slug]`, `/use-cases`, `/about`, `/faq`, `/contact` and
+ *     `/purchase-policy` take their content from the overlay
+ *     (`template-overlay/content/en/**`, copied whole into `templates/` by
+ *     `build-templates.mjs`). `/software/[slug]` is the product's own detail
+ *     page (`/software/product`, a SoftwareProduct), which replaced the
+ *     `/features` stand-in (#6658 D3); its route is core, like `/about`.
+ *     `/use-cases` lists the three UseCase pages at `/use-cases/[slug]`
+ *     (#6658 D4).
+ *   - `/pricing`, `/privacy`, `/terms`, `/glossary`, `/newsletter`,
+ *     `/book-a-call` and the three UseCase pages take their content from the
+ *     base layer (`site-templates/_base/content/**`, #5618 D1), which every
+ *     template reaches by declaring `extends` — installed before the module
+ *     bundles and the template's own tree, so a template may override a base
+ *     page by shipping the same path. Their surfaces are module-less by
+ *     construction (parent § D16, #6658 D5): a template enables them by
+ *     NAMING them in its roster — `scaffold()` selects their
+ *     `GATEABLE_SURFACES` entries from the merged roster's routes (#5469 D10).
  *
- *   - `/`, `/how-it-works`, `/features`, `/about`, `/faq`, `/contact` and
- *     `/sign-in` are in EVERY scaffold, template or not: their content is the
- *     always-copied overlay (`template-overlay/content/en/**`, copied whole by
- *     `build-templates.mjs`) and their routes are core (`CORE_ROUTE_DIRS` —
- *     the three LandingPage pages render through the generic `[slug]` route,
- *     #5469 D2). They are declared here anyway, so the manifest a template
- *     publishes (`build-template-manifest.mjs`) lists the whole page set and
- *     the roster is what a template IS, not merely what it adds.
- *   - `/pricing`, `/privacy` and `/terms` are module-less by construction
- *     (parent § D16): no module owns these surfaces, their route files live in
- *     `apps/web` and are snapshotted into the starter like every other route,
- *     and a template enables them by NAMING them in its roster — `scaffold()`
- *     selects their `GATEABLE_SURFACES` entries from the merged roster's
- *     routes (#5469 D10). Their seed content ships ONCE, in the base layer
- *     (`site-templates/_base/content/**`, #5618 D1), which every template
- *     reaches by declaring `extends` — installed before the module bundles
- *     and the template's own tree, so a template may override a base page
- *     by shipping the same path.
+ * `/software`, `/sign-in` and `/sign-up` carry no `content`: they are code
+ * routes (the SoftwareProduct listing, the SignInCard island, the sign-up
+ * form), like the API-backed rows the scheduling module contributes — listed
+ * so the manifest is a complete install record, where the generator marks
+ * them `kind: route` (#6646 D2).
  *
- * `/sign-in` carries no `content`: it is a code route (the SignInCard island),
- * like the API-backed rows the scheduling module contributes.
+ * `/purchase-policy` is the product-shape purchase policy (#6646 D3): its
+ * overlay seed carries returns, shipping and refunds sections — the overlay,
+ * not `_base`, because the route is core and a scaffold naming no template
+ * serves it too. A service-shape template overrides that seed with its own
+ * cancellation and refunds file.
  *
  * `/blog` is deliberately NOT here (#5469 D3): the docs-blog module
  * contributes its own `/blog` row, so a base row would make `mergeRoster`
@@ -54,24 +133,33 @@ export class TemplateError extends Error {
  */
 const TEMPLATE_BASE_ROSTER = [
     { route: "/", content: ["content/en/HomePage/home.mdx"] },
+    { route: "/software" },
+    { route: "/software/[slug]", contentDir: "content/en/SoftwareProduct" },
     {
-        route: "/how-it-works",
-        content: ["content/en/LandingPage/how-it-works.mdx"],
+        route: "/use-cases",
+        content: ["content/en/UseCasesList/use-cases.mdx"],
     },
-    { route: "/features", content: ["content/en/LandingPage/features.mdx"] },
+    { route: "/use-cases/[slug]", contentDir: "content/en/UseCase" },
     { route: "/pricing", content: ["content/en/Pricing/pricing.mdx"] },
     { route: "/about", content: ["content/en/AboutPage/about.mdx"] },
     { route: "/faq", content: ["content/en/FAQPage/faq.mdx"] },
     { route: "/contact", content: ["content/en/ContactPage/contact.mdx"] },
+    ...SHAPE_INDEPENDENT_ROWS,
     { route: "/sign-in" },
+    { route: "/sign-up" },
     { route: "/privacy", content: ["content/en/PrivacyPage/privacy.mdx"] },
     { route: "/terms", content: ["content/en/TermsPage/terms.mdx"] },
+    {
+        route: "/purchase-policy",
+        content: ["content/en/PurchasePolicyPage/purchase-policy.mdx"],
+    },
 ];
 /**
- * The Free `/blog` teaser (#5469 D3) — one static LandingPage (`schema: Blog`)
- * that says what the Pro docs-blog module gives you. It is served by the
- * generic `[slug]` route over `content/en/LandingPage/blog.mdx`, which ships
- * in the always-copied overlay. `/blog` degrades by DIRECTORY PRECEDENCE, not
+ * The Free `/blog` teaser (#5469 D3) — one static BlogList page (schema `Blog`
+ * with an empty `ItemList`; the correct page type, not a LandingPage) that
+ * says what the Pro docs-blog module gives you. It is served by the generic
+ * `[slug]` route — which probes `LandingPage` first, then `BlogList` — over
+ * `content/en/BlogList/blog.mdx`, which ships in the always-copied overlay. `/blog` degrades by DIRECTORY PRECEDENCE, not
  * by a module gate: in a keyed docs-blog scaffold the module's own
  * `blog/[[...slug]]/page.tsx` directory exists and Next.js resolves the static
  * segment first, so the teaser file is inert; keyless, no `blog/` directory
@@ -80,16 +168,36 @@ const TEMPLATE_BASE_ROSTER = [
  */
 const FREE_BLOG_TEASER_ROW = {
     route: "/blog",
-    content: ["content/en/LandingPage/blog.mdx"],
+    content: ["content/en/BlogList/blog.mdx"],
 };
+/**
+ * The rows for the `signal-collectors` bundle's six sample pages (#6646
+ * disposition (a)) — the project listing, its two project pages and the
+ * three thank-you pages its `installMap` lands. The module contributes no
+ * row for any of these routes (`module-architecture.ts`'s installMap
+ * comment), so a template that takes the module declares them, and the
+ * roster names every page the scaffold installs. `/projects` is a
+ * module-less `GATEABLE_SURFACES` entry, so naming it here also copies the
+ * route directory the samples render through (`rosterSurfaces`).
+ */
+const SIGNAL_COLLECTORS_SAMPLE_ROWS = [
+    { route: "/projects", content: ["content/en/ProjectsList/projects.mdx"] },
+    { route: "/projects/[slug]", contentDir: "content/en/Project" },
+    { route: "/thanks/[slug]", contentDir: "content/en/ThankYouPage" },
+];
 /**
  * `minimalism-site`'s own rows (#5589) — the one declared template that does
  * not reuse `TEMPLATE_BASE_ROSTER`. Its page set is the issue's ROSTER, and
  * the rows it does NOT carry are as deliberate as the ones it does: no
- * `/how-it-works`, `/features` or `/pricing` (a reports-first site sells
+ * `/how-it-works`, product page or `/pricing` (a reports-first site sells
  * nothing from a pricing table), and no `/sign-in` (a code route every
  * scaffold carries regardless — `CORE_ROUTE_DIRS` — which this template
- * simply does not advertise as one of its pages).
+ * simply does not advertise as one of its pages). It does carry the three
+ * pages every starter carries (`SHAPE_INDEPENDENT_ROWS`, #6658), with its
+ * own `/book-a-call` seed pointing at the scheduling module's `/meet`.
+ *
+ * `/purchase-policy` is the service-shape purchase policy (#6646 D3) — this
+ * template's own cancellation and refunds seed, overriding `_base`'s.
  *
  * `/meet`, `/meet/[slug]`, `/meet/confirmed`, `/reports/[slug]` and the three
  * `/flows/*` rows are absent here on purpose: they are the `scheduling` and
@@ -102,20 +210,26 @@ const MINIMALISM_ROSTER = [
     { 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: "/services/[slug]", contentDir: "content/en/Service" },
     { route: "/contact", content: ["content/en/ContactPage/contact.mdx"] },
     { route: "/referral", content: ["content/en/LandingPage/referral.mdx"] },
     { route: "/faq", content: ["content/en/FAQPage/faq.mdx"] },
+    ...SHAPE_INDEPENDENT_ROWS,
     { route: "/privacy", content: ["content/en/PrivacyPage/privacy.mdx"] },
     { route: "/terms", content: ["content/en/TermsPage/terms.mdx"] },
+    {
+        route: "/purchase-policy",
+        content: ["content/en/PurchasePolicyPage/purchase-policy.mdx"],
+    },
+    ...SIGNAL_COLLECTORS_SAMPLE_ROWS,
 ];
 /**
  * `simple-service`'s own rows (#6087) — the T1 lawn-care roster of Epic #5778.
  * The second declared template that does not reuse `TEMPLATE_BASE_ROSTER`: a
  * lawn-care site sells three named services from `/services`, not from a
- * pricing table, so `/how-it-works`, `/features` and `/pricing` are absent —
- * `/pricing`'s `_base` seed still lands on disk, it simply has no rostered
- * route, exactly as it does for `minimalism-site`.
+ * pricing table, so `/how-it-works`, the product page and `/pricing` are absent —
+ * and so are their seeds: `scaffold()` installs a `_base` or overlay seed
+ * only for a row that names it (#6646 D1), exactly as for `minimalism-site`.
  *
  * `/meet`, `/meet/[slug]`, `/meet/confirmed` and `/appointments` are absent
  * here on purpose: they are the `scheduling` module's own
@@ -135,33 +249,35 @@ const MINIMALISM_ROSTER = [
  * claimant, the template's own roster is the only place that can declare
  * them, and doing so trips no collision.
  *
+ * `/thanks/[slug]` is declared here for the same reason (#6646 D2): the
+ * post-purchase thank-you route ships base tree and no module claims it.
+ *
+ * `/purchase-policy` is the service-shape purchase policy (#6646 D3) — its
+ * cancellation and refunds sections replace the three #5947 policy rows.
+ *
  * `/account` carries no `content`: it is a code route (the `(authed)` group),
  * like `/sign-in` on the base roster and like the API-backed rows the
- * scheduling module contributes. `/services/[slug]` likewise declares none —
- * its seed is a whole DIRECTORY (`content/en/Service`), and a roster row's
- * `content` names files the manifest generator reads frontmatter from.
+ * scheduling module contributes. `/services/[slug]` declares its seed
+ * DIRECTORY (`contentDir`, `content/en/Service`) — the three service pages.
  */
 const SIMPLE_SERVICE_ROSTER = [
     { route: "/", content: ["content/en/HomePage/home.mdx"] },
     { route: "/services", content: ["content/en/ServicesList/services.mdx"] },
-    { route: "/services/[slug]" },
+    { route: "/services/[slug]", contentDir: "content/en/Service" },
     { route: "/about", content: ["content/en/AboutPage/about.mdx"] },
     { route: "/contact", content: ["content/en/ContactPage/contact.mdx"] },
     { route: "/faq", content: ["content/en/FAQPage/faq.mdx"] },
-    { route: "/returns", content: ["content/en/ReturnsPolicyPage/returns.mdx"] },
+    ...SHAPE_INDEPENDENT_ROWS,
     {
-        route: "/cancellation",
-        content: ["content/en/CancellationPolicyPage/cancellation.mdx"],
-    },
-    {
-        route: "/shipping",
-        content: ["content/en/ShippingPolicyPage/shipping.mdx"],
+        route: "/purchase-policy",
+        content: ["content/en/PurchasePolicyPage/purchase-policy.mdx"],
     },
     { route: "/privacy", content: ["content/en/PrivacyPage/privacy.mdx"] },
     { route: "/terms", content: ["content/en/TermsPage/terms.mdx"] },
     { route: "/account" },
     { route: "/purchase/success" },
     { route: "/purchase/cancel" },
+    { route: "/thanks/[slug]" },
 ];
 /**
  * The three settled templates and their fixed `requires` lists — settled by
@@ -194,7 +310,12 @@ export const TEMPLATE_MANIFESTS = Object.freeze({
     "marketing-site-free": {
         name: "marketing-site-free",
         requires: ["marketing"],
+        // The demo site carries the "Get started with this template" banner
+        // (operator ruling 2026-09-23); every other layout knob keeps its default.
+        layout: { announcementBanner: true },
         categories: ["accounting", "legal", "technology"],
+        shape: "organization-product",
+        design: "standard",
         extends: BASE_LAYER_DIR,
         roster: [...TEMPLATE_BASE_ROSTER, FREE_BLOG_TEASER_ROW],
     },
@@ -221,8 +342,10 @@ export const TEMPLATE_MANIFESTS = Object.freeze({
             "technology",
             "medical-specialty",
         ],
+        shape: "organization-product",
+        design: "standard",
         extends: BASE_LAYER_DIR,
-        roster: TEMPLATE_BASE_ROSTER,
+        roster: [...TEMPLATE_BASE_ROSTER, ...SIGNAL_COLLECTORS_SAMPLE_ROWS],
     },
     /**
      * Pro Plus — the Pro list plus `multi-tenant`, which is correctly in the
@@ -243,8 +366,10 @@ export const TEMPLATE_MANIFESTS = Object.freeze({
             "multi-tenant",
         ],
         categories: ["technology", "medical-specialty"],
+        shape: "organization-product",
+        design: "standard",
         extends: BASE_LAYER_DIR,
-        roster: TEMPLATE_BASE_ROSTER,
+        roster: [...TEMPLATE_BASE_ROSTER, ...SIGNAL_COLLECTORS_SAMPLE_ROWS],
     },
     /**
      * The second Pro template (#5589) — the reports-first, scroll-snap deck
@@ -256,11 +381,17 @@ export const TEMPLATE_MANIFESTS = Object.freeze({
      *
      * It declares its OWN roster rather than reusing `TEMPLATE_BASE_ROSTER`
      * (the only declared template that does): the deck home 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 its seed content, and the
-     * roster is what the template IS, so an unrostered page simply has no
-     * route directory copied (`rosterSurfaces`).
+     * document-scroll home, and `/how-it-works`, the product page, `/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
+     * (`rosterSurfaces`) nor its `_base`/overlay seed (#6646 D1).
+     *
+     * It declares NO `layout` block (#6638): the deck home, mark-only nav and
+     * centered footer are the `minimalism` design's, supplied by
+     * `DESIGN_LAYOUTS` from `design:` — the look any shape can wear. The
+     * roster rows the `organization-service` shape does not derive
+     * (`/reports`, `/referral`) are recorded with their reasons in this
+     * template's TEMPLATE-MANIFEST.md § 3a.
      *
      * `/reports` and `/referral` carry no `GATEABLE_SURFACES` entry and need
      * none: both are single-segment `LandingPage` slugs served by the generic
@@ -268,24 +399,18 @@ export const TEMPLATE_MANIFESTS = Object.freeze({
      * uses. `/reports/[slug]` (the reader) is the signal-collectors module's
      * own contributed row.
      *
-     * `/services/[slug]` declares no `content`: its seed is a whole DIRECTORY
-     * (`content/en/Service`, as `routes-map.ts` records it), and a roster
-     * row's `content` names files the manifest generator reads frontmatter
-     * from. The three samples ride the template tree unmapped, landing at
-     * that directory.
+     * `/services/[slug]` declares its seed DIRECTORY as `contentDir`
+     * (`content/en/Service`, as `routes-map.ts` records it). The three
+     * samples ride the template tree unmapped, landing at that directory.
      */
     "minimalism-site": {
         name: "minimalism-site",
         requires: ["marketing", "scheduling", "signal-collectors"],
         categories: ["real-estate", "technology", "legal"],
+        shape: "organization-service",
+        design: "minimalism",
         extends: BASE_LAYER_DIR,
         roster: MINIMALISM_ROSTER,
-        layout: {
-            nav: "mark-only",
-            footer: "centered",
-            announcementBanner: false,
-            home: "deck",
-        },
     },
     /**
      * The T1 lawn-care template (#6087, Epic #5778) — the first site shape
@@ -303,14 +428,16 @@ export const TEMPLATE_MANIFESTS = Object.freeze({
      * `scheduling` and `commerce` are both paid, so `templateDelivery`
      * returns `"paid"` from either one alone.
      *
-     * It declares NO `layout` block: the default marketing-site chrome is the
-     * one a lawn-care site wants, and the issue's STOP boundary excludes
-     * layout knobs the spec does not name.
+     * It declares NO `layout` block: the default chrome (full nav, column
+     * footer, no announcement banner) is the one a lawn-care site wants, and
+     * the issue's STOP boundary excludes layout knobs the spec does not name.
      */
     "simple-service": {
         name: "simple-service",
         requires: ["marketing", "scheduling", "commerce"],
         categories: ["landscaping"],
+        shape: "local-business-service",
+        design: "standard",
         extends: BASE_LAYER_DIR,
         roster: SIMPLE_SERVICE_ROSTER,
     },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-ailk",
-  "version": "0.6.0",
+  "version": "0.7.0",
   "description": "Scaffolder for AI Launch Kit — `pnpm create ailk@latest <dir>` produces a starter repo consuming @working-theory/* from npm (per ADR 0007).",
   "type": "module",
   "main": "./dist/index.js",
@@ -25,8 +25,8 @@
     "tar": "^7.5.21"
   },
   "devDependencies": {
-    "@working-theory/schema": "0.25.0",
-    "@working-theory/templates": "0.25.0"
+    "@working-theory/schema": "0.27.0",
+    "@working-theory/templates": "0.27.0"
   },
   "repository": {
     "type": "git",
@@ -58,6 +58,8 @@
     "build-catalog": "node scripts/build-component-catalog.mjs",
     "check-catalog": "node scripts/build-component-catalog.mjs --check",
     "manifest:build": "node scripts/build-template-manifest.mjs --template marketing-site-free",
-    "manifest:check": "node scripts/build-template-manifest.mjs --template marketing-site-free --check && node scripts/build-template-manifest.mjs --template marketing-site --check"
+    "manifest:check": "node scripts/build-template-manifest.mjs --template marketing-site-free --check && node scripts/build-template-manifest.mjs --template marketing-site --check",
+    "page-types:build": "tsx scripts/generate-page-types-reference.ts",
+    "page-types:check": "tsx scripts/generate-page-types-reference.ts --check"
   }
 }

package/site-templates/_base/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": "Get in touch", "href": "/contact" },
+        },
+    },
+    {
+      "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. The call to action sends visitors to your contact page; a template that carries the scheduling module overrides this file to point it at the /meet booker. 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/_base/content/en/GlossaryList/glossary.mdx

@@ -0,0 +1,66 @@
+---
+type: "GlossaryList"
+slug: "glossary"
+title: "{Glossary: the terms your customers look up}"
+description: "{One sentence on the subject these terms cover and who they help}"
+placeholder: true
+sections:
+  [
+    {
+      "id": "hero",
+      "type": "hero",
+      "data":
+        {
+          "eyebrow": "Glossary",
+          "headline": "{Glossary: the terms your customers look up}",
+          "subheadline": "{One sentence on the subject these terms cover and who they help}",
+          "primaryCta": { "label": "{Primary CTA}", "href": "/contact" },
+        },
+    },
+    {
+      "id": "glossary-index",
+      "type": "glossary-index",
+      "data":
+        {
+          "headline": "{Terms, A to Z}",
+          "description": "{One sentence on how to use this list}",
+          "variant": "columns",
+          "terms":
+            [
+              {
+                "term": "{Term 1}",
+                "slug": "term-1",
+                "definition": "{One plain sentence that defines this term the way your customers would say it}",
+                "letter": "T",
+              },
+              {
+                "term": "{Term 2}",
+                "slug": "term-2",
+                "definition": "{One plain sentence that defines this term the way your customers would say it}",
+                "letter": "T",
+              },
+              {
+                "term": "{Term 3}",
+                "slug": "term-3",
+                "definition": "{One plain sentence that defines this term the way your customers would say it}",
+                "letter": "T",
+              },
+              {
+                "term": "{Term 4}",
+                "slug": "term-4",
+                "definition": "{One plain sentence that defines this term the way your customers would say it}",
+                "letter": "T",
+              },
+              {
+                "term": "{Term 5}",
+                "slug": "term-5",
+                "definition": "{One plain sentence that defines this term the way your customers would say it}",
+                "letter": "T",
+              },
+            ],
+        },
+    },
+  ]
+---
+
+{/* Rendered from frontmatter `sections[]` by the /glossary route. Each `glossary-index` term becomes a DefinedTerm in the page's JSON-LD DefinedTermSet, so write the definition an agent should quote. Placeholder copy — replace every {brace} with your own words, and add or remove terms, before you launch. */}

package/site-templates/_base/content/en/NewsletterSignup/newsletter.mdx

@@ -0,0 +1,68 @@
+---
+type: "NewsletterSignup"
+slug: "newsletter"
+title: "{Newsletter: what subscribers get and how often}"
+description: "{One sentence on what this newsletter covers and who it is for}"
+placeholder: true
+schema:
+  mainEntity:
+    "@type": "Offer"
+    name: "{Your newsletter name}"
+    price: 0
+    priceCurrency: "USD"
+sections:
+  [
+    {
+      "id": "hero",
+      "type": "hero",
+      "data":
+        {
+          "eyebrow": "Newsletter",
+          "headline": "{Newsletter: what subscribers get and how often}",
+          "subheadline": "{One sentence on what this newsletter covers and who it is for}",
+          "primaryCta": { "label": "Subscribe", "href": "#signup" },
+        },
+    },
+    {
+      "id": "signup",
+      "type": "newsletter",
+      "data":
+        {
+          "headline": "Subscribe",
+          "description": "{One sentence on what lands in the inbox}",
+          "action": "/v1/leads/subscribe",
+          "source": "newsletter",
+          "placeholder": "you@example.com",
+          "submitLabel": "Subscribe",
+          "consentText": "{One line on how you use the address, and that readers can unsubscribe any time}",
+          "pattern": "none",
+        },
+    },
+    {
+      "id": "faq",
+      "type": "faq",
+      "data":
+        {
+          "headline": "FAQs",
+          "presentation": "expanded",
+          "items":
+            [
+              {
+                "question": "{How often will I hear from you?}",
+                "answer": "{Answer in one or two plain sentences}",
+              },
+              {
+                "question": "{What will I get?}",
+                "answer": "{Answer in one or two plain sentences}",
+              },
+              {
+                "question": "{Can I unsubscribe?}",
+                "answer": "{Answer in one or two plain sentences}",
+              },
+            ],
+        },
+    },
+  ]
+---
+
+{/* Rendered from frontmatter `sections[]` by the /newsletter route. The form posts the address to lead capture (`/v1/leads/subscribe`), which records a subscriber and sends no verification email. The `schema:` Offer is the page's JSON-LD main entity — a free subscription. Placeholder copy — replace every {brace} with your own words before you launch. */}