CMS

What It Does

CMS capabilities are provided by:

• @kit/fumadocs for MDX/docs rendering pipelines.
• @kit/notion for Notion-backed content retrieval, rendering, search, and markdown export.
• @kit/cms for reusable docs/content UI blocks.

When To Use

• You need documentation or blog content architecture.
• You want either Git-based MDX or Notion as source-of-truth.

Prerequisites

• Decide content source model: repository MDX vs Notion API.

How To Use

• Use Fumadocs for content stored in your repo.
• Use Notion for editorial workflows in Notion.
• Reuse CMS UI components like TOC, Ask AI, and search where needed.

MCP Context

Copy to Clipboardcapability: cms_architecture
entrypoints:
  - @kit/fumadocs
  - @kit/notion
  - @kit/cms
inputs:
  - content_source_choice
outputs:
  - documentation_or_blog_runtime
constraints:
  - notion mode requires Notion credentials and schema mapping
side_effects:
  - external API requests in Notion mode

Agent Recipe

1. Select source model (MDX or Notion).
2. Apply corresponding package config and routes.
3. Add optional UX components (TOC, Ask AI, search).

Troubleshooting

• If content fails in Notion mode, validate Notion schema mapping keys.
• If MDX content is not indexed, verify source config and meta.json structure.

Related

• Fumadocs
• Notion