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.

Install this blueprintView Docs
2 content types14 fields3 sample records

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
versionTextrequiredVersion label shown as the entry heading, e.g. v2.4.0
slugSlugrequiredURL segment for deep-linking to this release
release_dateDaterequiredThe day the release shipped, used for ordering
summaryTextoptionalOne-line description used in feeds and in-app notifications
highlightsRichTextoptionalNarrative writeup of the headline changes, with media
release_typeEnumrequiredOne of: major, minor, patch, hotfix
breaking_changesBooleanoptionalFlags the release with a breaking-change warning
banner_imageImageoptionalOptional visual for feature releases and social sharing

Change Entry

A single change within a release, typed for keep-a-changelog style grouping.
6 fields
titleTextrequiredShort description of the change, e.g. Bulk export for reports
change_typeEnumrequiredOne of: added, changed, fixed, removed, deprecated, security
descriptionRichTextoptionalDetails, migration notes, or screenshots for the change
releaseReferencerequiredReference to the Release this entry ships in
reference_linkLinkoptionalLink to the related doc, issue, or pull request
internal_onlyBooleanoptionalHides the entry from the public changelog

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

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.

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

More in Content & Publishing

Blog

A complete editorial model with posts, authors, and categories ready for any frontend.

Documentation

Structured docs with sections, ordering, and lifecycle status for product knowledge bases.

FAQ

Categorized questions and answers that keep support pages tidy and easy to maintain.

Start with the Changelog blueprint

Install it in one click, explore the sample data, then adapt every field to your needs.

Start FreeBrowse all blueprints
No credit card required
3 months free trial
Cancel anytime