create-ailk 0.7.0 → 0.9.0

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

@@ -1,23 +0,0 @@
-{
-  "name": "minimalism-site",
-  "requires": ["marketing", "scheduling", "signal-collectors"],
-  "extends": "_base",
-  "$comment": "The second Pro template (#5589) — the reports-first, scroll-snap deck site. NOT marketing-site plus a module: requires omits docs-blog, so this template and marketing-site are siblings under _base (#5618 D2), never a lineage. Composed base → modules → template: /privacy and /terms arrive with the _base layer this extends (its unrostered /pricing seed does not install, #6646); /meet, /meet/<slug> and /meet/confirmed with the scheduling bundle; the /flows/* routes, the /reports/<slug> reader route and the sample report PDF at apps/web/public/reports/sample-report.pdf with the signal-collectors bundle; the Free contact/faq/about compositions with the overlay, which this template's own /about, /contact and /faq files then override; the overlay's other seeds (/use-cases, the /software/product page, the /blog teaser) are unrostered here and do not install (#6646). This tree holds ONLY its own compositions, its placeholder copy and its generated placeholder assets. layout (nav mark-only, footer centered, announcementBanner off, home deck) is the minimalism design's, supplied by DESIGN_LAYOUTS from the TEMPLATE_MANIFESTS entry's design field (#6638), not declared here — the code registry is authoritative for a template create-ailk ships, and a block here would be a second authority for one fact. installMap: bundle-relative source -> scaffold-relative destination; the stager reads only installMap/postInstall/patches. Unmapped content/en/** lands at the scaffold root's content/, exactly as marketing-site-free's does.",
-  "installMap": {
-    "provenance.json": ".ailk-template.json",
-    "TEMPLATE-MANIFEST.json": ".ailk-site-manifest.json",
-    "assets/hero-backdrop.svg": "apps/web/public/hero-backdrop.svg",
-    "assets/wordmark-placeholder.svg": "apps/web/public/wordmark-placeholder.svg",
-    "assets/logo-placeholder-1.svg": "apps/web/public/logo-placeholder-1.svg",
-    "assets/logo-placeholder-2.svg": "apps/web/public/logo-placeholder-2.svg",
-    "assets/logo-placeholder-3.svg": "apps/web/public/logo-placeholder-3.svg",
-    "assets/avatar-placeholder-1.svg": "apps/web/public/avatar-placeholder-1.svg",
-    "assets/avatar-placeholder-2.svg": "apps/web/public/avatar-placeholder-2.svg",
-    "assets/avatar-placeholder-3.svg": "apps/web/public/avatar-placeholder-3.svg",
-    "assets/avatar-placeholder-4.svg": "apps/web/public/avatar-placeholder-4.svg",
-    "assets/avatar-placeholder-5.svg": "apps/web/public/avatar-placeholder-5.svg",
-    "assets/avatar-placeholder-6.svg": "apps/web/public/avatar-placeholder-6.svg",
-    "flows/referral.flow.json": "database/flows/referral.flow.json"
-  },
-  "postInstall": "Template minimalism-site installed. The home page is a NINE-SLIDE SCROLL-SNAP DECK (content/en/HomePage/home.mdx): one full-viewport panel per section, the brand mark hidden on slide 1 and revealed from slide 2 on, no nav items, and the footer bottom bar carrying Privacy, Terms, FAQ, the social row, the theme toggle and the locale switcher. Its module pages arrived with their bundles: the booker at /meet from scheduling, the report reader at /reports/<slug> and the flow routes from signal-collectors; /privacy, /terms, /glossary and /newsletter came with the base layer, and /book-a-call is this template's own override of the base seed, its call to action opening the /meet booker. This template adds the deck, /reports, /about, /services (+ three samples), /contact, /faq, /referral, four sample reports and the referral flow at /flows/referral/start. RENAMING /about: many sites want /partners, /team, /family or /company instead. That is a route rename in YOUR scaffold, never a content move - keep content/en/AboutPage/ (AboutPage is a schema type, not a URL), rename the route directory (git mv 'apps/web/app/[locale]/about' 'apps/web/app/[locale]/partners'), and update the one footer label that names it (messages/<locale>.json). Once the routes map ships in the scaffold it is one row: the /about row's route plus a legacyRoutes entry so the old path 301s. EVERY line of copy, all four sample reports, the three logo placeholders, the six portrait placeholders, the wordmark lockup on slide 1 and the hero backdrop are placeholders - replace them before you launch."
-}

package/site-templates/minimalism-site/content/en/AboutPage/about.mdx

@@ -1,110 +0,0 @@
----
-type: "AboutPage"
-slug: "about"
-title: "About"
-description: "The people behind {your company}. Placeholder copy and placeholder portraits — replace both before you launch."
-sections:
-  [
-    {
-      "id": "intro",
-      "type": "content-block",
-      "data":
-        {
-          "variant": "narrow",
-          "eyebrow": "About",
-          "headline": "We work with a small number of {the people you serve}, for a long time",
-          "body": "{Two or three sentences on how the practice started, what it does now, and what it refuses to do. Keep the paragraph short — this page is read standing up.}",
-        },
-    },
-    {
-      "id": "partners",
-      "type": "team",
-      "data":
-        {
-          "headline": "Partners",
-          "variant": "with-large-images",
-          "hoverReveal": true,
-          "largePhotos": true,
-          "members":
-            [
-              {
-                "name": "{Name One}",
-                "role": "{Role}",
-                "bio": "{One line on what this person does here.}",
-                "avatar":
-                  { "src": "/avatar-placeholder-1.svg", "alt": "{Name One}" },
-              },
-              {
-                "name": "{Name Two}",
-                "role": "{Role}",
-                "bio": "{One line on what this person does here.}",
-                "avatar":
-                  { "src": "/avatar-placeholder-2.svg", "alt": "{Name Two}" },
-              },
-              {
-                "name": "{Name Three}",
-                "role": "{Role}",
-                "bio": "{One line on what this person does here.}",
-                "avatar":
-                  { "src": "/avatar-placeholder-3.svg", "alt": "{Name Three}" },
-              },
-              {
-                "name": "{Name Four}",
-                "role": "{Role}",
-                "bio": "{One line on what this person does here.}",
-                "avatar":
-                  { "src": "/avatar-placeholder-4.svg", "alt": "{Name Four}" },
-              },
-              {
-                "name": "{Name Five}",
-                "role": "{Role}",
-                "bio": "{One line on what this person does here.}",
-                "avatar":
-                  { "src": "/avatar-placeholder-5.svg", "alt": "{Name Five}" },
-              },
-              {
-                "name": "{Name Six}",
-                "role": "{Role}",
-                "bio": "{One line on what this person does here.}",
-                "avatar":
-                  { "src": "/avatar-placeholder-6.svg", "alt": "{Name Six}" },
-              },
-            ],
-        },
-    },
-    {
-      "id": "closing",
-      "type": "cta",
-      "data":
-        {
-          "variant": "minimal",
-          "headline": "Work with us",
-          "primaryCta": { "label": "Hire me →", "href": "/meet" },
-          "secondaryCta":
-            {
-              "label": "Contact me →",
-              "href": "/contact",
-              "variant": "outline",
-            },
-        },
-    },
-  ]
----
-
-{/\*
-RENAMING THIS PAGE. A site whose partners page should read `/partners`,
-`/team`, `/family` or `/company` renames it in two moves, both in the
-scaffold, neither of them here:
-
-    1. `git mv content/en/AboutPage content/en/<NewType>` is NOT one of them —
-       `AboutPage` is a content TYPE in the schema registry, not a URL. Keep the
-       directory. Rename the ROUTE:
-       `git mv "apps/web/app/[locale]/about" "apps/web/app/[locale]/partners"`.
-    2. Point the renamed route at the same content and update the one nav/footer
-       label that names it (`apps/web/lib/nav-config.ts`, `messages/<locale>.json`).
-
-Once #5572's routes map lands in the scaffold this collapses to ONE row —
-the `/about` row's `route` (and its `legacyRoutes` entry, so the old path
-301s). Documented, never implemented here: a template declares pages, it does
-not move a customer's routes for them.
-\*/}

package/site-templates/minimalism-site/content/en/BookCall/book-call.mdx

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

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

@@ -1,34 +0,0 @@
----
-type: "ContactPage"
-slug: "contact"
-title: "Contact"
-description: "One form, one field group, an inline confirmation. Placeholder copy — replace before you launch."
-sections:
-  [
-    {
-      "id": "hero",
-      "type": "hero",
-      "data":
-        {
-          "variant": "centered",
-          "eyebrow": "Contact",
-          "headline": "Say what you are trying to do",
-          "subheadline": "{One line on what happens after you send this, and how long it takes.}",
-        },
-    },
-    {
-      "id": "closing",
-      "type": "cta",
-      "data":
-        {
-          "variant": "minimal",
-          "headline": "Would a call be faster?",
-          "primaryCta": { "label": "Hire me →", "href": "/meet" },
-        },
-    },
-  ]
----
-
-{/_ The /contact route mounts the page's one contact surface — the guided
-intake, with its fallback form — which posts to the site's own API
-(`/v1/leads/submit`) and confirms inline. Placeholder copy. _/}

package/site-templates/minimalism-site/content/en/FAQPage/faq.mdx

@@ -1,57 +0,0 @@
----
-type: "FAQPage"
-slug: "faq"
-title: "FAQ"
-description: "The questions people ask before they get in touch. Placeholder copy — replace every answer before you launch."
-sections:
-  [
-    {
-      "id": "faq",
-      "type": "faq",
-      "data":
-        {
-          "headline": "Questions",
-          "variant": "centered",
-          "initialOpen": "first",
-          "items":
-            [
-              {
-                "question": "{What exactly do you do?}",
-                "answer": "{Answer in two or three sentences. Say the thing plainly; do not sell here.}",
-              },
-              {
-                "question": "{Who is this for, and who is it not for?}",
-                "answer": "{Name both. A reader who rules themselves out here is a reader you did not waste an hour on.}",
-              },
-              {
-                "question": "{How long does it take?}",
-                "answer": "{Give a real range and say what moves it.}",
-              },
-              {
-                "question": "{What does it cost?}",
-                "answer": "{Give the shape even if you cannot give the number — fixed fee, retainer, day rate — and what it excludes.}",
-              },
-              {
-                "question": "{How do the reports work?}",
-                "answer": "{One or two sentences on cadence, who gets them and whether they are public.}",
-              },
-            ],
-          "supportLink":
-            { "label": "Still stuck? Get in touch", "href": "/contact" },
-        },
-    },
-    {
-      "id": "closing",
-      "type": "cta",
-      "data":
-        {
-          "variant": "minimal",
-          "headline": "Still have a question?",
-          "primaryCta": { "label": "Contact me →", "href": "/contact" },
-        },
-    },
-  ]
----
-
-{/_ Linked from the footer bottom bar, not from a nav item — this template
-renders no nav items (`layout.nav: "mark-only"`). Placeholder copy. _/}

package/site-templates/minimalism-site/content/en/LandingPage/referral.mdx

@@ -1,77 +0,0 @@
----
-type: "LandingPage"
-slug: "referral"
-title: "Refer someone"
-description: "The referral magnet — what a referrer gets, and the one-step request that starts it. Placeholder copy; replace before you launch."
-sections:
-  [
-    {
-      "id": "hero",
-      "type": "hero",
-      "data":
-        {
-          "variant": "centered",
-          "eyebrow": "Referrals",
-          "headline": "Know someone who should be on this list?",
-          "subheadline": "{One line on why an introduction is worth making — what the person you refer gets, and what you get.}",
-          "checklist":
-            [
-              "{What a good referral looks like}",
-              "{What happens after you send one}",
-              "{What you get when it lands}",
-            ],
-          "primaryCta":
-            { "label": "Refer someone →", "href": "/flows/referral/start" },
-          "ctaSize": "xl",
-        },
-    },
-    {
-      "id": "how-it-works",
-      "type": "stair-steps",
-      "data":
-        {
-          "headline": "Three steps, about a minute",
-          "tiles":
-            [
-              {
-                "title": "Send the introduction",
-                "body": "{One line on what you tell us — a name, a way to reach them, one sentence of why.}",
-              },
-              {
-                "title": "We reach out",
-                "body": "{One line on the timeline and the tone of the first message.}",
-              },
-              {
-                "title": "You hear back either way",
-                "body": "{One line on what you are told, and when.}",
-              },
-            ],
-        },
-    },
-    {
-      "id": "request",
-      "type": "cta",
-      "data":
-        {
-          "variant": "minimal",
-          "headline": "Make an introduction",
-          "description": "{One line restating the ask. Keep it to a single sentence.}",
-          "primaryCta":
-            { "label": "Refer someone →", "href": "/flows/referral/start" },
-        },
-    },
-  ]
----
-
-{/\*
-The magnet's pitch. Its bottom action opens the referral REQUEST, which is a
-`signal-collectors` flow at `/flows/referral/start` — `flows/referral.flow.json`
-in this tree, installed to `database/flows/referral.flow.json`.
-
-Why a flow and not a `/referral/request` route: the issue named that path, but
-it has no `ROUTES` row and no route directory, so serving it would mean
-shipping a `page.tsx` into every scaffold for one template's page — which a
-template may never do (a template is data and content, never code). The flow
-engine already serves exactly this shape at a route every signal-collectors
-scaffold has. Recorded on #5589 and in the PR body; Sam's call supersedes.
-\*/}

package/site-templates/minimalism-site/content/en/LandingPage/reports.mdx

@@ -1,73 +0,0 @@
----
-type: "LandingPage"
-slug: "reports"
-title: "Reports"
-description: "Every report {your company} has published, newest first. Placeholder samples — replace before you launch."
-sections:
-  [
-    {
-      "id": "hero",
-      "type": "hero",
-      "data":
-        {
-          "variant": "centered",
-          "eyebrow": "Reports",
-          "headline": "Research on {your field}, published in full",
-          "subheadline": "{One line on the cadence: how often a report lands and who it is written for.}",
-        },
-    },
-    {
-      "id": "all-reports",
-      "type": "reports-list",
-      "data":
-        {
-          "variant": "cards",
-          "reports":
-            [
-              {
-                "slug": "state-of-the-market-2026",
-                "title": "State of {Your Market} 2026",
-                "date": "May 2026",
-                "description": "{One line on the question this report answers.}",
-              },
-              {
-                "slug": "platform-shift-2025",
-                "title": "The {Platform Shift} Report",
-                "date": "March 2025",
-                "description": "{One line on the question this report answers.}",
-              },
-              {
-                "slug": "annual-letter-2024",
-                "title": "Annual Letter",
-                "date": "December 2024",
-                "description": "{One line on the question this report answers.}",
-              },
-              {
-                "slug": "field-notes-2023",
-                "title": "Field Notes",
-                "date": "2023",
-                "description": "{One line on the question this report answers.}",
-              },
-            ],
-        },
-    },
-    {
-      "id": "closing",
-      "type": "cta",
-      "data":
-        {
-          "variant": "minimal",
-          "headline": "Want the next one as it lands?",
-          "primaryCta": { "label": "Contact me →", "href": "/contact" },
-        },
-    },
-  ]
----
-
-{/_
-`/reports` is served by the generic `[slug]` route over
-`content/<locale>/LandingPage/reports.mdx` (#5469 D2) — the same mechanism
-Free's `/how-it-works` uses, and the reason this row needs no route directory
-and no `GATEABLE_SURFACES` entry. Each card links to `/reports/<slug>`, the
-signal-collectors module's chrome-off reader (#5562).
-_/}

package/site-templates/minimalism-site/content/en/ReportPage/annual-letter-2024.mdx

@@ -1,52 +0,0 @@
----
-type: "ReportPage"
-slug: "annual-letter-2024"
-title: "Annual Letter"
-description: "{One line on the question this report answers. Replace before you launch.}"
-schema:
-  datePublished: "2024-12-09"
-  author:
-    "@type": Organization
-    name: "Your Company"
-sections:
-  [
-    {
-      "id": "header",
-      "type": "report-header",
-      "data":
-        {
-          "title": "Annual Letter",
-          "eyebrow": "December 2024",
-          "backHref": "/reports",
-          "backLabel": "All reports",
-          "tone": "on-dark",
-        },
-    },
-    {
-      "id": "document",
-      "type": "document-viewer",
-      "data":
-        {
-          "src": "/reports/sample-report.pdf",
-          "geometry": "16:9",
-          "pages": 8,
-          "downloadFilename": "annual-letter-2024.pdf",
-          "outline":
-            [
-              { "id": "opening", "label": "Opening", "startPage": 1 },
-              { "id": "findings", "label": "Findings", "startPage": 3 },
-              { "id": "outlook", "label": "Outlook", "startPage": 6 },
-            ],
-        },
-    },
-  ]
----
-
-{/_
-A PLACEHOLDER report. Its bytes are the signal-collectors module's own sample
-PDF (`apps/web/public/reports/sample-report.pdf`, installed by that module's
-bundle), shared by all four samples so the template ships no binary of its
-own. Point `src` at your real document and set `pages` to its real page
-count — the count reserves the reader's layout before the renderer loads, so
-a wrong number shows as a jump.
-_/}

package/site-templates/minimalism-site/content/en/ReportPage/field-notes-2023.mdx

@@ -1,52 +0,0 @@
----
-type: "ReportPage"
-slug: "field-notes-2023"
-title: "Field Notes"
-description: "{One line on the question this report answers. Replace before you launch.}"
-schema:
-  datePublished: "2023-09-19"
-  author:
-    "@type": Organization
-    name: "Your Company"
-sections:
-  [
-    {
-      "id": "header",
-      "type": "report-header",
-      "data":
-        {
-          "title": "Field Notes",
-          "eyebrow": "2023",
-          "backHref": "/reports",
-          "backLabel": "All reports",
-          "tone": "on-dark",
-        },
-    },
-    {
-      "id": "document",
-      "type": "document-viewer",
-      "data":
-        {
-          "src": "/reports/sample-report.pdf",
-          "geometry": "16:9",
-          "pages": 8,
-          "downloadFilename": "field-notes-2023.pdf",
-          "outline":
-            [
-              { "id": "opening", "label": "Opening", "startPage": 1 },
-              { "id": "findings", "label": "Findings", "startPage": 3 },
-              { "id": "outlook", "label": "Outlook", "startPage": 6 },
-            ],
-        },
-    },
-  ]
----
-
-{/_
-A PLACEHOLDER report. Its bytes are the signal-collectors module's own sample
-PDF (`apps/web/public/reports/sample-report.pdf`, installed by that module's
-bundle), shared by all four samples so the template ships no binary of its
-own. Point `src` at your real document and set `pages` to its real page
-count — the count reserves the reader's layout before the renderer loads, so
-a wrong number shows as a jump.
-_/}

package/site-templates/minimalism-site/content/en/ReportPage/platform-shift-2025.mdx

@@ -1,52 +0,0 @@
----
-type: "ReportPage"
-slug: "platform-shift-2025"
-title: "The {Platform Shift} Report"
-description: "{One line on the question this report answers. Replace before you launch.}"
-schema:
-  datePublished: "2025-03-11"
-  author:
-    "@type": Organization
-    name: "Your Company"
-sections:
-  [
-    {
-      "id": "header",
-      "type": "report-header",
-      "data":
-        {
-          "title": "The {Platform Shift} Report",
-          "eyebrow": "March 2025",
-          "backHref": "/reports",
-          "backLabel": "All reports",
-          "tone": "on-dark",
-        },
-    },
-    {
-      "id": "document",
-      "type": "document-viewer",
-      "data":
-        {
-          "src": "/reports/sample-report.pdf",
-          "geometry": "16:9",
-          "pages": 8,
-          "downloadFilename": "platform-shift-2025.pdf",
-          "outline":
-            [
-              { "id": "opening", "label": "Opening", "startPage": 1 },
-              { "id": "findings", "label": "Findings", "startPage": 3 },
-              { "id": "outlook", "label": "Outlook", "startPage": 6 },
-            ],
-        },
-    },
-  ]
----
-
-{/_
-A PLACEHOLDER report. Its bytes are the signal-collectors module's own sample
-PDF (`apps/web/public/reports/sample-report.pdf`, installed by that module's
-bundle), shared by all four samples so the template ships no binary of its
-own. Point `src` at your real document and set `pages` to its real page
-count — the count reserves the reader's layout before the renderer loads, so
-a wrong number shows as a jump.
-_/}

package/site-templates/minimalism-site/content/en/ReportPage/state-of-the-market-2026.mdx

@@ -1,52 +0,0 @@
----
-type: "ReportPage"
-slug: "state-of-the-market-2026"
-title: "State of {Your Market} 2026"
-description: "{One line on the question this report answers. Replace before you launch.}"
-schema:
-  datePublished: "2026-05-14"
-  author:
-    "@type": Organization
-    name: "Your Company"
-sections:
-  [
-    {
-      "id": "header",
-      "type": "report-header",
-      "data":
-        {
-          "title": "State of {Your Market} 2026",
-          "eyebrow": "May 2026",
-          "backHref": "/reports",
-          "backLabel": "All reports",
-          "tone": "on-dark",
-        },
-    },
-    {
-      "id": "document",
-      "type": "document-viewer",
-      "data":
-        {
-          "src": "/reports/sample-report.pdf",
-          "geometry": "16:9",
-          "pages": 8,
-          "downloadFilename": "state-of-the-market-2026.pdf",
-          "outline":
-            [
-              { "id": "opening", "label": "Opening", "startPage": 1 },
-              { "id": "findings", "label": "Findings", "startPage": 3 },
-              { "id": "outlook", "label": "Outlook", "startPage": 6 },
-            ],
-        },
-    },
-  ]
----
-
-{/_
-A PLACEHOLDER report. Its bytes are the signal-collectors module's own sample
-PDF (`apps/web/public/reports/sample-report.pdf`, installed by that module's
-bundle), shared by all four samples so the template ships no binary of its
-own. Point `src` at your real document and set `pages` to its real page
-count — the count reserves the reader's layout before the renderer loads, so
-a wrong number shows as a jump.
-_/}