Managing the Roadmap Board
Go to WP Super Docs → Roadmap for a drag-and-drop board that mirrors the public one, but editable.

Adding an item#
Each column header has a + button that opens a new roadmap item already set to that column’s status. If you run more than one product and currently have one selected in the product switcher at the top of the page, the new item is also pre-assigned to that product.
Moving a card between columns#
Drag a card into a different column to change its status. The card moves immediately; if something goes wrong saving the change, it moves back to where it was and you’ll see an error.
Reordering within a column#
Every column except Shipped can be reordered by hand, drag a card up or down within its column. Shipped is always sorted by ship date, newest first, so it can’t be manually reordered.
Under Consideration is a special case: it stays sorted by vote count until you manually drag a card in it, the moment you do, the whole column switches to your manual order and stays there. A Sort by votes link appears next to the column header once you’ve done this, click it to drop your manual order and go back to vote-count sorting.
Planned and In Progress are sorted by timeframe first, and by your manual order second for items that share the same timeframe.
The card menu#
Click the ⋯ on any card for:
- Move to: jump straight to any other column, same effect as dragging.
- Move up / Move down: nudge the card one position within its column (hidden on Shipped cards, since that column can’t be reordered).
- Edit: opens the full classic edit screen.
- View on the roadmap: opens the item’s public page. Only shown for published items.
- Move to Trash.
The menu always opens on top of the whole board, even near the edge of a scrolling column, so it’s never cut off.
On touch screens, where dragging is harder to do precisely, use this menu’s Move to, Move up, and Move down instead of trying to drag.
Editing an item’s details#
Click Edit (from the card menu, or the card’s title) to open the classic edit screen, with a Roadmap Details panel in the sidebar for:
- Status: one of the four columns.
- Product: which product this item belongs to. If you run only one product, this field is replaced with a note explaining the product is assigned automatically, there’s nothing to set here in that case.
- Timeframe: free text like “Q1 2027,” used to sort and group Planned and In Progress items.
- Shipped on: set automatically to today the first time an item’s status becomes Shipped, or set it yourself.
- Changelog entry: link this item to a changelog entry so readers can see what shipped, if you use the product changelog feature.
- Related docs: the IDs of docs that explain this item, separated by commas, for example
412, 418. They’re shown on the item’s public page under Read the docs. You’ll find a doc’s ID in its edit address (post=412). - Votes: read-only, the current vote count.

If the item came in as a visitor-submitted feature request, a second panel shows who submitted it and lets you write a public reply, see The Feature Requests Inbox for the easier way to do this in bulk.
Read the docs#
When an item has related docs, its public page lists them under Read the docs, between the item’s details and the Response from the team. It’s most useful on shipped items: readers who upvoted a feature can go straight to the docs that explain how to use it.

Only published docs are listed. Internal-only docs are only listed for logged-in readers.
Managing the roadmap with Claude#
If Claude is connected (see Connecting Claude to Your Docs (MCP)) with an Editor or Administrator account, it can work with the roadmap for you:
- List items and requests: what’s on the board, what’s shipped, and feature requests waiting for approval, with votes, product, timeframe and team response.
- Add items and change their status, timeframe, description and product.
- Ship an item: move it to Shipped, link the changelog entry and the docs that cover it, and write the team response.
- Approve a feature request, so it appears on the public roadmap.
- Merge duplicate requests into one item. Their votes are added to that item and the duplicates move to the trash.
Try: “We shipped Outlook calendar sync in 2.4. Mark it shipped, link the 2.4 changelog entry and the Calendar Sync doc, and thank everyone who asked for it.” Or: “Find duplicate feature requests and merge them.”
Claude never sees who submitted a request: names and email addresses are left out of everything it can read.
New items are drafts. Putting an item on the public roadmap, or approving a request, needs Let Claude publish to be on, and you to ask. Otherwise a person approves it under Feature Requests.
Changes to items already on the public roadmap, including merging a published item into another, follow the same rule as published docs: Claude can make them only when your site lets Claude publish, or when changes to published docs go live right away.
Was this helpful?
Thanks for your feedback!
✓ Feedback received. Thank you!