ReactJS Sports App Scaffold
Budget: ₹600 – ₹1,500 INR
I need a React 18 codebase that lays the foundation for a sports-management web app. Your job is to set up a clean project structure, wire in Tailwind CSS for styling, and build a handful of reusable components and starter pages so future features can drop straight in.
Core requirements
• Configure Vite (or CRA if you strongly prefer) with React Router, eslint, prettier, and absolute path aliases.
• Integrate Tailwind CSS with a minimal but sensible base theme.
• Build authentication from scratch: email / password signup, login, protected route handling, and token storage (localStorage is fine for now). All auth endpoints can hit my mock API; just keep the logic modular so I can swap in the real service later.
• Create starter screens: Dashboard, Teams, Players, Schedule, plus a 404 fallback. Each should demonstrate component composition and responsive layout.
• Provide two or three example reusable UI pieces (table, modal, toast) that follow Tailwind utility conventions.
• Leave clear placeholder services where future calls for team management, player stats, and event scheduling will plug in.
Acceptance will be based on:
1. Project runs with `npm install && npm run dev` out of the box.
2. Pages navigate without full reloads and protected routes redirect unauthenticated users.
3. Code is lint-clean, well-commented, and organized in feature folders.
4. A short README explains structure, scripts, and how to point to real APIs later.
If this first phase goes smoothly there’s much more work ahead, but for now I just want a rock-solid scaffold.
Core requirements
• Configure Vite (or CRA if you strongly prefer) with React Router, eslint, prettier, and absolute path aliases.
• Integrate Tailwind CSS with a minimal but sensible base theme.
• Build authentication from scratch: email / password signup, login, protected route handling, and token storage (localStorage is fine for now). All auth endpoints can hit my mock API; just keep the logic modular so I can swap in the real service later.
• Create starter screens: Dashboard, Teams, Players, Schedule, plus a 404 fallback. Each should demonstrate component composition and responsive layout.
• Provide two or three example reusable UI pieces (table, modal, toast) that follow Tailwind utility conventions.
• Leave clear placeholder services where future calls for team management, player stats, and event scheduling will plug in.
Acceptance will be based on:
1. Project runs with `npm install && npm run dev` out of the box.
2. Pages navigate without full reloads and protected routes redirect unauthenticated users.
3. Code is lint-clean, well-commented, and organized in feature folders.
4. A short README explains structure, scripts, and how to point to real APIs later.
If this first phase goes smoothly there’s much more work ahead, but for now I just want a rock-solid scaffold.