How gowtham-mg-2006/esports-tournament-management-platform works
This is a full-stack esports tournament management platform. Players register and verify accounts, create or join teams, register teams for tournaments, and view matches, brackets, and standings; organizers manage tournament stages, seeding, brackets, and results, while admins manage users and resources. The frontend routes pages through a shared API client to a Django REST API, whose domain models persist tournament, team, match, and user data. The README documents capabilities beyond the sampled source; arrows for those features are included only where documented. Not every backend view or frontend page was sampled.
Main entry points: client.ts HTTP client · App.tsx Route application · services.py Bracket and results · AdminPage.tsx Admin console
Components 23
Web application
- Route application
frontend/src/App.tsx - Authentication state
frontend/src/context/AuthContext.tsx - Login and verification
frontend/src/pages/LoginPage.tsx - Team pages
frontend/src/pages/TeamsPage.tsx - Tournament pages
frontend/src/pages/TournamentsPage.tsx - Tournament detail
frontend/src/pages/TournamentDetailPage.tsx - Admin console
frontend/src/pages/AdminPage.tsx
API and identity
- HTTP client
frontend/src/api/client.ts - Authentication API
frontend/src/api/auth.ts - Team API
frontend/src/api/teams.ts - Tournament API
frontend/src/api/tournaments.ts - Match API
frontend/src/api/matches.ts - User administration API
frontend/src/api/users.ts - Account and OTP
backend/users/services.py - Email notifications
backend/app/core/email.py
Competition workflows
- Team management
backend/teams/views.py - Tournament lifecycle
backend/tournaments/views.py - Bracket and results
backend/matches/services.py
Domain data
- Users
backend/users/models.py - Teams
backend/teams/models.py - Tournaments and registrations
backend/tournaments/models.py - Matches
backend/matches/models.py
Other components
- Player / organizer
Connections 34
- Player / organizer → Route application: uses
frontend/src/App.tsx - Route application → Login and verification: routes to
frontend/src/App.tsx - Route application → Team pages: routes to
frontend/src/App.tsx - Route application → Tournament pages: routes to
frontend/src/App.tsx - Route application → Tournament detail: routes to
frontend/src/App.tsx - Route application → Admin console: routes to
frontend/src/App.tsx - Route application → Authentication state: wrapped by
frontend/src/main.tsx - Authentication state → Authentication API: calls
frontend/src/context/AuthContext.tsx - Authentication API → HTTP client: sends requests
frontend/src/api/auth.ts - Team pages → Team API: uses
- Tournament pages → Tournament API: uses
frontend/src/pages/TournamentsPage.tsx - Tournament detail → Tournament API: uses
frontend/src/pages/TournamentDetailPage.tsx - Admin console → User administration API: uses
frontend/src/pages/AdminPage.tsx - Admin console → Tournament API: uses
frontend/src/pages/AdminPage.tsx - Admin console → Team API: uses
frontend/src/pages/AdminPage.tsx - Admin console → Match API: uses
frontend/src/pages/AdminPage.tsx - Tournament API → HTTP client: sends requests
frontend/src/api/tournaments.ts - Team API → HTTP client: sends requests
- Match API → HTTP client: sends requests
- HTTP client → Account and OTP: calls API
README.md - HTTP client → Team management: calls API
README.md - HTTP client → Tournament lifecycle: calls API
README.md - HTTP client → Bracket and results: calls API
README.md - Account and OTP → Users: reads and writes
backend/users/services.py - Account and OTP → Email notifications: sends OTP
backend/users/services.py - Team management → Teams: reads and writes
backend/teams/views.py - Tournament lifecycle → Tournaments and registrations: reads and writes
backend/tournaments/views.py - Tournament lifecycle → Teams: uses teams
backend/tournaments/views.py - Tournament lifecycle → Bracket and results: uses match data
backend/tournaments/views.py - Tournament lifecycle → Email notifications: notifies registrants
backend/tournaments/views.py - Bracket and results → Tournaments and registrations: reads registrations
backend/matches/services.py - Bracket and results → Matches: creates and updates
backend/matches/services.py - Bracket and results → Teams: uses teams
backend/matches/services.py - Bracket and results → Email notifications: notifies teams
backend/matches/services.py