
Overview
A production web platform built to run the digital side of SMUCT CSE Fest v3.0 – from participant registration to submissions, payments, judging, and result publication.
#The Challenge
The festival involved multiple competitions with different eligibility rules, team structures, registrations, payments, submissions, and administrative workflows. Managing these manually would have created unnecessary coordination and data-entry overhead.
The goal was to bring the core event workflow into one reliable platform for both participants and organizers.
#What I Built
- Competition discovery with eligibility, rules, schedules, and event details
- Participant and team registration workflows
- Eligibility-aware registration experience
- Submission management for participating teams
- Payment and verification workflows
- Admin dashboard for registrations, teams, payments, and submissions
- Judging and score management with result publication
- Authentication with separate participant, coordinator and admin access
- Responsive interface designed for students and organizers
#My Role
As Lead Developer, I worked across the frontend, backend integration, database workflows, authentication, and production deployment.
#Production
This was my first real production application – deployed on a university VM and used by actual participants and organizers during the festival.
I handled production deployment with Next.js, Nginx, Supabase, SSL, and Windows services, while troubleshooting authentication, reverse-proxy, deployment, and server issues during the event.
#Outcome
The platform became the central digital workflow for the festival's registration and submission process, replacing several manual processes with a single system built for real users and real event constraints.
#What I Learned
The project pushed me beyond writing application code into production engineering – deployment, infrastructure, authentication, debugging, reliability, and operating software under real-world pressure.
Lessons Learned
- Built and operated a real production system.
- Learned to troubleshoot deployment and infrastructure issues.
- Saw firsthand how real users change software requirements.