ZarfToken
I was one of six people building ZarfToken, a MERN platform that centralizes event discovery, approval, QR registration, and participation data for the GUC community.
Context
The platform brings campus trips, company visits, community activities, and technical events into one role-based experience for students, faculty, vendors, and administrators.
Product Scope
Platform features
- Centralised event creation and approval workflows
- QR-based registration for events
- Real-time synchronisation of event and participation data
- Role-based authentication across student, faculty, vendor, and admin roles
Completed Work
Event platform, built on MERN
A full-stack event management system covering discovery, registration, approval workflows, and real-time participation insights for a university community.
- Built with
- React, MongoDB, Express, Node.js, RESTful APIs
- Contribution
- One of six team members, working mainly across the platform's React components and API layer.
- Outcome
- Live at zarf-token.vercel.app, covering 80+ tracked requirements across 5+ user roles.
Technical Stack
Technical skills
React, MongoDB, REST API design, Role-based authentication
Tools and platforms
MERN stack, Vercel
Working style
Team-based delivery, Requirements management
Summary
- Requirements implemented
- 80+
- User roles supported
- 5+
- Team size
- 6
- Live deployment
- zarf-token.vercel.app
Looking back
- With six of us and more than 80 requirements to track, the hard part wasn't writing the code. It was making sure everyone knew what they owned and in what order things needed to land.
- Once we had five different user roles to support, role-based access control wasn't something we could bolt on later. It had to be part of the design from day one.