Empty States

Empty States Overview

Empty States lets you structure design systems work so it stays readable, testable, and easy to scale. Instead of ad-hoc code, you follow a clear pattern that other developers can recognise immediately.

The key is to keep empty states focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

<ds-card>
  <h3 slot="title">Plan</h3>
  <p slot="body">Everything your team needs.</p>
  <ds-button slot="actions" variant="primary">Choose</ds-button>
</ds-card>

Slot-based composition lets consumers place content while the component controls structure and style.

Empty States Example

/* Tokens flow into components, which flow into products */
:root { --color-brand-500: #2563eb; }
.button { background: var(--color-brand-500); }

• Start from a minimal Empty States example and grow it only as needed.
• Keep configuration explicit so Empty States behaves the same in every environment.
• Name things clearly so teammates understand your Empty States at a glance.
• Add tests around Empty States early to lock in expected behaviour.

Design System Cheatsheet

Quick reference for empty states within a modern design system.

How Empty States Fits into a Design System

Empty States connects the design decisions in your system to the code teams actually ship. When it is defined once and reused, products stay consistent and updates roll out everywhere.

Slot-based composition lets consumers place content while the component controls structure and style.

• Define it once as a token or shared component.
• Document intended usage with clear examples.
• Make it themeable and accessible by default.
• Version and release changes so consumers can upgrade safely.

Getting Teams to Adopt Empty States

Adoption is where design systems succeed or stall. Make empty states the easiest option: great docs, sensible defaults, and clear migration paths beat mandates every time.

Common Mistakes

• Skipping error handling and edge cases when wiring up empty states.
• Leaving empty states untested, so regressions slip into production.
• Over-engineering empty states before you actually need the extra flexibility.
• Ignoring documentation, which makes empty states hard for the next developer to change.

Key Takeaways

• Empty States is a core part of working effectively with design systems.
• Start small and keep empty states focused on a single responsibility.
• Apply consistent patterns so empty states scales across your project.
• Test and document empty states to keep it maintainable over time.