Wevise
Led the creation of Wevise's first design system, building the foundations, 290 components, and the documentation that let a small team design and ship faster together.
Context
Wevise is a nonprofit that connects people breaking into tech with mentors who've walked the same path. As the product grew, every screen had started to look and behave a little differently. Without a shared design language, each new page took longer to build and was harder to maintain, and the experience felt fragmented to the people using it.
Role
Led the design system end to end, working with designers, engineers, and PMs, and getting buy-in from the CEO, CTO, and Director of Product. I built it on Material Design and MUI so it would map cleanly to what engineering was already using, then ran regular workshops to keep everyone aligned as it grew. V1 shipped in Figma, React, and Storybook, built for responsiveness and accessibility.
The opportunity
A volunteer team doesn't have time to reinvent a button on every project. The goal was to give designers and developers one place to start, so their energy could go into the mentorship experience itself instead of rebuilding the basics.
The homepage before the system, where every section had its own style.
The homepage before the system, where every section had its own style.
The guide covering naming, accessibility, and a build checklist for every new component.
Colours flow from raw values to semantic roles to components
Buttons across every state, size, and variant
Selection controls, built to stay accessible in every state.
Text fields, from single line to multiline and dropdown