avinashsharma01/academic_notes_mana...

gnUp, etc. | | `Components/` | Reusable UI components: Navbar, Footer, Card, Spinner, etc. | | `Sessions/`, `Courses/`, `Branches/`, `Semesters/`, `Subject/`, `Notes/` | Each contains cards/components for that academic level. | | `AdminPages/`, `SuperAdminPages/` | Admin/SuperAdmin-specific pages. | **Navigation flow (frontend):** ``` Home → Dashboard (Sessions) → Course Cards → Branch Cards → Semester Cards → Subject Cards → Notes Listing ``` --- ## 8. Authentication System — The Complete Flow ### 8.1 Three-Role Architecture | Role | Model | Cookie | JWT Key | |------|-------|--------|---------| | **Student** | `User` | `authToken` | `id`, `role: "student"` | | **Admin** | `Admin` | `authToken` | `id`, `role: "admin"` | | **SuperAdmin** | `SuperAdmin` | `SuperauthToken` | `id`, `role: "superadmin"` | **Why separate cookies?** SuperAdmin routes use `SuperauthToken` so they don't interfere with regular user auth. A SuperAdmin can still access user routes because `authenticateUser