Blume

Why it's ranked here

The surface here is wider than most documentation generators, and that is the reason to spend time on it. Fifteen subcommands are registered, covering work other tools leave to you: link validation, an SEO audit of the built HTML, client bundle budgets that can fail a build, translation, and a command that has an agent answer your questions using only the docs. Agent access is a first class path: the server exposes four tools whose schemas drive both validation and discovery. The cost is a heavy dependency surface and a single copyright holder.

What's good

The agent facing server never rejects a tool call on argument shape: a bare string is accepted where a list is expected, and an out of range result limit is clamped into the allowed one to twenty window instead of erroring. The advertised tool schema is generated from the same definitions the runtime parses with, so the two cannot drift. The repository documents a per file line and function coverage gate enforced by the test runner config. Comments record why a low level protocol server was chosen over the convenience wrapper. Hosted search upload failures warn and let the build finish.

Tradeoffs

Weight is the trade. The published package declares close to eighty runtime dependencies, pulling in Astro, React, Tailwind, Shiki, Mermaid, Sharp and an OpenAPI parser whether your site uses them or not. Node 22.12 or newer is required. The most interesting commands, translation, documentation evals, and agent applied audit fixes, shell out to Claude Code or Codex, so they do nothing without one of those installed. Copyright sits with one person. Because the framework generates and owns the project, deep customization means component overrides or a one way exit to a plain Astro app.

How to use it well

Best fit is a team whose docs already live as Markdown beside the code, and who want coding agents reading those docs without scraping HTML. It earns a slot in continuous integration: link validation, the built site audit, and the JavaScript budget gates all signal through exit codes next to your test job. Take the exit path early if marketing pages and docs must share one codebase. It does not write or edit content for you, gives non technical authors no editing interface, and hosting stays your problem.

Observed

License

MIT, single copyright holder

Language

TypeScript, ES modules throughout

Install surface

npm package exposing a single blume binary

Interfaces

CLI, importable library with subpath exports, and a Model Context Protocol server (HTTP plus a stdio subcommand)

Package managers

Bun, pnpm, npm and yarn all supported

Deploy targets

Static output, or server output via Vercel, Netlify, Node and Cloudflare adapters

Search

Local Orama by default; Pagefind, FlexSearch, Algolia, Typesense, Orama Cloud and Mixedbread are optional peers

Localization

Built-in locale packs merged onto English, community maintained

Repository shape

Bun and Turborepo monorepo: the published package plus a docs site built with the tool itself

Configuration

TypeScript config validated by a zod schema, authored through typed helpers