Blume vs GitHub Wiki.When your docs outgrow the wiki.
A GitHub wiki is the fastest place to start: no setup, a web editor, and pages beside your code. Blume turns the same Markdown into a docs site that search engines and agents can read, with clean URLs, llms.txt, and changes reviewed in pull requests.
npx blume migrate github-wiki --codex| Blume | GitHub Wiki | |
|---|---|---|
| Price | BlumeFree and open source, with no seat limits | GitHub WikiFree in public repositories; private wikis need GitHub Pro, Team, or Enterprise |
| Hosting | BlumeAny host: Vercel, Netlify, Cloudflare, Node, or static files | GitHub WikiOn github.com beside your code, in GitHub's own layout |
| Editing | BlumeMarkdown and MDX in your repo, in any editor | GitHub WikiA web editor on GitHub, or Git pushes to the wiki's own repository |
| Navigation | BlumeFolders, with meta.ts for order and titles | GitHub WikiAn alphabetical page list, plus a hand-written _Sidebar.md and _Footer.md |
| Search | BlumeLocal search with no keys, or Pagefind, Algolia, and more by adapter | GitHub WikiGitHub's site search filtered to wikis, plus a page filter |
| Search engines | BlumeA sitemap, canonical URLs, Open Graph cards, and JSON-LD | GitHub WikiIndexed only with 500+ stars and editing restricted to collaborators |
| Agent features | Blumellms.txt, Markdown mirrors, and a JSON API by default; an opt-in MCP server | GitHub WikiGitHub's APIs and MCP server don't read wikis; agents can clone its Git repo |
| Versioning | Blumeblume version snapshots with a switcher and scoped search | GitHub WikiRevision history for each page, with diffs and reverts |
GitHub Wiki details are from its own pages as of October 7, 2026: About wikis, Editing, Permissions, Sidebar and footer, Search, MCP server. Something out of date? Let us know
Your docs come with you.Your pages stay Markdown, and an agent does the move.
- Every page gets a clean URL.
/wiki/Getting-Startedbecomes/getting-started: one flat, lowercase route per page, wherever its file sat in the wiki.- The sidebar becomes folders.
- Each
_Sidebar.mdgroup becomes a folder with ameta.ts, and pages the sidebar didn't list go in a collapsed More pages group. - Links, alerts, and images convert.
[[Page Name]]links become Markdown links, alerts become:::callouts, and images stored in the wiki move beside the pages.- A stub for every old page.
- The old URLs stay on github.com, so the agent prepares a link stub for every wiki page, for you to push once the new site is live.
GitHub Wiki
Blume
- Home.mddocs/index.md
- /wiki/Getting-Started/getting-started
- _Sidebar.md(group)/meta.ts
- [[Page Name]][Page Name](/page-name)
- [[text|Page Name]][text](/page-name)
- > [!WARNING]:::warning
- _Footer.mdfooter.links
When GitHub Wiki might suit you better.Blume isn't the right fit for every team.
- You want zero setup.
- Every GitHub repository comes with a wiki: no config, no build, and no deploy. Pages go live as soon as you save them.
- You want anyone to edit in the browser.
- Each wiki page has an Edit button on GitHub, and a public wiki can open editing to anyone with a GitHub account. Blume pages are files in your repository, changed through Git.
- Your docs are private to the repository.
- A private repository's wiki is readable only by people with access to the repository, behind GitHub's sign-in. Blume has no sign-in of its own, so a private Blume site relies on your host's access protection.
- 1
Run one command in your docs project.
Using Claude Code? Swap
--codexfor--claude. - 2
Review the agent's edits.
It follows Blume's migration playbook for MintlifyFumadocsDocusaurusStarlightNextraGitBookMkDocsReadMeVitePressFernRedoclyVuePressDocsifyDocusmdBookJekyllGitHub Wiki, 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 GitHub Wiki to Blume.
Why move from a GitHub wiki?
Search engines index a wiki only once it has 500 or more stars and editing is restricted to collaborators, and GitHub's APIs and MCP server can't read wiki pages. Blume publishes your docs as a site of their own, with a sitemap, llms.txt, Markdown mirrors, and changes that go through pull requests with the code.
Can I keep my wiki pages?
Yes. npx blume migrate github-wiki --codex gives every page a clean URL, converts [[wiki links]] and alerts, moves the wiki's images beside the pages, and rebuilds _Sidebar.md as folders.
Will my old wiki links redirect?
No. The old pages stay on github.com, where Blume's redirects can't reach. The agent prepares a one-line link stub for every wiki page, so once you push them, old links from issues and bookmarks land one click from the new page.
Can my docs stay on GitHub?
Yes. The docs can live in a folder of your main repository and change in the same pull requests as the code, and blume build outputs static files that GitHub Pages can serve from an Actions workflow.
What doesn't the migration carry over?
Editing in the browser, each page's revision history (unless you bring it in with git subtree), the Pages list, footer text other than a copyright line, sidebar prose, image sizes, and GeoJSON maps and 3D models. Old wiki URLs never redirect, so the agent prepares stubs instead and reports everything it dropped.
Upgrade your docs with Blume.
Install today and ship a production-grade docs site in minutes. Free and open source, forever.
npx blume init