As the educative team grew rapidly, it became really important to maintian styling consistency across the product. We needed a design language to guide our developers, designers, marketing team and the seniority to put in their collective efforts in a much more systematic and orderly way.

The initial idea to have a collection of reusable components was already implemented in 2018 but as the time went on, new developers and designers became a part of the team and started shaping the product in their own ways - this caused a lot of inconsistency. There, the need for clear principles and set rules had become imperative. As a result we explored our options and came up to the idea of implementing an atomic design system - breaking down complex UI components to their basic building blocks and then building back up.