Public Docs Plan — docs.cmmd.ai

Customer-facing documentation does NOT live in Confluence (or internal-docs). It goes to docs.cmmd.ai — a dedicated docs site, mirroring how OpenAI and Anthropic run their public docs.

Field	Value
Status	Proposed — pending implementation
Owner	@aphaiboon
Target launch	Phase 1 within 30 days of plan approval

TL;DR

Build docs.cmmd.ai on Mintlify. Same stack as docs.anthropic.com. Open-source alternative is Docusaurus (used by Meta). Pick Mintlify for speed-to-launch; revisit Docusaurus at year 2 if vendor lock-in becomes painful.

Why public docs must be a separate product

This is the #1 KB anti-pattern to avoid. Mixing internal wiki and customer docs in one tool fails on:

Concern	Why a shared tool loses
SEO	Wiki URLs are unfriendly, slow to index, locked to wiki domain
Design control	Wiki themes are locked — can’t match cmmd.ai brand
Public access	Permission split inside one tool is fragile — high accidental-exposure risk
Build / deploy	Wiki content can’t be version-controlled with the codebase
AI-friendly	Mintlify ships built-in AI search; wiki customer-facing search is sub-par

Anthropic, OpenAI, Stripe, Linear all keep these strictly separate.

Tool comparison

Option A: Mintlify (recommended)

What it is: Hosted SaaS that turns MDX files in a Git repo into a polished docs site. What docs.anthropic.com runs on.

Pros	Cons
Launches in days, not weeks	Vendor lock-in (export possible but painful)
Beautiful out-of-box (literally identical to Anthropic’s docs)	Pricing scales with seats
MDX with rich components (cards, tabs, code groups)	Custom design beyond their theme is limited
Built-in AI search (“Ask AI” on every page)	Less community ecosystem than Docusaurus
Auto-renders OpenAPI specs into API reference pages	—
Custom domain, dark mode, search included	—

Pricing (2026 estimate): Free tier for OSS / unlisted. ~$120/mo for production custom domain + analytics.

Option B: Docusaurus

What it is: Open-source MDX docs framework by Meta. Used by Algolia, Storybook, Supabase.

Pros	Cons
Free, self-hostable on Vercel / Netlify	More setup — 1–2 weeks vs. days
Full design ownership (any React component)	Design polish is on you
No vendor lock-in	Search via Algolia DocSearch (free if approved, ~$50/mo otherwise)
Huge community + plugin ecosystem	OpenAPI integration is via plugin
Versioning + i18n built-in	—

Option C: Custom build

Don’t. Stripe-style custom docs ($100k+ engineering investment) is not where a small team should burn cycles.

Recommendation: Mintlify for v1

Mirror what works for our biggest reference customers (Anthropic, Resend, Cursor). Re-evaluate at year 2.

Information architecture (docs.cmmd.ai)

Same shape as docs.anthropic.com / docs.openai.com:

docs.cmmd.ai/
├── Get Started
│   ├── Quickstart
│   ├── Set up your workspace
│   ├── Name your Sidekick
│   └── Your first task / project / thread
├── Concepts
│   ├── The 30-Second Rule
│   ├── Sidekick: Modes, Tools, Threads
│   ├── Brain: Documents, Memory, Core
│   ├── Apps & Marketplace
│   ├── Workspaces & Teams
│   └── Privacy & Data Ownership
├── Guides
│   ├── Onboarding a new team
│   ├── Using Sidekick to plan your day
│   ├── Importing data from Notion / ClickUp / Linear
│   ├── Configuring integrations (Slack, Google, GitHub)
│   ├── EOS-style operating cadence with CMMD
│   └── Setting up workspace SSO
├── App Reference
│   ├── Sidekick (one page per mode + tools list)
│   ├── Brain
│   ├── Comms
│   ├── Calendar
│   ├── Tasks
│   ├── Projects
│   ├── Strategy & Goals
│   ├── CRM
│   └── Accounting
├── Integrations
│   ├── Slack
│   ├── Google (Gmail, Calendar, Drive)
│   ├── GitHub
│   ├── Stripe
│   └── (full Composio catalog)
├── API Reference (when public API ships)
│   └── (OpenAPI auto-rendered)
├── FAQ
├── Troubleshooting
└── Changelog & Release Notes

Top nav: Get Started · Concepts · Guides · App Reference · API · Changelog · Status (link to status.cmmd.ai)

Phased rollout

Phase	Scope	Timing
M0 (now)	This plan document, lock domain docs.cmmd.ai	Week 0
M1 — Soft launch	Mintlify setup, register domain, ship 5 pages: Quickstart, Sidekick overview, Brain overview, Integrations overview, Changelog	Week 1–2
M2 — Public beta	Full Concepts + App Reference (one page per app). Link from cmmd.ai header.	Week 3–6
M3 — GA	Guides + FAQ + Troubleshooting populated. Sidekick “Ask the docs” widget on cmmd.ai. SEO baseline.	Week 7–10
M4 — API docs	When public REST API ships, add API Reference auto-generated from OpenAPI	Aligned with API launch

What goes where — internal-docs vs. docs.cmmd.ai

Content	internal-docs (this wiki)	docs.cmmd.ai
Architecture, runbooks, ADRs	Engineering	Never
Sales playbook, demo script	GTM	Never
Internal HR policies	People & Ops	Never
Roadmap (with target dates / unreleased features)	Product	Public version only (“Now / Next / Later”)
App reference (how Sidekick modes work)	Mirrored — durable copy in App Catalog	Customer-facing version
API reference	Internal API only	Public API only
Getting started guide	Not duplicated	Lives here
Changelog	Engineering history (raw PR list)	Curated customer-facing version

Rule of thumb: if it has a target date, an unreleased feature, an internal architecture detail, or revenue numbers — it stays in internal-docs. If a customer would benefit from reading it — it goes on docs.cmmd.ai.

Open questions

• Who owns docs.cmmd.ai day-to-day? (Suggest: rotating eng-on-deck for app reference; PM for guides; @aphaiboon for changelog voice)
• Auth-gated docs for enterprise customers? (Likely yes for API keys + admin guides — Mintlify supports this)
• Translation? (English-only at launch; reassess at year 2)
• Tone & voice guide?

Decision needed

• CEO approval: Mintlify for docs.cmmd.ai — @aphaiboon
• Budget: ~$120/mo + ~$15/yr domain ≈ $1.5k/yr Y1
• First-PR owner: pick an eng to set up the repo + first 5 pages

Related

• How We Use This Wiki
• App Catalog
• Templates