EduQuest

The system follows a domain‑driven modular architecture where each functional area (auth, assignments, submissions, payments, wallet) lives in its own API route folder and is backed by dedicated Mongoose models (User, Assignment, Submission, TokenWallet, Transaction, Payment). Authentication uses JWTs stored in HTTP‑only cookies, providing a 7‑day session that gates access to teacher‑only pages via client‑side guards (useAuth).

Data ingestion begins when a teacher creates an assignment via /api/assignments. The payload is validated, persisted, and made queryable through GET /api/assignments endpoints. Students retrieve assignments by code, record voice input, and submit answers to /api/submissions. The submission handler invokes the NLPEngine (abstracted in lib/) to generate auto‑graded feedback and updates token balances in TokenWallet.

Payment flow is mediated by the RazorPayGateway. When a student purchases tokens, the client calls POST /api/payments/create-order, which creates a Razorpay order, stores a Payment document, and on verification updates the wallet balance. All financial state transitions are recorded in the Transaction collection, ensuring auditability.

Security guardrails include server‑side password hashing with bcrypt, JWT signature verification, role‑based redirects, and strict TypeScript typings for request/response contracts. The monorepo leverages Yarn workspaces to share ESLint configs and TypeScript settings across the web and admin packages, simplifying CI/CD pipelines.

Build topology uses Next.js’s edge‑runtime for API routes, enabling fast cold‑start times, while UI components are compiled with TailwindCSS for a responsive design. The admin console runs on a separate port (3002) and provides analytics via Recharts, consuming the same MongoDB data layer for consistency.