Skip to content

[FE-82] Consistent empty states across list views #1181

Description

@yusuftomilola

Overview

Assets, users, departments, and reports all render lists. A blank region reads as a broken page, and for a system replacing spreadsheets the first-run empty state is the most important onboarding moment there is.

Tasks

  • Build a reusable EmptyState component (icon, heading, description, primary action) in components/ui/.
  • Apply it to every list view with context-specific copy.
  • Distinguish "nothing yet" from "no results for this filter" — the latter offers a clear-filters action.
  • Point the first-run empty state at the highest-value next action ("Add your first asset" / "Import from spreadsheet").
  • Keep empty, loading, and error visually distinct.

Acceptance Criteria

  • Every list view has a purposeful empty state.
  • Filtered-to-zero differs from genuinely-empty and offers to clear filters.
  • Empty, loading, and error states are never confusable.

Notes for Contributors

Comment below to be assigned.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions