Flowershow for:Changelogs

Turn your CHANGELOG.md into a changelog page.

Keep the CHANGELOG.md you already have and Flowershow renders it as a timeline, with an anchor link for every version. Or write one Markdown file per update in a changelog folder, and each entry gets its date, authors, image and its own page. Free to start; your own domain on Premium.

Free forever, no credit card required

The Flowershow changelog: a timeline of updates with dates, authors and screenshots
No config

Two ways to write it.

Pick the one that fits how you ship. Both render as the same timeline.

A folder of updates

One Markdown file per update in a changelog folder, newest first. Each entry can show a date, version, authors, summary and image, and gets its own page.

A changelog folder rendered as a timeline, with dates and version labels beside each entry
Write your first entry →

One CHANGELOG.md

The file your project already has. Keep a Changelog, Changesets, release-please and conventional-changelog headings are recognized. Each version gets its own anchor, and a Compare link when its heading links to a diff.

# Changelog ## [0.4.0] - 2026-11-21### Added- Export answers to CSV from any form. ## [0.3.1] - 2026-11-04### Fixed- Dates are read day first in UK English.
A CHANGELOG.md rendered as a timeline: Unreleased first, then version 0.4.0 with its date and a Compare link
Publish your CHANGELOG.md →

Any folder or file can be a changelog: add layout: changelog to the file's frontmatter, or to the folder's README.md.

Ways to publish

Publish from wherever you write.

Pick one. Switch later — your changelog is always plain Markdown.

Using an AI agent?

The Flowershow skill writes release notes and publishes them — in whichever workflow you already use.

Instructions for your agent →

GitHub

Connect the repo and your changelog republishes on every push.

Learn more →

Obsidian

Keep release notes in your vault and publish them with the rest of your notes.

Learn more →

Drag & drop

Upload your changelog folder in the browser and get a live page.

Learn more →

CLI

Publish straight from the terminal. Script it if you want.

Learn more →
Features

A real changelog, out of the box.

Everything a release-notes page needs, from the files you already write.

A single changelog entry page with its date, author and screenshot

A page for every entry

Each update gets its own page, with links to the previous and next updates and a preview card when you share it. Link to one release, not the whole list.

Learn more →

Versions and authors

Add a version label beside each date, and authors with avatars and links to their pages. In a changelog folder, the newest update comes first, ten to a page.

Learn more →

Readers follow along

Turn on the RSS feed and every dated entry in a changelog folder goes into it. Turn on llms.txt and AI assistants can find and read your changelog as Markdown.

Learn more →
Part of a product site

Your changelog, beside your docs, blog and pricing.

Keep it in the same folder as the rest of your site, and one publish updates them all. Add a landing page and you have a whole product site.

Showcase

Changelogs published with Flowershow

A few of the 2,600+ sites already published.

The Flowershow changelog published with Flowershow
Changelog

Flowershow ships its own release notes from a changelog folder, one file per update, with screenshots and authors.

flowershow.app/changelog →
The Wilber Wiki changelog published with Flowershow
Changelog

Wilber Wiki, a wiki of Ken Wilber's ideas, logs every new figure and page in its changelog.

wilber.wiki/changelog →

Markdown to URL. Instantly. Free.

Join the writers, researchers, and teams behind 2,600+ sites already published with Flowershow.

Get started →

No credit card required · Free plan, forever

Built with LogoFlowershow