Midhun P M — Case studyIEEE Sahrdaya Website
- Next.js 15
- Appwrite
The problem
A student branch's website is where every event registration, announcement, and first impression happens. Ours needs to handle real traffic — 1000+ users a week — without anyone on the team babysitting it.
What I built
This one's a team effort, and my role is contributor, not sole author. As the branch's Technical Coordinator, I ship features to the production site and work on performance — the kind of unglamorous changes that make pages load fast on hostel wifi and stay up during event registration rushes.
The site runs on Next.js 15 with Appwrite as the backend. It also hosts the branch's bigger experiments — WC Predict '26 lived under the same roof at ieeesahrdaya.com/fifa.
Tech decisions
Next.js 15. Server components and static rendering where possible — most of what a branch site serves is content that doesn't change by the second, so it should be cached like it.
Appwrite for the backend. Auth, database, and storage without running a server ourselves. For a student team where maintainers graduate every few years, managed beats clever.
What I learned
Maintaining someone else's production codebase is a different skill from greenfield projects. You read more than you write, you respect decisions made before you arrived, and you make changes small enough that the next coordinator can understand them. A student org's codebase outlives every contributor — write for the person who inherits it.