Design systems
Colour and type as tokens declared once and read by the code, so the design file and the build use the same values.
Documented on every case study
ABOUT
Designing with clarity.
Building with care.
Product Designer & Frontend Engineer
I came to design through engineering. I spent my NYSC year building React applications at an agency, then a stretch of freelance frontend work, and I still design with the build in mind.
So I build what I design. When I write the components myself, the spacing, empty states and focus styles ship the way they were designed.
HOW I WORK
How I work.
Each one points to a case study where you can see it in the work.
Information architecture
Deciding what a product needs to say before how it looks. On Atelier I built the content model before designing any page.
AtelierAccessibility, checked not assumed
Contrast ratios calculated, alt text required in the CMS, and keyboard focus kept through page transitions.
Atelier, 1st BlessedDesigning for the actual reader
On a care home site read largely by people in their sixties and seventies, the base text size went from sixteen pixels to eighteen, and every size and gap in the system was measured against it.
1st BlessedContent models a client can use
CMS schemas clients publish from without a developer.
Atelier, 1st Blessed, JTAHFrontend engineering
Next.js, TypeScript and Tailwind, with tokens as custom properties, components small enough to read in one screen, and data fetched once at the top of a page rather than per component.
All five case studiesNEXT