docs(roadmap): reflect the current state of the issue tracker - #283
Merged
Conversation
Resource pages (#272) shipped in 0.15.0 but were still listed as In Progress, and the page had never mentioned on-site guides, community profiles and likes (epic #167 phases 1-2), the Dev Portal, or the search-visibility work (#244, #257, #215) — all of which are done. Discord announcements (#24) moves the other way, from In Progress to Planned: the ingestion was never merged, no code for it exists on main, and the retraction problem (#142) is still unanswered. Adds Planned entries for the open issues the page omitted — verified reviews and the install reporting they depend on (#278), following and an activity feed (#193), notifications (#196), profiles linked to factions (#195), MCP access tokens (#280, #281), and a knowledge-base section backed by the DPC Zettelkasten (#282) — and lists Minecraft-version compatibility (#162) and badges and roles (#194) as In Progress, each naming the half that shipped and the half that has not. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The Road Map page is driven by
pages/data/roadmap.json. It had drifted from the issue tracker, so this brings the two back into line. Data only — no changes topages/roadmap.tsx.Moved to Completed
Moved back to Planned
V11dropped the table it created, no code for it exists onmain, and there is no open PR — so nothing is under way. The description now says so and names the unanswered retraction problem (Discord announcements persist on the News page after being deleted on Discord #142).New Planned items, one per open issue the page omitted
Verified reviews and the per-plugin install reporting they depend on (#278), following and an activity feed (#193), notifications (#196), profiles linked to factions (#195), MCP access tokens (#280, #281), and a knowledge-base section backed by the DPC Zettelkasten (#282).
New In Progress items
Descriptions were also refreshed where the feature has grown since it was written (the leaderboard, the UX and accessibility item, the editable-catalogue item now that
V15exists).Coverage
Every open issue is now represented: #271's phases (#273–#276) and #278, epic #167's phase 3 (#192–#196), #162, #142/#24, #87, #57, #280, #281, #282.
Verification
roadmap.jsonparses and every item validates against theRoadmapItemshape the page expects (13 Completed, 2 In Progress, 14 Planned; no duplicate titles). No test references the road-map data and the page component is untouched, so the suite is unaffected; CI will confirm.This pull request was drafted by Claude on behalf of Daniel Stephenson.
🤖 Generated with Claude Code