create-ailk 0.4.0 → 0.6.0

package/dist/template-manifest.js

@@ -1,21 +1,17 @@
-/**
- * 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) {
@@ -24,19 +20,148 @@ export class TemplateError extends Error {
     }
 }
 /**
- * `/pricing`, `/privacy` and `/terms` — the three module-less rows every
- * declared template brings itself.
- *
- * 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. Registering the three as `GATEABLE_SURFACES` entries is #5479's; the
- * rows are declared here because the roster is what a template is.
+ * 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"] },
+];
+/**
+ * `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`.
+ *
+ * `/meet`, `/meet/[slug]`, `/meet/confirmed` and `/appointments` are absent
+ * here on purpose: they are the `scheduling` module's own
+ * `pageContributions`, merged in by `mergeRoster`. Declaring one here would
+ * make that merge refuse the template outright (§ D8's both-claimants
+ * refusal).
+ *
+ * `/purchase/success` and `/purchase/cancel` ARE declared here, and that is a
+ * documented divergence from spec § D3. The spec was written at a pin where
+ * #6084 was expected to add the pair to `MODULE_SLICES.commerce`'s
+ * `pageContributions`. It did not: the operator's shape-2 disposition
+ * (#6084 D12) ships the return pair BASE TREE — `CORE_ROUTE_DIRS` carries
+ * `[locale]/purchase`, and neither `GATEABLE_SURFACES` nor
+ * `MODULE_SURFACES.commerce` gained an entry — so the `commerce` slice
+ * contributes no rows at all and nothing else claims these two routes. The
+ * issue's AC-1 requires the merged roster to carry them; with no module
+ * claimant, the template's own roster is the only place that can declare
+ * them, and doing so trips no collision.
+ *
+ * `/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.
+ */
+const SIMPLE_SERVICE_ROSTER = [
+    { route: "/", content: ["content/en/HomePage/home.mdx"] },
+    { route: "/services", content: ["content/en/ServicesList/services.mdx"] },
+    { route: "/services/[slug]" },
+    { 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"] },
+    {
+        route: "/cancellation",
+        content: ["content/en/CancellationPolicyPage/cancellation.mdx"],
+    },
+    {
+        route: "/shipping",
+        content: ["content/en/ShippingPolicyPage/shipping.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" },
 ];
 /**
  * The three settled templates and their fixed `requires` lists — settled by
@@ -46,15 +171,21 @@ const TEMPLATE_BASE_ROSTER = [
  * `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 not express it in any case —
- * `RECOGNIZED_MODULES` is the six names and `workspace` is not among them.
+ * 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 = {
+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
@@ -63,7 +194,9 @@ export const TEMPLATE_MANIFESTS = {
     "marketing-site-free": {
         name: "marketing-site-free",
         requires: ["marketing"],
-        roster: TEMPLATE_BASE_ROSTER,
+        categories: ["accounting", "legal", "technology"],
+        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
@@ -73,6 +206,22 @@ export const TEMPLATE_MANIFESTS = {
     "marketing-site": {
         name: "marketing-site",
         requires: ["marketing", "docs-blog", "scheduling", "signal-collectors"],
+        // The flagship is the general-purpose template: it carries the whole
+        // registry, so every group tile on the hub has at least one template.
+        categories: [
+            "accounting",
+            "legal",
+            "hvac",
+            "roofing",
+            "plumbing",
+            "electrical",
+            "landscaping",
+            "auto-repair",
+            "real-estate",
+            "technology",
+            "medical-specialty",
+        ],
+        extends: BASE_LAYER_DIR,
         roster: TEMPLATE_BASE_ROSTER,
     },
     /**
@@ -93,9 +242,79 @@ export const TEMPLATE_MANIFESTS = {
             "signal-collectors",
             "multi-tenant",
         ],
+        categories: ["technology", "medical-specialty"],
+        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"],
+        categories: ["real-estate", "technology", "legal"],
+        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
+     * that composes `scheduling` and `commerce`: three priced services, a
+     * booker, a checkout return pair and the three #5947 policy pages.
+     *
+     * `requires` lists `marketing` for the registry convention every other
+     * manifest keeps: it is free (`module-tier.ts`'s `FREE_MODULES`), so it
+     * cannot change `templateDelivery`'s verdict, and listing it keeps the
+     * template's own declaration — not `DEFAULT_MODULES` — the authority for
+     * what a bare `--template simple-service` run installs. The order is
+     * `RECOGNIZED_MODULES` order, which is also `normalizeModules`' output
+     * order, so the declared list and the merge order read the same.
+     *
+     * `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.
+     */
+    "simple-service": {
+        name: "simple-service",
+        requires: ["marketing", "scheduling", "commerce"],
+        categories: ["landscaping"],
+        extends: BASE_LAYER_DIR,
+        roster: SIMPLE_SERVICE_ROSTER,
+    },
+});
 /** Look up a declared template. @throws TemplateError on an undeclared name. */
 export function resolveTemplate(name) {
     const manifest = TEMPLATE_MANIFESTS[name];
@@ -104,6 +323,39 @@ export function resolveTemplate(name) {
     }
     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).

package/dist/template-names.d.ts

@@ -37,5 +37,5 @@
  * 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"];
+export declare const RECOGNIZED_TEMPLATES: readonly ["marketing-site-free", "marketing-site", "saas-product", "minimalism-site", "simple-service"];
 export type TemplateName = (typeof RECOGNIZED_TEMPLATES)[number];

package/dist/template-names.js

@@ -41,4 +41,6 @@ export const RECOGNIZED_TEMPLATES = [
     "marketing-site-free",
     "marketing-site",
     "saas-product",
+    "minimalism-site",
+    "simple-service",
 ];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-ailk",
-  "version": "0.4.0",
+  "version": "0.6.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",
@@ -12,6 +12,8 @@
     "dist",
     "templates",
     "site-templates",
+    "versions.json",
+    "component-catalog.json",
     "component-catalog.md",
     "README.md",
     "LICENSE"
@@ -22,6 +24,10 @@
   "dependencies": {
     "tar": "^7.5.21"
   },
+  "devDependencies": {
+    "@working-theory/schema": "0.25.0",
+    "@working-theory/templates": "0.25.0"
+  },
   "repository": {
     "type": "git",
     "url": "git+https://github.com/working-theory-labs/ai-launch-kit.git",
@@ -50,6 +56,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. */}