Onam Festival Website
A full-stack cultural event and commerce platform for MIT ADT University's Onam celebration, processing 105 orders and INR 40K+ in sales across a 7-day festival commerce workflow.
- Role
- Full-Stack Developer and UI/UX Designer
- Year
- 2025
- Category
- Event Commerce Platform
Tech stack
- React 18
- Vite 7
- React Router
- Tailwind CSS
- Node.js
- Express.js
- MongoDB
- Mongoose
- Nodemailer
- express-validator
- GitHub Actions
- Netlify
- Render
Project cover

Architecture
This architecture shows users accessing the Onam React/Vite frontend through Netlify, which serves the static SPA with security headers and redirects. The frontend communicates with the Node.js/Express backend through API requests for config, order, and email-related operations. The backend connects to MongoDB for order storage, uses SMTP for email delivery, and is supported by GitHub Actions CI and Render-compatible deployment.
Product gallery
A focused snapshot of the key screens and flows from this build.




The Challenge
University festival operations can become difficult to manage when event information, merchandise orders, payment coordination, and communication are handled manually. The goal was to create a festive, responsive platform that could present Onam celebration content while supporting backend order workflows.
The Solution
I built a full-stack Onam festival portal with cultural landing sections, Sadya information, event highlights, a traditional shopping catalog, backend-powered order handling, email utilities, and safe production controls. The frontend focuses on clear navigation and festive visuals, while the backend supports order creation, retrieval, filtering, status updates, validation, and diagnostics.
Technical Implementation
The frontend uses React, Vite, React Router, and Tailwind CSS. The backend uses Express.js, MongoDB, Mongoose, Nodemailer, express-validator, CORS controls, rate limiting, request IDs, structured logging, and health diagnostics. I implemented 4 order-management APIs for order creation, lookup, filtering, and status updates with MongoDB persistence and server-side total validation. The checkout flow is feature-flagged for controlled activation.
Outcome
The platform supported a 7-day university festival commerce workflow, processing 105 orders and INR 40K+ in sales. It also introduced production controls such as checkout feature flags, CORS allowlists, rate limiting, request IDs, health diagnostics, and structured logging.
What I learned
- Shipping commerce under a time-bound festival meant prioritizing safe toggles over feature breadth.
- Server-side total validation prevented inconsistent order states when the catalog changed mid-event.
- Clear request IDs in logs turned chaotic festival-week debugging into traceable timelines.