Engineering teams routinely spend two to three days wiring up documentation tooling before writing a single sentence of actual docs.

The config tax on developer documentation finally has a receipt

Every serious project needs docs, but the standard workflow buries developers in boilerplate: choose a static site generator, configure routing, wire up search, set up theming, and hope Core Web Vitals survive the process. That entire setup loop now has a direct replacement.

Drop a folder of Markdown files, get a production docs site

Meet Blume reads a directory of Markdown or MDX files and outputs a full documentation site complete with navigation, search, theming, and Open Graph images. You run the CLI, point it at your content folder, and Blume generates a hidden Astro project in a .blume/ directory that renders every page through a single catch-all route. The core theme ships zero client-side JavaScript by default, so pages score well on Core Web Vitals without any manual optimization.

Documentation debt hits these teams first

• Developer advocates who need to ship external docs fast without pulling in a frontend engineer to configure the site
• Open-source maintainers who want a professional docs presence but cannot justify maintaining a custom Astro or Next.js setup
• Platform engineers who manage internal tooling docs and need AI-ready output their LLM pipelines can actually consume

The MIT license and npm availability mean any of these users can adopt Blume inside a corporate environment without a procurement conversation.

AI-readable documentation is becoming a procurement requirement

As LLM-powered developer tools increasingly index and query documentation directly, teams that ship structured, machine-readable docs gain a concrete distribution advantage over teams still exporting static PDFs or poorly structured wikis. Blume was built by a developer at OpenAI, and the AI-ready output is not an afterthought, which signals where documentation standards are heading at the infrastructure level.

What you can actually do on day one

• Ship a docs site from an existing Markdown folder in under ten minutes
• Override individual components without ejecting the entire project
• Eject to a standalone Astro app when you need full build control
• Run hot reload during editing without rebuilding the full Astro project

Blume is free and open-source under the MIT license, published to npm at version 1.0.3.

The one real limitation: it requires Node.js 22.12 or newer, which will block teams still running older Node versions in locked-down CI environments.

If you need more customization out of the box, Astro Starlight is the closest structural alternative. For teams already deep in a React ecosystem, Docusaurus remains the default choice, though it brings significantly more configuration overhead.

Zero-config documentation is quietly raising the baseline expectation

Tools like Blume compress what used to be a multi-day setup into a single CLI command, and that compression is starting to make legacy documentation pipelines look expensive. We cover tools like this every Friday — subscribe here and we’ll send the best ones straight to you.