pattern-library 2 linked patterns checked

Atlassian Design System Empty State

Documents empty states for moments when there is no content to show, with clear explanation, relevant next action, and variants for error, filtered, and permission cases.

Read with a purpose

What this source can teach

Use this source to compare a documented solution with the task and states in your own product.

  1. Start with the original. Open the source and find the guidance or example relevant to your task.
  2. Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
  3. Check the setting. Compare the source's platform, people, and constraints with your own decision.

Pattern Decisions This Source Supports

Pattern Supported decision Required contract Claim note
Dead-end empty state Flag dead-end empty state when a blank area lacks a specific object name, cause, and reachable next action. A blank or actionless content region is not a valid terminal state. Atlassian documents empty states with explanation, action, and variants for permission, filtered, and error causes.
Empty state Choose empty state only after the system knows the area is legitimately empty rather than loading, filtered, or failed. The empty state identifies what is absent and why the absence is expected. Atlassian documents empty states with explanation, action, and variants for permission, filtered, and error causes.

Comparisons supported by this source

Evidence Role

This source is treated as pattern-library evidence. Its value comes from the specific claims and setting described above.

Publisher: Atlassian Design System. Last checked: .

Saved items