A UI library that had to work in any framework

Haiilo is an employee engagement platform built around knowledge sharing. They wanted to improve their UI and UX across a product surface owned by several different teams — which meant the shared component layer had to stop being framework-specific.

What I built

I developed and maintained the core UI components library: a framework-agnostic design system built on Stencil, Web Components and SCSS. Framework-agnostic was the requirement, not a preference — the components had to drop into whatever each product team was already using.

Getting teams to agree

I worked closely with multiple product teams to align component behaviour and drive adoption. Most of that work was not code. It was reaching agreement on what a component should do when teams had each solved the same problem slightly differently, and then picking one answer.

Accessibility

I implemented accessibility standards — A11y, WCAG and ADA — as a business requirement, not a nice-to-have. Building it into the shared library meant every product team inherited it instead of each one re-solving it, badly, later.

This was a part-time engagement running alongside my main role.