Design-Systems-Resources icon indicating copy to clipboard operation
Design-Systems-Resources copied to clipboard

Design-Systems-Resources

Books / Guides

Lone Writers Guide

This is a great resource for writing documentation, which is very important in any design system.


Sites


Presentations

Design Systems and Front-End Architecture

The Future of Design Systems

  • Haley Hughes (Airbnb)

Tools


Articles

Overviews

The Full Stack Design System

In each case, the objects don’t just describe a UI widget. They mean something very specific in the context of the product.

The myth that design systems solve easy problems

Design systems fix the common problems, not the easy ones

Distilling How We Think About Design Systems

Don’t get trapped in defining things instead of explaining things. Sarah Federman

What I learned about leading a design system in 2017

Of all the investments and effort we put into improving our documentation site, our biggest success this year came from the time we put into the UI kit we created for Sketch.

What I learned about leading a design system in 2018

Implementing Spectrum: How Adobe is Coming Together to Build a New Design System

Introducing Spectrum: How Adobe Is Building a Design System at Scale

How To Make Design Systems Work

design systems should be like the ship of Theseus — as their components change and are replaced, they should fundamentally remain the same vessel with the same purpose.

The ABCs of Design Systems

Your design systems ability to bridge gaps between disciplines is a superpower

Think like a chef: how to use a design system

The components act as your ingredients, while the patterns and guides act as your recipes.

Reimagining Design Systems at Spotify

This time, we wanted to design our design system, just like we’d design one of our product experiences. We weren’t starting with a completely blank slate, though. We wanted to consolidate the resources we had, and create a system that felt unified, accessible, collaborative, and based on a coherent vision. Most importantly, we wanted a system that would fit with Spotify’s culture of autonomy—one that could scale across multiple platforms and use cases.

State of Design Systems 2019

Design systems are not just an embodiment of aesthetics and brand identity, they represent an organization’s workflow and processes.


Process

Systems Thinking, Unlocked: Building an inclusive design language system

When creating a sustainable culture, your design system is only as strong as your relationships with the teams who use it.

Practicing Design Systems

This article is great for the early stages of design system development. It includes a great activity to get everyone on the same page with the priority of high-level user stories such as "As an adopter, how do I get updates".

Starting a Design System

A good design system should be a collection of your organization’s best institutional knowledge.

An illustrated pseudo-scientific approach to design system principles

Having product principles to help guide individual and team decision making meaningfully improves our collective product process.

What makes a good design principle

Good design principles are memorable. Good design principles help you say no. Good design principles aren’t truisms. Good design principles are applicable.

Art of Diplomacy

At the end of the day, the system is an internal tool and our coworkers are its users. Their human, just like us, and they want to do a good job, just like us. By empathizing, reassuring, educating, remaining flexible, sharing, communicating, and staying positive we’ve overcome many hurdles and are excited to take on new challenges in the future.

Design Quality Components

A quality component feels like the company and works as intended every time for all users — a crafted balance of brand essence and science.

Pairing is the key to evangelizing your design system

But it turns out a design system can't be perfected in solitude because it's rooted in human relationships. It serves as a mirror for the company, a reflection of the dynamics at play between designers, engineers, product managers and even customers.

Size in Design Systems

Stability in Design Systems

Reduce the distance between your documentation and code. By co-locating documentation and code, it’s more likely that you’ll remember to update the documentation when a component changes.

Tracking Polaris

Barriers to involvement are often invisible The more complex an organization gets, the more we need to lean on a system to enable competent, cohesive decisions

Sustainable Design Systems | decoupling purpose from outputs

If you try to over-optimize for UI consistency, you’ll end up with a system that is too rigid or can’t adapt to consumer needs. If you over-emphasize development speed, you’ll likely sacrifice quality. Instead, we should optimize for resilience and adaptability. Alan B Smith

A Design System Governance Process

Product teams’ primary concern is getting work out the door, not to uphold the integrity of the design system.


Documentation

How we built a component library that people actually enjoy using

Great documentation should be less like a document and more like a workshop.

Myths of Documenting Components

The most important thing I’ve learned about writing doc is to always be writing doc. Don’t trigger it by a step in the process. Instead, start a living document that grows as you research, design, code and complete a system feature.

  • Adam Rowe, Morningstar Design System

Authoring Component Documentation

There’s always more stories to tell, more scenarios to exhibit, more guidelines you could write. Some of them are important. But maybe not as much as other things you could do. And that’s ok. Don’t get anxious about it. Your end goal isn’t doc, it’s end-customer experience quality and speed-to-market.

7 tips for starting writing and maintaining your documentation

Update when someone asks you a question — this is probably my biggest piece of advice on the topic of documentation.

Handling example copy in design systems

In the GOV.UK Design System, which I work on, we use realistic copy in most of our examples. We’ve found it helps to give our users an idea of how something works in context and shows, at least implicitly, what good copy looks like.

Readme driven development


Tokens / Theming / Styles

Tokens in Design Systems

The Themes Are Always Changing But The Tokens Stay The Same

Themeable Design Systems

Getting design system customization just right

Guided theme building allows your components to be themed to a degree that allows third parties to use them to create their own product, with its own look and feel, but removes the risk of people over-customizing them.

How Fluent UI Unlocks the Next Generation of Microsoft 365 Experiences

Centralized style libraries, accessible by both design and development tools, will serve as the place to make updates without having to revise coded components.


Colors

Re-approaching Color

Colors at scale

Adaptive Color in Design Systems

Introducing Adaptive Color Palettes

Adaptive Color in Spectrum, Adobe’s Design System

Polishing Gitlab's UI: A New Color System

Designing Systematic Colors

Colors at scale: Redefining SE Suite UI’s Color Palette

Because, colors are beautiful

Designing accessible color systems

When designing an accessible color system, using a perceptually uniform color model (like CIELAB) helped us understand how each color appears to our eyes as opposed to how it appears to a computer.


Animation

Including Animation In Your Design System

The most effective design systems contain a branded point of view unique to them — things that make their design system more specific to the product they’re for — along with common design best practices.

Integrating Animation Into a Design System


Adoption

Driving design system adoption

... since launch, we’ve found that our early adopters highly value our documentation as a single source of truth.

Measuring the impact of a design system

The reason for introducing a design system in a company is not because so people can work less, but because so people can work better. I want people to focus on the important things, and reduce the amount of repetitive work they do.


Research

Maintaining design systems with user research

Even though there is plenty of design systems by other companies, they all address certain business needs which most likely differ from ours.


Naming

How to name UI components

Good names help team members who did not design or build the patterns understand their use. Good names help onboard new hires faster. Good names are memorable.


Versioning / Releasing

Versioning Design Systems


Content

Why your design system should include content

When copy components work — and when they fail

Use all your powers to give your offsite / unsupported teams every conceivable resource and tool they’ll need to help themselves. You can never guarantee that their copy will be wonderful, but at least you’re helping establish some kind of baseline. Unremarkable functional copy is always better than utterly fucked copy.

Content in, for, and of Design Systems


Technology

managing technology-agnostic design systems

Creating a technology dependency in order to achieve a specific UI style inherently limits where that UI can go.


Components

Component API Design Guidelines


Unorganized

Articles