create-ailk 0.7.0 → 0.8.0

package/site-templates/simple-service/TEMPLATE-MANIFEST.md

@@ -1,333 +0,0 @@
-# Template manifest — `simple-service`
-
-> 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 a purchase policy (cancellation and refunds, #6646). Generated file: the regions between `<!-- generated:begin <id> -->` and `<!-- generated:end -->` are produced by `scripts/build-template-manifest.mjs --template simple-service` from the composed layer stack (this tree → its required modules → `_base` → the always-copied overlay), each roster row's MDX `sections[]`, and `component-catalog.json`. Everything outside the markers is written by hand.
-
-| Field                  | Value                                                                                                                     |
-| ---------------------- | ------------------------------------------------------------------------------------------------------------------------- |
-| Template               | `simple-service`                                                                                                          |
-| Level                  | Pro (derived from `requires` — `scheduling` and `commerce` are paid; never declared)                                      |
-| `requires`             | `[marketing, scheduling, commerce]` — the first template to take `commerce`                                               |
-| `extends`              | `_base` — lineage only, never level                                                                                       |
-| Delivery               | licence-checked module bundle (#5441); never in the Free tarball                                                          |
-| Sample content posture | every line of copy, and all three service prices, are **placeholders** — and the prices are PUBLISHED as JSON-LD `Offer`s |
-
-## 1. Chrome
-
-This template declares **no `layout` block**. The default marketing-site chrome is what a lawn-care site wants — a nav row a reader can reach `/services` from, the four-column footer, and the document-scroll home — and the issue's STOP boundary excludes layout knobs the spec does not name.
-
-### Layout knobs (#5612)
-
-The template's `layout` block — resolved with `resolveSiteChrome`, defaults filled.
-
-<!-- generated:begin layout -->
-
-| Knob                 | Value     |
-| -------------------- | --------- |
-| `nav`                | `full`    |
-| `footer`             | `columns` |
-| `announcementBanner` | `false`   |
-| `home`               | `default` |
-
-<!-- generated:end -->
-
-### Theme (locked)
-
-The template's `theme:` block as `_site.mdx` declares it — the shape knobs and the colour overlay. Generated, so a change to a locked template's look is a red `manifest:check`, not a silent drift (starter-template contract R3.5).
-
-<!-- generated:begin theme -->
-
-| Setting                  | Value      |
-| ------------------------ | ---------- |
-| `corners`                | `square`   |
-| `eyebrowCase`            | `sentence` |
-| `placeholders`           | `fill`     |
-| `checkmarks`             | `plain`    |
-| `colors.light.bg`        | `#ffffff`  |
-| `colors.light.bgMuted`   | `#ffffff`  |
-| `colors.light.surface`   | `#ffffff`  |
-| `colors.light.border`    | `#000000`  |
-| `colors.light.text`      | `#000000`  |
-| `colors.light.textMuted` | `#333333`  |
-| `colors.light.primary`   | `#000000`  |
-| `colors.light.primaryFg` | `#ffffff`  |
-| `colors.light.accent`    | `#000000`  |
-| `colors.dark.bg`         | `#000000`  |
-| `colors.dark.bgMuted`    | `#000000`  |
-| `colors.dark.surface`    | `#000000`  |
-| `colors.dark.border`     | `#ffffff`  |
-| `colors.dark.text`       | `#ffffff`  |
-| `colors.dark.textMuted`  | `#cccccc`  |
-| `colors.dark.primary`    | `#ffffff`  |
-| `colors.dark.primaryFg`  | `#000000`  |
-| `colors.dark.accent`     | `#ffffff`  |
-
-<!-- generated:end -->
-
-## 2. The money path
-
-The whole point of this template is the first roster that takes a booking **and** the payment for it:
-
-| Step      | Where it lives                                                                                                                                                                                           |
-| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Discovery | `/services` and the three `/services/<slug>` pages. Each detail page's top-level `price` + `priceCurrency` + `provider` become one schema.org `Offer` in its JSON-LD (#5838) — the free discovery floor. |
-| Booking   | `/meet`, `/meet/<slug>`, `/meet/confirmed` — the `scheduling` module's own contributed rows; `/appointments` is the site owner's own list (#6086).                                                       |
-| Payment   | a provider-hosted page on the seller's own Stripe account. Nothing on this site renders a card form.                                                                                                     |
-| Return    | `/purchase/success` and `/purchase/cancel` — base tree under #6084 D12's shape-2 disposition, gated at request time on the `commerce` licence claim.                                                     |
-| Policies  | `/purchase-policy` (#6646) — cancellation and refunds sections, this template's service-shape override of the overlay's product-shape seed.                                                              |
-
-## 3. Pages
-
-One `page=<route>` region per roster row, generated from the seed file the composed layer stack lands for that route.
-
-`/`:
-
-<!-- generated:begin page=/ -->
-
-| #   | Section                                                    | Component | Copy (first line)                              |
-| --- | ---------------------------------------------------------- | --------- | ---------------------------------------------- |
-| 1   | `hero` (centered · eyebrow "{Your service area}" · 2 CTAs) | `Hero`    | {Lawn care that turns up when it says it will} |
-| 2   | `items` (columns=3 · items ×3)                             | `Items`   | What we do                                     |
-| 3   | `cta` (minimal · 2 CTAs)                                   | `CTA`     | Ready for a tidier yard?                       |
-
-<!-- generated:end -->
-
-`/services`:
-
-<!-- generated:begin page=/services -->
-
-| #   | Section                                | Component | Copy (first line)        |
-| --- | -------------------------------------- | --------- | ------------------------ |
-| 1   | `hero` (centered · eyebrow "Services") | `Hero`    | Three jobs, three prices |
-| 2   | `items` (columns=3 · items ×3)         | `Items`   | What we do               |
-| 3   | `cta` (minimal · 1 CTA)                | `CTA`     | Not sure which one?      |
-
-<!-- generated:end -->
-
-`/services/[slug]`:
-
-<!-- generated:begin page=/services/[slug] -->
-
-_Detail route over `content/en/Service/` — 3 seed pages: `landscape-design.mdx`, `lawn-maintenance.mdx`, `seasonal-cleanup.mdx`._
-<!-- generated:end -->
-
-`/about`:
-
-<!-- generated:begin page=/about -->
-
-| #   | Section                                    | Component      | Copy (first line)                          |
-| --- | ------------------------------------------ | -------------- | ------------------------------------------ |
-| 1   | `content-block` (narrow · eyebrow "About") | `ContentBlock` | {A small crew, the same yards, every week} |
-| 2   | `cta` (minimal · 2 CTAs)                   | `CTA`          | Want us to take a look?                    |
-
-<!-- generated:end -->
-
-`/contact`:
-
-<!-- generated:begin page=/contact -->
-
-| #   | Section                               | Component | Copy (first line)        |
-| --- | ------------------------------------- | --------- | ------------------------ |
-| 1   | `hero` (centered · eyebrow "Contact") | `Hero`    | Tell us about the yard   |
-| 2   | `cta` (minimal · 1 CTA)               | `CTA`     | Would a visit be faster? |
-
-<!-- generated:end -->
-
-`/faq`:
-
-<!-- generated:begin page=/faq -->
-
-| #   | Section                                                       | Component | Copy (first line)      |
-| --- | ------------------------------------------------------------- | --------- | ---------------------- |
-| 1   | `faq` (centered · items ×5 · supportLink · initialOpen first) | `FAQ`     | Questions              |
-| 2   | `cta` (minimal · 1 CTA)                                       | `CTA`     | Still have a question? |
-
-<!-- generated:end -->
-
-`/glossary`, `/newsletter` (base-layer seeds every starter carries, #6658 D5):
-
-<!-- generated:begin page=/glossary -->
-
-| #   | Section                             | Component       | Copy (first line)                            |
-| --- | ----------------------------------- | --------------- | -------------------------------------------- |
-| 1   | `hero` (eyebrow "Glossary" · 1 CTA) | `Hero`          | {Glossary: the terms your customers look up} |
-| 2   | `glossary-index` (columns)          | `GlossaryIndex` | {Terms, A to Z}                              |
-
-<!-- generated:end -->
-
-<!-- generated:begin page=/newsletter -->
-
-| #   | Section                               | Component    | Copy (first line)                                |
-| --- | ------------------------------------- | ------------ | ------------------------------------------------ |
-| 1   | `hero` (eyebrow "Newsletter" · 1 CTA) | `Hero`       | {Newsletter: what subscribers get and how often} |
-| 2   | `newsletter`                          | `Newsletter` | Subscribe                                        |
-| 3   | `faq` (expanded · items ×3)           | `FAQ`        | FAQs                                             |
-
-<!-- generated:end -->
-
-`/book-a-call` (this template's own override of the base seed — the call to action opens the `/meet` booker the scheduling module supplies, not `/contact`):
-
-<!-- generated:begin page=/book-a-call -->
-
-| #   | Section                                | Component | Copy (first line)                          |
-| --- | -------------------------------------- | --------- | ------------------------------------------ |
-| 1   | `hero` (eyebrow "Book a call" · 1 CTA) | `Hero`    | {Book a call: what a visitor gets from it} |
-| 2   | `items` (columns=3 · items ×3)         | `Items`   | What happens on the call?                  |
-
-<!-- generated:end -->
-
-`/purchase-policy`:
-
-<!-- generated:begin page=/purchase-policy -->
-
-| #   | Section                             | Component         | Copy (first line) |
-| --- | ----------------------------------- | ----------------- | ----------------- |
-| 1   | `document-chassis` (layout=article) | `DocumentChassis` | Purchase Policy   |
-
-<!-- generated:end -->
-
-`/privacy`:
-
-<!-- generated:begin page=/privacy -->
-
-| #   | Section                             | Component         | Copy (first line) |
-| --- | ----------------------------------- | ----------------- | ----------------- |
-| 1   | `document-chassis` (layout=article) | `DocumentChassis` | Privacy Policy    |
-
-<!-- generated:end -->
-
-`/terms`:
-
-<!-- generated:begin page=/terms -->
-
-| #   | Section                             | Component         | Copy (first line) |
-| --- | ----------------------------------- | ----------------- | ----------------- |
-| 1   | `document-chassis` (layout=article) | `DocumentChassis` | Terms of Service  |
-
-<!-- generated:end -->
-
-`/account`:
-
-<!-- generated:begin page=/account -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/purchase/success`:
-
-<!-- generated:begin page=/purchase/success -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/purchase/cancel`:
-
-<!-- generated:begin page=/purchase/cancel -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/thanks/[slug]`:
-
-<!-- generated:begin page=/thanks/[slug] -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/meet`:
-
-<!-- generated:begin page=/meet -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/meet/[slug]`:
-
-<!-- generated:begin page=/meet/[slug] -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/meet/confirmed`:
-
-<!-- generated:begin page=/meet/confirmed -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-`/appointments`:
-
-<!-- generated:begin page=/appointments -->
-
-_Code route — no content, no sections._
-<!-- generated:end -->
-
-## 4. Roster, as the registry declares it
-
-`simple-service` is 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`, the product page (`/software/product`) and `/pricing` are not pages this site has. The roster is what the template IS, so an unrostered page has neither a route directory nor its seed: `scaffold()` installs a `_base` or overlay seed only for a row that names it (#6646), so `content/en/Pricing/pricing.mdx` does not land. The merged roster, as the registry composes it:
-
-<!-- generated:begin roster -->
-
-```
-simple-service:
-  requires: [marketing, scheduling, commerce]
-  categories: [landscaping]
-  shape: local-business-service
-  design: standard
-  roster:
-    - { route: "/",                 kind: page, content: ["content/en/HomePage/home.mdx"] }
-    - { route: "/services",         kind: page, content: ["content/en/ServicesList/services.mdx"] }
-    - { route: "/services/[slug]",  kind: page, contentDir: "content/en/Service" }
-    - { route: "/about",            kind: page, content: ["content/en/AboutPage/about.mdx"] }
-    - { route: "/contact",          kind: page, content: ["content/en/ContactPage/contact.mdx"] }
-    - { route: "/faq",              kind: page, content: ["content/en/FAQPage/faq.mdx"] }
-    - { route: "/glossary",         kind: page, content: ["content/en/GlossaryList/glossary.mdx"] }
-    - { route: "/newsletter",       kind: page, content: ["content/en/NewsletterSignup/newsletter.mdx"] }
-    - { route: "/book-a-call",      kind: page, content: ["content/en/BookCall/book-call.mdx"] }
-    - { route: "/purchase-policy",  kind: page, content: ["content/en/PurchasePolicyPage/purchase-policy.mdx"] }
-    - { route: "/privacy",          kind: page, content: ["content/en/PrivacyPage/privacy.mdx"] }
-    - { route: "/terms",            kind: page, content: ["content/en/TermsPage/terms.mdx"] }
-    - { route: "/account",          kind: route }
-    - { route: "/purchase/success", kind: route }
-    - { route: "/purchase/cancel",  kind: route }
-    - { route: "/thanks/[slug]",    kind: route }
-    - { route: "/meet",             kind: route }
-    - { route: "/meet/[slug]",      kind: route }
-    - { route: "/meet/confirmed",   kind: route }
-    - { route: "/appointments",     kind: route }
-```
-
-<!-- generated:end -->
-
-By source:
-
-```
-template:    / · /services · /services/<slug> · /about · /contact · /faq
-             /purchase-policy · /privacy · /terms · /account
-             /purchase/success · /purchase/cancel · /thanks/<slug>
-scheduling:  /meet · /meet/<slug> · /meet/confirmed · /appointments
-```
-
-**Why the two `/purchase/*` rows are the TEMPLATE's and not the `commerce` module's.** #6084 landed the checkout return pair under the operator's shape-2 disposition (#6084 D12): `CORE_ROUTE_DIRS` carries `[locale]/purchase`, and neither `GATEABLE_SURFACES` nor `MODULE_SURFACES.commerce` gained an entry, so `MODULE_SLICES.commerce` contributes **no** `pageContributions` at all. Nothing else claims the two routes, so declaring them here trips no both-claimants refusal — and the issue's AC-1 requires the merged roster to carry them. The four scheduling rows, by contrast, **are** the module's, and declaring one here would make `mergeRoster` refuse this template outright.
-
-`/account` and `/purchase-policy` carry no `GATEABLE_SURFACES` entry and need none: `(authed)` ships unconditionally, and `/purchase-policy` has no gateable surface at all, so it is always copied. The six module-less surfaces this roster enables are `book-a-call`, `glossary`, `newsletter`, `privacy`, `services` and `terms`.
-
-## 5. Component inventory
-
-Every component the roster rows' seed content composes today (generated):
-
-<!-- generated:begin inventory -->
-
-| Tier     | Used by this template                                                                           |
-| -------- | ----------------------------------------------------------------------------------------------- |
-| Shell    | `MarketingShell`                                                                                |
-| Chrome   | `Nav`, `Footer`, `Banner` (+ `BannerConsentIsland`, `BannerDismissIsland`)                      |
-| Sections | `ContentBlock`, `CTA`, `DocumentChassis`, `FAQ`, `GlossaryIndex`, `Hero`, `Items`, `Newsletter` |
-
-<!-- generated:end -->
-
-## 6. Known gaps this manifest depends on
-
-| Gap                                                                                          | Issue |
-| -------------------------------------------------------------------------------------------- | ----- |
-| No routes-map row for `/account`, `/appointments` or `/purchase/*`, so those rows show blank | #5572 |
-| The Pro demo host `simple-service.ailaunchkit.ai` — provisioning is the runbook's act        | #5778 |

package/site-templates/simple-service/ailk-template.json

@@ -1,11 +0,0 @@
-{
-  "name": "simple-service",
-  "requires": ["marketing", "scheduling", "commerce"],
-  "extends": "_base",
-  "$comment": "The T1 lawn-care template (#6087, Epic #5778) — the first site shape that composes scheduling and commerce. Composed base -> modules -> template: /privacy and /terms arrive with the _base layer this extends (its unrostered /pricing seed does not install, #6646), and /purchase-policy is this tree's own service-shape override of the overlay's product-shape seed (#6646 — cancellation and refunds sections); /meet, /meet/<slug>, /meet/confirmed and /appointments with the scheduling bundle; /purchase/success and /purchase/cancel are BASE TREE (#6084 D12 shape 2 — CORE_ROUTE_DIRS carries [locale]/purchase and the commerce licence claim, not the scaffold, decides whether they serve); the Free about/contact/faq 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 and its placeholder copy. It declares no layout block — the default marketing-site chrome is what this template renders with, and the code registry (TEMPLATE_MANIFESTS) is authoritative for a template create-ailk ships, so a duplicate 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"
-  },
-  "postInstall": "Template simple-service installed. This is the lawn-care shape: three priced services at /services (content/en/Service/), a booker at /meet from the scheduling module, the site owner's own list at /appointments, and the checkout return pair at /purchase/success and /purchase/cancel. /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 home page, /services and its three detail pages, /about, /contact, /faq and /purchase-policy (cancellation and refunds). THE THREE PRICES ARE PLACEHOLDERS AND THEY ARE PUBLISHED: each service page's top-level price and priceCurrency become a schema.org Offer in that page's JSON-LD, which is what an agent reading your site quotes back to a buyer — replace all three, and the provider name with them, before you launch. Taking money needs the commerce licence claim and your own Stripe account: without the claim the return pages 404 by design. EVERY line of copy on this site is a placeholder too — replace it before you launch."
-}

package/site-templates/simple-service/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/simple-service/content/en/ContactPage/contact.mdx

@@ -1,32 +0,0 @@
----
-type: "ContactPage"
-slug: "contact"
-title: "Contact"
-description: "One form, three fields, an inline confirmation. Placeholder copy — replace before you launch."
-sections:
-  [
-    {
-      "id": "hero",
-      "type": "hero",
-      "data":
-        {
-          "variant": "centered",
-          "eyebrow": "Contact",
-          "headline": "Tell us about the yard",
-          "subheadline": "{One line on what happens after you send this, and how long it takes. If a call is faster, say so.}",
-        },
-    },
-    {
-      "id": "closing",
-      "type": "cta",
-      "data":
-        {
-          "variant": "minimal",
-          "headline": "Would a visit be faster?",
-          "primaryCta": { "label": "Book a visit →", "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/simple-service/content/en/FAQPage/faq.mdx

@@ -1,56 +0,0 @@
----
-type: "FAQPage"
-slug: "faq"
-title: "FAQ"
-description: "The questions people ask before they book. Placeholder copy — replace every answer before you launch."
-sections:
-  [
-    {
-      "id": "faq",
-      "type": "faq",
-      "data":
-        {
-          "headline": "Questions",
-          "variant": "centered",
-          "initialOpen": "first",
-          "items":
-            [
-              {
-                "question": "{Which areas do you cover?}",
-                "answer": "{Name the towns, the radius or the postcodes. A reader outside them should know it here.}",
-              },
-              {
-                "question": "{How often do you visit?}",
-                "answer": "{Give the real cadence for the recurring job, and say what happens in winter.}",
-              },
-              {
-                "question": "{What does it cost?}",
-                "answer": "{The three service pages carry the prices. Say here what moves them — yard size, access, waste removal.}",
-              },
-              {
-                "question": "{How do I pay?}",
-                "answer": "{Say when payment is taken and how. Checkout runs on your own Stripe account; the card details never touch this site.}",
-              },
-              {
-                "question": "{What if I need to cancel?}",
-                "answer": "{Point at the cancellation policy and give the notice period in one line.}",
-              },
-            ],
-          "supportLink":
-            { "label": "Still stuck? Get in touch", "href": "/contact" },
-        },
-    },
-    {
-      "id": "closing",
-      "type": "cta",
-      "data":
-        {
-          "variant": "minimal",
-          "headline": "Still have a question?",
-          "primaryCta": { "label": "Contact us →", "href": "/contact" },
-        },
-    },
-  ]
----
-
-Placeholder copy. Replace every answer before you launch.

package/site-templates/simple-service/content/en/HomePage/home.mdx

@@ -1,85 +0,0 @@
----
-type: "HomePage"
-slug: "home"
-title: "Your Company"
-description: "Placeholder home for the simple-service template — a lawn-care site that books a visit and takes the payment. Replace every line before you launch."
-sections:
-  [
-    {
-      "id": "hero",
-      "type": "hero",
-      "data":
-        {
-          "variant": "centered",
-          "eyebrow": "{Your service area}",
-          "headline": "{Lawn care that turns up when it says it will}",
-          "subheadline": "{One line on who you serve and what they get. Name the street, the town or the county — a local reader is looking for their own.}",
-          "primaryCta": { "label": "Book a visit →", "href": "/meet" },
-          "secondaryCta":
-            {
-              "label": "See services",
-              "href": "/services",
-              "variant": "outline",
-            },
-        },
-    },
-    {
-      "id": "services",
-      "type": "items",
-      "data":
-        {
-          "headline": "What we do",
-          "columns": 3,
-          "items":
-            [
-              {
-                "title": "{Lawn maintenance}",
-                "description": "{One line on the recurring visit — what it includes and how often it runs.}",
-                "link":
-                  {
-                    "label": "Read more",
-                    "href": "/services/lawn-maintenance",
-                  },
-              },
-              {
-                "title": "{Seasonal cleanup}",
-                "description": "{One line on the spring and autumn clear-down.}",
-                "link":
-                  {
-                    "label": "Read more",
-                    "href": "/services/seasonal-cleanup",
-                  },
-              },
-              {
-                "title": "{Landscape design}",
-                "description": "{One line on the design-and-plant job, and what a customer ends up with.}",
-                "link":
-                  {
-                    "label": "Read more",
-                    "href": "/services/landscape-design",
-                  },
-              },
-            ],
-        },
-    },
-    {
-      "id": "closing",
-      "type": "cta",
-      "data":
-        {
-          "variant": "minimal",
-          "headline": "Ready for a tidier yard?",
-          "description": "{One line inviting the reader to pick a time rather than fill in a form.}",
-          "primaryCta": { "label": "Book a visit →", "href": "/meet" },
-          "secondaryCta":
-            {
-              "label": "Ask a question",
-              "href": "/contact",
-              "variant": "outline",
-            },
-        },
-    },
-  ]
----
-
-Placeholder copy. Every headline, every line of body copy and every price on this site is a placeholder — replace them before you launch.

package/site-templates/simple-service/content/en/Service/landscape-design.mdx

@@ -1,40 +0,0 @@
----
-type: "Service"
-slug: "landscape-design"
-title: "{Landscape design}"
-description: "{One line on what this job is and who it suits. Replace before you launch.}"
-price: 1250
-priceCurrency: "USD"
-provider:
-  name: "{Your Company}"
-schema:
-  serviceType: "{Landscape design}"
-  areaServed: "{Your service area}"
----
-
-# \{Landscape design\}
-
-\{Open with the situation a reader is in when they come looking for this. Two or
-three sentences, no more — the detail belongs under the headings below.\}
-
-## What it covers
-
-- \{The first thing you actually do\}
-- \{The second thing you actually do\}
-- \{The third thing you actually do\}
-
-## How it runs
-
-\{One paragraph on the shape of the visit: how it is scheduled, how long it
-takes, who turns up, and what you need from the customer beforehand.\}
-
-## What you end up with
-
-\{One paragraph on the result. Be concrete — describe the yard when the crew
-drives away.\}
-
-## What it costs
-
-\{The price in this page's frontmatter is a PLACEHOLDER. It is what the site
-publishes as a schema.org `Offer`, so an agent reading this page quotes it —
-replace it with your real number before you launch.\}

package/site-templates/simple-service/content/en/Service/lawn-maintenance.mdx

@@ -1,40 +0,0 @@
----
-type: "Service"
-slug: "lawn-maintenance"
-title: "{Lawn maintenance}"
-description: "{One line on what this job is and who it suits. Replace before you launch.}"
-price: 149
-priceCurrency: "USD"
-provider:
-  name: "{Your Company}"
-schema:
-  serviceType: "{Lawn maintenance}"
-  areaServed: "{Your service area}"
----
-
-# \{Lawn maintenance\}
-
-\{Open with the situation a reader is in when they come looking for this. Two or
-three sentences, no more — the detail belongs under the headings below.\}
-
-## What it covers
-
-- \{The first thing you actually do\}
-- \{The second thing you actually do\}
-- \{The third thing you actually do\}
-
-## How it runs
-
-\{One paragraph on the shape of the visit: how it is scheduled, how long it
-takes, who turns up, and what you need from the customer beforehand.\}
-
-## What you end up with
-
-\{One paragraph on the result. Be concrete — describe the yard when the crew
-drives away.\}
-
-## What it costs
-
-\{The price in this page's frontmatter is a PLACEHOLDER. It is what the site
-publishes as a schema.org `Offer`, so an agent reading this page quotes it —
-replace it with your real number before you launch.\}