How to Use the WordPress Release Hub Block (2026 Guide)

Shipping releases is only half the job. Users also need a place to read what changed, vote on ideas, and see what is coming next. A WordPress Release Hub block solves that by combining release notes, feedback, and a public roadmap in one Gutenberg block—so you stop maintaining three separate pages that drift out of sync.

Changeloger is a visual changelog, release notes, and user-feedback plugin for WordPress. Its Release Hub block pulls structured releases from the admin Release Builder and presents them beside feedback and roadmap tabs. This guide shows when the hub helps, how to set it up accurately, and how to customize layout, tabs, and filters without inventing features that are not in the product.

What the WordPress Release Hub block actually does

The Release Hub is one of Changeloger’s three Gutenberg blocks (alongside the standard Changeloger block and Tabbed Changeloger). It is designed as a unified product updates page:

• Releases tab — structured versioned release notes from the admin builder, with badges, categories, and optional pagination.
• Feedback tab — a frontend board where users submit feature requests and bug reports (free plan includes a limited feedback pool; Pro unlocks voting, comments, and higher limits).
• Roadmap tab — a Kanban-style public roadmap with status columns (Pro roadmap builder).

Because the hub reads admin-managed data, editors do not paste plain text into the block every release. You publish a release once in Changeloger → Releases, then the hub reflects it on the frontend. That workflow is what makes a Release Hub different from a one-off changelog paste.

When a Release Hub beats a single changelog page

Use the Release Hub when your audience asks three questions on every update cycle: What shipped? What are people requesting? What is planned? Typical fits:

• SaaS and plugin products that already collect feedback but still email screenshots of roadmaps.
• Teams replacing SaaS tools (Canny, Featurebase-style boards) with a WordPress-native page.
• Support teams that want changelog + voting context without sending users to a separate app.

If you only need a static list of versions pasted from a text file, the standard Changeloger block may be enough. Choose the hub when you want releases, feedback, and roadmap in one tabbed interface. Compare capabilities on the Free vs Pro page and the Gutenberg Blocks overview.

Prerequisites before you insert the Release Hub

• WordPress 6.0+ with the block editor available on the page or post.
• Changeloger installed and activated (Pro if you need unlimited products, full roadmap, voting, email subscription, URL import, and advanced filters).
• At least one product created in the Release Builder with a few published releases.
• Feedback and roadmap modules enabled in Changeloger settings when you plan to show those tabs.
• Editor or Administrator access to publish the updates page.

Step-by-step: add the Release Hub block in Gutenberg

1. Create or edit the page that should become your public updates hub (for example, /changelog/ or /whats-new/).
2. In the block inserter, search for Release Hub and insert it.
3. Select the product whose releases, feedback, and roadmap the block should load.
4. In the block sidebar, review tab visibility: show or hide Releases, Feedback, and Roadmap per your audience.
5. Set custom tab labels if you prefer product language (for example, “What’s New” instead of “Releases”).
6. Choose the default tab so visitors land on Releases, Feedback, or Roadmap first.
7. Configure Releases options: layout style (including Compact), releases per page for server-side pagination, and container width per tab.
8. Preview on desktop and mobile, then save as draft for SEO review before publishing.

Changeloger also documents per-block customization—compact layout, pagination, container width, tab labels, subscribe header, and badge filters—in the helpdesk guide for Release Hub customization.

Build releases in admin so the hub stays accurate

The hub is only as clear as the Release Builder data behind it. For each version:

• Set a clear version number (SemVer-friendly when possible) and release date.
• Add change items under categories such as Features, Fixes, and Improvements, with customizable badges.
• Save drafts until copy is approved, then publish so the frontend hub updates.
• Use file import for existing .txt changelogs when migrating from GitHub-style notes.
• Use bulk actions when you need to draft, publish, or delete multiple releases at once.

Feedback and roadmap tabs that match real product process

On the Feedback tab, visitors can submit requests and (with Pro) upvote, downvote, and discuss items. Status workflows such as Under Review, Planned, In Progress, Completed, and Closed help support and product teams triage without a spreadsheet. Categories like Feature Request, Bug Report, Improvement, and Question keep the board readable.

On the Roadmap tab (Pro), publish a Kanban board with status columns, priorities, optional vote counts, and drag-and-drop status updates in admin. Link roadmap items to feedback when an idea graduates from vote to committed work. This closes the loop the Release Hub is meant to show: request → plan → ship.

Filters, pagination, and UX details that reduce bounce

Long release histories benefit from Releases Per Page with numbered pagination, Compact layout for denser lists, and badge/product filtering modes in the Release Hub. Container width controls let the roadmap span wider than a narrow theme content column while releases stay aligned with your blog layout. Enable subscription UI where Pro email notifications are part of your launch checklist so power users opt into future releases from the same page.

See Features, Pricing, and the free plugin on WordPress.org to validate the hub on staging first.

Launch checklist for your updates hub page

• Product name and branding colors match the rest of the site.
• At least three published releases with consistent badges.
• Tab labels and default tab match how you talk to customers.
• Feedback statuses and roadmap columns reflect real process names.
• Mobile preview shows readable cards and working tab switches.
• Rank Math (or your SEO plugin) title/description mention the primary keyword once naturally.
• Internal links from documentation and footer menus point to the hub.

When this checklist is green, publish the page and share it in release emails or in-app banners.

Frequently asked questions

Ready to replace scattered update pages with one hub? Install Changeloger, publish a few releases in the builder, insert the WordPress Release Hub block, and customize tabs until the page matches how your product actually ships.