About this block

Changelog List Dated is the release history as a rail. Four entries run down a hairline rule, each with a dot, the date, a version chip, a release title, and one sentence that says what users can now do. The header pairs the shipping cadence claim with a link to the full changelog, so the section works as a teaser of a longer page.

The entries are one array of date, version, title, and text. Write the sentences as user outcomes rather than internal work, run five variants beats refactored branching engine. Four entries is the sweet spot for a marketing page, the full archive belongs behind the link.

When to use

Reach for this block on homepages and product pages of teams that ship visibly and want credit for it. A dated rail with believable cadence is product proof of life, the strongest churn antidote a marketing site can show. It shares its anatomy with story-timeline but speaks in versions rather than years, and pairs with whats-new-banner which teases what this section details.

A natural flow around it on a Marketing Pro page:

Before

• Features showing the product the entries keep improving

After

• Roadmap sections turning past cadence into future confidence
• Newsletter offering the changelog by email

What you can display

One strong use is the last four meaningful releases. Other rails:

• API changelog. Versioned API changes with deprecation notes in the sentences.
• Template drops. New library content by date for a template driven product.
• Policy updates. Terms and pricing changes, dated, for radical transparency brands.

Tip: the cadence claim in the lede must match the dates below it, readers do that arithmetic instinctively.