Introducing Blume 🪷 A world-class docs framework for everything you ship. Drop Markdown into a folder and ship a full docs site with no app boilerplate. → zero-config setup → automatic SEO and AEO → 30+ components → powered by astro + vite → open source, free forever

Blume is the answer to a problem we tried to solve at Vercel: docs should be fast, AI-ready and require zero config / code - even the template. Blume builds your docs site around your content. When you want to customize, you can start replacing the built-in components, modifying the single configuration file or even ejecting if you want the Astro site directly.

It's still early, but Blume is already powering the docs for itself, Files SDK, Ultracite, Batchwork and infra-ts It's also powering the @QuiverAI docs and @neondatabase's add-mcp docs. Thank you @xn1cklas and others for the early feedback 🙌

Let's explore how it works! Create your first project with 𝚗𝚙𝚡 𝚋𝚕𝚞𝚖𝚎 𝚒𝚗𝚒𝚝. Then run 𝚋𝚕𝚞𝚖𝚎 𝚍𝚎𝚟 to preview your site.

The Markdown parser supports everything you expect nowadays - code blocks, directives, package install commands, diagrams and more. The template comes with 30+ polished components built-in, with more coming in future releases. You can replace any one of them by running 𝚗𝚙𝚡 𝚋𝚕𝚞𝚖𝚎 𝚊𝚍𝚍 [𝚌𝚘𝚖𝚙𝚘𝚗𝚎𝚗𝚝], pulling the component source code into your codebase to manage.

Blume is controlled primarily the 𝚋𝚕𝚞𝚖𝚎.𝚌𝚘𝚗𝚏𝚒𝚐.𝚝𝚜 file in the root. Here you can personalize your site, add advanced things like automatic MCP servers and even toggle entire features!

Blume has first-class support for changelogs, fantastic if you're building an npm library or SDK. You can even point Blume to your open source GitHub repo and it will render your changelog for you automatically. It also has full OpenAPI / AsyncAPI support built-in through. Just point Blume to your schema and it will generate the docs for you.

Blume is optimized for humans and agents out of the box. → structured data for google → opengraph images → rss feeds → sitemap and robots → optional Ask AI → llms.txt + llms-full.txt → raw Markdown at every .md URL → copy as Markdown → open in chat (chatgpt, cursor, etc.) → hosted MCP server

Content can stay local or come from somewhere else. Mix filesystem docs with remote MDX, GitHub Releases, Notion, Sanity, or a custom source.

Deploy static HTML anywhere, or switch to server output for Ask AI and MCP. On Vercel, Netlify, and Cloudflare Pages, Blume detects the site URL and adapter for you. Static builds output to dist/.

Blume also has full internationalization support built-in. Serve your docs in multiple languages with locale-aware routing, per-language navigation, translated UI, and SEO - all convention-first.

Want to create custom pages, like a homepage and pricing? Just create a .astro file at the path you want and you're good to go. You can even import layouts and components from Blume to keep things consistent. Because it's built on Astro, it has support for islands. You can add custom components in React, Vue or Svelte. It even has React Compiler enabled by default to automatically optimize your React components 🫪

Here's the source code. Any and all feedback is appreciated so we can work on making Blume the best docs system ever.

I hope you like Blume! Follow me @haydenbleasel for more updates. Also, Like/Repost the quote below if you can:

toby mcguire got bit by a spider but you must have been bitten by a goat

highest praise ever this is going in my diary

@fuma_nama When the fans become your haters 😭😭

i don't hate fumadocs lol - @fuma_nama is creating an amazing ecosystem of tools. i just wanted something architecturally different. something closer to the authoring experience of mintlify with all the bells and whistles wired up and enabled by default; and convention over configuration. i want to spend more time writing content and less time managing boilerplate code and dependencies.

@amanvarshney01 @fuma_nama Could you please explain the differences between Fumadocs and Blume? Actually, it would also be helpful to have a dedicated page comparing Blume with other major documentation frameworks and platforms.

@amanvarshney01 @fuma_nama I might do a comparison page eventually but for now @grok can you give a comprehensive comparison of Blume and Fumadocs?

**Blume vs Fumadocs comparison:** **Blume** (Astro + Vite, new v1 by haydenbleasel): Zero-config markdown-first. Drop MD/MDX in a folder → full site. Inferred nav, built-in components (no imports), Orama search, strong AI (llms.txt, Ask AI, MCP server), SEO, ejectable to Astro. Fast, static, AI-agent ready. Great for quick beautiful docs. **Fumadocs** (React, mature): Composable layers (Core/UI/MDX). Excellent for Next.js + React apps. Advanced MDX (Twoslash, Shiki, OpenAPI), dynamic content via RSC, highly customizable themes. More flexible for complex/dev-heavy docs. **Summary**: Blume wins on simplicity + AI features. Fumadocs wins on composability + React ecosystem depth. Both solid—depends if you want zero boilerplate or deep integration. Would love that comparison page on 🚀

@haydenbleasel @donbeave @amanvarshney01 @fuma_nama What about fumapress vs blume?

@haydenbleasel @donbeave @amanvarshney01 @fuma_nama Ask Grok is currently available to Premium and Premium+ subscribers only. Subscribe to unlock this feature:

Nice, I always felt like Fumadocs was too heavy, I'm going to give this a shot

Awesome video man 😍 Did you use anything from Remocn?

i did indeed! remocn is fantastic

this is awesome, let us know if we can improve anything @scalar! (other than AsyncAPI support which we are working on!)

this is what makes it so powerful, @astrodotbuild is so GOATed for static sites

Congrats and happy that Takumi helps powering the SEO experience 😁

Nice

Awesome work Hayden!!

Name a more dynamic duo than Hayden and docs framework 🤝

i stg if im known as the "docs guy"

So good

Really great! You should also look at the Varlock docs of a really incredible docs implementation of an Astro / vite example to see if there’s any great ideas to glean from them as well (Their docs are really really fantastic, and very agent-use focused too)

hit this exact wall last month trying to ship docs for a side project ended up 3 hours deep in remark plugins just to get tabbed code blocks working. does the component set actually cover that or is multi-language code still a bring-your-own situation?

good call - we have a code group component but i can look into making it even better, what did yours end up looking like?

If you want something lightweight and just ask powerful: It’s also Astro.

Zero-config setup is always such a nice experience. Hope this does for my docs site what ultracite did for my linting

wow!

yo this is so cool! 🥳

🔥

Looks great

OMG🤯

Yay finally ❤️

This is nice.

awesome, congrats on the launch !

This is great. Gotta try it for later.

Hope this solves my endless search for modern, easy to maintain docs frameworks

huge

Looks cool, but my heart is to @fuma_nama

awesome. 🫶👌🥃

zero config breaks once docs need versioned api examples across products

good call, we'll add versioning at some point

brroooooo, please rest for once😭

💚🔥👨‍🚀🔥💚

this is amazing!

hayden strikes again

looks interesting, Hayden, congrats on the release.