Skip to content

Post-Login User Journey and Competition Workspace #286

Description

@PhilipWoulfe

Epic E: Post-Login User Journey and Competition Workspace

Summary

Design and implement the post-login journey so users land in the right competition context, review standings clearly, and drill down into participant selections and migration context.

Why This Epic

Users need a predictable flow after login. Today, context and review goals are not explicit enough for fast navigation and reliable decision-making.

Goals

  • Provide role-aware landing behavior after authentication.
  • Make competition-season context selection explicit and persistent.
  • Expose score-source clarity in leaderboard and detail views.
  • Improve deep-link and workflow continuity for admin review.

Non-Goals

  • Changing migration scoring math.
  • Rebuilding unrelated site navigation.

User Stories

Story E1: Define role-based landing page after login

As a user, I want a role-appropriate landing destination so I can start in the right workspace.

Story E2: Add competition and season selector with last-used context

As a frequent user, I want context recall so repeated visits are faster.

Story E3: Add competition leaderboard with clear score-source labeling

As a participant, I want transparent score-source labels so standings interpretation is unambiguous.

Story E4: Add participant drilldown into race picks, preseason, and H2H

As a reviewer, I want per-person drilldown so totals can be validated against component outcomes.

Story E5: Add migration-run visibility and status chips in admin journey

As an admin, I want migration status visibility in my normal flow so operational health is obvious.

Story E6: Add shareable deep links to competition, participant, and run context

As an operator, I want URL-stable links so reviews can be shared without losing state.

Story E7: Add end-to-end accessibility and keyboard flow for review workflows

As a keyboard and screen-reader user, I want full workflow coverage so review actions are accessible.

Definition of Done

  • Post-login flow is role-based and deterministic.
  • Competition-season context is selectable, persisted, and deep-linkable.
  • Leaderboard and participant drilldowns show clear score-source semantics.
  • Accessibility and keyboard flow coverage exists for primary review tasks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions