Blume vs Docusaurus.The zero-config Docusaurus alternative.
Versioning, i18n, blog posts with RSS, and search like Docusaurus, plus API references, llms.txt, Markdown mirrors, and an MCP server built in. All from a folder of Markdown, with no React app to maintain.
npx blume migrate docusaurus --claude| Blume | Docusaurus | |
|---|---|---|
| You maintain | BlumeA folder of Markdown, plus one optional config file | DocusaurusA React site: docusaurus.config, sidebars.js, and any swizzled components |
| License | BlumeFree and open source (MIT) | DocusaurusFree and open source (MIT), maintained by Meta |
| Search | BlumeLocal search with no keys, or Pagefind, Algolia, and more by adapter | DocusaurusAlgolia DocSearch first-class; local search through community plugins |
| Agent features | Blumellms.txt, Markdown mirrors, and a JSON API by default; an opt-in MCP server | DocusaurusCommunity plugins for llms.txt and Markdown routes; no official MCP server |
| AI assistant | BlumeAsk AI on the model you choose, billed by your provider | DocusaurusAsk AI through Algolia DocSearch, off by default |
| API references | BlumeOpenAPI, AsyncAPI, and GraphQL, with a Try it playground | DocusaurusOpenAPI and GraphQL through community plugins |
| Versioning | Blumeblume version snapshots with a switcher and scoped search | DocusaurusBuilt-in versioning with docs:version |
| Languages | Blumeblume translate fills in every locale with your coding agent | DocusaurusBuilt-in i18n with Git or Crowdin workflows |
Docusaurus details are from its own pages as of September 23, 2026: Search, Versioning, i18n, Community plugins, llms.txt issue. Something out of date? Let us know
Your docs come with you.Your admonitions already fit, and an agent does the rest.
- Admonitions already fit.
:::note,:::tip, and the rest are directives in both (in.mdxpages on Blume), and Tabs and TabItem become Tabs and Tab.- Sidebars move into folders.
- Autogenerated sidebars become Blume's filesystem navigation, and each
_category_.jsonbecomes a typedmeta.ts. - Versions, blog, and locales come along.
- The agent migrates your latest version, keeps the blog's RSS feed at
/blog/rss.xml, and moves translations into locale folders. - Plugins become config.
- OpenAPI and GraphQL doc plugins, static client redirects, and Mermaid become built-in Blume config.
Docusaurus
Blume
- docusaurus.config.tsblume.config.ts
- _category_.jsonmeta.ts
- <TabItem label="…"><Tab title="…">
- sidebar_positionsidebar.order
- static/public/
- :::tip Title:::tip[Title]
- ```bash npm2yarn```package-install
When Docusaurus might suit you better.Blume isn't the right fit for every team.
- You want the largest ecosystem.
- Docusaurus has years of production use, around a million weekly npm downloads, and a plugin for nearly everything.
- You translate through Crowdin.
- Docusaurus documents a Crowdin workflow and extracts UI strings for translators. Blume translates with your coding agent instead.
- You want to own a React app.
- Docusaurus gives you React pages, swizzling for any theme component, and a plugin lifecycle API. Blume keeps the app hidden until you eject.
- 1
Run one command in your docs project.
Using Codex? Swap
--claudefor--codex. - 2
Review the agent's edits.
It follows Blume's migration playbook for MintlifyFumadocsDocusaurusStarlightNextra, rewriting your config and pages in place, so you review the whole move as one diff.
- 3
Preview the result.
Run
npx blume dev, then read the agent's summary of anything it dropped or approximated.
Questions, answered.About moving from Docusaurus to Blume.
Why switch from Docusaurus if both are free?
Because Blume has nothing to maintain. There's no React app or swizzled theme to upgrade, and API references, local search, llms.txt, Markdown mirrors, and an MCP server are built in rather than community plugins.
Can Blume version my docs like Docusaurus?
Yes. blume version freezes a snapshot of the current docs, and Blume adds the version switcher, an old-version banner, version-scoped search, and canonical links to the latest. The agent migrates your latest Docusaurus version by default.
Do my admonitions and MDX carry over?
Yes. Docusaurus admonitions are already directive syntax, so :::note and :::tip carry over. Blume reads directives in MDX only, so the agent renames every .md page that uses one to .mdx, converts Tabs, and moves static/ into public/.
What happens to my blog?
Posts become Blume blog pages with an RSS feed at the same /blog/rss.xml. The agent moves dates from filenames into frontmatter and adds redirects for the old dated URLs.
What doesn't the migration carry over?
Swizzled theme components, React pages under src/pages, footer columns, and a few frontmatter keys. The agent reports each one so you can rebuild it with a layout slot or a custom page, or leave it out.
Upgrade your docs with Blume.
Install today and ship a production-grade docs site in minutes. Free and open source, forever.
npx blume init