create-ailk 0.3.0 → 0.5.0

package/dist/template-manifest.js

@@ -0,0 +1,337 @@
+/**
+ * Site-template registry, and the roster merge that composes a template with
+ * the modules it takes (spec 5478, unit A of the site-templates mechanism;
+ * design record docs/specs/5462-site-templates-module-bundles-spec.md).
+ *
+ * A site template is DATA AND CONTENT, NOT CODE: a page roster, seed content
+ * and config — never a `page.tsx` (parent § D16). This file declares what a
+ * template IS. It declares no delivery channel, reads no licence, and touches
+ * no disk: the `--template` flag, the bundle fetch and the landing order are
+ * #5481's, and `GET /v1/templates/:name/:version` is #5480's.
+ *
+ * A CODE registry, not per-template JSON (parent § D2): in TypeScript,
+ * `requires` is checked against `RECOGNIZED_MODULES` at compile time, and this
+ * package already twice records that a fixed template FILE is the drift a
+ * registry removes.
+ */
+import { classifyModules } from "./lib/module-tier.js";
+import { MODULE_SLICES, normalizeModules, } from "./module-architecture.js";
+/**
+ * The base layer's directory under `site-templates/` (#5618 D1) — the seed
+ * files every template reaches by declaring `extends`, installed by
+ * `installBundleTree` before any module bundle and only when `--template`
+ * is named, so a scaffold naming no template is byte-identical to before it
+ * existed. It is NOT a template: it has no `TEMPLATE_MANIFESTS` entry (so
+ * `--template _base` stays unrecognized — `RECOGNIZED_TEMPLATES` is exactly
+ * that object's key set) and is never published as a registry bundle. The
+ * leading underscore is what `build-module-bundles.mjs`'s template loop and
+ * the directory-scanning tests key their skip on.
+ */
+export const BASE_LAYER_DIR = "_base";
+/** Thrown on an undeclared template name or a route claimed twice. Mirrors `SurfaceError`'s shape. */
+export class TemplateError extends Error {
+    constructor(message) {
+        super(message);
+        this.name = "TemplateError";
+    }
+}
+/**
+ * The ten rows every declared template brings itself — one declared page set,
+ * whichever mechanism scaffolds each (the Free manifest § 3, #5469 D4).
+ *
+ * Two mechanisms, one roster:
+ *
+ *   - `/`, `/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.
+ *
+ * `/sign-in` carries no `content`: it is a code route (the SignInCard island),
+ * like the API-backed rows the scheduling module contributes.
+ *
+ * `/blog` is deliberately NOT here (#5469 D3): the docs-blog module
+ * contributes its own `/blog` row, so a base row would make `mergeRoster`
+ * refuse every template that takes that module. The Free teaser row is
+ * declared on `marketing-site-free` alone, below.
+ */
+const TEMPLATE_BASE_ROSTER = [
+    { route: "/", content: ["content/en/HomePage/home.mdx"] },
+    {
+        route: "/how-it-works",
+        content: ["content/en/LandingPage/how-it-works.mdx"],
+    },
+    { route: "/features", content: ["content/en/LandingPage/features.mdx"] },
+    { 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"] },
+    { route: "/sign-in" },
+    { route: "/privacy", content: ["content/en/PrivacyPage/privacy.mdx"] },
+    { route: "/terms", content: ["content/en/TermsPage/terms.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
+ * 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
+ * exists and the teaser renders. Declared on the Free template only — on
+ * `marketing-site` the docs-blog contribution claims the route.
+ */
+const FREE_BLOG_TEASER_ROW = {
+    route: "/blog",
+    content: ["content/en/LandingPage/blog.mdx"],
+};
+/**
+ * `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
+ * 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).
+ *
+ * `/meet`, `/meet/[slug]`, `/meet/confirmed`, `/reports/[slug]` and the three
+ * `/flows/*` rows are absent here on purpose: they are the `scheduling` and
+ * `signal-collectors` modules' own `pageContributions`, merged in by
+ * `mergeRoster`. Declaring one here would make that merge refuse the
+ * template outright (§ D8's both-claimants refusal).
+ */
+const 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"] },
+];
+/**
+ * The three settled templates and their fixed `requires` lists — settled by
+ * Sam, 2026-09-14 (parent § D12). The plain name is the Pro one: it is the
+ * flagship and the demo.
+ *
+ * `workspace` appears in none of them. It is a Pro module, but an authed app
+ * surface contributing no PUBLIC page to a marketing site, and `requires`
+ * names what the roster uses (parent § D15). A Pro key unlocks it regardless
+ * of any template. `ModuleName` could express it either way — `workspace` is
+ * one of the seven `RECOGNIZED_MODULES` names; it is simply not one any
+ * template's fixed `requires` list names.
+ *
+ * `commerce` is likewise in none of them: it is a per-site add-on available at
+ * any level, so a template for it would contradict the offering model and
+ * multiply the set combinatorially (parent § D13). It still contributes rows
+ * to whichever template takes it, through `mergeRoster` below.
+ *
+ * Frozen (#5507): this registry is also the issuer's authorization allowlist
+ * (spec 5480 § C7) — a mutable global there could be monkey-patched at
+ * runtime. A caller needing a different registry for a test injects its own
+ * fixture rather than mutating this one.
+ */
+export const TEMPLATE_MANIFESTS = Object.freeze({
+    /**
+     * The Free template, and the mechanism's own proof (parent § D11): it
+     * requires only `marketing`, so the keyless merge path is exercised by a
+     * template we ship anyway rather than by a throwaway fixture.
+     */
+    "marketing-site-free": {
+        name: "marketing-site-free",
+        requires: ["marketing"],
+        extends: BASE_LAYER_DIR,
+        roster: [...TEMPLATE_BASE_ROSTER, FREE_BLOG_TEASER_ROW],
+    },
+    /**
+     * The Pro flagship. Its module list is OFFERINGS § 4 offering 3's tiers line
+     * — "docs, scheduling and flows modules" — where "flows" is
+     * `signal-collectors` (`MODULE_SURFACES` maps it to `["flows"]`).
+     */
+    "marketing-site": {
+        name: "marketing-site",
+        requires: ["marketing", "docs-blog", "scheduling", "signal-collectors"],
+        extends: BASE_LAYER_DIR,
+        roster: TEMPLATE_BASE_ROSTER,
+    },
+    /**
+     * Pro Plus — the Pro list plus `multi-tenant`, which is correctly in the
+     * list because it DOES contribute pages (the org and workspace surfaces).
+     * Its `pageContributions` is nonetheless unset today, deferred to its own
+     * instance, so this template's merged roster carries the same contributed
+     * rows as `marketing-site`'s and no more. That is a module which has
+     * declared no rows yet — visible in the diff — not a merge that dropped
+     * declared rows.
+     */
+    "saas-product": {
+        name: "saas-product",
+        requires: [
+            "marketing",
+            "docs-blog",
+            "scheduling",
+            "signal-collectors",
+            "multi-tenant",
+        ],
+        extends: BASE_LAYER_DIR,
+        roster: TEMPLATE_BASE_ROSTER,
+    },
+    /**
+     * The second Pro template (#5589) — the reports-first, scroll-snap deck
+     * site. NOT `marketing-site` plus a module: its `requires` omits
+     * `docs-blog`, so the two Pro templates are siblings under `_base`
+     * (#5618 D2), never a lineage. Level still derives from `requires`:
+     * `scheduling` and `signal-collectors` are paid, so `templateDelivery`
+     * returns `"paid"` exactly as it does for `marketing-site`.
+     *
+     * 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`).
+     *
+     * `/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. `/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.
+     */
+    "minimalism-site": {
+        name: "minimalism-site",
+        requires: ["marketing", "scheduling", "signal-collectors"],
+        extends: BASE_LAYER_DIR,
+        roster: MINIMALISM_ROSTER,
+        layout: {
+            nav: "mark-only",
+            footer: "centered",
+            announcementBanner: false,
+            home: "deck",
+        },
+    },
+});
+/** Look up a declared template. @throws TemplateError on an undeclared name. */
+export function resolveTemplate(name) {
+    const manifest = TEMPLATE_MANIFESTS[name];
+    if (!manifest) {
+        throw new TemplateError(`unknown template "${name}". Declared: ${Object.keys(TEMPLATE_MANIFESTS).join(", ")}`);
+    }
+    return manifest;
+}
+/**
+ * Resolve a template's `extends` chain — `[name, …ancestors, "_base"]` — in
+ * the client registry, before any fetch (#5618 D2). `_base` is the only
+ * valid terminus: an `extends` naming neither it nor a declared template is
+ * refused naming the field, the value and the recognized set, in
+ * `resolveTemplate`'s message shape; a cycle is refused naming the whole
+ * chain. The registry is a parameter for the same reason `TEMPLATE_MANIFESTS`
+ * is frozen (#5507): a test needing a cyclic or dangling fixture injects its
+ * own rather than mutating the shipped one.
+ *
+ * @throws TemplateError on an undeclared name, an unknown parent or a cycle.
+ */
+export function resolveTemplateLineage(name, registry = TEMPLATE_MANIFESTS) {
+    const chain = [];
+    let current = name;
+    for (;;) {
+        if (chain.includes(current)) {
+            throw new TemplateError(`template "${name}": cyclic "extends" chain ${[...chain, current].join(" → ")}`);
+        }
+        chain.push(current);
+        if (current === BASE_LAYER_DIR)
+            return chain;
+        const manifest = registry[current];
+        if (!manifest) {
+            const declared = [...Object.keys(registry), BASE_LAYER_DIR].join(", ");
+            if (chain.length === 1) {
+                throw new TemplateError(`unknown template "${current}". Declared: ${declared}`);
+            }
+            throw new TemplateError(`template "${chain[chain.length - 2]}": "extends" names unknown template "${current}". Declared: ${declared}`);
+        }
+        current = manifest.extends;
+    }
+}
+/**
+ * Compose a template's roster: its base rows, then each taken module's
+ * contributed rows in `normalizeModules` order (parent § D7).
+ *
+ * `normalizeModules` is REUSED rather than re-sorted here. It already returns
+ * the unique set ordered by `RECOGNIZED_MODULES`, and `scaffold()` already
+ * calls it — a second sort at this call site would be a second ordering
+ * authority that could drift from the one `deriveArchitecture` depends on.
+ * That also makes the merge a pure function of the module SET: the same set in
+ * any argument order returns identical rows.
+ *
+ * The merge is pure and writes nothing. Staging a contributed row's seed
+ * content is the bundle producer's job (`build-module-bundles.mjs`, #5481);
+ * doing it here would put a filesystem dependency in a function three sibling
+ * units import for its return value.
+ *
+ * @param modules the modules this scaffold takes. A template's `requires` are
+ *   taken by definition — a required module whose bundle cannot be had refuses
+ *   the install outright (parent § D17, #5481) rather than merging short.
+ * @throws TemplateError when two sources claim one route (parent § D8). Both
+ *   the base roster and every contribution are compile-time known, so the
+ *   collision is caught by a test before a bundle exists — never resolved at
+ *   runtime by a base-wins or module-wins precedence rule, either of which
+ *   silently produces a site missing a page someone declared.
+ */
+export function mergeRoster(manifest, modules) {
+    const merged = [];
+    /** route → the source that claimed it, for the collision message. */
+    const claimedBy = new Map();
+    const take = (rows, source) => {
+        for (const row of rows) {
+            const owner = claimedBy.get(row.route);
+            if (owner !== undefined) {
+                throw new TemplateError(`route "${row.route}" is claimed by both ${owner} and ${source}`);
+            }
+            claimedBy.set(row.route, source);
+            merged.push(row);
+        }
+    };
+    take(manifest.roster, `template "${manifest.name}"`);
+    for (const module of normalizeModules([...modules])) {
+        take(MODULE_SLICES[module].pageContributions ?? [], `module "${module}"`);
+    }
+    return merged;
+}
+/**
+ * Whether a template installs on the keyless path or needs a verified
+ * `AILK_LICENSE_KEY` — derived from `requires`, never declared (parent § D3).
+ *
+ * The derivation goes through the existing `classifyModules` rather than a
+ * second list of paid names, which would drift. This is deliberately the
+ * CLIENT half of a two-derivation split: the issuer derives the commercial
+ * LEVEL from the same `requires` via `TIER_SPECS` (#5480). One shared
+ * derivation would force this package to import
+ * `@working-theory/license-manifest` — a `restricted` package — breaking
+ * `pnpm install` for every Free consumer, not merely gating the paid path.
+ */
+export function templateDelivery(manifest) {
+    return classifyModules([...manifest.requires]).paid.length > 0
+        ? "paid"
+        : "free";
+}

package/dist/template-names.d.ts

@@ -0,0 +1,41 @@
+/**
+ * The `--template` flag's vocabulary, and nothing else.
+ *
+ * WHY THIS FILE EXISTS, measured rather than assumed. Spec 5481 § 3 DD1 has
+ * `parse-args.ts` validate `--template` against `TEMPLATE_MANIFESTS` through a
+ * runtime import, on the grounds that the registry's own dependency on
+ * `parse-args.ts` (for `ModuleName`) is `import type` and so erases at
+ * compile. That is true of the DIRECT edge and false of the graph:
+ * `template-manifest.ts` imports `lib/module-tier.js` and
+ * `module-architecture.js` as RUNTIME values, and BOTH of those import
+ * `RECOGNIZED_MODULES` — a runtime value — back from `parse-args.ts`.
+ * `module-tier.ts` then reads it at MODULE SCOPE to derive `PAID_MODULES`.
+ * So `parse-args.ts` importing the registry closes a runtime cycle whose
+ * first read lands in the temporal dead zone:
+ *
+ *     ReferenceError: Cannot access 'RECOGNIZED_MODULES' before initialization
+ *
+ * — reproduced against the built `dist/` while implementing this unit, not
+ * theorised. `surfaces.ts`'s header warns about exactly this relationship
+ * ("Deliberately imports nothing from `parse-args.ts`: that module imports
+ * THIS one … so a back-import would close a cycle"), and `surfaces.ts` is the
+ * precedent this file follows: the flag's vocabulary lives in a module the
+ * parser can import because it imports nothing at all.
+ *
+ * THE REGISTRY IS STILL `template-manifest.ts` (parent record D2). This file
+ * declares NAMES; that one declares what a template IS — `requires`, the
+ * roster, the `installMap`, the free-vs-paid derivation — and it stays the
+ * single place a template is defined. The two cannot drift: the names here
+ * are asserted equal to `Object.keys(TEMPLATE_MANIFESTS)` by
+ * `__tests__/template-scaffold.test.ts`, so adding a template without listing
+ * it here (or the reverse) fails the suite rather than shipping a flag that
+ * accepts a name the registry does not know.
+ *
+ * Rejected: lazifying `module-tier.ts`'s `PAID_MODULES` to break the cycle at
+ * its source. It is the correct structural fix and it is not this unit's to
+ * make — `module-tier.ts` is a READ row in spec 5481 § 4, and `PAID_MODULES`
+ * is consumed as a plain array across the package.
+ */
+/** The declared site templates, in `TEMPLATE_MANIFESTS` declaration order. */
+export declare const RECOGNIZED_TEMPLATES: readonly ["marketing-site-free", "marketing-site", "saas-product", "minimalism-site"];
+export type TemplateName = (typeof RECOGNIZED_TEMPLATES)[number];

package/dist/template-names.js

@@ -0,0 +1,45 @@
+/**
+ * The `--template` flag's vocabulary, and nothing else.
+ *
+ * WHY THIS FILE EXISTS, measured rather than assumed. Spec 5481 § 3 DD1 has
+ * `parse-args.ts` validate `--template` against `TEMPLATE_MANIFESTS` through a
+ * runtime import, on the grounds that the registry's own dependency on
+ * `parse-args.ts` (for `ModuleName`) is `import type` and so erases at
+ * compile. That is true of the DIRECT edge and false of the graph:
+ * `template-manifest.ts` imports `lib/module-tier.js` and
+ * `module-architecture.js` as RUNTIME values, and BOTH of those import
+ * `RECOGNIZED_MODULES` — a runtime value — back from `parse-args.ts`.
+ * `module-tier.ts` then reads it at MODULE SCOPE to derive `PAID_MODULES`.
+ * So `parse-args.ts` importing the registry closes a runtime cycle whose
+ * first read lands in the temporal dead zone:
+ *
+ *     ReferenceError: Cannot access 'RECOGNIZED_MODULES' before initialization
+ *
+ * — reproduced against the built `dist/` while implementing this unit, not
+ * theorised. `surfaces.ts`'s header warns about exactly this relationship
+ * ("Deliberately imports nothing from `parse-args.ts`: that module imports
+ * THIS one … so a back-import would close a cycle"), and `surfaces.ts` is the
+ * precedent this file follows: the flag's vocabulary lives in a module the
+ * parser can import because it imports nothing at all.
+ *
+ * THE REGISTRY IS STILL `template-manifest.ts` (parent record D2). This file
+ * declares NAMES; that one declares what a template IS — `requires`, the
+ * roster, the `installMap`, the free-vs-paid derivation — and it stays the
+ * single place a template is defined. The two cannot drift: the names here
+ * are asserted equal to `Object.keys(TEMPLATE_MANIFESTS)` by
+ * `__tests__/template-scaffold.test.ts`, so adding a template without listing
+ * it here (or the reverse) fails the suite rather than shipping a flag that
+ * accepts a name the registry does not know.
+ *
+ * Rejected: lazifying `module-tier.ts`'s `PAID_MODULES` to break the cycle at
+ * its source. It is the correct structural fix and it is not this unit's to
+ * make — `module-tier.ts` is a READ row in spec 5481 § 4, and `PAID_MODULES`
+ * is consumed as a plain array across the package.
+ */
+/** The declared site templates, in `TEMPLATE_MANIFESTS` declaration order. */
+export const RECOGNIZED_TEMPLATES = [
+    "marketing-site-free",
+    "marketing-site",
+    "saas-product",
+    "minimalism-site",
+];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-ailk",
-  "version": "0.3.0",
+  "version": "0.5.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",
@@ -11,6 +11,9 @@
   "files": [
     "dist",
     "templates",
+    "site-templates",
+    "versions.json",
+    "component-catalog.json",
     "component-catalog.md",
     "README.md",
     "LICENSE"
@@ -21,6 +24,9 @@
   "dependencies": {
     "tar": "^7.5.21"
   },
+  "devDependencies": {
+    "@working-theory/templates": "0.24.0"
+  },
   "repository": {
     "type": "git",
     "url": "git+https://github.com/working-theory-labs/ai-launch-kit.git",
@@ -49,6 +55,8 @@
     "test:coverage": "jest --coverage",
     "build-templates": "tsc -b && node scripts/build-templates.mjs",
     "build-catalog": "node scripts/build-component-catalog.mjs",
-    "check-catalog": "node scripts/build-component-catalog.mjs --check"
+    "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"
   }
 }

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

@@ -0,0 +1,6 @@
+{
+  "name": "_base",
+  "requires": [],
+  "$comment": "The BASE LAYER (#5618 D1) — not a template. Every declared template reaches this tree by `extends: \"_base\"`; scaffold() installs it through installBundleTree before any module bundle and before the template's own tree, only when --template is named. It carries the seed content every template brings itself and no module owns: /pricing, /privacy and /terms (spec 5462 D16). No installMap: every file here is unmapped and lands at its own path under the scaffold root's content/, so a template overrides a base page by shipping the same path. Never published as a registry bundle; the leading underscore is the skip signal for the bundle producer and the site-templates/ directory scans.",
+  "postInstall": "Base layer installed: seed copy for /pricing, /privacy and /terms is in content/en/ - replace the placeholder copy before you launch."
+}

package/site-templates/_base/content/en/Pricing/pricing.mdx

@@ -0,0 +1,169 @@
+---
+type: "Pricing"
+slug: "pricing"
+title: "Pays for itself in {tangible value or outcome}"
+description: "This is a great place to communicate any important details you want everyone to know about how your pricing works."
+sections:
+  [
+    {
+      "id": "hero",
+      "type": "hero",
+      "data":
+        {
+          "eyebrow": "Pricing",
+          "headline": "Pays for itself in {tangible value or outcome}",
+          "subheadline": "This is a great place to communicate any important details you want everyone to know about how your pricing works.",
+          "primaryCta": { "label": "{Primary CTA}", "href": "/contact" },
+          "secondaryCta":
+            {
+              "label": "{Secondary CTA}",
+              "href": "/how-it-works",
+              "variant": "outline",
+            },
+        },
+    },
+    {
+      "id": "plans",
+      "type": "pricing",
+      "data":
+        {
+          "variant": "three-tiers-with-toggle",
+          "eyebrow": "Pricing",
+          "headline": "Pays for itself in {tangible value or outcome}",
+          "description": "This is a great place to communicate any important details you want everyone to know about how your pricing works.",
+          "billingToggle": true,
+          "plans":
+            [
+              {
+                "name": "Basic plan",
+                "price": { "monthly": "$19/mo", "annual": "$180/yr" },
+                "features":
+                  [
+                    "Feature text goes here",
+                    "Feature text goes here",
+                    "Feature text goes here",
+                  ],
+                "cta": { "label": "{Primary CTA}", "href": "/contact" },
+              },
+              {
+                "name": "Business plan",
+                "price": { "monthly": "$29/mo", "annual": "$280/yr" },
+                "features":
+                  [
+                    "New feature text goes here",
+                    "Feature text goes here",
+                    "Feature text goes here",
+                    "Feature text goes here",
+                  ],
+                "cta": { "label": "{Primary CTA}", "href": "/contact" },
+              },
+              {
+                "name": "Enterprise plan",
+                "price": { "monthly": "$49/mo", "annual": "$480/yr" },
+                "features":
+                  [
+                    "New feature text goes here",
+                    "Feature text goes here",
+                    "Feature text goes here",
+                    "Feature text goes here",
+                    "Feature text goes here",
+                  ],
+                "cta": { "label": "{Primary CTA}", "href": "/contact" },
+              },
+            ],
+        },
+    },
+    {
+      "id": "logo-cloud",
+      "type": "logoCloud",
+      "data":
+        {
+          "headline": "Don’t just take our word for it",
+          "logos":
+            [
+              { "name": "Placeholder logo", "src": "/logomark.svg" },
+              { "name": "Placeholder logo", "src": "/logomark.svg" },
+              { "name": "Placeholder logo", "src": "/logomark.svg" },
+              { "name": "Placeholder logo", "src": "/logomark.svg" },
+              { "name": "Placeholder logo", "src": "/logomark.svg" },
+              { "name": "Placeholder logo", "src": "/logomark.svg" },
+            ],
+          "layout": "inline",
+          "treatment": "monochrome",
+        },
+    },
+    {
+      "id": "testimonial",
+      "type": "testimonials",
+      "data":
+        {
+          "variant": "featured",
+          "items":
+            [
+              {
+                "quote": "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat.",
+                "author": "John Smith",
+                "role": "CEO, Google",
+              },
+            ],
+        },
+    },
+    {
+      "id": "switch",
+      "type": "cta",
+      "data":
+        {
+          "variant": "box",
+          "headline": "Switch to {your product} in {time amount} or less",
+          "description": "You shouldn't have to {experience a painful problem}. With {your product}, you can finally {achieve a value outcome or get a big improvement}.",
+          "chips":
+            ["No credit card required", "Cancel any time", "Live chat support"],
+          "primaryCta": { "label": "{Primary CTA}", "href": "/contact" },
+          "secondaryCta":
+            {
+              "label": "{Secondary CTA}",
+              "href": "/pricing",
+              "variant": "outline",
+            },
+          "closingLine": "{Social Proof goes here}",
+        },
+    },
+    {
+      "id": "faq",
+      "type": "faq",
+      "data":
+        {
+          "headline": "FAQs",
+          "description": "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique.",
+          "supportLink": { "label": "Contact", "href": "/contact" },
+          "presentation": "accordion",
+          "initialOpen": "first",
+          "items":
+            [
+              {
+                "question": "Vel odio odit voluptatum ut veritatis. Ex rerum aspernatur voluptas unde officia. Dolorem officiis laboriosa?",
+                "answer": "Vel odio odit voluptatum ut veritatis. Ex rerum aspernatur voluptas unde officia. Dolorem officiis laboriosa odio odit voluptatum ut veritatis. Ex rerum aspernatur voluptas unde officia. Dolorem officiis laboriosa.",
+              },
+              {
+                "question": "Dolorem consectetur quia maxime sunt ut sint. Fuga optio dolorem animi voluptatem laudantium error. Quis accusamus deleniti rer?",
+                "answer": "Vel odio odit voluptatum ut veritatis. Ex rerum aspernatur voluptas unde officia. Dolorem officiis laboriosa odio odit voluptatum ut veritatis. Ex rerum aspernatur voluptas unde officia. Dolorem officiis laboriosa.",
+              },
+              {
+                "question": "Totam nihil esse. Itaque optio temporibus adipisci. Rerum nisi aperiam aliquid doloremque aliquam?",
+                "answer": "Vel odio odit voluptatum ut veritatis. Ex rerum aspernatur voluptas unde officia. Dolorem officiis laboriosa odio odit voluptatum ut veritatis. Ex rerum aspernatur voluptas unde officia. Dolorem officiis laboriosa.",
+              },
+              {
+                "question": "Delectus minus officiis et. Perspiciatis illum nisi vitae. Sed consequuntur animi corrupti distinctio ipsam accusamus?",
+                "answer": "Vel odio odit voluptatum ut veritatis. Ex rerum aspernatur voluptas unde officia. Dolorem officiis laboriosa odio odit voluptatum ut veritatis. Ex rerum aspernatur voluptas unde officia. Dolorem officiis laboriosa.",
+              },
+              {
+                "question": "Aperiam perferendis voluptatem est sit enim sed eaque perspiciatis enim. Est explicabo ea explicabo et et dignissimos aliquid?",
+                "answer": "Vel odio odit voluptatum ut veritatis. Ex rerum aspernatur voluptas unde officia. Dolorem officiis laboriosa odio odit voluptatum ut veritatis. Ex rerum aspernatur voluptas unde officia. Dolorem officiis laboriosa.",
+              },
+            ],
+        },
+    },
+  ]
+---
+
+{/* Rendered from frontmatter `sections[]`. Seed content — replace the plan names, prices and features above with your own before you launch. */}