Skip to content

Add architecture diagram for the analytics data flow #569

Description

@phertyameen

Description

Add a diagram (Mermaid, following the style of ONBOARDING_FLOW_DIAGRAM.md) showing the path from an in-app action to a dashboard number: module emits event → listener persists to AnalyticsEvent → nightly job rolls up → provider reads → API → frontend.

Why this matters

A visual data-flow diagram makes it much faster for new contributors to understand where their change fits in the pipeline.

Files to touch

  • backend/src/analytics/ANALYTICS_FLOW_DIAGRAM.md

Acceptance Criteria

  • Diagram covers the full path from event emission to dashboard display
  • Diagram references real file names from the module (not placeholders)

Notes

This issue is part of the new analytics module effort (tracking, aggregation,
and reporting on player/game activity). Please keep new code inside
backend/src/analytics/ following the same module/controller/service/provider
layout used by existing modules (e.g. progress, streak, quests).

Activity

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

Metadata

Metadata

Assignees

Labels

GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardOfficial Campaign | FWC26Campaign: Official Campaign | FWC26analyticsdocumentationImprovements or additions to documentation

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions