Skip to content
Beginner~15 minutes5 steps

Publish what you shipped

The pages that make a small product look alive. A changelog is the cheapest credibility on a marketing site — it is evidence, not a claim — and it costs one block plus the discipline to write two lines per release.

Take all 5 at once

npx hoverlab add changelog-timeline roadmap-columns community-band newsletter-signup footer-mega

Or through the shadcn CLI, with nothing installed first:

npx shadcn@latest add https://hoverlab5.netlify.app/r/path-product-updates.json

This path is a published registry item — one name that pulls in all 5 blocks. Or work down the list and copy each one from its page; the order is what matters, not how the files get there.

  1. 1

    Dated entries, newest first. Start it the day you launch: a changelog with three months of history is worth far more than one begun when you finally have something big to announce.

  2. 2

    Shipped, in progress, considering. Answers "is this abandoned" and "will you build my thing" without you replying to either email.

  3. 3

    Where to argue with the roadmap. A public plan without somewhere to respond to it is just a longer press release.

  4. 4

    The people who liked an entry enough to want the next one. Put it at the bottom of the changelog, where interest is already proven.

  5. 5

    Links these pages from everywhere else. A changelog nothing points at gets read by you and no one else.

    Or: Minimal Footer Bar

When you are done

Keep the entries in markdown or a CMS and map them onto the timeline — the block takes a list, so the source is your choice.