Skip to content

Update design QA considerations for empty states #47917

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lukeheath merged 1 commit into from
Jun 20, 2026
Merged

Update design QA considerations for empty states #47917

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/Contributing/guides/ui/design-qa-considerations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,6 +146,7 @@ This is meant to be a helpful checklist of 'events' or 'transactions' to help ca
- Error states (conditions, clientside vs. server side, location of error message, trigger onBlur/onChange/onSubmit)
- Disabled states (conditions, on button, on form fields)
- Dynamic views (show/hide buttons, dynamic help text, edge case views)
- Views that load data have an empty state defined.

## Responsiveness and low-width browsers
- Long database names rendered in the UI e.g. fleet names, scripts, software titles...
Expand Down
Loading