⏤ Why this document?
The increasing complexity of digital products and cross-platform usage has become a major challenge for businesses where loss of growth and consistency is often the result. I note the emergence of the Design System as a solution to these problems of scalability.
⏤ For who ?
This document is the result of my learning about implementation of design systems at Qwant, Ekwateur and Anycommerce. As a designer in this type of company which has in common the fact of being very mature in the production and feature development processes it is important to be able to ensure consistency through design.
⏤ What ?
To keep in mind that is evoluting, use simple naming to implement your colors, fonts, sizing, shadow, radius, motion time, opacity...
⏤ But why ?
Primitives are useful to create the first structure with value as a point of reference to easly update brand system.
⏤ What ?
To structure your UI assets start by define the specific name of every element used on your system.
⏤ But why ?
Semantics link to primitive allows you to speak the same language, adapted to the use of your system as a point of consistency.
⏤ What ?
Build your component to create the system by using your semantic.
⏤ But why ?
To standardize the System and optimize the creation process with a rationalized approach.
⏤ What ?
Create only the page templates that you identify with redundancies in your use
⏤ But why ?
To standardize, guide and document the content pages.
Hope it was useful.
