Blume 2
Blume 2 is a fast and AI-ready static site generator focused on documentation sites. It allows users to drop Markdown and MDX content into folders and build a production-grade documentation site without the need to write or maintain application boilerplate. Blume 2 includes support for AI-assisted features, search, deployment adapters, content sources integration, API reference rendering, and analytics adapters.
Ratings & Reviews
Write a reviewBe the first to share a thoughtful review.
Information
Website checks
Automated checks of the public website by Google Lighthouse 13.5.0. Scores can vary between runs.
Checked Oct 24, 2026
Test this website on PageSpeedWebsite checks refresh automatically each week.
- Performance
- 88 out of 100, Needs improvement
- Accessibility
- 100 out of 100, Good
- Best Practices
- 100 out of 100, Good
- SEO
- 100 out of 100, Good
Around the Web
Set it up on a small internal docs site over the weekend to replace a Docusaurus install that had gotten slow to build. The one-command deploy on Astro actually works as advertised, and the search felt instant compared to what I had before. Theming was straightforward without fighting the config. Still poking at whether it handles a really large doc set (500+ pages) as well as it handles the smaller one I tried, so holding back a star until I've pushed it further.
galdayan · Review on Product Hunt
Can I add a custom React or Astro component inside a markdown page, like a small demo or a pricing table? Or is it plain markdown only..?
joy_wilson1 · Imported from Product Hunt
"Drop Markdown into a folder and ship" is the part I like.. No app boilerplate to set up or keep updated. I've lost whole afternoons just getting a docs site to build.
ben_wigham5 · Imported from Product Hunt
Zero config docs where you just drop Markdown into a folder and get a production ready site is exactly what most projects want, and being open source forever is a strong promise. Building it AI ready from the start makes sense now that agents read docs as often as people do. Nice work shipping 2.0 so soon after launch.
karimbenkeroum · Imported from Product Hunt
the "scored by two independent scanners" bit in the screenshots caught my eye more than the zero-config pitch - docs getting an agent-readability score feels like the SEO audit equivalent for a different reader. we write most of our internal docs by just pointing Claude at the codebase and having it draft the markdown, and I've never had a way to check if the output is actually easy for an agent to parse later vs just easy for a human to skim. what does the scanner actually check - structure/headings, or does it get into things like whether code examples are runnable as-is
galdayan · Imported from Product Hunt