USRSE / USRSE/usrse.github.io

feat(admin): build leadership admin dashboard

Open
#1,920 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
33
Forks
104
Avg merge
12h 3m
Merged PRs (30d)
10

Description

Summary

Build an admin dashboard for board members and staff to manage the membership, view analytics, and perform administrative actions.

Requirements

Member Management
  • Member directory with search, sort, and filter
  • View full member details (all profile fields + internal metadata)
  • Add members manually (invite by email)
  • Remove/deactivate members with reason
  • Edit member roles (promote to admin, demote)
  • Bulk actions (export, role changes)
Analytics & Visualization
  • Member growth chart (line chart: members over time)
  • Institution breakdown (bar chart: top institutions by member count)
  • Geographic distribution (if location data available)
  • Working group participation (which groups are most active)
  • New members per month trend
  • Retention metrics (active vs inactive)
Data Export
  • Export member list as CSV
  • Configurable columns (select which fields to export)
  • Date range filtering for exports
Audit Log
  • View all admin actions (who did what, when)
  • Filter by action type, admin user, date range
  • Log entries for: role changes, member removal, manual additions

Context

Parent issue: #1916
Depends on: #1917 (schema), #1918 (auth — admin role required), #1919 (profiles — member data to display)

Implementation Notes

  • Route: /admin with sub-routes (/admin/members, /admin/analytics, /admin/audit)
  • Charts: Recharts or @visx (both work well with React + Tailwind)
  • Dashboard layout: sidebar nav + main content (different from the public site layout)
  • Must be fully protected — only admin and super_admin roles can access
  • Consider real-time updates via polling or WebSocket for active member counts

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the /admin entry point and its planned /admin/members, /admin/analytics, and /admin/audit sub-routes, then review dependencies #1917, #1918, and #1919. Choose Recharts or @visx for the React + Tailwind dashboard and ensure access is limited to admin and super_admin roles. Done means the listed member management, analytics, export, and audit-log requirements are implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, tailwindcss
Domain
analytics, authorization, data, full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.