Tessli

Guided research path

Design systems worth studying

Goal

Public design systems that demonstrate foundations, tokens, content guidance, accessibility, component architecture, and product-specific patterns.

Audience

Product designers, design-system teams, and frontend leads defining foundations, components, content, and governance.

Expected decision

A documented set of design-system decisions grounded in relevant public systems rather than copied visual conventions.

Continue in Boards

Save sources here, then use Boards to record the choices you want to carry into your project.

Ordered research sequence

Inspect one stage at a time

Start with the first stage, inspect each source against its prompt, and save the references that help you make the decision.

Stage 1

Compare foundations

Inspect
Study broad platform and enterprise systems to compare tokens, foundations, component scope, and documentation structure.
Decision supported
Choose the foundation categories and documentation depth the project actually needs.
  1. Role — Why included
    Material Design 3 provides a broad reference for tokens, adaptive foundations, and component guidance.
    Inspect
    Study broad platform and enterprise systems to compare tokens, foundations, component scope, and documentation structure.
    Decision prompt
    Choose the foundation categories and documentation depth the project actually needs.
  2. Role — Why included
    Apple Human Interface Guidelines shows platform-specific interaction and presentation constraints.
    Inspect
    Study broad platform and enterprise systems to compare tokens, foundations, component scope, and documentation structure.
    Decision prompt
    Choose the foundation categories and documentation depth the project actually needs.
  3. Role — Why included
    IBM Carbon demonstrates enterprise component architecture and documentation breadth.
    Inspect
    Study broad platform and enterprise systems to compare tokens, foundations, component scope, and documentation structure.
    Decision prompt
    Choose the foundation categories and documentation depth the project actually needs.

Stage 2

Study product context

Inspect
Inspect systems shaped by commerce, collaboration, creative tools, and productivity products.
Decision supported
Decide which product-specific patterns transfer and which are context-bound.
  1. Role — Why included
    Shopify Polaris shows a design system shaped by commerce workflows and product language.
    Inspect
    Inspect systems shaped by commerce, collaboration, creative tools, and productivity products.
    Decision prompt
    Decide which product-specific patterns transfer and which are context-bound.
  2. Role — Why included
    Atlassian Design System provides patterns for dense collaborative software.
    Inspect
    Inspect systems shaped by commerce, collaboration, creative tools, and productivity products.
    Decision prompt
    Decide which product-specific patterns transfer and which are context-bound.
  3. Role — Why included
    Adobe Spectrum demonstrates cross-platform consistency for creative applications.
    Inspect
    Inspect systems shaped by commerce, collaboration, creative tools, and productivity products.
    Decision prompt
    Decide which product-specific patterns transfer and which are context-bound.

Stage 3

Learn from public-service rigor

Inspect
Review systems where accessibility, content, service consistency, and contribution governance are explicit.
Decision supported
Define the accessibility, content, and governance standards required for the project.
  1. Role — Why included
    Microsoft Fluent 2 offers another large-scale foundation and component model.
    Inspect
    Review systems where accessibility, content, service consistency, and contribution governance are explicit.
    Decision prompt
    Define the accessibility, content, and governance standards required for the project.
  2. Role — Why included
    GitHub Primer connects components, CSS, product patterns, and open contribution.
    Inspect
    Review systems where accessibility, content, service consistency, and contribution governance are explicit.
    Decision prompt
    Define the accessibility, content, and governance standards required for the project.
  3. Role — Why included
    GOV.UK Design System foregrounds accessible service patterns, content, and evidence.
    Inspect
    Review systems where accessibility, content, service consistency, and contribution governance are explicit.
    Decision prompt
    Define the accessibility, content, and governance standards required for the project.
  4. Role — Why included
    U.S. Web Design System adds public-sector tokens, components, and implementation guidance.
    Inspect
    Review systems where accessibility, content, service consistency, and contribution governance are explicit.
    Decision prompt
    Define the accessibility, content, and governance standards required for the project.