Districtr V2 Launch Roadmap

[nofurtherinformation]

This discussion is to track key milestones needed for Districtr V2 to launch as the official Districtr offering.

This is a high level milestone tracking thread, but it is not a detailed issue/technical planning document.

[nofurtherinformation]

Monthly roadmap

Here's a roadmap of an ideal scenario. The comments in the thread below reflect a guess at direct development time, but don't necessarily reflect UX testing, coordination, etc.

December 2025:

• Save revamp / refactor PR filed
• Roadmap created

January 2026:

• [Done ahead of time] Review and revise of Save refactor
• Gallery page stabilization
• Side quest: Navajo Nation module
  • New feature requirement: paint within area control
  • New feature: overlays (esp. city boundaries, paint whole city option)

February 2026:

• Hire made, start date in March
• Revise and finalize side quest
• Finish district level comments

March 2026:

• Onboard new hire
• New hire explores code base and orients to project
• PR for community mode
  • if accelerated, then also work on coalition builder

April 2026:

• New hire reviews community mode
• PR for evaluation view
• Dylan reviews evaluation view

May 2026:

• Modifiable number of districts
• Populate additional map modules
• Bug fix pass

June 2026:

• ?

⚠️ This will change over time.

[nofurtherinformation]

Milestone 1: Save revamp / refactor

Goal:

Revamp save and share to focus on manual checkpoint saves rather than automatic saves. Clean up share system. Stabilize app overall.

Timeline:

• Build out initial PR: ~3-4 weeks
• Review time: ~3-4 weeks
• Revise time: ~2-3 weeks

Issue Link(s):

PR Link(s):

#464

[nofurtherinformation]

Milestone 2: District Level Comments

Goal:

Users can add district level comments on a plan.

Timeline:

• Build out initial PR: 2 weeks
• Review time: ~3 days
• Revise time: ~1 weeks

PR Link(s):

#458
#489

[nofurtherinformation]

Milestone 3: Community Mode

Goal:

Modules can be use "community mode" that allows overlapping areas.

Timeline:

• Build out initial PR: 3 weeks
• Review time: 5 days
• Revise time: 2 week

PR Link(s):

[nofurtherinformation]

Milestone 4: Evaluation View

Goal:

Users can view an advanced plan statistics / evaluation view. These include stats like election metrics, geometric metrics (compactness), etc.

Timeline:

• Build out initial PR: 2-3 weeks
• Review time: ~1 day
• Revise time: ~1/2 - 1 weeks

PR Link(s):

?

[nofurtherinformation]

Milestone 5: Modifiable district numbers

Goal:

Users can change the number of districts in a plan on the fly.

Timeline:

• Build out initial PR: ~1 week
• Review time: ~1/2 day
• Revise time: ~1 day

PR Link(s):

[nofurtherinformation]

Outstanding and important questions

• A rough timeline of hiring looks like finalizing a candidate ~January to February with a start in March-April and meaningful contributions in April or May. Will that happen?
• How do we want to handle legacy districtr URLs (pages, maps, etc.)?

[nofurtherinformation]

Milestone 6: Refreshed Content Management

Goal:

Existing CMS interface is cleaned up OR ripped out and a more fully featured CMS is implemented.

Timeline:

• Build out initial PR: ~1-2 week(s)
• Review time: ~1-2 days
• Revise time: ~2-5 days

PR Link(s):

[nofurtherinformation]

Milestone 7: Easier Module Creation

Goal:

Users can request modules more easily with a form or an admin panel.

Timeline:

• Build out initial PR: Needs scoping
• Review time: Needs scoping
• Revise time: Needs scoping

PR Link(s):

[mduchin]

notes from me

elements from earlier Districtr "punchlist"

• content management
  • nice interface for partners' requests and materials
  • ease of use for non-coders to create modules in "sandbox mode"
• gallery pages -- are those stable? do those fully replace "portals"? are thumbnails in good shape?
  • search feature?
• site architecture, including navigation experience
  • new copy?
  • info about data sourcing and licensing
  • within mapping modules, it should be possible to navigate to event page / state page / data info page
• iPad and phone useability? ADA compliance? security?
• within the mapping modules
  • turn various boundary lines on and off?
  • import and export need work
  • other kinds of locking behavior?
  • coalition builder?
• "gravy" modules
  • VRA dashboard (JN)
  • COI cluster viewer (Anthony)
  • MMD mode (Max Hully)