How athilingam3336-dotcom/cricket1 works
CFVD CricNative combines a public district-cricket portal, mobile access to that portal, and authenticated team, administrator, and scorer workflows backed by an Express API. The public workflow presents federation information, fixtures, scorecards, standings, player statistics, registrations, and media. Scorers authenticate, configure a match, record deliveries, and view scorecards; teams register and manage profiles, while administrators oversee approvals and federation data. Backend excerpts establish key routes, service calls, scoring persistence, and authentication; README capabilities supplement unsampled portal features.
Main entry points: App.js Portal shell · db.js Database store · authService.js Authentication service · scorerRoutes.js Scorer routes
Components 34
Public cricket portal
- Portal shell
App.js - Cricket content data
src/data/cricketData.js - Registration portal
src/components/RegistrationModal.js - Match scorecards
src/components/ScorecardModal.js - Standings and stats
src/components/PointsTableSection.js - Federation features
src/components
Mobile experiences
- Mobile app host
mobile_frontend/App.tsx - Admin workspace
mobile_frontend/src/admin - Team access screens
mobile_frontend/src/screens/team/TeamLoginScreen.tsx - Scorer workflow screens
mobile_frontend/src/screens/scorer/LiveScoringScreen.tsx - Admin API client
mobile_frontend/src/admin/services/adminApi.ts - App API client
mobile_frontend/src/services/api.ts
Identity and administration
- Express API server
backend/server.js - Admin routes
backend/routes/adminRoutes.js - Admin management
backend/controllers/adminDashboardController.js - Admin approvals
backend/services/adminService.js - Authentication routes
backend/routes/authRoutes.js - Authentication controller
backend/controllers/authController.js - Authentication service
backend/services/authService.js - Token authorization
backend/middleware/authMiddleware.js
Competition operations
- Team routes
backend/routes/teamRoutes.js - Team registration
backend/services/teamService.js - Scorer routes
backend/routes/scorerRoutes.js - Scorer match views
backend/services/scorerService.js - Match setup
backend/services/matchService.js - Ball scoring engine
backend/services/scoringEngine.js - Player services
backend/services/playerService.js
Data and messaging
- Database store
backend/config/db.js - User records
backend/models/userModel.js - Scorer records
backend/models/scorerModel.js - Team records
backend/models/teamModel.js - OTP service
backend/services/otpService.js - Email delivery
backend/config/mailer.js
Other components
- Federation visitor
Connections 39
- Federation visitor → Portal shell: browses
- Portal shell → Cricket content data: uses content
App.js - Portal shell → Registration portal: opens enrollment
App.js - Portal shell → Match scorecards: opens scorecard
- Portal shell → Standings and stats: shows standings
- Portal shell → Federation features: presents
App.js - Mobile app host → Portal shell: embeds portal
mobile_frontend/App.tsx - Mobile app host → Scorer workflow screens: opens scorer mode
mobile_frontend/App.tsx - Mobile app host → Team access screens: opens team mode
mobile_frontend/App.tsx - Admin workspace → Admin API client: requests data
mobile_frontend/src/admin/context/AdminAuthContext.tsx - Team access screens → App API client: requests data
- Scorer workflow screens → App API client: requests data
- Express API server → Admin routes: mounts routes
backend/server.js - Express API server → Team routes: mounts routes
backend/server.js - Express API server → Player services: mounts player API
- Admin routes → Admin management: dispatches requests
backend/routes/adminRoutes.js - Admin routes → Admin approvals: calls approvals
backend/routes/adminRoutes.js - Admin routes → Token authorization: guards routes
backend/routes/adminRoutes.js - Admin management → Database store: reads and writes
backend/controllers/adminDashboardController.js - Authentication routes → Authentication controller: dispatches requests
backend/routes/authRoutes.js - Authentication controller → Authentication service: calls authentication
backend/controllers/authController.js - Authentication controller → Email delivery: checks mail
backend/controllers/authController.js - Authentication service → User records: uses user records
backend/services/authService.js - Authentication service → Scorer records: uses scorer records
backend/services/authService.js - Authentication service → OTP service: generates OTP
backend/services/authService.js - Team routes → Team registration: calls team operations
backend/routes/teamRoutes.js - Team registration → Team records: uses team records
- Scorer routes → Authentication service: handles registration
backend/routes/scorerRoutes.js - Scorer routes → Scorer match views: loads match views
backend/routes/scorerRoutes.js - Scorer routes → Match setup: configures matches
backend/routes/scorerRoutes.js - Scorer routes → Ball scoring engine: records deliveries
backend/routes/scorerRoutes.js - Ball scoring engine → Database store: updates score state
backend/services/scoringEngine.js - Ball scoring engine → Scorer match views: publishes live updates
- Admin approvals → Database store: uses persistence
backend/services/adminService.js - Admin approvals → OTP service: uses verification codes
backend/services/adminService.js - Admin approvals → Email delivery: sends email
backend/services/adminService.js - User records → Database store: reads and writes
backend/models/userModel.js - Scorer records → Database store: reads and writes
backend/models/scorerModel.js - Team records → Database store: reads and writes
backend/models/teamModel.js