Fumadocs best practices

Use when building or reviewing documentation sites with Fumadocs.

Mental model

• Fumadocs is a composable docs framework, not a closed box. Think in layers: content source, core, and UI.
• Prefer using the built-in abstractions where they fit, but keep ownership explicit when you customize layouts, sources, or rendering behavior.
• Treat the docs site as a real app: routing, layout, search, and content transforms should be understandable and testable.

Framework integration

• Keep the underlying React framework explicit. Fumadocs integrates with Next.js, TanStack Start, React Router, Waku, and other React environments, but deployment and runtime constraints still come from the host framework.
• Let the host framework own app-level concerns such as routing, runtime, and deployment configuration.
• Be careful with environment-specific behavior such as static export, server-only code, or framework-specific dynamic route behavior.

Content source and MDX