Everything the docs need. Nothing they don’t.
Flame is a build-time bridge between tooling and content. It reads Markdown, compiles it with React, and writes flat HTML. Twelve things it does well, in one place.
Bun / Node / Deno. Same output.- 01 / No runtime
Build time only.
Markdown compiles to flat static HTML. Bun, Node or Deno power the toolchain, never production.
- 02 / Markdown contract
Write Markdown, not JSX.
Common markdown plus a small set of directives. Readable in any editor, any diff, and by any agent.
- 03 / Directives
Components by name.
Callouts, tabs, cards, accordions, steps and file trees, written as markdown and resolved by Flame.
- 04 / Incremental builds
Only what changed.
A content-hash build cache and deterministic bundle hashing recompile changed pages only.
- 05 / Dev server + HMR
Stay in the edit.
Memoized compilation and instant reload on content changes. Repeat navigations never re-parse.
- 06 / Built-in search
Found at build time.
A full-text index generated during the build. Connect Algolia when you outgrow it.
- 07 / Plugin system
Hooks, not forks.
Extend the build pipeline and dev server with hooks, registered from docu.json.
- 08 / Config-driven themes
One color. A whole theme.
Switch presets or set custom colors in docu.json. Light and dark follow along.
- 09 / Eval-free hydration
A strict CSP, no exceptions.
Content compiles to static ESM modules. No new Function, so no 'unsafe-eval'.
- 10 / Filesystem routing
docs/ is the sitemap.
Pages are discovered from the docs folder. Folders become sections, files become routes.
- 11 / Subpath ready
/docs, a prefix, or root.
Links, canonical URLs, search records and generated nginx rules follow the base path.
- 12 / Deploy anywhere
Just files.
Static output for Netlify, Vercel, Cloudflare, nginx, or any host that serves HTML.
Your toolchain. Your choice.
- Bun
- Node.js
- Deno
The generated site needs no runtime or server process.
Less platform. More publishing.