Baseline CMS Documentation

CMS-agnostic content architecture — models, content examples, and documentation for a complete site system.

Getting Started

• Getting Started — Zero to working site: clone, configure UCM, sync schemas to your CMS, set up your frontend

Editor Roles

• Editor Roles — Role-based access control: 🔴 Admin, 🟠 Site Editor, 🟢 Content Editor, 🔵 Translator — mapped to CMS-native permissions

Site Structure

How the content model is organized, from the global site singleton down to individual pages.

• 🔴 Site — Global singleton: identity, icons, SEO defaults, navigation, error pages, and references to all configuration
• 🟢 Page — URL-addressable unit: SEO metadata, layouts, robots directives, navigation overrides, and the fallback chain from page to site
• 🟠 Error Page — Maps HTTP status codes (401, 403, 404, 500, 503) to custom page entries

Layouts

• 🟢 Layout — Content sections on a page: hero banners, card grids, feature lists, etc.
• 🟠 Layout Config — Layout configuration presets: responsive breakpoints, spacing, grid settings, animations, and overflow

Navigation

• 🟠 Navigation — Navigation containers and items: simple menus, dropdown menus, mega menus with columns and promotional slots, footer columns, and sidebar trees

Configuration

Referenced singletons for infrastructure settings, each with a dedicated visual editor and independent webhook lifecycle.

• 🔴 Crawler Config — robots.txt, web app manifest (manifest.json), and LLM index (llms.txt / llms-full.txt)
• 🔴 Sitemap — sitemap.xml generation: Vercel (built-in), Cloudflare (prebuild or Worker), and vanilla
• 🔴 Headers Config — Content Security Policy, Permissions-Policy, and Referrer-Policy
• 🔴 Security Config — security.txt for vulnerability disclosure (RFC 9116)
• 🔴 External Scripts — Third-party script management: analytics, consent, marketing, support

Content Features

• 🟠 Personas — Audience-specific search experiences with LLM system prompts and content retrieval bias
• 🔵 Translations — Namespace-based UI string localization, built into flat locale files at deploy time

Specifications

Core UCM specifications and platform-specific details are maintained in the sibling Unified Content Model project (@browser.style/unified-content).

• UCM Specification — Unified type system and CMS platform mappings
• UCF Specification — Unified Content Format for portable content instances

Platform Guides

Detailed implementation guides for each deployment platform — how to serve robots.txt, security headers, navigation, pages, and more.

• Vercel (Next.js) — Edge Config, route handlers, middleware, ISR
• Cloudflare (Workers / Pages) — Workers KV, fetch handlers, Cache API

Implementation Plans

Architecture plans and setup checklists.

• Webhook & Edge Delivery — Architecture plan: webhooks, edge stores, and generated files
• Markdown Endpoints — Serve pages as clean markdown for LLM consumption