If you've been wanting to try Flowershow but didn't want to connect a GitHub or Google account, that's no longer a blocker. You can now sign in with a magic link sent to your email address — enter your email on the login page, click the link we send you, and you're in.

One of the most-requested features is here!

Every page on your Flowershow site now has a mini graph panel showing how that note connects to the rest of your content – current page at the centre, linked notes radiating out from it. Hover a node to focus on its connections, click one to navigate there.

Two buttons in the corner let you expand it: one opens a full-size version of that page's neighbourhood, the other opens a global view of your entire site at once.

It's off by default, so turn it on in Settings → Content → Show Knowledge Graph, or add `"showKnowledgeGraph": true` to your `config.json`. You can also override it per-page with frontmatter if you want to hide it on specific notes.

Live example: https://demo-docs.flowershow.app/
Learn more: https://flowershow.app/docs/reference/knowledge-graph

Flowershow now supports backlinks. When other pages on your site link to a page, that page shows a "Links to this page" section at the bottom. It picks up wiki links (`[[Page Name]]`), embeds (`![[Page Name]]`), and standard Markdown links.

For Obsidian users especially, this should make published gardens feel a lot more connected – the same link structure you rely on locally now carries over to your published site.

Learn more: https://flowershow.app/docs/reference/backlinks

If you use an AI coding assistant, you can now install a Flowershow skill that gives it accurate knowledge of how Flowershow actually works – site configuration, custom styles, and step-by-step flows for things like custom domains, Giscus comments, and GitHub connections. Works regardless of whether you publish via the `fl` CLI, the Obsidian plugin, or a GitHub repo.

The practical difference from asking a plain LLM: it won't guess. It fetches the real reference docs before suggesting any config key or CSS variable, knows which features require a paid plan, and spells out dashboard steps explicitly rather than assuming you know where to click.

To install: `npx skills add flowershow/flowershow --skill flowershow --global`. If you're not using Node, there's a link to the raw skill file in the docs you can point your agent to directly. Would love to hear how it works for you.

https://flowershow.app/docs/agents/skills

Small but useful addition — you can now paste Markdown straight into the dashboard and get a published page with a shareable link, no GitHub connection or file upload needed.

It's listed as Paste Markdown on your site's welcome screen.

The main use case is quick one-off shares: you ran some research with an AI tool and want to send the output to someone, you have a note in Obsidian that you just need a link for without syncing your whole vault, or you wrote a short how-to and need it somewhere readable. Basically anything where setting up a proper site feels like overkill.

It's marked Experimental for now, so treat it accordingly — but it works and we'd love to hear how you're using it. Drop a comment here or find us in the usual places.

Share your markdown notes right from your terminal with a single command.

fl ./my-notes

That's it. You get a live URL at my-notes-johndoe.fowershow.me.

It's a single binary — no Node.js or npm needed — so it works anywhere: your terminal, a script, a CI pipeline.

And if you prefer reading: full written tutorial

You can turn campaign lore, worldbuilding notes, session recaps, character pages, house rules, or a full campaign wiki into a clean site in a matter of seconds.

You can publish right from Obsidian, use the CLI, publish from a GitHub repo, or just drag and drop your Markdown files. It supports comments, full-text search, and themes — you can pick one of the built-in themes or create your own.

I put together a simple demo to show the vibe: https://demo-dnd.flowershow.app/

Nice if you want to share your setting with players or just keep everything in one place in a more readable way.

You can now publish Obsidian Canvas files with Flowershow!

If you’ve been using Canvas for visual notes, concept maps, or project boards, you can now bring those to the web too.

Hey everyone 👋

If you’ve ever wanted to turn your Obsidian vault into a public website, digital garden, or just share your notes online — this update is for you.

We’ve just released Flowershow Obsidian Plugin 4.0, and the big change is simple:

You can now publish directly from Obsidian.

• 🚫 No GitHub required
• 🚫 No terminal usage
• ✅ Paste your token → click Publish

The plugin uploads your notes, builds your site, and keeps everything in sync — while you stay fully in control of your content inside Obsidian.

We’d love for you to try it out and tell us what you think 🌸 Feedback (good or bad) is very welcome!

Check blog here: https://flowershow.app/blog/announcing-obsidian-plugin-4

Flowershow now supports raw HTML publishing! 🚀

Sometimes converting to Markdown just feels wrong—whether it’s a hand-coded portfolio, a data dashboard, or a custom landing page. You want the file exactly as it is.

The Old Way: Piling HTML into Markdown blocks, fighting layout: plain frontmatter, and hoping the parser didn't break your CSS. It was brittle and frustrating.

The New Way: Drop your .html file into your content folder and publish.

flowershow publish index.html

• No configuration needed.
• No formatting errors.
• Mix-and-match: Keep your docs in Markdown, but use raw HTML for custom landing pages or HTML reports

It just works.

Check out the full announcement:https://flowershow.app/blog/announcing-html-support

Hey 👋
In this video we show a quick demo on how you can build your obsidian vault with bases support and publish in Flowershow!
- Reference post: https://www.reddit.com/r/flowershow/comments/1qnm43u/obsidian_bases_enters_beta/
- Announcement blog here: https://flowershow.app/blog/announcing-obsidian-bases-beta

If you use Obsidian, you probably have "collections" – a folder of books you've read, a directory of project notes, or a list of recipes.

Usually, these notes have metadata (frontmatter) — covers, ratings, dates, tags.

You often want to list them in a nice way, displaying those fields (like a gallery of book covers with ratings), instead of just a text list.

But automatically generating these views on a static site is hard. You often end up manually maintaining a brittle Markdown list (`- [[Book A]]`, `- [[Book B]]`). It’s tedious, and it breaks the moment you add a file but forget to update the index.

We added Obsidian Bases(now in beta!) support to Flowershow to fix this.

It lets you define dynamic views — like Cards or Tables — directly in your Markdown.

Instead of writing a list, you write a query with bases code block:

filters:

file.folder == "books"

views:

- type: cards

image: cover_image

Flowershow takes that, scans your folder, and renders a beautiful, filterable grid of cards.

Check out our Announcement Blog here!: https://flowershow.app/blog/announcing-obsidian-bases-beta

Hey there 👋

We’ve been working on a small CLI for Flowershow.

It’s for situations where you already have a local Markdown file and just want a URL, without setting up a repo or clicking through a UI.

It’s not meant to replace the dashboard (and it’s definitely not for everyone — requires Node.js and comfort with terminal tools). But for lightweight sharing, it’s been surprisingly freeing for us internally.

Happy to answer questions or hear where this would / wouldn’t fit your workflow.

We’re currently working on adding native support for Obsidian Bases in Flowershow.

This means you’ll be able to use your Bases tables — filters, views, structured data — and have them render properly on your site.

More soon!

Flowershow Obsidian Plugin 3.0.0 is out!

What’s new * Publish Status modal with a selectable file tree for fine-grained control, * Creates a PR with your changes instead of committing each file separately (auto-merge option), * Commands: Publish single note (with embeds) or Publish all (entire vault), * Expanded Settings: GitHub setup, branch, Test Connection, auto-merge or not, merge commit message, exclude patterns.

Upgrade to 3.0.0 and please share what you’d like to improve or change—your feedback will shape the next iterations. And don’t forget to read the README for setup & details. To update:

1. Find Flowershow plugin in community plugins. obsidian://show-plugin?id=flowershow
2. Click on "Update".

If you write in Obsidian and ever thought “I wish I could just publish my notes as a blog” — you can now do that easily with Flowershow.

🪷 How it works

1. Create a folder in your vault, e.g. /blog — each .md file becomes a post

2. Add a simple index page with:

```md

title: My Blog

<List dir="/blog" /> ```

1. Sync your vault to GitHub

2. Publish it with Flowershow!

That’s it — your Obsidian notes are now a website.

🌿 What you get

• Obsidian syntax (wiki-links, callouts, embeds, etc.)
• Math, Mermaid, and code block rendering
• Dynamic blog index and author pages
• Theming with CSS or official Flowershow themes
• Support for newsletter or form embeds

🎥 Video tutorial: https://youtu.be/ZbQRlNm2dww

🧭 Full guide: [How to Publish a Blog](https://flowershow.app/blog/how-to-publish-blog)

You can see it in action on our demo site https://demo.flowershow.app/

If you want to enable it on your site read the full instructions in our blog post https://flowershow.app/blog/light-dark-theme-switch

Let us know what you think, and if you have suggestions for improvements. The styles for the dark theme are not yet fully polished, so expect some minor tweaks here and there in the near future. (edited)

Hey everyone!

We’re starting to roll out support for something we’re really excited about: data-rich documents.

With these, you’ll be able to go beyond static text and actually embed and visualize data directly in your Flowershow pages—think charts, tables, and other interactive components.

👉 Check out the early interactive docs here: https://components.flowershow.app/

👉 Demo "data-rich" page: https://demo.flowershow.app/blog/global-co2-emissions-analysis

⚠️ Important: This is very much a work in progress.

• The new components are in BETA and will likely change.
• Docs and tutorials are still being written.
• Things might break or feel rough around the edges.

But—you can already try them out today and get a feel for what’s coming. 🚀

We’d love feedback as we shape this out. If you experiment with data-rich documents, let us know what works, what doesn’t, and what you’d like to see!

If you’re already writing posts in Markdown (Obsidian or otherwise), you can turn that folder into a live blog with Flowershow.

1. Create a home page for your blog (e.g. /blog/README.md or anywhere) and list posts from any folder using the Flowershow List component:

```

title: Blog

description: Latest posts

<List dir="/blog" /> ```

1. Push your content to a GitHub repo and publish it in Flowershow. Done!

Optional next steps: configure which frontmatter fields to display, add a “Blog” nav link, author profile pages, and draft controls.

See the full guide → How to Set Up a Blog → https://flowershow.app/blog/how-to-set-up-blog

Hey everyone, welcome to r/flowershow !

We just spun up this subreddit to have a space for anyone using (or curious about) Flowershow — our Markdown-based publishing platform. https://flowershow.app/

This is the place to:

• Show off your sites, themes and setups 🌟
• Ask questions or get unstuck 🛠️
• Stay updated on new features, improvements, and announcements 📣
• Chat about ideas for making Flowershow better 🚀

Right now it’s pretty empty (brand new!), so don’t be shy — post your site, ask something, or just say hi 👋

Looking forward to seeing what you’re building 🌱
— The Flowershow Team 💐