Build a Company Design System - Course Introduction

Which technologies we will be using in this course

Build a Company Design System - Course Overview

What are Design Systems and Why are They so Popular?

How to think of design systems and model them appropriately

Pace Layering and Atomic Design System Mental Models

How to convert a Figma file to requirements

How to Turn a Figma Design System Into Code

Introduction

Module 2 Introduction

How to structure a design system monorepo

How to Structure a Design System Monorepo

Using yarn workspace to create a monorepo

Using Yarn Workspaces to Create a Monorepo

How to Build a Dynamic Design System With TypeScript

Create ESLint and Prettier Configs for a Design System

Design System Monorepo

Module 3 Introduction

How to Work With and Structure Design Tokens

Transforming raw design tokens with Style Dictionary

A Guide to Transforming Design Tokens with Style Dictionary

Creating a Tailwind CSS preset with JavaScript design tokens

Creating Tailwind CSS Presets With Design Tokens

Using `tsc` to build the foundation package

Building the foundation

Foundation package

Module 4 Introduction

Setting up the react component library package

Setting Up A React Component Library for Design Systems

How to Write React Components for a Company Design System

React package

Module 5 Introduction

Developing the component library with Storybook

Setting Up Storybook for Company Design Systems

Using Storybook to document our component library

Creating Your First Stories in Storybook

Storybook controls and Accessibility addon panel

Controls and A11y testing

Storybook package

Module 6 Introduction

Styling React components with JavaScript design tokens

How to Style React Components With Design Tokens

Styling React components with Tailwind CSS preset

How to Use Tailwind CSS With JavaScript Design Tokens

Styling components

Module 7 Introduction

Using React Testing Lirary to test React components

React Testing Library - Install and Write Your First Test

Finding accessibility issues using AXE with Jest

Using jest-axe to Find Accessibility Issues in React Components

What is Visual Testing and How Does it Work?

Testing components

Module 8 Introduction

What are Changesets and How Do They Manage Versioning?

How to test & publish our packages from CI (Github Actions)

How to Setup a CI/CD Pipeline in GitHub Actions

CI, Changelogs and Publishing

Thank you 🙏

Summary

In this course, we will dive into the world of design systems. We will learn how they can help developers increase their productivity, create consistency across a company's products, and ultimately speed up the development process.

We will start by covering the fundamental concepts of design systems, then move on to the architecture of a monorepo codebase. We will set up shared configurations for TypeScript, ESLint, and Prettier, and create a foundation package for hosting and distributing design tokens and assets.

Next, we will create a React package with demo components that are styled using our design system's style tokens. We will also create a Storybook package and learn the best practices for developing and documenting components with TypeScript. We will focus on styling our components in two ways: using CSS-in-JS with styled-components and JavaScript design tokens, as well as Tailwind CSS classes.

Finally, we will learn how to create tests for our React components using React Testing Library and AXE, and manage releases using changesets and set up a CI pipeline with GitHub Actions.

This course aims to be a comprehensive guide, or a cookbook, to building a complete company design system from scratch. By the end of the course, you will have the knowledge and skills to create a practical and maintainable design system for any organization.

This course is a comprehensive guide to publishing your first component library and design assets using React, TypeScript, Storybook, Tailwind CSS, and Styled Dictionary. You’ll create a flexible, enterprise-grade design system library that your co-workers will actually enjoy.

Build a Complete Company Design System

Transform design tokens with Style Dictionary.

Manage an enterprise design system monorepo with Yarn workspaces.

How a simple monorepo works with Yarn workspaces

What design tokens are, and how to generate them with Styled-Dictionary

Automate testing for accessibility issues (Axe) and visual changes (Chromatic)

Develop and document our design system with Storybook

How to publish with Github Actions and Changesets

How to provide a Tailwind configuration for other teams

, it is a tool that helps you to enforce a consistent style in your code and can quickly pinpoint problems that we may miss.

It helps greatly in large teams, because it speeds up review time and comments, so instead of a reviewer telling you something about the code styling, the linter will help you solve this even before pushing the code to the git repository.

We know at least two packages will use React (

 config that will enforce the best practices for React, JS and TypeScript. To do this, let's create a 

 file in the root of the project and paste the following code inside:

module.exports = {
  extends: [
    'eslint:recommended',
    'plugin:react/recommended',
    'plugin:@typescript-eslint/recommended',
    'plugin:react-hooks/recommended',
    'plugin:jsx-a11y/recommended',
    'plugin:prettier/recommended',
  ],
  parser: '@typescript-eslint/parser',
  plugins: ['react', 'jsx-a11y', '@typescript-eslint'],
  rules: {
    'react/jsx-curly-brace-presence': 'error',
    'react/jsx-uses-react': 'off',
    'react/react-in-jsx-scope': 'off',
  },
};

The configuration is quite simple, as we extend what is recommended by ESLint folks with 

 packages. ​​We further extend the rules with accessibility rules from 

​ which helps us pinpoint accessibility issues beforehand. Finally we use 

​ which adds prettier's style guidlines as eslint rules so all prettier issues show as eslint warnings/errors.

, in the root of the project and pasting the following code inside:

{
  "printWidth": 80,
  "singleQuote": true
}

It's really minimal, but this will do the job. Prettier will help us format the code programmatically, so we avoid inconsistencies between developers.

---
title: Create ESLint and Prettier Configs for a Design System
privateVideoUrl: https://fullstack.wistia.com/medias/53acwth90s
---

## ESLint and Prettier configs

### ESLint config

Let's continue the config journey with [`ESLint`](https://eslint.org/). If you are not familiar with **ESLint**, it is a tool that helps you to enforce a consistent style in your code and can quickly pinpoint problems that we may miss.

It helps greatly in large teams, because it speeds up review time and comments, so instead of a reviewer telling you something about the code styling, the linter will help you solve this even before pushing the code to the git repository.

We know at least two packages will use React (`react` and `storybook`), so let's create an **ESLint** config that will enforce the best practices for React, JS and TypeScript. To do this, let's create a `.eslintrc.js` file in the root of the project and paste the following code inside:

```js
module.exports = {
  extends: [
    'eslint:recommended',
    'plugin:react/recommended',
    'plugin:@typescript-eslint/recommended',
    'plugin:react-hooks/recommended',
    'plugin:jsx-a11y/recommended',
    'plugin:prettier/recommended',
  ],
  parser: '@typescript-eslint/parser',
  plugins: ['react', 'jsx-a11y', '@typescript-eslint'],
  rules: {
    'react/jsx-curly-brace-presence': 'error',
    'react/jsx-uses-react': 'off',
    'react/react-in-jsx-scope': 'off',
  },
};
```

The configuration is quite simple, as we extend what is recommended by ESLint folks with `eslint:recommended`, then the rules recommended for `react` packages. ​​We further extend the rules with accessibility rules from `plugin:jsx-a11y/recommended`​ which helps us pinpoint accessibility issues beforehand. Finally we use `plugin:prettier/recommended`​ which adds prettier's style guidlines as eslint rules so all prettier issues show as eslint warnings/errors.

### Prettier config

Let's now create the [prettier config](https://prettier.io/) by creating a file, `.prettierrc`, in the root of the project and pasting the following code inside: