How shiva-ganesh-varikuppala/jee-blueprint works
JEE Blueprint is a personal JEE study planner. A user signs in, then the React app routes them to a dashboard and study tools; task and syllabus actions use the authenticated API and persist through the Flask backend. The source confirms task and syllabus progress flows, while component names and routing identify additional study features. Backend internals and several feature implementations are only partially sampled, so uncertain service wiring is omitted.
Main entry points: main.tsx App router · Auth.tsx API client · app.py Flask API · App.tsx Dashboard
Components 17
Study app
- App router
src/main.tsx - Sign-in
src/Auth.tsx - Dashboard
src/App.tsx - API client
src/Auth.tsx
Planning tools
- Task tracker
src/Tasks.tsx - Study planner
src/Planner.tsx - Study strategy
src/Strategy.tsx - Personal timetable
src/PersonalTimetable.tsx - Focus tools
src/FocusTools.tsx
Study resources
- Syllabus tracker
src/Syllabus.tsx - Syllabus content
backend/syllabus.py - AI study assistant
src/AiTutor.tsx - Formula book
src/FormulaBook.tsx - Analytics
src/Analytics.tsx
API and state
- Flask API
backend/app.py - Application database
backend/app.py
Other components
- Student
Connections 20
- Student → App router: uses
- App router → Sign-in: renders
- App router → Dashboard: routes to
- App router → Study planner: renders
- App router → Study strategy: renders
- App router → Task tracker: renders
- App router → Focus tools: routes to
- App router → Syllabus tracker: routes to
- App router → AI study assistant: routes to
- App router → Personal timetable: routes to
- App router → Analytics: routes to
- App router → Formula book: routes to
- Sign-in → API client: calls
- Dashboard → API client: calls
- Task tracker → API client: calls
- Syllabus tracker → API client: calls
- Personal timetable → API client: calls
- API client → Flask API: sends requests
- Flask API → Application database: reads and writes
- Flask API → Syllabus content: loads content