Fumadocs FrontendBeautiful developer documentation, fast
Fumadocs is our framework of choice for building modern documentation sites — full-text search, MDX authoring, versioning, and API reference pages that developers actually enjoy reading.
Fumadocs is a modern documentation framework built on Next.js App Router — purpose-built for developer documentation sites that need full-text search, MDX content authoring, API reference generation, and versioning out of the box. Unlike generic static site generators, Fumadocs gives you a polished reading experience with syntax highlighting, content collections, and interactive components while keeping everything statically generated for instant loads. It's our go-to when clients need documentation that developers actually enjoy using.
Quick start
npx create-fumadocs-app my-docs
cd my-docs
npm run devRead the full documentation at fumadocs.vercel.app
MDX-powered content
Write docs in Markdown with custom React components — callouts, tabs, code groups, and more.
Full-text search
Built-in search with Orama or Algolia — instant results as users type, no extra backend.
Auto-generated API reference
Point Fumadocs at your OpenAPI spec and get a fully rendered, interactive API reference.
Versioned docs
Manage multiple release versions side by side — users always see the docs for their version.
Static generation
Built on Next.js App Router — every page is statically generated for instant first loads.
Shiki syntax highlighting
Server-side code highlighting with Shiki — accurate grammar, zero client-side JS cost.
Why it's hard
Next.js App Router knowledge required
Fumadocs is tightly coupled to Next.js App Router conventions — teams unfamiliar with RSC, layouts, and the app directory will face a learning curve before customizing effectively.
Custom component integration
While MDX support is excellent, building custom interactive components (live code editors, API playgrounds) requires understanding Fumadocs' plugin system and serialization boundaries.
Search configuration complexity
Choosing between built-in Orama search, Algolia, or a custom search backend — and configuring indexing, relevance tuning, and facets — requires careful planning for large doc sites.
Multi-version documentation management
Managing docs for multiple product versions simultaneously (v1, v2, beta) introduces content duplication challenges and requires a clear branching and content strategy.
Best practices
Use content collections with Zod schemas
Define strict schemas for your frontmatter — title, description, category, version. This catches errors at build time and enables type-safe content queries.
Organize docs by user journey, not API structure
Structure navigation around what users need to do (Getting Started, Guides, Reference) rather than mirroring your internal code organization.
Enable OpenAPI integration for API docs
Point Fumadocs at your OpenAPI spec to auto-generate interactive API reference pages — keeps docs in sync with your actual API without manual maintenance.
Pre-render everything with static generation
Fumadocs on Next.js App Router can statically generate every page — use generateStaticParams for instant loads and zero server cost.
Frequently asked questions
Related technologies
Related services
Looking for end-to-end delivery? These services complement Fumadocs projects.
Web Design
Websites that load fast, look sharp, and convert visitors into customers
Web App Development
Full-stack web applications built for real users and real scale
SaaS Development
Subscription software built to scale from day one
Performance Optimization
Find the bottlenecks and fix them — in code, queries, and infrastructure
Want to build with Fumadocs?
Talk to our engineering team about your Fumadocs architecture. We'll respond within 24 hours.
We limit intake each month so every project gets the focus it deserves.