PARCEL Design System
Manutan
Context
Manutan had a Figma UI Kit, but the gap between design and development was significant, and no multi-brand consistency existed. The replatforming project created the opportunity to rebuild everything from scratch, with a shared language as the true north.
0 → 1
built from scratch
0 → 1
built from scratch
Challenge
Three problems to solve simultaneously: closing the gap between design and dev outputs, establishing a shared token-based language across teams, and ensuring consistency across Manutan's multiple brands, all while the replatforming was already in motion.
Approach
We built PARCEL from the ground up: tokenized foundations (color, typography, spacing, brand themes), structured Figma libraries, and documentation in Supernova. The name? Voted by the team. A small detail that says a lot about how we worked.
137
components delivered
137
components delivered
Adoption
We introduced dedicated rituals: separate syncs for designers and developers, with a shared review cadence to ensure every component was adopted, understood, and maintained on both sides. Design and engineering finally spoke the same language.
7 + 20
designers & devs aligned
7 + 20
designers & devs aligned
Designer
Supernova
Developer
Storybook
Outcome
Before PARCEL: a UI Kit living in isolation. After: a design system embedded in the front-end's daily workflow. More than a deliverable, a shift in how design and development collaborate at Manutan.