Nicolas Muha

I have a seriously wide and fundamental knowledge and experience specifically in the design systems. 

I created and rebuild my own project by implementing a design system to it. 

It took me 10 months and includes a lot of stages:

• Defining necessary groups of elements components and also unnecessary ones;

• Collecting together all kinds of possible components and it's sorting. For defining which parent master components will be created and how it would be better to create in terms of reusability, universal scalability and etc.;

• Building fundamental principles of behaviour of a product's design:

    • Spacing values and principles;

    • Typography basics, molecules, and organisms;

    • Color conventions. Including main colors, its secondary color shades, a system of the grey functional pallet;

    • Developing grid systems for any kind of breakpoints, for any possible layouts, that products can use;

    • Developing a base of Ui containers and their headers;

• Work on cleaning and merging similar atoms, components, and organisms;

• Creating a separation "sectors" for an existing design massive ( Products, Fundamentals, Data display, navigation, Swichers, List items, Data entry, Unsorted folder, For future ( it's about a bunch of hard references for other huge design team's solutions to get inspired and learn from ), Luggage ( some kind of internal design system for my design system (sorry for tautology)) );

• View mentions about direct creating components:

    • First of all we are talking about scalable interfaces. It is all about 100% auto-layout built components;

    • Secondly - each component ( doesn't matter if it is atomic, molecular, or organism size ) has an unlimited necessary bunch of customisable variants. In terms of sizes, colors, states, 

    • I created a "template" that allows me to create any size of variants for each component. (Simplest example explains this is 500 or more variants sets of variants for button components without any disappointments and brain pains );

    • Design system built-in explainers for unusual solutions for other designers. (Use cases, principles, mentions, explainers "How to use" ); Other words - Documentation footnotes.

    • Also a very exclusive thing on board is innovative tips about multi-level used design system "constructor" components. Which is really amazing and innovative ( For me at least. ); 

• Next step is integration and testing. Actually, this topic is about rebuilding any existing user interface from a clean 1280s frame using only design system components. 

• Testing each solution in terms of scaling behavior, the ds component's workability, and other possible tests.

I'm sure it's impossible to mention everything.

8 years of product design

Bachelor degree. Economical sector