The story behind each update.

A list of fixes tells you what changed. It leaves less room for why we made those changes and what we want them to make possible. We wanted our release history to carry more of that context.

The idea is to turn the work we already do into useful posts. Future updates can draw on the discussions leading up to a release: the problem, the intended benefit, and the choices along the way. The concrete changes still have their own place, so you can quickly check what shipped.

We used the public updates feed in AnnounceKit as a reference: a browsable index, short excerpts, and a dedicated page for each post. URLs use simple descriptive words and stay the same after publication. Existing changelog links continue to work.

We also want these posts to help people discover Tap To Yap. Each page now includes readable HTML and search and sharing metadata. That gives us a foundation for discovery; it does not yet tell us whether the posts will bring new readers. The next step is to keep publishing useful context as the product develops.