How we build the thing that publishes your changelog, your blog and your release notes.
Somebody deciding whether to buy your product reads the changelog for something your marketing pages cannot tell them: whether anyone is still working on it, and what happens to them when something changes.
A changelog migration is four decisions, not a copy and paste: where the entries live from now on, what address each one answers at, what happens to the links people already shared, and who writes the next entry.
A changelog entry that links well converts better than one that sells. The rule is destination, not persuasion: link where the reader goes to use the thing, and cut every link that exists to move them somewhere you wanted them.
Entries that open with "we've added" put the team in the subject position and leave the reader to translate. The repair is grammatical: make the thing the reader controls the subject of the sentence, and delete the team from it.
Most deploys do not deserve a changelog entry, and publishing one per deploy turns the page into a build log. A four-question test for which ships earn an entry, what to do with the ones that fail it, and why silence is a correct output.
Cadence follows releases, not the calendar. The cost of stopping is not a missed post; it is a page whose most prominent fact becomes the date of the last entry.
A product changelog is read by people who will see the change on screen. An API changelog is read by people whose code will stop working, and that audience needs the symbol name, the date and a feed a machine can poll.
A breaking change is the one entry a reader cannot skim. It has to name what stops working, the date it stops, and the replacement — and no common changelog standard gives it a category of its own, so the title and the body carry it.
The reader of a bug-fix entry is asking one question: did this happen to me, and is anything I am holding still wrong? Four sentences can answer it.
A version label answers one question: is this change in the copy I have? If your readers cannot check that, the number is decoration and the date is the label.
An unreported bug is not an unexperienced bug. The entry that earns its place describes the symptom a reader might have seen, the conditions it happened under, and whether there is anything left for them to do.
A changelog is a record, and deleting from a record is how history stops being trustworthy. Here is what archiving does instead, and what it deliberately cannot undo.
A changelog entry declares one language, as a BCP-47 tag, and inherits the app's when it declares none. That is enough to run two languages properly, and it is not an hreflang cluster.
Market4 turns one release note into a changelog page, a blog post, a mail-out and a week of social posts — and then tells you which of them brought anyone back.