Coop Design System

Why use CDS

CDS helps teams design and build digital products with the same building blocks. Instead of solving spacing, colour, accessibility, and component behaviour again in every team, those decisions are defined once and reused. That means teams can move faster, work more consistently, and spend less time translating between design and code.

What CDS helps with

  • Build faster with reusable tokens and components
  • Create more consistent experiences across products and platforms
  • Improve accessibility by using patterns that are already reviewed and tested
  • Make collaboration between design and development easier through shared building blocks

What you get with CDS

CDS gives Coop a shared set of tokens, components, and usage guidelines for web and native products.

Designers use the same tokens and components in Figma that developers use in code. That shared structure reduces unnecessary interpretation, makes onboarding easier, and helps teams work in a more predictable way.

CDS sits between brand and product delivery. It turns visual and interaction principles into reusable building blocks that teams can apply in their own products.

How CDS is managed

The CDS team maintains the shared system: tokens, components, and documentation. They decide what is included in CDS, manage updates, and plan releases.

Product teams use CDS in their own products and can extend locally when needed. Product-specific logic, flows, and decisions stay with the product team.

Want to suggest a new component or request a change? Use the CDS contribution process: [link or contact info here].

Shared vocabulary

Tokens, components, patterns, and primitives should mean the same thing across teams. The Terminology page explains the terms used in CDS.

On this page