Comparison

Ardo is for React teams that want modern static docs without leaving React or moving their docs into a closed platform.

That makes the comparison more specific than "which docs tool is best?" Docusaurus, Starlight, VitePress, Nextra, Fumadocs, and Mintlify are all strong tools. The better question is: where should your docs live, and how much of your existing React code should they reuse?

At a glance

	Ardo	Docusaurus	Starlight	VitePress	Nextra	Fumadocs	Mintlify
Best fit	React teams, static docs	Mature OSS docs	Content-heavy Astro docs	Vue docs	Next.js docs	Composable React docs	Hosted API docs
UI model	React 19	React	Astro	Vue	Next.js	React	Hosted platform
Build model	Vite 8 + React Router	Webpack	Astro/Vite	Vite	Next.js	Depends on React framework	SaaS/Git workflow
React component reuse	Native	Native	Via islands	No	Native	Native	Platform-dependent
TypeScript API docs	TypeDoc built in	Plugin	Plugin	External	TSDoc	Type tables/OpenAPI	API tooling
Ownership	Open source, self-hosted files	Open source	Open source	Open source	Open source	Open source	Hosted SaaS
Measured Ardo first page	~155 KB gzip including assets	Heavier React stack	Lighter non-React stack	Lighter Vue stack	Next runtime	Depends on setup	Platform hosted

Docusaurus

Docusaurus is the established React documentation framework. It is mature, widely adopted, backed by Meta, and has built-in answers for documentation versioning, localization, blog content, search integrations, and a large plugin ecosystem.

Where it fits: large open-source projects, teams that need mature i18n/versioning today, and projects that benefit from the existing Docusaurus ecosystem.

Where Ardo differs: Ardo is built on Vite and React Router instead of webpack-era architecture. It has a smaller configuration surface, static output by default, and a more codebase-native model for teams already using modern React tooling.

Choose Docusaurus if maturity, plugin coverage, and versioned docs matter more than staying close to a Vite/React Router app stack.

Starlight

Starlight is an excellent Astro-powered docs framework. It is fast, accessible, polished, and especially strong for content-heavy documentation that does not need much app-level interactivity.

Where it fits: prose-heavy docs, low-JavaScript sites, Astro teams, and projects where content quality matters more than sharing React application components.

Where Ardo differs: Ardo treats React as the native component model. You can use your React providers, hooks, design system, and interactive examples directly in MDX. In Starlight, React runs through Astro islands, which is powerful but creates a different boundary.

Choose Starlight if page weight and Astro's content model are your top priorities.

VitePress

VitePress is the cleanest mental comparison for Ardo: a Vite-powered static documentation framework with a strong default theme and a content-first workflow.

Where it fits: Vue teams, Vite ecosystem projects, and documentation sites that want Vite speed with Vue-enhanced Markdown.

Where Ardo differs: Ardo brings that simple static-docs shape to React. If your app, examples, and design system are React, Ardo lets you reuse them instead of rewriting them in Vue.

Choose VitePress if your team is already in Vue or your docs do not need React component reuse.

Nextra

Nextra is a strong choice for Next.js teams. It combines MDX with Next.js routing, optimized links/images, search, i18n, and the rendering options you expect from the Next ecosystem.

Where it fits: teams whose product already lives in Next.js, or docs sites that need Next-specific rendering and deployment behavior.

Where Ardo differs: Ardo is not tied to Next.js. It is a Vite + React Router docs stack that outputs static files. That makes it a better fit when your React app is not a Next app, or when you want documentation as a smaller, focused static build.

Choose Nextra if your docs should be a first-class Next.js app.

Fumadocs

Fumadocs is a powerful React documentation toolkit. It is highly composable, supports multiple React frameworks, and offers deep building blocks for teams that want to assemble a custom docs system.

Where it fits: design-system-heavy teams, docs teams that want headless/composable primitives, and projects that need advanced content blocks such as OpenAPI, Storybook-style component docs, or custom sources.

Where Ardo differs: Ardo is intentionally narrower. It gives you a complete static docs product around React Router, Vite, MDX, and TypeDoc, with fewer architectural choices to make.

Choose Fumadocs if you want a docs framework toolkit. Choose Ardo if you want a ready-to-ship static React docs site.

Mintlify

Mintlify is a hosted developer documentation platform. It is strong for commercial API docs, hosted editing workflows, API playgrounds, analytics, and AI-oriented documentation features.

Where it fits: teams that want a managed docs platform, hosted collaboration, built-in API playground workflows, and less ownership of the build pipeline.

Where Ardo differs: Ardo is open source and codebase-native. Your docs live in your repository, build in your CI, deploy as static files, and render with your React components.

Choose Mintlify if a hosted docs product is the goal. Choose Ardo if source control, self-hosting, and React ownership matter more.

Who should not use Ardo?

Ardo is deliberately focused. It may not be the right tool if:

• you need mature i18n or versioned docs today;
• you want the lowest possible JavaScript payload and do not need React components;
• your docs should be a hosted SaaS workflow with analytics and API playground management;
• your product stack is Vue, Astro, or Next.js and you want docs to live inside that ecosystem;
• you need OpenAPI-first docs before Ardo's OpenAPI integration lands.

Those are good reasons to choose another tool.

The bottom line

Use Ardo when your documentation should feel like part of your React codebase: same component model, same styling strategy, same routing vocabulary, same repository, static output.

If that is your constraint, create your first Ardo project and start from the default theme.