Fumadocs knowledge-base comparison

What it is

Fumadocs combines a Next.js documentation application with MDX content and documentation navigation. This evaluation will preserve the complete publicly available Datalumina company knowledge-base example while adapting it to the official static-export starter.

Why test it against Quartz

Quartz already publishes this operational wiki from Markdown. Fumadocs is being evaluated for a more application-like handbook: structured navigation, employee profiles, rich React/MDX pages, and browser-side documentation search. This is a comparison, not a demonstrated replacement for Quartz. Quartz upstream supplies the wiki baseline.

flowchart LR
  A[Verified upstream sources] --> B[Application preparation pending]
  B --> C[Build and interaction proof pending]
  D[Quartz operational wiki] --> E[Setup and release evidence]

Verified versions and source

Verified on 2026-09-27: create-fumadocs-app 16.2.9; fumadocs-core and fumadocs-ui 16.15.14; fumadocs-mdx 15.4.5. The Datalumina content source is pinned to b01ec5e5a50bd718b8233710a9510be5e35c99ad. Its unmodified server application does not support static export.

Fumadocs · official static deployment · complete source example · Datalumina guide

Version lookups establish source provenance, not installed or deployed versions. The project versions.json records exact source pins, lookup dates, and unknown values separately.

Read by task

• setup — source-derived preparation, output paths, and acceptance checks.
• Restricted operations — the intended authenticated full-build operations route.
• Application destination — intended destination, not a current availability claim.

Current status

Application pending. This is the initial wiki-first preparation. No application build, deployment, search interaction, shared chat integration, browser screenshot, or authentication proof is claimed here. Wiki configuration and source content have been prepared; publication and live route verification remain the release owner’s responsibility.

The intended access split is an authenticated application, a public wiki root, and an authenticated full wiki under /private/. This describes the deployment contract, not observed ingress behavior. The public build excludes the source private directory; frontmatter alone is not an access control.