{
  "slug": "hot-features",
  "title": "Hot Features",
  "description": "What's new and worth knowing right now in @webhouse/cms — the patterns we recommend by default for new sites.",
  "category": "",
  "order": 99,
  "locale": "en",
  "translationGroup": "hot-features-group-2026-05",
  "helpCardId": null,
  "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.",
  "excerpt": "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\nT",
  "seo": {}
}