Assessment

This assessment separates hands-on impressions from externally verifiable facts. Package and documentation facts were checked on 2026-07-19.

Bottom line

Hands-on impression (subjective): Fumadocs offers the richest composable baseline of the React-oriented samples so far. The default UI is polished, the content loader and page tree are coherent, and the static-search path is thoughtful. That flexibility also means more concepts and configuration than a small Markdown-first generator.

Strengths

• Hands-on impression: The Core / MDX / UI separation makes framework boundaries visible without making the default theme feel unfinished.
• Evidence in this site: one loader supplies routes, localized sidebars, previous/next navigation, and structured data for search.
• Evidence in this site: the official static-template pattern produces directory-style HTML plus a browser-side Orama index, with no production server.
• Evidence in this site: React components, math, Mermaid, CSS tokens, dark mode, and bilingual UI coexist without replacing the docs layout.

Concerns and trade-offs

• Hands-on impression: The layered package model (fumadocs-core, fumadocs-mdx, UI, Next.js, Tailwind, and integrations) has more upgrade surfaces than VitePress's small baseline.
• Evidence: Fumadocs provides i18n primitives and layout navigation, not complete application translation. This project still owns locale routing, Japanese strings, and 1:1 content parity.
• Evidence: Mermaid and math need configured integrations. GitHub-style alert markers do not receive a dedicated alert treatment in this baseline; Fumadocs Callout is the native UI alternative.
• Evidence: static search downloads the exported index into the browser; the official guide warns that this can become expensive for large sites.

Maintenance snapshot — 2026-07-19

Externally verifiable facts: the current official generator produced fumadocs-core and @fumadocs/base-ui 16.11.5, fumadocs-mdx 15.2.0, and Next.js 16.2.10 for its static template. npm lists fumadocs-core@16.11.5 and @fumadocs/base-ui@16.11.5, while the public release history shows ongoing package releases. Version numbers demonstrate recent publishing, not future support guarantees.

The official documentation describes static builds, Next.js internationalization, and static Orama search, matching the implementation exercised here.

Decision guidance

Choose Fumadocs when a React/Next.js team wants an excellent default docs UI without giving up headless content and layout composition. Budget for its layered dependency surface and for application-owned i18n. A leaner generator is easier when the team only needs Markdown, a sidebar, and static output.