Skip to content

Feature: Member role — pages + role-aware foundation #92

Description

@FadyGergesRezk

Why

Build the Member role experience in the web client, plus the shared role-aware foundation the other roles build on. The Member is the base lens: a member who reads their own club data.

Role naming

role string UI label
member Member
trainer Coach
director Director
admin Admin

What to build

Shared foundation (used by all roles):

  • Read the signed-in user's role and show the matching label
  • Role-filtered sidebar that shows only the tabs a role can use
  • Mock data so the app runs without a backend

Member pages:

  • Dashboard — next training, balance, development snapshot, recent feedback
  • Events — read-only list and detail, including which past events were missed
  • Feedback — read-only, feedback about me
  • Payments — own balance and transactions
  • Teams — the teams the member belongs to
  • Development — the member's own report

Metadata

Metadata

Labels

buildclientIssue regarding the client frontend

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions