Fast, AI-ready, and zero-config. Drop Markdown into a folder and ship a production-grade docs site with no app boilerplate to write or maintain. Free and open source, forever.
"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.
Report
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..?
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.
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
Replies
always be launching!
first launched 2 months ago, @Blume 2.0 is already here. fast, AI-optimized, with zero-config, this open-source @Mintlify alternative is used by products like @Neon and supported by @Cloudflare and @CodeRabbit.
s/o to @haydenbleasel for this new launch! 👏👏
"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.
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 You can bring your own components from lots of languages - Astro, React, Vue, etc.
https://useblume.dev/docs/configuration/customization
https://useblume.dev/docs/content/islands
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.
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