How dachrisch/leaguesphere works
LeagueSphere is a Django-based sports league and gameday management application with several React interfaces. A typical organizer designs or schedules a gameday, records game results, and uses those results for standings and live or administrative views; officials and player eligibility have separate workflows. The tree and sampled files support the designer, schedule creation, ranking, and dashboard roles, but do not establish every endpoint-to-service call. The graph therefore shows the documented/runtime boundaries and omits uncertain wiring.
Main entry points: urls.py Django application · views.py Designer backend · models.py Gameday data · useDesignerController.ts Designer controller
Components 23
Gameday planning
- Designer UI
gameday_designer/src/App.tsx - Designer controller
gameday_designer/src/hooks/useDesignerController.ts - Designer API
gameday_designer/src/api/designerApi.ts - Designer backend
gameday_designer/views.py - Template services
gameday_designer/service/template_application_service.py - Gameday services
gamedays/service/gameday_service.py - Schedule creation
gamedays/management/schedule_manager.py - Gameday data
gamedays/models.py
Game operations
- Scorecard UI
scorecard/src/components/App.jsx - Scorecard backend
scorecard/views.py - Game API
gamedays/api/game_views.py - Game services
gamedays/service/game_service.py
League services
- Officials management
officials/service/official_service.py - Player eligibility
passcheck/service/passcheck_service.py - Standings API
league_table/api/views.py - Ranking engine
league_table/service/ranking/engine.py - League data
league_table/models.py
Live and insights
- Live ticker
liveticker/src/components/LivetickerApp.jsx - Journey dashboard
journey_dashboard/src/App.tsx - Journey API
journey/api/progress_views.py
Application platform
- Django application
league_manager/urls.py
Other components
- Organizer
- League user
Connections 27
- Organizer → Designer UI: designs schedule
- Designer UI → Designer controller: dispatches actions
- Designer controller → Template services: generates tournament
- Designer controller → Designer API: requests data
- Designer API → Designer backend: calls API
- Designer backend → Template services: applies templates
- Designer backend → Gameday data: persists gameday
- Organizer → Schedule creation: creates schedule
- Schedule creation → Gameday data: writes games
- League user → Scorecard UI: records results
- Scorecard UI → Scorecard backend: submits game data
- Scorecard backend → Game API: requests game data
- Game API → Game services: handles game operations
- Game services → Gameday data: reads game records
- Game services → Gameday data: updates results
- League user → Officials management: manages officials
- League user → Player eligibility: checks eligibility
- League user → Standings API: requests standings
- Standings API → Ranking engine: computes rankings
- Ranking engine → League data: uses league rules
- League user → Live ticker: views live games
- League user → Journey dashboard: views progress
- Journey dashboard → Journey API: fetches metrics
- Django application → Designer backend: routes requests
- Django application → Game API: routes requests
- Django application → Standings API: routes requests
- Django application → Journey API: routes requests