Turn a folder of Markdown files into a live docs site, in seconds.
Keep docs in your repo.
Push changes — they auto-sync.
Drag in your Markdown files. Get a site link instantly.
Get started →Keep writing in your vault. Publish with our official Obsidian plugin.
Get started →Publish from the terminal. Script it if you want.
Get started →
Your folders become sections. Your files become pages. URLs follow the same structure. No separate navigation config.
Learn more →
Start with plain Markdown. Add richer blocks when they help. Your docs stay readable as files — not trapped in a proprietary editor.
Flowershow is intentionally minimal. But you still get the few knobs that matter — branding, domains, and a place for your own CSS.
Created a theme you're proud of? Share it with the community!
No. Upload your Markdown files or connect a GitHub repository. Navigation is generated from your folders and your site is live in seconds. There’s no theme setup or build pipeline to manage.
Push to GitHub. Or sync via CLI or Obsidian. Refresh the page — your changes are there. No manual deployment step.
Yes. Your repository stays the source of truth. Flowershow publishes directly from it and auto-syncs changes. There’s no proprietary editor to migrate to.
Yes. You can publish public documentation or keep it internal. The workflow is the same either way.
Your documentation is just Markdown files. You can take them anywhere — another host, another tool, or your own infrastructure.
No. If you can organize files into folders, you can publish documentation. You don’t need to know what a static site generator is.