Buildora — Alumni Portal + Hackathon & Event Hosting Platform for Sister Nivedita University
Buildora is a web platform designed for Sister Nivedita University under Techno India Group to run two high-friction institutional workflows in one place: 1. an Alumni portal with verified registration and structured data capture, and 2. a hackathon / event competition hosting system that handles participant onboarding, team formation, submissions, and completion states without spreadsheets or chaotic coordination. The core UX goal wasn’t “nice UI.” It was operational reliability: reduce drop-offs, prevent incomplete submissions, and make the process idiot-proof for both participants and admins.
Alumni Registration That Doesn’t Feel Like a Government Form
Alumni portals usually fail because they ask too much too early and feel bureaucratic. This flow is designed to be structured but not suffocating: name, email, contact number, enrollment number, attendance confirmation, dietary preference — and then a clear CTA to verify via OTP.
Verification-first to reduce junk data
OTP-based verification is built into the flow so the database doesn’t fill up with fake entries and the university can trust contactability. The UI messaging is clear about what’s happening and what the user should do next (which is where most OTP flows fail).
Minimal friction, maximum usability
The form layout is clean, grouped logically, and avoids visual clutter. This matters because alumni registration is not a “delight” moment — it’s a task. The job is to get it done fast without confusion.
Product-Grade Authentication + Verification Flow
The onboarding system supports quick entry with email plus OAuth options (Google/GitHub). After sign-in, the verification step is designed to be unmissable: large OTP input boxes, resend timer, and clear fallback instructions. This reduces drop-off at the exact point most platforms lose users.
Designed to prevent abandonment
You’ll notice the UX decisions are defensive: clear microcopy, visible resend timing, and a back option. The design assumes users are impatient and distracted — so it keeps the path obvious and forgiving.
Hackathon & Event Engine Built for Real Submission Workflows
The event flow (example shown: Hack4Bengal Season 4 inside the platform) is structured as a multi-step guided journey with completion visibility. It covers: • Participant info capture • Team formation (Create / Join with invite code) • Project details (description, repo link, live/demo link, demo video) • Track selection + tech stack tagging • Submission guidelines acknowledgment + final submit • A completion confirmation screen after successful submission This turns “event operations” into a repeatable system instead of ad-hoc admin work.
