LiveChat Design System

Installation

Run the following command using npm (or with you other favorite package manager, eg. yarn):

npm install @livechat/design-system-react-components @livechat/design-system-icons --save

Basic usage

It is required to import the CSS directly into your project so it could be applied to components:

import '@livechat/design-system-react-components/dist/style.css';

You can import components directly from the npm package:

import { Button } from '@livechat/design-system-react-components';

In case of icons there is a separate package to be used in conjunction:

import { Edit } from '@livechat/design-system-icons/react/tabler';
import { Icon } from '@livechat/design-system-react-components';

<Icon source={Edit} kind="primary" />;

Documentation

At this stage of the project we consider Storybook and Figma as parts of our documentation ecosystem.

Storybook - includes design system foundations, describes components API and allows to familiarize with the thier capabilities Figma - it's not an official documentation from design perspective but we follow a simple rule of working in public

Contributing

Design System is mainly maintained by the teams of:

Livechat

HelpDesk

KnowledgeBase

Any external contribution is welcome and teams mentioned above will help in the process of development or reporting problems or ideas. Design system is a proposed solution for authors building application targeting LiveChat Marketplace, therefore, we're open for any feedback from 3rd party developers.

Rules of contribution

In order to start working on changes, you must first create an issue on our board, using one of the templates depending on if this is a feature request or bug report here. If an issue turns out to be related to another which is already on the board, the DS team will take care of the appropriate connections. In addition to the description, the ticket should also contain an appropriate label, the contributor should be entered as an assignee, and should be added to the project (LiveChat Design System).
In order to start work, first update branch main, and then create a new branch from this branch in which future changes will be placed. We adopted the nomenclature for the branch feature/[task_id].
If changes require it, appropriate unit tests should also be included, and an additional case should be attached to the Storybook documentation (in the .stories.tsx file).
After the work is completed, create a pull request directed to branch main.
1. Conventional PR Naming: Ensure your pull request title follows the Conventional Commits naming pattern type(scope): description. This is crucial as, post squash merging, Git will use the PR name as the commit message.
  To mark changes as a breaking change, include a ! after the type and scope, followed by a colon and a space, like so: type(scope)!: description.
  For now we will use the following types:
  - feat - for new features
  - fix - for bug fixes
  - docs - for documentation changes
2. Review: In pull request, you should call livechat/design-system in the reviewers field.
3. Template: The merge template contains a checklist of things that need to be completed to meet the requirements, it will make the work easier for everyone.
You will probably notice in your pull request under "Some checks haven't completed yet" Chromatic pending checks approval. Chromatic is a tool that we use for visual regression testing. The check in this tool is required for general approval of changes and it's covered by design system team.
After the work is completed and the reviewers accept it, the responsibility for the rest of the changes is on the design system team side, which will perform the merge and release the changes in the future. Design system team deals with determining the status of the task on the board side, they close it with an appropriate comment.

Development

Required version of node.js is 16.13.2.

If you're a volta user, the project maintains node version entry within package.json.

You should start with installing dependencies:

npm install

After that just execute the start command. It will build all necessary packages in watch mode. Storybook should start automatically (if not - try visiting http://localhost:6006).

npm start

If Storybook is not enough, you can additionaly run npm start:example which will run example-react package in watch mode. example-react is a simple React app based on vite-react boilterplate. It has a direct dependency on react-components package, so every change should be reflected in the app via auto-reload.

Testing

We have prepared a document describing testing process and core principles in the area of quality here.

Releasing

The package releasing and related documentation is available here.

livechat / design-system