How bouazz-a/mtym-2026 works
This tree contains two related tournament-management applications: a participant/workshop platform under backend/ and frontend/, and a jury-focused tournament platform under jury_platform/. Their main user journey is role-based access to tournament information and tasks, followed by administration or jury evaluation; the jury platform additionally supports draws, report assignments, convocations, and results. Source excerpts establish app routing, API route registration, and authentication-to-database behavior. Other feature connections are kept at subsystem level where implementation details were not sampled.
Main entry points: src/App.tsx Role routing · src/App.tsx Role routing · auth.ts Account authentication · index.ts API routes
Components 24
Participant platform
- Participants
frontend/src/features/participant - Jury users
frontend/src/features/jury - Organizers
frontend/src/features/organizer - Role routing
frontend/src/App.tsx - API client
frontend/src/lib/api/client.ts
Participant API
- API routes
backend/src/routes/index.ts - Identity and roles
backend/src/middleware/auth.ts - Tournament data
backend/src/routes
Jury platform
- Administration
jury_platform/frontend/src/features/admin - Jury workflow
jury_platform/frontend/src/features/jury - Role routing
jury_platform/frontend/src/App.tsx - API client
jury_platform/frontend/src/lib/api/client.ts - Exports and results
jury_platform/frontend/src/lib/services/exportService.ts
Jury API
- API routes
jury_platform/backend/src/routes/index.ts - Account authentication
jury_platform/backend/src/routes/auth.ts - Token and access checks
jury_platform/backend/src/middleware/auth.ts - Tournament operations
jury_platform/backend/src/routes - Tournament services
jury_platform/backend/src/services
Runtime infrastructure
- Postgres access
backend/src/db.ts - Postgres access
jury_platform/backend/src/db.ts
Other components
- Participant
- Jury member
- Organizer
- Administrator
Connections 20
- Participant → Role routing: uses
- Jury member → Role routing: uses
- Organizer → Role routing: uses
- Role routing → Participants: routes to
frontend/src/App.tsx - Role routing → Jury users: routes to
frontend/src/App.tsx - Role routing → Organizers: routes to
frontend/src/App.tsx - API routes → Identity and roles: uses
backend/src/routes/index.ts - API routes → Tournament data: registers
backend/src/routes/index.ts - Identity and roles → Postgres access: looks up users
backend/src/middleware/auth.ts - Administrator → Role routing: uses
- Jury member → Role routing: uses
- Role routing → Administration: routes to
jury_platform/frontend/src/App.tsx - Role routing → Jury workflow: routes to
jury_platform/frontend/src/App.tsx - Administration → Exports and results: uses
- API routes → Account authentication: registers
- API routes → Tournament operations: registers
- Account authentication → Token and access checks: authenticates with
jury_platform/backend/src/routes/auth.ts - Token and access checks → Postgres access: reads accounts
jury_platform/backend/src/middleware/auth.ts - Account authentication → Postgres access: reads and updates
jury_platform/backend/src/routes/auth.ts - Exports and results → Tournament services: computes results
jury_platform/frontend/src/lib/services/exportService.ts