Skip to content
⌘K

Ardo vs Nimbus

Compare React and Astro documentation workflows, UI ownership, API references, agent services, and migration paths.

On this page

Ardo and Nimbus keep documentation in your repository and publish static HTML plus Markdown for agents. The main choices are the component model, who maintains the UI files, and the kind of API reference you need.

Checked November 10, 2026 against released Ardo 6.5.0, Nimbus 0.19.4, and the Nimbus scaffolder 0.8.3. Nimbus sources below are pinned to its 0.19.4 release commit, not unreleased main. Ardo's baseline is its 6.5.0 tag.

Which Workflow Fits?

Choose Ardo when your documentation and examples should share one React component model, the API comes from TypeScript, and you prefer upgrading packaged UI. Custom React roots and layouts remain available.

Choose Nimbus when owning the layout, component, and style files is central to your workflow, or you need its more extensive OpenAPI reference and optional server-side agent services. Its project structure separates the files you own from the framework dependency; updates do not simply overwrite your site.

Feature Comparison

AreaArdo 6.5.0Nimbus 0.19.4
Page modelReact pages and MDX, prerendered and hydrated; ordinary document navigation.Astro pages and MDX. Interactive framework components use Astro islands.
UI ownershipUI ships in the package; compose or replace it with React.Scaffolded layouts, components, and styles live in your repository.
API referenceNative TypeScript reference plus a static local OpenAPI generator.OpenAPI 3.x, with dedicated operations, schemas, API versions, and reference UI.
LanguagesComplete static locale trees; this site's four languages use Palamedes catalogs.Nimbus exposes a site-wide document locale; language routing and translation belong to the Astro project.
VersioningStatic major-version snapshots; guide/API directories can be versioned independently of site pages.Separate content collections and paths for earlier docs versions; API versions have their own model.
SearchBuilt-in MiniSearch with generated indexes.Static Pagefind search, or a project-supplied provider.
Agent filesPer-page Markdown, llms.txt, llms-full.txt, and optional Agent Skills discovery.Markdown and llms.txt, with optional agent services.
MCPNo framework-provided runtime MCP endpoint.Optional remote MCP: list_pages and get_page; requires a server adapter and SDK.
Check and lintBuild-free ardo check, authoring ardo lint, and build-time internal-link checks.nimbus-docs check and lint, including fixes and upgrade checks.
Recipesardo add prints version-matched recipes; it writes no files.add copies component source; features hand recipes to an agent.
Browser JavaScriptReact hydration and interactive UI; no client router.Astro's islands plus chosen components and scripts; payload depends on that composition.
HostingStatic files on any static host.Static by default; request rendering and remote MCP need a server adapter.

Ardo's API guide, configuration, internationalization, and agent instructions describe the Ardo side of this table. Nimbus is pre-1.0; check its release notes before assuming a later minor release behaves identically.

Coming from Nimbus

Nimbus projectArdo equivalent or migration work
src/content/docs/Move prose into app/routes/, with locale and guide directories when configured. Preserve old URLs with explicit redirects.
title, description, sidebar.orderKeep title and description; map sidebar.order to order. Review other frontmatter fields individually.
mode: customUse layout: bare for a page without the docs frame.
src/components.ts and Astro componentsReview each component and its props; port Astro code to React or use Ardo's MDX components. There is no automatic component conversion.
astro.config.ts and nimbus()Use ardo.config.ts for framework options and custom Vite plugins, and app/root.tsx for UI composition.
OpenAPI referencesStart with Ardo's local openapi configuration. Nimbus API versions, schema views, and interactive reference controls are not a drop-in mapping.

Audit drafts, hidden pages, and publishing rules before moving content; Nimbus flags do not automatically preserve their meaning in Ardo. Follow the setup instructions and verify the published route set, links, and examples in a production preview.

Gaps and Current Work

Nimbus also supports Git content sources and partial builds. Ardo's corresponding proposals remain #473 and #474. A CI checkout plus local content mapping is available today.

Ardo's authoring components, check/lint commands, static Mermaid rendering, and recipes are already implemented: #469, #470, #472, and #475. Automatic page share images are tracked in #471; they are not part of the released 6.5.0 baseline used here.

Edit this page on GitHubLast updated: November 13, 2026