100daysofcode - Day78
Hello folks, a new day is here and a lot of informations and knowledge are required to wrap this day in an amazing way. Yesterday we finished talking about Human computer interaction and its key role in the user experience journey. Today we will discover the design systems and their role in the UI/UX journey.
What is a design system ?
- A design system is a documented catalog of components and styles used within a product, including how and why each should be implemented . While design systems are often confused with style guides and pattern libraries, a design system is more strategic and high-reaching.
Why Use a Design System?
- Design (and development) work can be created and replicated quickly and at scale.
- It alleviates strain on design resources to focus on larger, more complex problems.
- It creates a unified language within and between cross-functional teams.
- It creates visual consistency across products, channels, and (potentially siloed) departments.
- It can serve as an educational tool and reference for junior-level designers and content contributors.
Why Not Use a Design System?
- Creating and maintaining a design system is a time-intensive activity which requires a dedicated team.
- It takes time to teach others how to use the design system.
- There may be a perception that projects are static, one-off creations, which generally don’t require reusable components.
Elements of a Design System
- Design-System Repository
- The people who manage it
Stay tuned, for tomorrow post where we will talk about the elements of the design system in deep details expanding each of them