2026 · Official chapter platform
IEEE
SB IIT.
[ a chapter that runs dozens of events needs more than a landing page ]
A home for every event, and a dashboard to run it.
The assignment
The official website of the IEEE Student Branch of IIT, built with a backend and admin dashboard so the committee can publish events, manage media and receive messages without touching code.
The branch runs CodeSprint, CodeRally, MicroMaze and a calendar of workshops across six chapters. Until now their history lived in posts and slide decks. The site makes it one browsable archive that the committee keeps current themselves.
02 / Desktop system
Every
interface.
Six key pages, from the first impression to the event archive, the committee and the contact desk.
.webp&w=3840&q=75)
.webp&w=3840&q=75)
.webp&w=3840&q=75)
.webp&w=3840&q=75)
.webp&w=3840&q=75)
One archive, many chapters
Built to outlast
any one committee.
03 / Mobile system
The whole
branch.
In hand.
Most students find an event from a phone. Every page holds the same hierarchy at 390 px.
.webp&w=3840&q=75)
.webp&w=3840&q=75)
.webp&w=3840&q=75)
.webp&w=3840&q=75)
.webp&w=3840&q=75)
[ the part visitors never see ]
The committee
runs the site.
Office bearers change every year, and none of them should need a developer to announce an event. A private dashboard sits behind a login and manages everything the public site reads.
- 01 · Events
- Title, date, venue, cover and body. Publishing one adds it to the archive, its filters and the stats.
- 02 · Media
- Event photography uploaded once and reused across pages.
- 03 · Messages
- Contact form submissions land in the dashboard, not a shared inbox.
- 04 · Users
- Committee members sign in to manage content. The public never sees the dashboard.
.webp&w=3840&q=75)
.webp&w=3840&q=75)
[ 05 · the inception 26 ]
The installation ceremony of the IEEE Student Branch and its chapters. The new committee is what the site is built for.
The people
behind it.
