± Fundamentals, Scenario-Driven and Vue

May 2, 2019

Design System Fundamentals via https://medium.com/microsoft-design/design-system-fundamentals-3ff6a4c98c43

That’s the general process. It’s really iterative. It really is hypothesis-driven, and we use data from shipping products and feedback to help us move forward. We do that internally, day to day, in designing and planning with partner teams around the company, and we do it externally through our feedback avenues.

A design system is iterative. It’s organic.

An Event Apart: Scenario-Driven Design Systems

In her Scenario-Driven Design Systems presentation at An Event Apart in Seattle, Yesenia Perez-Cruz shared lessons learned building design systems for multiple brands/Web sites and how specific user-scenarios are key to making flexible solutions.

Design Systems are not Legos.

Microsoft Introducing Fluent Design System

I would highly suggest you to visit Fluent Design System site. It’s packed with information about their universal design for the next evolution. Walking you through its different elements from: Sensory Experiences, Co-Creation, The Building Blocks, Light, Depth, Motion, Material and Scale.

Now’s the time for bold, scalable, universal design. This is a transformation. A step into the future of sensory experiences. The world is at our fingertips – join Microsoft in building a design evolution.

Vue Design System

Viljami lists Design Principles, Tokens, Elements, Patterns, and Templates as the way in which he structures a system and I think it’s a pretty interesting approach.

And love the Design Principles: https://github.com/viljamis/vue-design-system/blob/master/docs/principles.md

1. Design is how it works
2. Reduce concepts to increase confidence
3. Design with real data
4. Design systems, not pages
5. Involve code early
6. Fast is better than slow
7. Let content determine breakpoints
8. Strive for universality

Balancing Flexibility and Consistency in Design Systems

Strictly enforcing consistency might not result in the best experience for the end users and would certainly hurt adoption of the system.