As a developer working on a design system, you're responsible for extracting design specifications from design files and translating them into code. If that code cannot scale across all the applications that are consuming the design system, or that will consume the design system in the future, the company suffers.
You can easily get stuck building very narrow tools, like a React component library without a firm foundation. Because a React component library is great, but it can be costly if you do it too soon. At any company, applications can vary by platform (i.e. web) and technology (i.e. React). If all you have is a React component library, as soon as you introduce an application with a different technology (i.e. Vue), then you have to find a way to share the design specifications between the React component library and the Vue component library. So, you might create a CSS-in-JS library that can encapsulate the design specifications and be consumed by the React and Vue component libraries respectively.
But, what happens when a request arises for an encapsulation of the design specifications in a way that would work for a plain HTML site Well, you could move the encapsulation of the design specifications from a CSS-in-JS library to a plain CSS file. However, that limits the React and Vue developers from using their preferred technologies, and that breaks down when a non-web application is introduced (i.e. an Android mobile app). Usually what happens is that the React and Vue developers would carry along with a CSS-in-JS library and the plain HTML developers carry along with a plain CSS file. The issue is that you have your design specifications represented in code in multiple places. You can no longer know which one is the "source of truth." You generate an increased risk that the various applications in a company are out of sync with the official design system and with each other.
At the end of the day, you need to represent your design specifications in code in a single place. From that single "source of truth," you can then generate the platform deliverables (i.e. CSS variables, JS modules, etc.) What you don't want to do is to create platform deliverables without a single source of truth, without a mechanism to keep all the consumers of those deliverables in sync with the design system and one another.
It turns out that many companies have been looking into these problems including Shopify, Adobe, Discovery Education, Morningstar, Orbit, Salesforce, Bloomberg, and more.
The solution is creating design tokens and managing a style dictionary.
Design Systems for Developers is a deep dive into the need for design tokens, an explanation of them, and practical solutions for using them to launch design system tools into production.
Moreover, I emphasize the fact that tools and automation are only useful if good communication is happening between designers and developers in the first place.
In this book, you'll not only learn the technical skills that go into building design system tools for production, but also the soft skills required for collaboration between designers and developers.
Whether you're a designer or a developer, this book is for you.
I trust that after reading this book, developers will be able to work on a design system for any company, regardless of the number of applications and the platform and technologies that those applications are geared for.
I also trust that designers will have a better understanding of their role in collaborating with developers to create a robust design system.
In this book, we'll outline the problems associated with creating tools, like a React UI component library, to encapsulate the styles of a design system, such as the inflexibility of scaling when new applications arise targeting a different platform and tech stack.
From there, we go over how these problems may be solved by creating design tokens, representations of design specifications in code, and style dictionaries, a central management system for storing design tokens and transfog them into platform deliverables.
We'll write some code, discuss different approaches, and cover the very practical details, like how to schedule meetings to collaborate with designers.
Table of Contents
1 - The Mission
2 - The Problem
3 - Introducing Design Tokens
4 - Introducing Style Dictionaries
5 - Extracting Design Tokens
6 - Naming Design Tokens
7 - Valuing Design Tokens
8 - Storing and Transfog Design Tokens
9 - Delivering Design Tokens
10 - Creating Tools and Assets From Design Tokens
11 - Ideas for Real-World Collaboration
12 - The Conclusion



DOWNLOAD
uploadgig.com


rapidgator.net


nitro.download