How abhay-kushwaha/study-planner works
Project type and purpose
• This is a full-stack web application called “Study Planner.”
• The frontend is a React (Vite + Tailwind CSS) single-page app.
• The backend is a Python HTTP API (likely FastAPI or Flask style) with routes for auth, plan generation, and user management.
File structure
• Top-level:
• backend/ – Python API
– app/main.py (entry point)
– app/controllers (business logic)
– app/routes (API endpoints: auth, plan, api)
– app/models (data models: user.py)
– app/middleware (e.g., logging)
– app/utils (generate_plan logic)
– requirements.txt, package.json (possibly for nodemon or front-end package bundling), railway.json (deployment on Railway)
• frontend/ – React single-page application
– src/pages (Landing, Login, SignUp, Dashboard, StudyPlanner, etc.)
– src/components (UI: HeroSection, PlanCard, Modal)
– src/services/api.js (wrapper for HTTP calls)
– Vite/Tailwind config, netlify.toml (deploy on Netlify)
Insights from README
• Title “Study Planner” – no further architecture comments, so we infer a classic SPA + REST API + database.