| Table of Contents |
|---|
...
Type | Usage | Illustration | Full page | Widget |
|---|---|---|---|---|
No results found | Use when a user’s search criteria returns no results. |  |  |  |
No <entities> defined | Use when no entities, such as forms, have been added/defined. |  | Render the LUX frame, including the VerinTop. Replace the full content area with the empty state.  | |
You’re all caught up | Use when a user has no new notifications to review. |  | Render the LUX frame, including the VerinTop. Replace the content pane area with the empty state.  | |
Waiting | Use when an action is in progress. |  | Render the LUX frame, including the VerinTop. Replace the full content area with the empty state.  |
...
Usage & Behaviour
General guidelines
Structure
...
Empty states can be used to display a wide variety of content. For example, they can include a list without list items, or a search that returns no results. Although these states aren’t typical, they should be designed catered for to prevent confusion and improve the UX.
Use sentence-case capitalisation.
Use contextual, light-hearted visual content to supplement the information provided.
Use an accurate explanation that details the current state the application is currently in.
Use contextual cues relevant to the user’s task to educate users on how to use the application in real time.
Where relevant, include direct links to the steps that need to be taken in the user’s workflow to accomplish a task/populate the screen.
Interaction
Empty states have no intrinsic interactions. For component-specific interactions see the documentation of that component.
...
When content does not yet exist for a screen or pane to provide guidance on how to populate the area with that content.
Contextual prompts (i.e., text links) that help a user to accomplish their taskusers with getting started on key tasks.
Clear, concise written explanations.
Neutral illustrations that are representative of the state, reduce stress and add aesthetic appeal to the interface.
...
Totally empty states, this approach creates confusion for users.
Inaccurate written explanations.
Irrelevant actions.
Unrelated visual content.
General
<…>
Accessibility Compliance
Unless otherwise specified, see our general compliance information in Fundamentals - Accessibility
...