create-ailk 0.6.1 → 0.7.0

package/templates/.claude/skills/suggest-site-pages/references/categories.md

@@ -1,287 +0,0 @@
-# Site-page categories — v1 corpus
-
-The 10 business categories `suggest-site-pages` knows about, with the
-ordered page list and primary schema.org type for each page. Schemas
-are drawn from the 60 page types `@working-theory/schema` builds; nothing in
-this file should reference a type the package can't generate.
-
-## How to read this file
-
-Each category section has:
-
-1. **Name and description** — what the category covers.
-2. **Entity tag** — `organization`, `person`, or `both`. Drives whether
-   `suggest-site-pages` asks the Person-vs-Organization disambiguation
-   question.
-3. **Page list** — ordered. The slug is what `scaffold-page` will use.
-4. **Primary schema per page** — the `Schema.orgType` to emit.
-
-When the entity tag is `both`, some pages (typically home, about,
-contact) carry an identity that flips between `Organization` and
-`Person` based on the consumer's answer. The page's _own_ schema type
-(`HomePage`, `AboutPage`, `ContactPage`) does not change; only the
-identity attached inside the JSON-LD does.
-
----
-
-## SaaS
-
-Software-as-a-service products — anything where the value prop is
-"sign up and use the software." Includes vertical SaaS, horizontal
-tools, dev platforms, and self-serve B2B.
-
-- **Entity tag:** `organization`
-- **Pages:**
-
-| Slug       | Schema.orgType | Purpose                                            |
-| ---------- | -------------- | -------------------------------------------------- |
-| `home`     | `HomePage`     | top-of-funnel landing with the headline value prop |
-| `about`    | `AboutPage`    | company story and team                             |
-| `pricing`  | `Product`      | public price tiers and feature comparison          |
-| `features` | `ServicesList` | what the product does, broken into capabilities    |
-| `contact`  | `ContactPage`  | sales and support entry point                      |
-| `privacy`  | `PrivacyPage`  | privacy policy                                     |
-| `terms`    | `TermsPage`    | terms of service                                   |
-
----
-
-## E-commerce
-
-Direct-to-consumer or B2B storefronts selling physical or digital
-goods. The catalog is the primary surface; everything else supports it.
-
-- **Entity tag:** `organization`
-- **Pages:**
-
-| Slug      | Schema.orgType | Purpose                                     |
-| --------- | -------------- | ------------------------------------------- |
-| `home`    | `HomePage`     | featured products and category entry points |
-| `shop`    | `ProductsList` | the full catalog                            |
-| `about`   | `AboutPage`    | brand story and what the company makes      |
-| `contact` | `ContactPage`  | customer-service entry point                |
-| `faq`     | `FAQPage`      | shipping, returns, sizing, common questions |
-| `privacy` | `PrivacyPage`  | privacy policy                              |
-| `terms`   | `TermsPage`    | terms of service                            |
-
-Per-product pages use `Product` and live under `shop/<product-slug>`.
-`scaffold-page` handles them one at a time once the user has the
-catalog page.
-
----
-
-## Service business
-
-Restaurant, salon, contractor, gym, plumber, cleaner — anyone whose
-business is "show up and do the work." Owner is usually an entity
-(LLC / corp), occasionally a sole proprietor.
-
-- **Entity tag:** `both`
-- **Pages:**
-
-| Slug           | Schema.orgType     | Purpose                                             |
-| -------------- | ------------------ | --------------------------------------------------- |
-| `home`         | `HomePage`         | what the business does, where, and how to book      |
-| `services`     | `ServicesList`     | menu of services offered                            |
-| `about`        | `AboutPage`        | the operator's story and credentials                |
-| `contact`      | `ContactPage`      | hours, address, booking link                        |
-| `testimonials` | `TestimonialsList` | customer reviews and quotes                         |
-| `faq`          | `FAQPage`          | common questions about service, pricing, scheduling |
-| `privacy`      | `PrivacyPage`      | privacy policy                                      |
-| `terms`        | `TermsPage`        | terms of service                                    |
-
-Individual services go under `services/<service-slug>` with `Service`
-as the type. The home/about/contact pages anchor on `Organization` for
-a business entity, `Person` for a sole proprietor.
-
----
-
-## Professional services
-
-Law firms, accounting firms, consulting shops, marketing agencies — fee-for-engagement
-expertise. Almost always firm-shaped at scale, but plenty of solo practitioners.
-
-- **Entity tag:** `both`
-- **Pages:**
-
-| Slug           | Schema.orgType    | Purpose                                           |
-| -------------- | ----------------- | ------------------------------------------------- |
-| `home`         | `HomePage`        | who the firm serves and what kinds of engagements |
-| `services`     | `ServicesList`    | practice areas or service lines                   |
-| `team`         | `TeamList`        | the people clients will work with                 |
-| `case-studies` | `CaseStudiesList` | engagement outcomes and references                |
-| `about`        | `AboutPage`       | firm history, philosophy, credentials             |
-| `contact`      | `ContactPage`     | how to reach out about an engagement              |
-| `blog`         | `BlogList`        | thought leadership and updates                    |
-| `privacy`      | `PrivacyPage`     | privacy policy                                    |
-| `terms`        | `TermsPage`       | terms of service                                  |
-
-For solo practitioners, drop the `team` page and anchor home/about/contact
-on `Person` instead of `Organization`.
-
----
-
-## Marketplace
-
-Two-sided platforms — buyers on one side, sellers/providers on the
-other. Always organizational; an individual cannot be a marketplace.
-
-- **Entity tag:** `organization`
-- **Pages:**
-
-| Slug          | Schema.orgType | Purpose                                          |
-| ------------- | -------------- | ------------------------------------------------ |
-| `home`        | `HomePage`     | the value prop for both sides of the marketplace |
-| `for-buyers`  | `ServicesList` | what buyers get and how it works                 |
-| `for-sellers` | `ServicesList` | what sellers get and how to onboard              |
-| `browse`      | `ProductsList` | the searchable catalog of listings               |
-| `about`       | `AboutPage`    | who runs the platform and why                    |
-| `contact`     | `ContactPage`  | support entry point                              |
-| `faq`         | `FAQPage`      | trust, payments, dispute resolution              |
-| `privacy`     | `PrivacyPage`  | privacy policy                                   |
-| `terms`       | `TermsPage`    | terms of service                                 |
-
----
-
-## Content / Blog
-
-Publications, personal blogs, newsletters with a website. The
-defining feature: posts are the primary surface, not products or
-services.
-
-- **Entity tag:** `both`
-- **Pages:**
-
-| Slug      | Schema.orgType | Purpose                                   |
-| --------- | -------------- | ----------------------------------------- |
-| `home`    | `HomePage`     | recent and featured posts                 |
-| `blog`    | `BlogList`     | the full archive                          |
-| `about`   | `AboutPage`    | who writes and why                        |
-| `contact` | `ContactPage`  | how to reach the author or editorial team |
-| `privacy` | `PrivacyPage`  | privacy policy                            |
-| `terms`   | `TermsPage`    | terms of service                          |
-
-Individual posts use `BlogPosting`. A "personal" blog (one writer,
-their name on the site) is `Person`; an editorial publication with a
-masthead is `Organization`. Phrases like "personal" or "my" in the
-description settle it as Person without asking.
-
----
-
-## Course / Education
-
-Course providers, schools, online academies, individual instructors
-selling courses. Core surface is the course catalog.
-
-- **Entity tag:** `both`
-- **Pages:**
-
-| Slug           | Schema.orgType     | Purpose                                          |
-| -------------- | ------------------ | ------------------------------------------------ |
-| `home`         | `HomePage`         | who the courses are for and the headline outcome |
-| `courses`      | `CoursesList`      | catalog of available courses                     |
-| `about`        | `AboutPage`        | instructor or institution story                  |
-| `testimonials` | `TestimonialsList` | student outcomes and quotes                      |
-| `contact`      | `ContactPage`      | enrollment and support                           |
-| `faq`          | `FAQPage`          | format, prerequisites, certification             |
-| `privacy`      | `PrivacyPage`      | privacy policy                                   |
-| `terms`        | `TermsPage`        | terms of service                                 |
-
-Individual courses use `Course`. A solo instructor anchors on `Person`;
-a school anchors on `Organization`.
-
----
-
-## Real estate
-
-Brokerages, individual agents, property-management firms. The
-disambiguation matters here: a solo agent's site looks different from
-a brokerage's.
-
-- **Entity tag:** `both`
-- **Pages:**
-
-| Slug           | Schema.orgType     | Purpose                                                 |
-| -------------- | ------------------ | ------------------------------------------------------- |
-| `home`         | `HomePage`         | what kinds of properties and which markets              |
-| `listings`     | `ProductsList`     | available properties (treat each property as a Product) |
-| `services`     | `ServicesList`     | buyer / seller / rental representation                  |
-| `about`        | `AboutPage`        | the agent's or brokerage's story and credentials        |
-| `team`         | `TeamList`         | the agents at the brokerage (skip for solo agents)      |
-| `testimonials` | `TestimonialsList` | client reviews                                          |
-| `contact`      | `ContactPage`      | how to reach out about a property                       |
-| `privacy`      | `PrivacyPage`      | privacy policy                                          |
-| `terms`        | `TermsPage`        | terms of service                                        |
-
-Words like "brokerage", "team", "our agents" → `Organization`. "Solo
-agent", "I represent" → `Person`. Drop the `team` page for solo
-agents.
-
----
-
-## Healthcare / Medical
-
-Clinics, solo practitioners, group practices, dental offices,
-therapists, specialty practices. Privacy and credibility are
-load-bearing here.
-
-- **Entity tag:** `both`
-- **Pages:**
-
-| Slug       | Schema.orgType | Purpose                                                |
-| ---------- | -------------- | ------------------------------------------------------ |
-| `home`     | `HomePage`     | what care is offered and for whom                      |
-| `services` | `ServicesList` | conditions treated and procedures offered              |
-| `team`     | `TeamList`     | the providers (skip for solo practitioners)            |
-| `about`    | `AboutPage`    | practice philosophy, credentials, affiliations         |
-| `faq`      | `FAQPage`      | insurance, scheduling, what to expect                  |
-| `contact`  | `ContactPage`  | hours, address, intake form link                       |
-| `privacy`  | `PrivacyPage`  | privacy policy (HIPAA-relevant; flag this to the user) |
-| `terms`    | `TermsPage`    | terms of service                                       |
-
-Solo practitioner → `Person`; clinic or group practice → `Organization`.
-Drop `team` for solo practitioners.
-
-When emitting the privacy line, mention HIPAA: "Healthcare sites need
-a HIPAA-aware privacy policy. The default `PrivacyPage` is a starting
-point, not a finished policy."
-
----
-
-## Nonprofit / Org
-
-Nonprofits, advocacy groups, professional associations, foundations.
-Always organizational by nature; even a one-person foundation
-operates as an entity.
-
-- **Entity tag:** `organization`
-- **Pages:**
-
-| Slug       | Schema.orgType | Purpose                                                       |
-| ---------- | -------------- | ------------------------------------------------------------- |
-| `home`     | `HomePage`     | mission and what the org does this year                       |
-| `programs` | `ServicesList` | programs the org runs                                         |
-| `about`    | `AboutPage`    | history, mission, governance                                  |
-| `team`     | `TeamList`     | staff and board                                               |
-| `partners` | `PartnersList` | funders, partners, supporting organizations                   |
-| `events`   | `EventsList`   | upcoming events and campaigns                                 |
-| `donate`   | `Service`      | donation entry point (treat the act of donating as a Service) |
-| `contact`  | `ContactPage`  | how to reach the org                                          |
-| `privacy`  | `PrivacyPage`  | privacy policy                                                |
-| `terms`    | `TermsPage`    | terms of service                                              |
-
----
-
-## Schema-builder coverage
-
-Every `Schema.orgType` referenced above is a member of the
-`SchemaOrgType` union exported by `@working-theory/schema` and has a builder
-function. The v1 catalog uses 21 of the 60 supported types:
-
-`HomePage`, `AboutPage`, `ContactPage`, `PrivacyPage`, `TermsPage`,
-`Organization`, `Person`, `ServicesList`, `Service`, `ProductsList`,
-`Product`, `FAQPage`, `TestimonialsList`, `TeamList`, `PartnersList`,
-`EventsList`, `CoursesList`, `Course`, `BlogList`, `BlogPosting`,
-`CaseStudiesList`.
-
-The remaining 39 types are available to `scaffold-page` and `add-schema`
-for per-page use but don't drive category recommendations.

package/templates/apps/web/app/[locale]/cancellation/page.tsx

@@ -1,44 +0,0 @@
-// CancellationPolicyPage route (#5947). Reads the CancellationPolicyPage MDX frontmatter, renders sections via
-// SectionRenderer, and emits a JSON-LD <script>.
-import type {
-  getMdxSource as defaultGetMdxSource,
-  getPageSections as defaultGetPageSections} from "@working-theory/page-renderer";
-import {
-  renderPage,
-  renderPageMetadata
-} from "@working-theory/page-renderer";
-import type { Metadata } from "next";
-import type { ReactElement } from "react";
-
-interface Props {
-  params: Promise<{ locale: string }>;
-  getMdxSource?: typeof defaultGetMdxSource;
-  getPageSections?: typeof defaultGetPageSections;
-}
-
-export async function generateMetadata({
-  params,
-}: Pick<Props, "params">): Promise<Metadata> {
-  const { locale } = await params;
-  return renderPageMetadata({ type: "CancellationPolicyPage", slug: "cancellation", locale });
-}
-
-export default async function Page({
-  params,
-  getMdxSource,
-  getPageSections,
-}: Props): Promise<ReactElement> {
-  const { locale } = await params;
-  return renderPage({
-    type: "CancellationPolicyPage",
-    slug: "cancellation",
-    locale,
-    // Without a namespace `renderPage` 404s on a missing seed — and a scaffold
-    // IS a missing-seed environment, since `build-templates.mjs` snapshots
-    // `apps/` but deliberately not `content/`. The namespace makes this route
-    // render the #4154 authoring empty state at 200, exactly as /terms does.
-    translationsNamespace: "cancellation",
-    ...(getMdxSource !== undefined && { getMdxSource }),
-    ...(getPageSections !== undefined && { getPageSections }),
-  });
-}

package/templates/apps/web/app/[locale]/returns/page.tsx

@@ -1,44 +0,0 @@
-// ReturnsPolicyPage route (#5947). Reads the ReturnsPolicyPage MDX frontmatter, renders sections via
-// SectionRenderer, and emits a JSON-LD <script>.
-import type {
-  getMdxSource as defaultGetMdxSource,
-  getPageSections as defaultGetPageSections} from "@working-theory/page-renderer";
-import {
-  renderPage,
-  renderPageMetadata
-} from "@working-theory/page-renderer";
-import type { Metadata } from "next";
-import type { ReactElement } from "react";
-
-interface Props {
-  params: Promise<{ locale: string }>;
-  getMdxSource?: typeof defaultGetMdxSource;
-  getPageSections?: typeof defaultGetPageSections;
-}
-
-export async function generateMetadata({
-  params,
-}: Pick<Props, "params">): Promise<Metadata> {
-  const { locale } = await params;
-  return renderPageMetadata({ type: "ReturnsPolicyPage", slug: "returns", locale });
-}
-
-export default async function Page({
-  params,
-  getMdxSource,
-  getPageSections,
-}: Props): Promise<ReactElement> {
-  const { locale } = await params;
-  return renderPage({
-    type: "ReturnsPolicyPage",
-    slug: "returns",
-    locale,
-    // Without a namespace `renderPage` 404s on a missing seed — and a scaffold
-    // IS a missing-seed environment, since `build-templates.mjs` snapshots
-    // `apps/` but deliberately not `content/`. The namespace makes this route
-    // render the #4154 authoring empty state at 200, exactly as /terms does.
-    translationsNamespace: "returns",
-    ...(getMdxSource !== undefined && { getMdxSource }),
-    ...(getPageSections !== undefined && { getPageSections }),
-  });
-}

package/templates/content/en/CancellationPolicyPage/cancellation.mdx

@@ -1,108 +0,0 @@
----
-type: "CancellationPolicyPage"
-slug: "cancellation"
-title: "Cancellation Policy"
-description: "How to cancel or reschedule a booking on this site, the notice required, and what a late cancellation or no-show costs."
-updatedAt: "2026-09-17"
-sections:
-  [
-    {
-      "id": "cancellation-document",
-      "type": "document-chassis",
-      "data":
-        {
-          "headline": "Cancellation Policy",
-          "backHref": "/",
-          "backLabel": "Back home",
-          "navGroupLabel": "Contents",
-          "stats":
-            [
-              { "label": "Last updated", "sublabel": "17 September 2026" },
-              { "label": "Applies to", "sublabel": "Bookings made on this site" },
-            ],
-          "sections":
-            [
-              {
-                "id": "intro",
-                "heading": "Cancellation Policy",
-                "blocks":
-                  [
-                    {
-                      "kind": "paragraph",
-                      "text": "This page explains how cancellations and reschedules work for bookings made on this site. Replace the starter copy below with the policy you actually operate — the headings are the ones a customer and an agent both look for, so keep them and fill in your own terms.",
-                    },
-                  ],
-              },
-              {
-                "id": "notice",
-                "heading": "How much notice is required",
-                "blocks":
-                  [
-                    {
-                      "kind": "paragraph",
-                      "text": "State the notice period in hours before the appointment, and say how it is measured. A customer reading at midnight should be able to work out, without arithmetic you have not shown them, whether they are still inside it.",
-                    },
-                  ],
-              },
-              {
-                "id": "how-to-cancel",
-                "heading": "How to cancel or reschedule",
-                "blocks":
-                  [
-                    {
-                      "kind": "paragraph",
-                      "text": "Give one route to cancel and one to reschedule, and say whether a reschedule inside the notice period counts as a cancellation. If a booking confirmation carries a self-service link, name it here.",
-                    },
-                  ],
-              },
-              {
-                "id": "fees",
-                "heading": "Late cancellations and no-shows",
-                "blocks":
-                  [
-                    {
-                      "kind": "paragraph",
-                      "text": "Say what a late cancellation costs and what a no-show costs, as a figure or a share of the booking, and when each is charged. If you hold a deposit, say what happens to it in each case.",
-                    },
-                  ],
-              },
-              {
-                "id": "our-cancellations",
-                "heading": "If we cancel",
-                "blocks":
-                  [
-                    {
-                      "kind": "paragraph",
-                      "text": "Set out what a customer gets if you cancel or move an appointment — a full refund, a rebooking, or both — and how quickly you tell them. A policy that only binds one side reads as one.",
-                    },
-                  ],
-              },
-              {
-                "id": "exceptions",
-                "heading": "Exceptions",
-                "blocks":
-                  [
-                    {
-                      "kind": "paragraph",
-                      "text": "Name the circumstances in which you waive a fee — illness, bereavement, severe weather — and say what you need from the customer to apply the waiver. Vague discretion is worse for you than a short written list.",
-                    },
-                  ],
-              },
-              {
-                "id": "contact",
-                "heading": "Questions about a booking",
-                "blocks":
-                  [
-                    {
-                      "kind": "paragraph",
-                      "text": "Point to the one place a customer should write, and say roughly how quickly you answer.",
-                    },
-                  ],
-              },
-            ],
-        },
-    },
-  ]
----
-
-{/* Rendered from frontmatter `sections[]`; the MDX body is not read by the section-catalog renderer. schema.org has no cancellation-policy type, so this page emits a plain WebPage (#5947, D2) — a real policy field reaches the JSON-LD through the `schema:` escape hatch, never a coined @type. */}

package/templates/content/en/LandingPage/blog.mdx

@@ -1,83 +0,0 @@
----
-type: "LandingPage"
-slug: "blog"
-title: "Resources for {customer profile}"
-description: "Lorem ipsum dolor sit amet, consectetur adipiscing elit."
-sections:
-  [
-    {
-      "id": "hero",
-      "type": "hero",
-      "data":
-        {
-          "variant": "centered",
-          "eyebrow": "Blog",
-          "headline": "Resources for {customer profile}",
-          "subheadline": "Lorem ipsum dolor sit amet, consectetur adipiscing elit.",
-        },
-    },
-    {
-      "id": "pro-blog",
-      "type": "cta",
-      "data":
-        {
-          "headline": "The blog listing ships with the Pro docs-blog module",
-          "description": "This Free site carries one static resources page. The Pro docs-blog module adds the full blog — MDX posts, the paginated listing and the documentation surface — at this same /blog route; install it and this page is replaced by the real listing.",
-          "primaryCta": { "label": "See Pro pricing", "href": "/pricing" },
-          "secondaryCta":
-            { "label": "Talk to us", "href": "/contact", "variant": "outline" },
-        },
-    },
-    {
-      "id": "newsletter",
-      "type": "newsletter",
-      "data":
-        {
-          "headline": "Stay Up to Date with our {fequency} Newsletter",
-          "description": "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.",
-          "placeholder": "Enter your email",
-          "submitLabel": "Sign Up",
-          "consentText": "By clicking Sign Up you're confirming that you agree with our Terms and Conditions",
-          "successMessage": "Thank you! Your submission has been received!",
-          "action": "/v1/leads/subscribe",
-        },
-    },
-    {
-      "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",
-              },
-            ],
-        },
-    },
-  ]
----
-
-{/* The Free blog teaser (one static page, rendered by the generic `[slug]` route). With the Pro docs-blog module installed its own `blog/` route directory takes precedence and this file is inert. Placeholder copy — replace before you launch. */}

package/templates/content/en/LandingPage/features.mdx

@@ -1,103 +0,0 @@
----
-type: "LandingPage"
-slug: "features"
-title: "Medium length section heading goes here"
-description: "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."
-sections:
-  [
-    {
-      "id": "core-features",
-      "type": "feature",
-      "data": {
-        "eyebrow": "Core Features",
-        "headline": "Medium length section heading goes here",
-        "description": "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.",
-        "features": [
-          {
-            "title": "Feature 1",
-            "description": "Explain what a feature enables your customers to do in plain English. Avoid industry jargon.",
-            "link": {
-              "label": "Learn More",
-              "href": "/features"
-            }
-          },
-          {
-            "title": "Feature 2",
-            "description": "Explain what a feature enables your customers to do in plain English. Avoid industry jargon.",
-            "link": {
-              "label": "Learn More",
-              "href": "/features"
-            }
-          },
-          {
-            "title": "Feature 4",
-            "description": "Explain what a feature enables your customers to do in plain English. Avoid industry jargon.",
-            "link": {
-              "label": "Learn More",
-              "href": "/features"
-            }
-          },
-          {
-            "title": "Feature 3",
-            "description": "Explain what a feature enables your customers to do in plain English. Avoid industry jargon.",
-            "link": {
-              "label": "Learn More",
-              "href": "/features"
-            }
-          },
-          {
-            "title": "Feature 5",
-            "description": "Explain what a feature enables your customers to do in plain English. Avoid industry jargon.",
-            "link": {
-              "label": "Learn More",
-              "href": "/features"
-            }
-          }
-        ]
-      }
-    },
-    {
-      "id": "integrations",
-      "type": "cta",
-      "data": {
-        "headline": "Direct integrations with your favorite tools",
-        "description": "Describe what these integrations help your customers do and impressive facts about how they work.",
-        "primaryCta": {
-          "label": "Get Started",
-          "href": "/contact"
-        },
-        "secondaryCta": {
-          "label": "See all Integrations",
-          "href": "/features",
-          "variant": "outline"
-        }
-      }
-    },
-    {
-      "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}"
-      }
-    }
-  ]
----
-
-{/* Rendered from frontmatter `sections[]` by the generic `[slug]` route. Placeholder copy, verbatim from the reference — replace before you launch. */}