Published anonymously with FlowershowReport abuse

The CMS is over. Not WordPress; that runs a huge share of the web and will for years. The model is over: the idea that to put something online, you move your words into a place. A database behind a login, with an editor, a settings page and a list of plugins to update, forever.

That model made sense in 2005. You wrote on the web, so you wrote inside the website. Twenty years on, most writing doesn't start there. You write in Obsidian, in a text editor, in a chat with Claude. What comes out is a file. Then you open a second tool, log in, paste, fix the formatting and press Publish.

Who wants to manage content? Make publishing fast and fun again.

Code got its one-command moment. Content didn't.

Deploying code used to mean a server, SSH, git clone, install, restart, hope. Heroku made it git push. Then Zeit, now Vercel, made it one word: type now, get a URL. Today a developer putting a site on Vercel or Netlify is a non-event. The config disappeared because the host knows what you're shipping.

Content mostly didn't. If you wanted a site for your notes, your docs or a report, you either rented a place (Substack, Medium, Notion) and lived by its format and its address, or you assembled a stack: framework, Markdown plugins, math, diagrams, SEO tags, blog index, hosting, DNS. Then you kept it running.

There's an older version of this story. In 1985 PageMaker and the LaserWriter moved typesetting from the shop to the desk. Before that, your manuscript went to a specialist with its own equipment and its own format, and came back as pages. The CMS is the web's typesetting shop: your words go in, get converted into its posts and blocks, and live there. The shop still works. It's just no longer where the writing happens.

Everyone is a files person now

Files-over-app used to be a niche taste: Obsidian people, developers writing docs in Markdown, the odd stubborn blogger. AI made it the default without anyone choosing it. When you ask Claude or ChatGPT to write something, it writes Markdown. When it builds a page, it writes HTML. When an agent keeps your research notes, it keeps a folder. You never chose files. Your AI chose them for you.

So the finished format exists before publishing starts. Translating it into somebody's database, and keeping the two in sync, is a step backwards. Your files are already the finished format. Skip the shop.

Publishing becomes a step

Once your work is in files, publishing stops being somewhere you live and becomes something you do. You have a folder. You say "publish". You get a website back: navigation, search, a proper design, your own domain if you want one. When the files change, the same address updates. The site is a view of your folder, and the folder stays yours.

That's a verb, and anyone can call it: you, from Obsidian or GitHub; a coding agent, as the last step of its job; Claude, when you say "put this up".

A coach asks for a workshop handout, says "publish this", and sends a link instead of an attachment. A lab's agent reads papers overnight, and every morning the wiki is a website, backlinks and all. A small team's agent updates the docs alongside the code, so the docs are never stale.

What Flowershow is

Flowershow turns a folder of Markdown or HTML into a real website. Point it at a file, a folder or a whole Obsidian vault and you get navigation, search, a blog index, math and diagrams that render, social previews and your domain. Wiki-links, Bases and Canvas go up as they are. Publish from Obsidian, from GitHub, from the terminal or from Claude, and every publish updates the same URL.

Could you build this yourself? Yes, and with AI you could build it fast. But you'd make fifty decisions you don't care about: which framework, which Markdown processor, how math renders, what a social preview needs, where to host, how DNS works. Then you'd keep it all working through upgrades and broken builds. We made the fifty decisions, and we keep them working. That's the product.

Not for every site

Flowershow is deliberately narrow, and we like it that way. It is very good at notes, docs, wikis, reports and small sites, which is most of what people publish. It is not Astro or Next.js. If your site grows custom components or app logic, go to one of those and take your Markdown with you. Rufus did exactly that with one of his own sites. A folder of files can move.

Why we care

We think good thinking needs good venues. Too much knowledge sits in chats, shared drives and attachments nobody opens, or on platforms that decide how it looks and who sees it. We want more of it out in the open, in places that are elegant and easy to read and that belong to the people who made them. Publishing should be fast, easy and even a little fun. It used to be, before it became a job.

We're Rufus and Ola, plus a few friends, and we've been at this a while. No investors, our own money and time since 2022, and we publish our own work with it every day, this page included. We're in this for the long run. More about us, and how we keep it going, on About.

Rufus and Ola

Try it

Take a folder you already have and put it on show.

Publish for free · Connect your AI

Built with LogoFlowershow