Content & Publishing · Blueprint
Changelog
Publish product updates the way engineers ship them: releases with semantic types and dates, backed by individual change entries labeled added, changed, fixed, and more. Feed a changelog page, an in-app widget, and an RSS feed from the same records.
- content types
- 2
- fields
- 14
- sample records
- 3
Schema
What's inside
Every content type ships pre-configured with typed fields, validation and relationships.
Release
A shipped version with date, summary, and a rich highlights section.
8 fields
| version | Text | Version label shown as the entry heading, e.g. v2.4.0 |
| slug | Slug | URL segment for deep-linking to this release |
| release_date | Date | The day the release shipped, used for ordering |
| summary | Text | One-line description used in feeds and in-app notifications |
| highlights | RichText | Narrative writeup of the headline changes, with media |
| release_type | Enum | One of: major, minor, patch, hotfix |
| breaking_changes | Boolean | Flags the release with a breaking-change warning |
| banner_image | Image | Optional visual for feature releases and social sharing |
Change Entry
A single change within a release, typed for keep-a-changelog style grouping.
6 fields
| title | Text | Short description of the change, e.g. Bulk export for reports |
| change_type | Enum | One of: added, changed, fixed, removed, deprecated, security |
| description | RichText | Details, migration notes, or screenshots for the change |
| release | Reference | Reference to the Release this entry ships in |
| reference_link | Link | Link to the related doc, issue, or pull request |
| internal_only | Boolean | Hides the entry from the public changelog |
REST API
Release, as JSON.
Each content type of the blueprint is served by the REST API, with filtering, sorting, search and pagination.
Explore the API docs{
"id": 1,
"status": "published",
"data": {
"version": "v2.4.0",
"slug": "v2-4-0",
"release_date": "2026-09-22",
"summary": "…",
"highlights": "<p>…</p>",
"release_type": "…",
"breaking_changes": true,
"banner_image": { "url": "…" }
}
}Sample data
Ships with sample data
Install the blueprint and explore it with realistic example records.
- Sample
v2.4.0
A minor release with a highlights writeup and five typed change entries
- Sample
Bulk export for reports
An added entry in v2.4.0 linking to the export documentation
- Sample
Fixed timezone drift in scheduling
A fixed entry with a short note and a link to the issue
Features
Why this blueprint
- Keep-a-changelog structure Typed entries group naturally into Added, Changed, and Fixed sections, so every release reads consistently.
- One source, many surfaces The same records power your changelog page, an in-app What's New widget, and an RSS or email feed.
- Honest about breakage Breaking-change flags and per-entry migration notes give users the warning they need before upgrading.
Use cases
Built for
- A SaaS product publishing a public changelog and in-app release notes from one source
- An API platform warning integrators about breaking changes and deprecations
- A mobile team keeping App Store release notes and the web changelog in sync
- A developer tools company linking each change to its docs and pull requests
Related
More in Content & Publishing
Start with the Changelog blueprint
Install it in one click, explore the sample data, then adapt every field to your needs.
No credit card required · 3 months free trial · Cancel anytime