Skip to content

Sales & marketing

Generate release notes PDFs from your data

Release notes are read by people who did not ask for the change. One thing that matters, then the lists — what is new, what behaves differently, and the one thing that will break, said before it does.

3 designs, each a separate take on the same document rather than a recolour of one layout: Newspaper masthead, Minimal, type-led and Swiss grid.Every preview below is the actual compiled output, not a mock-up.

Open one in the editor and render it from your own JSON over the API — 1 page of A4 portrait, the same engine either way.

Designs
3
Page size
A4 portrait
Length
1 page
Document family
Executive narrative

Release notes designs

How the release notes designs differ

Same document, same data model, 3 different arguments about how it should look on paper. Pick on layout and typography — the content behaves identically.

DesignLayoutPaletteTypefacesPages
Changelog EditorialNewspaper mastheadInk & magentaPlayfair Display + Inter1 · A4 portrait
Plain ReleaseMinimal, type-ledEspresso & sageMerriweather + Inter1 · A4 portrait
Ship NoteSwiss gridGraphite & azureLibre Baskerville + Lato1 · A4 portrait

What your data drives in a release notes

Each design is authored against an explicit reflow contract, so it is defined up front which blocks are emitted once per record and which fields absorb longer content. That is what stops the layout falling apart at a hundred rows.

DesignRepeats per recordGrows with your data
Changelog Editorialfeature cards in the new band; rows in the changed and fixed bands; the breaking-change itemsthe lead standfirst; every feature description; every changed or fixed note
Plain Releasesections down the two columns; the rollout rows in the closing blockevery section's prose; the standfirst; the rollout note
Ship Noteone release per row, its version and date hung in the margin; the items under "next"every release note's prose; the standfirst; the "next" items

Start from one of these release notes designs

Open a design in the editor and the agent reshapes it around your schema — then render it from your own data over the API, or let your users edit it in the embedded editor.