Skip to content

otto-de/b2b-design-system

Folders and files

NameName
Last commit message
Last commit date

Latest commit

0d63984 · Feb 27, 2025
Jan 30, 2025
Apr 25, 2023
Aug 24, 2023
Nov 29, 2023
Feb 27, 2025
Jun 12, 2023
Oct 26, 2023
Apr 25, 2023
Aug 21, 2023
Apr 25, 2023
Apr 25, 2023
Apr 25, 2023
Feb 27, 2025
Dec 27, 2024
Jun 14, 2024
Oct 26, 2023
Apr 5, 2023
Jan 3, 2025
Dec 27, 2024
Jan 3, 2025
Apr 25, 2023
Oct 9, 2024
Feb 25, 2025
Jan 24, 2025
Jun 13, 2023
Jan 24, 2025
Jul 11, 2024
Jan 24, 2025
Apr 25, 2023
Apr 25, 2023

Repository files navigation

OTTO B2B DESIGN SYSTEM

OSS Lifecycle

About

The B2B Design System is the library of components used to build the Otto Marketplace. The goal of the B2B Design System is to provide frontend components that encapsulate styles and behaviour for teams to use out of the box.

We wish to support different frontend frameworks and for this goal we are building this solution using Web Components with Stencil.

You can find our documentation in this link.

Why open source?

The design system currently supports only the Otto Marketplace branding. But this can be easily configured by changing our design tokens. The main purpose for publishing our system is to become a source of inspiration for other teams creating similar products using Web Components.

The system is actively maintained and our main contributors are our Otto Marketplace teams.

Overview

This project is a monorepo that makes use of npm workspaces containing the source code of the 3 packages we distribute:

@otto-de/b2b-core-components

b2b-core-components - Core web components, can be used with Vue.

@otto-de/b2b-react-components

b2b-react-components - React wrapper library, exposes first class React components. Wrapper is created by Stencil.

@otto-de/b2b-tokens

b2b-tokens - These are atomic design decisions that can be used to centrally change the styles of our components. For more information about Design Tokens read here.

Development and Contributions

To start developing please follow the dev-guidelines to learn more about the tools we use and how to commit.

If you want to contribute by developing a component or fixing a bug, our dev-guidelines provide you with insights on how to develop and test a new component, add tokens, write documentation and create visual regression tests. You can refer to this checklist to make sure you've got everything covered. Once you're happy with your work, you can submit a Pull Request.

You can always open a discussion or issue if you have any improvement or suggestions.