Universal Components — Rebode's Design System

Every new Rebode property rebuilt the same header and footer. Four applications, four copies, four places to update every time anything changed. Nobody asked me to fix it — I documented the duplication, put a cost on it, and took it to leadership myself. That pitch became Universal Components.

I didn't start with code. I researched implementation routes and interviewed our lead developers and leadership before committing to one — a design system nobody adopts is just a very organized opinion.

Then I architected the whole thing: repo, scaffolding, Azure Artifacts, private NPM packages, automated version publishing and deployment pipelines. The pipeline work was some of the heaviest I did at Rebode — built hand in hand with our lead infra developer, and I wrote pipeline code myself, not just requirements.

A package nobody can install doesn't count. I documented the setup, trained every developer to consume private packages locally, and owned onboarding new contributors. Along the way I worked the header/footer redesign with the design team — what's live today is that work. With four properties, the duplicated work simply ended: build once, publish everywhere.

DUPLICATION ELIMINATED

~75%DUPLICATION ELIMINATED