docs: feature ICD prominently — new Hot Features page + intro callout + /ai sync

Christian wants ICD (Instant Content Deployment) elevated from "buried in
deploy docs" to the first thing new visitors see. Three placements:

1. **New /docs/hot-features page** (EN + DA) — opinionated tour of the
   recent features that change HOW you should build new sites: ICD,
   Beam, Headless API, Permission-based ACL, i18n with translation
   groups, AI Lock. Skim before starting a new project.

2. **Front-page CTA** — third button next to "Get Started" / "Read the
   Docs": "🔥 Hot Features" in gold outline. Visible above the fold.

3. **Introduction page callout** — short blockquote at the top of
   /docs/introduction (and DA twin) pointing at hot-features for
   default-pattern guidance.

4. **Sync /ai modules** — copy updated index.md and 18-deployment.md
   from cms repo's docs/ai-guide/ into cms-docs/src/ai-guide/. The /ai
   route serves these files at https://docs.webhouse.app/ai (and
   ai.webhouse.app/ai for AI agents). Now the index has the new
   "AI scaffolding new Next.js sites should default to ICD" note and
   the deployment module has the full ICD pattern.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: cbroberg

content/docs/hot-features-da.json

@@ -0,0 +1,13 @@
+{
+  "id": "h0t-feat-2026-05-da",
+  "slug": "hot-features-da",
+  "status": "published",
+  "locale": "da",
+  "translationGroup": "hot-features-group-2026-05",
+  "translationOf": "hot-features",
+  "data": {
+    "title": "Hot Features",
+    "description": "Hvad er nyt og værd at kende lige nu i @webhouse/cms — de patterns vi anbefaler som default for nye sites.",
+    "content": "## Hvad er hot i @webhouse/cms\n\nEn kort, holdningsstærk gennemgang af de nyeste features der ændrer *hvordan* du bør bygge nye sites — ikke bare en changelog. Skim det før du starter et nyt projekt; de defaults du baker ind her sparer dig uger af refaktorering senere.\n\n---\n\n## ⚡ Instant Content Deployment (ICD)\n\n**Den nye default for ethvert Next.js site med editor-drevet indhold.**\n\nGlem at trigge en Docker rebuild hver gang nogen retter en kommafejl. ICD pusher content-ændringer fra CMS admin direkte til dit deployede Next.js site via en HMAC-signed webhook. Sitet skriver opdateringen til disk og kalder `revalidatePath()` — indholdet går live på **~2 sekunder**.\n\n- Drop-in `app/api/revalidate/route.ts` template — copy, paste, deploy\n- Virker på enhver Next.js host med persistent filesystem (Fly.io med volumes, self-hosted Docker)\n- HMAC-SHA256 signerede payloads + timing-safe sammenligning\n- Header-pill `ICD · auto` i admin når konfigureret — redaktører ser live status\n- Fulde Docker deploys er stadig tilgængelige for kode/config ændringer; ICD håndterer kun *content*-vejen\n\n👉 [Fuld ICD guide](/docs/instant-content-deployment-da) · Også dækket i [AI Builder Guide modul 18](https://ai.webhouse.app/ai/18-deployment)\n\n---\n\n## 📦 Beam — single-file site export/import\n\nPak et komplet site (indhold + media + config + agents + settings) ind i ét `.beam` arkiv. Importér på en hvilken som helst anden CMS admin instans — indhold, secrets stripped automatisk, checksums verificeret.\n\nBrug det til:\n\n- Kloning af sites mellem dev / staging / prod\n- Onboarding af kunder på din production CMS\n- Backup før risikable migrationer\n\nLive Beam (HTTP push til en remote admin) er også tilgængelig for direkte admin-til-admin overførsel med chunked upload.\n\n---\n\n## 🤖 Headless Site API (F139)\n\nBrug CMS admin som **headless backend** inde i ethvert framework — Next.js, Astro, plain Node, you name it. Autentificér med et permanent `wh_` Access Token. Læs/skriv indhold, trigger deploys, læs form-indbakker, embed AI chatten i dit eget UI.\n\nTil projekter hvor design-systemet er for custom til at passe ind i vores default Next.js boilerplate.\n\n👉 [Headless API guide](/docs/headless-api-da)\n\n---\n\n## 🔐 Permission-baseret ACL (F55)\n\n20 fine-grained permissions — `content.publish`, `media.upload`, `forms.export`, `settings.edit` osv. Map til roller (admin / editor / viewer) eller tildel per bruger. Server-side håndhævelse på hver API route via `requirePermission()`. UI-knapper skjules når brugeren ikke kan handle.\n\n---\n\n## 🌍 i18n med translation groups (F48)\n\nLink dokumenter på tværs af locales via `translationGroup` felt. AI auto-translater ved create. Hreflang tags, locale routing, language switcher — alt indbygget. 18 AI routes til translation operationer.\n\n---\n\n## 🛡 AI Lock\n\nField-level beskyttelse: AI agents *kan ikke* overskrive menneskelige edits. WriteContext threader actor-identitet gennem hver CRUD-kald. Når du har manuelt poleret en sætning, rører ingen agent den uden eksplicit override.\n\n---\n\n## Hvad er nyt denne uge\n\nSe [changelog](/changelog) for fulde per-version noter."
+  }
+}

content/docs/hot-features.json

@@ -0,0 +1,12 @@
+{
+  "id": "h0t-feat-2026-05-en",
+  "slug": "hot-features",
+  "status": "published",
+  "locale": "en",
+  "translationGroup": "hot-features-group-2026-05",
+  "data": {
+    "title": "Hot Features",
+    "description": "What's new and worth knowing right now in @webhouse/cms — the patterns we recommend by default for new sites.",
+    "content": "## What's hot in @webhouse/cms\n\nA short, opinionated tour of the recent features that change *how* you should build new sites — not just the changelog. Skim this before you start a new project; the defaults you bake in here save you weeks of refactoring later.\n\n---\n\n## ⚡ Instant Content Deployment (ICD)\n\n**The new default for any Next.js site that needs editor-driven content updates.**\n\nForget triggering a Docker rebuild every time someone fixes a typo. ICD pushes content edits from CMS admin directly to your deployed Next.js site via an HMAC-signed webhook. The site writes the update to disk and calls `revalidatePath()` — content goes live in **~2 seconds**.\n\n- Drop-in `app/api/revalidate/route.ts` template — copy, paste, deploy\n- Works on any Next.js host with a persistent filesystem (Fly.io with volumes, self-hosted Docker)\n- HMAC-SHA256 signed payloads + timing-safe comparison\n- Header pill `ICD · auto` in admin once configured — editors see live status\n- Full Docker deploys are still available for code/config changes; ICD just handles the *content* path\n\n👉 [Full ICD guide](/docs/instant-content-deployment) · Also covered in [AI Builder Guide module 18](https://ai.webhouse.app/ai/18-deployment)\n\n---\n\n## 📦 Beam — single-file site export/import\n\nPack a complete site (content + media + config + agents + settings) into one `.beam` archive. Import on any other CMS admin instance — content, secrets stripped automatically, checksums verified.\n\nUse it for:\n\n- Cloning sites between dev / staging / prod\n- Onboarding clients onto your production CMS\n- Backing up before risky migrations\n\nLive Beam (HTTP push to a remote admin) is also available for direct admin-to-admin transfer with chunked upload.\n\n---\n\n## 🤖 Headless Site API (F139)\n\nUse CMS admin as a **headless backend** inside any framework — Next.js, Astro, plain Node, you name it. Authenticate with a permanent `wh_` Access Token. Read/write content, trigger deploys, read form inboxes, embed the AI chat in your own UI.\n\nFor projects where the design system is too custom to fit our default Next.js boilerplate.\n\n👉 [Headless API guide](/docs/headless-api)\n\n---\n\n## 🔐 Permission-based ACL (F55)\n\n20 fine-grained permissions — `content.publish`, `media.upload`, `forms.export`, `settings.edit` etc. Map to roles (admin / editor / viewer) or assign per user. Server-side enforcement on every API route via `requirePermission()`. UI buttons hide when user can't act.\n\n---\n\n## 🌍 i18n with translation groups (F48)\n\nLink documents across locales via `translationGroup` field. AI auto-translates on create. Hreflang tags, locale routing, language switcher — all built in. 18 AI routes for translation operations.\n\n---\n\n## 🛡 AI Lock\n\nField-level protection: AI agents *cannot* overwrite human edits. WriteContext threads actor identity through every CRUD call. Once you've manually polished a sentence, no agent will touch it without an explicit override.\n\n---\n\n## What's new this week\n\nSee the [changelog](/changelog) for full per-version notes."
+  }
+}

content/docs/introduction-da.json

@@ -7,7 +7,7 @@
   "data": {
     "title": "Introduktion",
     "description": "Hvad er @webhouse/cms og hvorfor det eksisterer — et filbaseret, AI-native CMS til TypeScript-projekter.",
-    "content": "## Hvad er @webhouse/cms?\n\n`@webhouse/cms` er en **filbaseret, AI-native CMS-motor** til TypeScript-projekter. Du definerer collections og felter i en `cms.config.ts`-fil, og CMS'et gemmer indhold som flade JSON-filer i en `content/`-mappe — én fil pr. dokument, organiseret efter collection.\n\nDet giver dig:\n\n- **REST API-server** — Hono-baseret API til læsning og skrivning af indhold\n- **Statisk site-builder** — 9-faset build-pipeline der genererer HTML, sitemap, RSS, robots.txt og AI-discovery-filer\n- **AI-indholdsgenerering** — indbyggede agenter til skrivning, SEO-optimering, oversættelse og mere\n- **Visuel admin-brugerflade** — fuld-udstyret editor på [webhouse.app](https://webhouse.app) med rich text, blokke, medier og planlægning\n- **MCP-integration** — Model Context Protocol-server til AI-platformes adgang til dit indhold\n\n## Hvem er det til?\n\n@webhouse/cms er designet til udviklere der bygger indholdsdrevne websites med Next.js. Det fungerer særligt godt når:\n\n- Du vil have **filbaseret indhold** der lever i dit Git-repository\n- Du har brug for **AI-drevne indholdsworkflows** (generering, oversættelse, SEO-optimering)\n- Du foretrækker **TypeScript-first** konfiguration frem for YAML eller markdown frontmatter\n- Du vil have en **visuel admin-brugerflade** uden kompleksiteten af et headless CMS\n\n## Arkitektur\n\n```\ncms.config.ts          → Collection- og feltdefinitioner\ncontent/               → JSON-dokumenter (én pr. fil)\npackages/cms           → Kernemotor (@webhouse/cms)\npackages/cms-admin     → Next.js admin-brugerflade (@webhouse/cms-admin)\npackages/cms-ai        → AI-agenter (@webhouse/cms-ai)\npackages/cms-cli       → CLI-værktøjer (@webhouse/cms-cli)\npackages/cms-mcp-*     → MCP-servere til AI-platformsadgang\n```\n\nKernepakken (`@webhouse/cms`) er framework-agnostisk — den læser og skriver JSON-filer. Admin-brugerfladen (`@webhouse/cms-admin`) er en selvstændig Next.js-applikation der forbinder til kernemotor.\n\n## Næste skridt\n\n- [Hurtig start](/docs/quick-start-da) — opret og kør dit første projekt på under 5 minutter\n- [Konfigurationsreference](/docs/config-reference-da) — lær hvordan du definerer collections og felter\n- [Felttyper](/docs/field-types-da) — udforsk alle 22 felttyper",
+    "content": "## Hvad er @webhouse/cms?\n\n`@webhouse/cms` er en **filbaseret, AI-native CMS-motor** til TypeScript-projekter. Du definerer collections og felter i en `cms.config.ts`-fil, og CMS'et gemmer indhold som flade JSON-filer i en `content/`-mappe — én fil pr. dokument, organiseret efter collection.\n\n> **🔥 Ny her?** Se [Hot Features](/docs/hot-features-da) for de patterns vi anbefaler som default for nye sites — Instant Content Deployment, Beam, Headless API og mere.\n\n\nDet giver dig:\n\n- **REST API-server** — Hono-baseret API til læsning og skrivning af indhold\n- **Statisk site-builder** — 9-faset build-pipeline der genererer HTML, sitemap, RSS, robots.txt og AI-discovery-filer\n- **AI-indholdsgenerering** — indbyggede agenter til skrivning, SEO-optimering, oversættelse og mere\n- **Visuel admin-brugerflade** — fuld-udstyret editor på [webhouse.app](https://webhouse.app) med rich text, blokke, medier og planlægning\n- **MCP-integration** — Model Context Protocol-server til AI-platformes adgang til dit indhold\n\n## Hvem er det til?\n\n@webhouse/cms er designet til udviklere der bygger indholdsdrevne websites med Next.js. Det fungerer særligt godt når:\n\n- Du vil have **filbaseret indhold** der lever i dit Git-repository\n- Du har brug for **AI-drevne indholdsworkflows** (generering, oversættelse, SEO-optimering)\n- Du foretrækker **TypeScript-first** konfiguration frem for YAML eller markdown frontmatter\n- Du vil have en **visuel admin-brugerflade** uden kompleksiteten af et headless CMS\n\n## Arkitektur\n\n```\ncms.config.ts          → Collection- og feltdefinitioner\ncontent/               → JSON-dokumenter (én pr. fil)\npackages/cms           → Kernemotor (@webhouse/cms)\npackages/cms-admin     → Next.js admin-brugerflade (@webhouse/cms-admin)\npackages/cms-ai        → AI-agenter (@webhouse/cms-ai)\npackages/cms-cli       → CLI-værktøjer (@webhouse/cms-cli)\npackages/cms-mcp-*     → MCP-servere til AI-platformsadgang\n```\n\nKernepakken (`@webhouse/cms`) er framework-agnostisk — den læser og skriver JSON-filer. Admin-brugerfladen (`@webhouse/cms-admin`) er en selvstændig Next.js-applikation der forbinder til kernemotor.\n\n## Næste skridt\n\n- [Hurtig start](/docs/quick-start-da) — opret og kør dit første projekt på under 5 minutter\n- [Konfigurationsreference](/docs/config-reference-da) — lær hvordan du definerer collections og felter\n- [Felttyper](/docs/field-types-da) — udforsk alle 22 felttyper",
     "category": "getting-started",
     "order": 0,
     "_seo": {
@@ -29,4 +29,4 @@
   "_fieldMeta": {},
   "createdAt": "2026-03-29T21:57:53.108Z",
   "updatedAt": "2026-03-29T22:24:50.154Z"
-}
+}

content/docs/introduction.json

@@ -7,7 +7,7 @@
   "data": {
     "title": "Introduction",
     "description": "What is @webhouse/cms and why it exists — a file-based, AI-native CMS for TypeScript projects.",
-    "content": "## What is @webhouse/cms?\n\n`@webhouse/cms` is a **file-based, AI-native CMS engine** for TypeScript projects. You define collections and fields in a `cms.config.ts` file, and the CMS stores content as flat JSON files in a `content/` directory — one file per document, organized by collection.\n\nIt provides:\n\n- **REST API server** — Hono-based API for reading and writing content\n- **Static site builder** — 9-phase build pipeline generating HTML, sitemap, RSS, robots.txt, and AI discovery files\n- **AI content generation** — built-in agents for writing, SEO optimization, translation, and more\n- **Visual admin UI** — full-featured editor at [webhouse.app](https://webhouse.app) with rich text, blocks, media, and scheduling\n- **MCP integration** — Model Context Protocol server for AI platform access to your content\n\n## Who is it for?\n\n@webhouse/cms is designed for developers building content-driven websites with Next.js. It works especially well when:\n\n- You want **file-based content** that lives in your Git repository\n- You need **AI-powered content workflows** (generation, translation, SEO optimization)\n- You prefer **TypeScript-first** configuration over YAML or markdown frontmatter\n- You want a **visual admin UI** without the complexity of a headless CMS\n\n## Architecture\n\n```\ncms.config.ts          → Collection + field definitions\ncontent/               → JSON documents (one per file)\npackages/cms           → Core engine (@webhouse/cms)\npackages/cms-admin     → Next.js admin UI (@webhouse/cms-admin)\npackages/cms-ai        → AI agents (@webhouse/cms-ai)\npackages/cms-cli       → CLI tools (@webhouse/cms-cli)\npackages/cms-mcp-*     → MCP servers for AI platform access\n```\n\nThe core package (`@webhouse/cms`) is framework-agnostic — it reads and writes JSON files. The admin UI (`@webhouse/cms-admin`) is a standalone Next.js application that connects to the core engine.\n\n## Next steps\n\n- [Quick Start](/docs/quick-start) — scaffold and run your first project in under 5 minutes\n- [Configuration Reference](/docs/config-reference) — learn how to define collections and fields\n- [Field Types](/docs/field-types) — explore all 22 field types",
+    "content": "## What is @webhouse/cms?\n\n`@webhouse/cms` is a **file-based, AI-native CMS engine** for TypeScript projects. You define collections and fields in a `cms.config.ts` file, and the CMS stores content as flat JSON files in a `content/` directory — one file per document, organized by collection.\n\n> **🔥 New here?** See [Hot Features](/docs/hot-features) for the patterns we recommend by default for new sites — Instant Content Deployment, Beam, Headless API, and more.\n\n\nIt provides:\n\n- **REST API server** — Hono-based API for reading and writing content\n- **Static site builder** — 9-phase build pipeline generating HTML, sitemap, RSS, robots.txt, and AI discovery files\n- **AI content generation** — built-in agents for writing, SEO optimization, translation, and more\n- **Visual admin UI** — full-featured editor at [webhouse.app](https://webhouse.app) with rich text, blocks, media, and scheduling\n- **MCP integration** — Model Context Protocol server for AI platform access to your content\n\n## Who is it for?\n\n@webhouse/cms is designed for developers building content-driven websites with Next.js. It works especially well when:\n\n- You want **file-based content** that lives in your Git repository\n- You need **AI-powered content workflows** (generation, translation, SEO optimization)\n- You prefer **TypeScript-first** configuration over YAML or markdown frontmatter\n- You want a **visual admin UI** without the complexity of a headless CMS\n\n## Architecture\n\n```\ncms.config.ts          → Collection + field definitions\ncontent/               → JSON documents (one per file)\npackages/cms           → Core engine (@webhouse/cms)\npackages/cms-admin     → Next.js admin UI (@webhouse/cms-admin)\npackages/cms-ai        → AI agents (@webhouse/cms-ai)\npackages/cms-cli       → CLI tools (@webhouse/cms-cli)\npackages/cms-mcp-*     → MCP servers for AI platform access\n```\n\nThe core package (`@webhouse/cms`) is framework-agnostic — it reads and writes JSON files. The admin UI (`@webhouse/cms-admin`) is a standalone Next.js application that connects to the core engine.\n\n## Next steps\n\n- [Quick Start](/docs/quick-start) — scaffold and run your first project in under 5 minutes\n- [Configuration Reference](/docs/config-reference) — learn how to define collections and fields\n- [Field Types](/docs/field-types) — explore all 22 field types",
     "category": "getting-started",
     "order": 0,
     "_seo": {
@@ -29,4 +29,4 @@
   "_fieldMeta": {},
   "createdAt": "2026-03-29T21:41:59.066Z",
   "updatedAt": "2026-03-29T21:41:59.067Z"
-}
+}

src/ai-guide/index.md

@@ -43,6 +43,7 @@ Common tasks → which modules to fetch:
 - **"Add a blog"** → 02, 03, 08, 13
 - **"Add a collection"** → 02, 03, 07
 - **"Set up SEO"** → 15
+- **"Deploy a Next.js site with live content updates"** → 18 (default to **ICD** — instant content delivery via `/api/revalidate` webhook; avoid full Docker rebuilds for every word edit)
 - **"Deploy to Vercel"** → 18
 - **"Add i18n"** → 17, 02
 - **"Create a product catalog"** → 02, 03, 04, 08
@@ -53,6 +54,13 @@ Common tasks → which modules to fetch:
 - **"Content relationships"** → 14, 02
 - **"Full config reference"** → 02, 03, 10
 
+> **Note for AI agents scaffolding new Next.js sites:** the recommended deploy
+> pattern is **Instant Content Deployment (ICD)** — your site gets a tiny
+> `/api/revalidate` route that receives HMAC-signed webhooks from CMS admin,
+> writes the document to disk, and calls `revalidatePath()`. Content edits
+> go live in ~2 seconds without a Docker rebuild. Bake this into the project
+> from day one. See module **18 (Deployment)** for the full template.
+
 ## Essential Quick Reference
 
 ### Document JSON format

src/app/page.tsx

@@ -223,6 +223,24 @@ export default function HomePage() {
           >
             Read the Docs
           </Link>
+          <Link
+            href="/docs/hot-features"
+            style={{
+              display: "inline-flex",
+              alignItems: "center",
+              gap: "0.4rem",
+              padding: "0.65rem 1.5rem",
+              border: "1px solid var(--color-gold)",
+              borderRadius: 8,
+              color: "var(--color-gold)",
+              fontWeight: 600,
+              fontSize: "0.9rem",
+              textDecoration: "none",
+            }}
+            title="What's new and worth knowing right now"
+          >
+            🔥 Hot Features
+          </Link>
           <a
             href="https://github.com/webhousecode/cms"
             target="_blank"