Search blocks by description or jump to a page.
Two changelog columns side by side, each led by a release count over a dated feed, a busy product feed beside a sparse rival.
The source for every Marketing block is included with Pro and Team. Start a plan to copy the code.
Already on a plan? Log in
Release Velocity argues that a feature table shows a product today while a changelog shows where it is heading. A centered header makes that case, then two columns place the last quarter of both public changelogs side by side. The product column leads with a large release count over a dense dated feed and a link to the full changelog; the competitor column shows a sparse feed, then a list of their longest open feature requests and the date their roadmap last moved. A footnote owns exactly how the releases were counted.
Both feeds and the open requests list each live in their own typed array, so dates, titles, and counts all swap out without touching the layout. The busy side and the quiet side share the same card shape so the contrast comes from the content, and the whole block is built from theme tokens with no external images.
Reach for this block when you ship faster than the incumbent and want momentum to count as a feature. On a comparison landing page for a project management tool it works well late in the story, after a feature table has shown parity today, where the changelog reframes the choice as buying into the product that keeps improving. The open requests list lands hardest, so pick real asks a rival has left sitting for months.
A natural flow around it on a Marketing Pro page:
Before
After
The obvious fit is your changelog against a slow moving competitor's. A few other ways to use the frame:
Tip: count maintenance releases on both sides and say so in the footnote. A comparison that gives the other side full credit is the one a skeptical reader believes.