Roadmap With Votes

About this block

Roadmap With Votes makes the roadmap a conversation. Feature request rows, ordered by votes, each carry a vote button with a count, the request title with a status badge, in progress tinted, planned outlined, exploring muted, and a one sentence description. The lede makes the governing claim, the top voted item ships, which is the entire credibility of community roadmaps.

The requests are one array, and the vote buttons are markup ready to wire to a backend. Descending vote order is non negotiable, the moment the order and the statuses disagree, the page reads as decoration. Real, slightly odd vote counts beat round numbers.

When to use

Reach for this block when you genuinely run a request board and ship from it, products with strong communities and public builders. It recruits customers into the roadmap the way roadmap-columns merely informs them. Only publish it if the votes actually move decisions, users can smell ceremonial voting from the URL.

A natural flow around it on a Marketing Pro page:

Before

• Community sections establishing the people whose votes these are

After

• Changelog showing previous winners shipping
• CTAs inviting visitors to add their vote

What you can display

One strong use is the live top four of a request board. Other boards:

• Integration requests. Vote on the next connection for an ecosystem with a long tail.
• Template requests. Community voted content for a library driven product.
• Talk topics. Vote on next webinar subjects for an events program.

Tip: the claim in the lede must be checkable, since we started counting invites the reader to verify, and that invitation is the persuasion.