Public Roadmap

What’s shipped, what’s active, and what comes next.

GameData Central is no longer a concept page. The platform has shipped through v1.9, content reporting is live, and v2.0 is now focused on community engagement systems that deepen identity, following, reputation, and guide history.

Live on gamedatacentral.com
v2.0 Community Engagement active
Phases 1–53 shipped
Shipped milestones
10+
v1.0 through v1.9 are complete, plus Phase 52 content reporting.
Current phase
54
Account settings and connected accounts cleanup is the next practical surface.
Roadmap focus
v2.0
Community engagement, social features, badges, and version history.
Build posture
Iterative
Ship stable slices, instrument behavior, and expand from real usage instead of slides.
Current Status

The product has moved beyond the original three-phase placeholder.

The old roadmap framed the platform as “Phase 1.2 live” with major core work still pending. That is no longer accurate. Payments, verification, ops hardening, structured logging, reporting, and analytics instrumentation are already shipped. The current public roadmap should reflect what is actually in production.

Active Track
v2.0 Community Engagement
The active roadmap is now centered on strengthening the user layer around the existing guide platform: connected accounts, following, social activity, contributor reputation, and versioned guide history.
53
Analytics instrumentation and event taxonomy Shipped April 3, 2026. Canonical events table, helper, admin snapshot endpoint, and dashboard analytics card.
54
Account settings and connected accounts Twitch connect and disconnect flows directly from the account page with clear UI feedback and analytics events.
55
User following and social activity feed Follow relationships, feed surfaces, and notification hooks so the guide ecosystem feels inhabited.
After That
Trust, identity, and history layers
Once following is in place, the roadmap shifts into contributor reputation and guide versioning. That creates the foundation for higher-trust community content and better editorial recovery when guides evolve over time.
56
Contributor reputation and badges Visible reputation tiers derived from published work, approved edits, bookmarks, and moderation outcomes.
57
Guide versioning History, diffs, and rollback support so edits remain transparent and recoverable.
Milestones

Recent roadmap reality, compressed.

These are the milestones that matter for understanding the current product. The platform is not waiting on “basic foundations” anymore. Those foundations are already in production.

v1.8
Shipped

Production readiness and revenue activation

Schema foundations, Stripe billing, email verification, production ops, and catalog hardening all shipped by March 31, 2026.

Phases 40–45 Shipped 2026-03-31
v1.9
Shipped

Revenue operations and observability

Webhook admin tooling, structured logging, health and revenue events, verification throttling, and documentation cleanup shipped by April 1, 2026.

Phases 46–51 Shipped 2026-04-01
Phase 52
Shipped

Content reporting

Reporting landed ahead of the formal v2.0 milestone chain, giving the platform a stronger moderation and trust baseline before deeper social features.

Pre-v2.0 Shipped 2026-04-03
v2.0
Active

Analytics instrumentation and taxonomy

The first v2.0 slice is already done: canonical analytics events, route instrumentation, and an admin-facing snapshot surface for decision support.

Phase 53 Shipped 2026-04-03
v2.0
Planned

Account settings and connected accounts

The next practical user-facing upgrade is cleaning up account settings and making Twitch linking feel native instead of auxiliary.

Phase 54 UI-focused
v2.0
Planned

Following, reputation, and guide history

Phases 55–57 turn the guide system into a real contributor platform with social graph, trust cues, and content history.

Phases 55–57 Community systems
Phase Timeline

Current public roadmap phases.

This page now focuses on the active roadmap window instead of relisting the earliest platform foundations as if they were still pending.

Shipped

Phase 53: Analytics instrumentation and event taxonomy

The platform now records significant account, billing, content, and moderation events in a canonical analytics stream. Admin surfaces can view rolling counts without forcing the product to depend on third-party dashboards for basic operational visibility.

Goal achieved Canonical event table, fire-and-forget helper, 28 instrumented events, admin snapshot endpoint.
Why it matters Later roadmap choices can be informed by actual platform behavior rather than intuition.
Next up

Phase 54: Account settings and connected accounts

Users should be able to connect and disconnect Twitch from the account page with clear, local feedback. This phase is small enough to ship cleanly and foundational enough to support the more social work that follows.

Primary outcome Account page becomes the canonical home for linked identity management.
Dependency role Supports future notifications, follow identity, and analytics on connected-account behavior.
Planned

Phases 55–57: Social graph, contributor trust, and version history

These phases turn the existing guides platform into a deeper community product. Following drives feed relevance, reputation drives trust signals, and version history makes guides safer to evolve over time.

Phase 55 Follow/unfollow, activity feed, and follow notifications.
Phase 56 Reputation score, contributor tiers, and badge display across profiles and guide cards.
Phase 57 Guide snapshots, history tab, diff viewing, and rollback support.
Build logic Identity first, then follow relationships, then visible trust, then edit history.
Principles

How roadmap decisions are made.

📊
Instrumentation before opinion
The platform now has a stronger analytics foundation. Roadmap sequencing should follow observed friction and adoption, not abstract feature appetite.
🧱
Stabilize before expanding
The public roadmap should stop pretending early infrastructure is missing and instead emphasize stable, incremental expansion from the current production baseline.
👥
Community trust matters
Following, reputation, moderation, and version history are not extras. They are the systems that determine whether community content feels reliable.
🔎
Public roadmap should be literal
If a milestone shipped, say it shipped. If a phase is next, say it is next. The roadmap should read like the product state, not like an old pitch deck.

Explore what is already live.

The roadmap is useful only if it points back to real surfaces. Browse the catalog, read the changelog, or create an account and work from the platform that already exists.

View Changelog Explore Community Open Account