Choose a changelog by how customers need to receive the update. Your CMS is enough for a public archive. Headway adds a focused changelog and widget; Beamer suits updates that need targeted in-product delivery.
Choose the delivery route
| Approach | Reader experience |
|---|---|
| Existing CMS | A stable public page to search and share |
| Headway | Public update history with an in-product widget |
| Beamer | Changelog plus targeted announcements and feedback |
Headway includes categories, team publishing and scheduled posts. Beamer combines release notes with in-app notifications. Buy the additional delivery workflow when customers need it, rather than moving an archive that already works.
Write one complete release note
Example:
CSV exports now include the account owner.
Available to paid accounts using Reports v2. Open Reports → Export → CSV. The file includes an Account owner column beside each account.
Still using Reports v1? Your export is unchanged; switch to v2 before using the new column.
The availability line prevents an existing customer from searching for a feature their version does not have. A “rolling out” label should similarly name who has access now.
Keep the note and instructions connected
Link the release note to the maintained instructions. The note explains what changed; the documentation explains how the product works now. When a feature is retired, preserve the old URL and point readers to its replacement.
Use the documentation guide for developer references or the help-content guide for support-owned instructions.
Budget for publishing and delivery
Compare the authors, subscribers, notification volume and targeting you actually need. Include the time to confirm availability and publish with each release. Before moving the archive, confirm that exports and redirects preserve useful URLs.
If you want to know when AI changes its answer about your brand, start with a free brand check.