Skip to content

app: drive /roadmap from GitHub milestones instead of static copy #55

Description

@joelpeace48-cell

Problem

app/roadmap/page.tsx is a placeholder, while the real roadmap now lives in
GitHub milestones across the three repositories. A hand-written roadmap page
starts drifting the day it ships.

What to do

  • Fetch milestone progress from the GitHub API for all three repos at build
    time (or ISR with a sensible revalidation window).
  • Show each milestone with its open/closed counts and completion percentage.
  • Link through to the issue lists.
  • Cache and degrade gracefully — a GitHub API failure must not break the page,
    and the token must stay server-side.

Acceptance criteria

  • Live milestone data from all three repositories
  • Progress per milestone with links to issues
  • Graceful degradation when the API is unavailable
  • No token in the client bundle

Notes

Delivery transparency is exactly what grant reviewers look for, and a roadmap
that updates itself is far more convincing than one that claims to be current.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

GrantFox OSSIssue tracked in GrantFox OSSThird CampaignCampaign: Third Campaignarea:appRoutes (app/)difficulty:mediumFamiliar patterns; touches a few files or conceptspriority:mediumValuable, not blockingtype:featNew capability

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions