Making the answer reusable.
Design-system work at Learning Equality was not about producing components; it was about reducing the number of product decisions each new Kolibri feature had to reinvent — under constraints most design systems never meet.
The constraint set
Kolibri runs in learning environments with old devices, small screens, shared computers, unreliable connections, multilingual content and Arabic RTL interfaces. A pattern that assumes fast networks or modern hardware fails quietly in exactly the places the product exists to serve. The design system had to encode those constraints so individual features did not have to rediscover them.
Scroll the frame sideways to read the full width.
One pattern, traced end to end
The clearest way to show the work is to follow one pattern through the system. A status pattern begins as a specification: what loading, success, warning and failure mean, how each state is announced to assistive technology, and how it behaves when a long-running task outlives its connection. Those states then carry into the products — the same status behaviour appears in the content-import workflow’s long-running downloads and in the coach dashboard’s progress surfaces, so an educator learns the vocabulary once.
The same discipline applied to tables, cards, grids, loaders, sidepanels and modal behaviour: reusable answers to recurring interaction problems, specified with accessibility, multilingual and RTL behaviour as part of the pattern rather than a final-pass correction.
Scroll the frame sideways to read the full width.
Status and boundary
Designed during my Learning Equality tenure, Aug 2022 to May 2026, as shared infrastructure for the Kolibri product family. The measured outcomes attached to this period — the usability-testing results for content import — are reported in that case study, not re-attributed to the design system.
