Changelog
ShippedWebsite

What's new is written once now, and published without a release

This page and the bell in the dashboard were two lists typed into the source code, unaware of each other. Every announcement was written twice, in two voices that drifted, and shipping one meant releasing the whole application. The unread dot had the same problem in miniature: it meant "the list is not empty", which is always true, so after the first look it told nobody anything. Both read one table now. A line is published by saving it, and the dot means what it says. Each item in the bell links to its own entry down this page instead of dropping you at the top of forty-five of them.

  • The changelog page and the dashboard bell read the same source, so they cannot say different things
  • The unread dot compares against the last entry this browser has seen, and clears when the bell is opened
  • The bell shows the four newest and links here for the rest, enforced in code rather than by remembering to delete the oldest
  • Every entry has its own address on this page, so a link can point at one thing
  • The page keeps a generated copy of itself, so a backend outage cannot leave you with an empty changelog that still reports success