Release notes and changelog templates
Version-stamped cards for release day. The version number becomes the headline your users recognize.
Release notes
Version headline in monospace with a code screenshot. For changelogs and release posts.
Version release
Version number as the headline, one line on what changed. For release day.
Feature update
Feature headline with a screenshot on the right and a NEW tag. For product updates.
Click a template to open it in the editor with the design loaded. Everything stays editable.
Release posts have a rhythm: version number, what changed, where to read more. These cards match it - a monospace version headline with a code screenshot, a stripped-down version card for majors, and a screenshot-forward layout for single-feature releases.
Monospace type is doing real work here: it signals "software release" before anyone reads a word. Swap the version, keep the design, and your changelog posts become a recognizable series.
Tips that make these work
- Put the version in the headline ("v2.4: faster renders") - users track versions, not dates.
- One release, one highlight: the card carries the biggest change, the changelog page carries the rest.
- Automate it: with a saved template and the API, your release pipeline can generate the card from the version string.
FAQ
What goes on a release notes card?
Version number and the headline change in the title, one supporting line, and optionally a screenshot. The CHANGELOG tag is a preset label you can edit.
Can my CI generate these automatically?
Yes - that's the API's signed-URL and REST rendering: save the design once, then render it with the new version text per release. See the API docs.
Why monospace fonts?
Convention: version numbers and code read naturally in monospace, and the audience for release posts recognizes the cue.
Related tools
Making these repeatedly? Save your design once and generate a card per post automatically.