How saketh010/cdc-portal works
Project Type and Purpose
• Full-stack web application for students/admins to browse, post, and apply for jobs.
• Built with Next.js (frontend + API routes), Node.js/Express style logic, MongoDB database, and SMTP for emails.
Main Components
a. Frontend (Next.js pages & React components)
• UI modules: Auth, Layout, Profile, SEO, Buttons/Inputs
• Pages: home, login, signup, job listings, admin dashboard, profile, etc.
b. Backend/API (Next.js API routes under pages/api)
• Auth routes: login, logout, password reset, OTP
• Jobs routes: list, detail, post, update
• Applications routes: apply, list, withdraw, email notifications
• Selections routes: add/get selection records
c. Database
• MongoDB collections via Mongoose models (User, Job, Application, Selections, etc.)
d. External Services
• SMTP email provider for notifications
• Docker/Docker-Compose for containerized deployment
Relationships & Data Flow
1. User’s browser → Next.js frontend (HTTP/HTTPS)
2. Frontend → API routes (REST calls)
3. API handlers → MongoDB (CRUD via Mongoose)
4. API handlers → SMTP service (send emails)
5. Docker Compose orchestrates frontend, backend, and database containers
Architectural Patterns & Design Principles
• Separation of Concerns: UI components vs. page layouts vs. API logic vs. data models
• RESTful API structure within Next.js routes
• Role-based access control enforced in Auth middleware components
• Containerization for environment consistency