Understanding Fumadocs

Fumadocs came from a simple goal: building docs should stay flexible. It aims to be a docs framework that does not lock you into a rigid box, but instead gives you something you can reshape when your product needs it.

Core Ideas

Less Abstraction: Fumadocs assumes you are comfortable writing code and wiring documentation into the rest of your app. Many documentation tools revolve around a single config file, but that often makes fine-grained control harder when you need to adjust rendering details or internal behavior. With Fumadocs, the implementation is visible, so you can understand how the site works instead of being limited to a narrow configuration surface.

Built on Next.js Fundamentals: The framework gives you utilities plus a polished UI layer, while you still rely on normal Next.js App Router capabilities such as Static Site Generation. That means Next.js developers are not forced into a brand-new mental model.

Opinionated Only About UI: Fumadocs UI, the default theme, is intentionally opinionated around User Interface. The focus is on responsive layouts and a solid user experience, while customization happens through a more flexible workflow inspired by Shadcn UI and powered by Fumadocs CLI. That approach also makes it easier to iterate on design and respond to feedback.

Why People Use Fumadocs

Flexibility is one of the main reasons.

You can use fumadocs-core as a headless UI library and apply your own visual system. Fumadocs MDX is also useful when you need to manage MDX content inside Next.js projects, and it ships with:

• Many built-in components.
• Typescript Twoslash, OpenAPI, and Math (KaTeX) integrations.
• Fast and optimized by default, natively built on App Router.
• Tight integration with Next.js, you can add it to an existing Next.js project easily.

If you want a side-by-side perspective, read Comparisons.

For Documentation Sites

Fumadocs puts strong emphasis on the authoring experience. It combines an attractive theme with automation features that help teams keep docs in step with the codebase.

Instead of treating documentation as an afterthought, it helps you keep shipping while your docs remain current. This very site is an example of a docs experience built with Fumadocs.

For Blog-Oriented Sites

Next.js already covers a lot on its own, so many blog features can be built with just Next.js.

What Fumadocs adds is a set of useful extras for documentation-heavy or content-heavy products, such as syntax highlighting, document search, and the default Fumadocs UI theme. That saves you from rebuilding the same pieces from scratch.

When It Fits Best

For many modern web apps, plain React.js is no longer enough by itself. Teams usually need a blog, landing pages, showcase content, FAQs, and documentation with a polished interface. In those situations, Fumadocs helps you assemble the docs portion with less boilerplate and less repeated setup.

Fumadocs is maintained by Fuma together with many contributors, with long-term maintainability in mind. Rather than chasing every possible feature request, the project focuses on keeping the essential features solid and well maintained. If that direction resonates with you, contributions are welcome.