New component

Create request → Describe your needs

→ We will work out it → Final review

Flow on the development side:

 

  • On the code side, make sure that none of the current organisms are suitable for solving the case (It is advisable to do this before starting a request for creating a new component)
  • It is necessary to synchronize with the DS team, perhaps the solution can be found at this stage (For example, it will be enough to add a new variation and modify what is already there).
  • If it turns out that the component is necessary, works it out within the case.
  • Then sends to the DS team branch, PR etc. , which reflect component functionality, checks consistency, tokens usage, finalize all the necessary states
  • Request review by the product & DS-Team
  • Add the component into product DS library or ask us to do that

Contact us in case of question

We are welcoming you to share with us any possible feedback or ask any question related to the product development process using Design-system! Feel fre to write me in DM - d.krikunov@mu.se.

In case of questions

These channels will help you to find an answer on any question somehow connected to the DS or around it. Please welcome with your ideas and problems here:

Channels:

#ug-design-system

#ug-design-system

#mu-design-system

#au-design-system

Your DS team

Dmitrii Krikunov

Design-system architect

d.krikunov@mu.se

Vitaliy Kapustyanov

Senior Designer

v.kapustyanov@mu.se

Alexander Komarov

Senior Frontend

a.komarov@mu.se

Azamat Dzebisov

Senior Frontend

a.dzebisov@mu.se

Peter Dorozhkin

Senior Frontend

p.dorozhkin@mu.se

Andrey Yakobchuk

Head of Frontend

a.yakobchuk@mu.se