How to Work on the Component Library

Welcome to freeCodeCamp’s ui library. The components are built mostly from scratch with basic HTML elements and Tailwind CSS.

The following steps are recommended when working on a new component:

• Research and planning
• Implement the component
• Display the use cases on Storybook
• Write unit tests

Researching and Planning

Before building or modifying a component, review the existing components in the ui library and document the behavior, appearance, and accessibility requirements for your use cases. Check which HTML elements and ARIA attributes are appropriate and how users will interact with the component using a keyboard. When modifying an existing component, inspect its current usages so that you can preserve the behavior and styles its consumers rely on.

Design the props interface around the component’s requirements and the patterns used by the ui library. For an existing component, consider how interface changes will affect its consumers. For a new component, use related ui components as references and expose the props its consumers need.

We prefer smaller pull requests rather than a large one, because they speed up the review time and reduce cognitive overload for the reviewers. For that reason, you should think about how you would break down the implementation and come up with a delivery plan.

We recommend opening a separate GitHub issue for each component and include all the notes in the issue description. It can be used as a place to host all of your working notes, as well as a way to communicate the approach with the reviewers. We will use the issue thread for further discussion if needed.

Implementing the Component

A new component can be created using the following command from the root directory:

pnpm run gen-component MyComponent

The command will generate a new folder inside the ui project, with the following files:

Each component is different, but in general, a component should:

• Support forwarding ref
• Be styled for both light and dark themes
• Be styled internally based on their props (the consumers should not need to restyle the component with the className prop)
• Utilize the built-in styling system from Tailwind instead of having custom styles

Using Colors

There are two color “layers” in the component library:

• The base layer, where the color names describe what the colors are, e.g. gray00, blue50
• The semantic layer, where the color names describe what the colors are for, e.g. foreground-primary, background-danger

Generally, when using colors in a component, you should choose semantic variables over the base ones. There are exceptions, however, specifically when you are styling the component’s states such as hover, active, disabled, etc. In these cases, we recommend using the base variables directly instead of creating new semantic variables, since each component can have different styles for its states.

Useful Links

• Tailwind CSS Configuration
• UI component implementations, stories, and tests

Displaying the Use Cases on Storybook

Use cases of the component should be added to the Storybook file (.stories.tsx).

To start Storybook, run the following command from the root directory:

pnpm run storybook

The Storybook page is available on http://localhost:6006.

Writing Unit Tests

We use React Testing Library to write unit tests. The tests should assert that the components behave as expected and are accessible.

To run tests against the component library, run the following command from the root directory:

pnpm run test

Proposing a Pull Request (PR)

After you’ve committed your changes, check here for how to open a Pull Request.

Adding Packages to the UI Library

We restrict adding new packages to the UI Library to help with the project’s maintainability. In the rare chance that you think a dependency is needed, please check with the maintainers first and then use the following command to add a package:

pnpm add package_name

Useful Links

• Testing for Accessibility
• Order of priority of React Testing Library’s queries
• Common mistakes with React Testing Library