[Empty States] Types and alternatives

[laurenmrice]

Acceptance criteria

Types

• Determine if empty states should be categorized into different "types" or "scenarios" like the following list below or if those are entirely separate components/patterns or things that are unrelated to empty states. This came from Kritvi's Monday doc and she got ideas from this article.

First time use: When new users first interact with a digital product. Empty state example with dummy data and helper text.
(This feels like it would be valid.)

User cleared: Completing tasks: The user has just completed a task or cleared all content associated with the app or site.
(This feels like it would be valid.)

Error state: The user has encountered a roadblock during the interaction.
(Question: Is this more of an error or notification instead of empty state?)

Failed to load: (thread).
(Question: Is this more of an error or notification instead of empty state?)

No data: The system has no data to display or no results from a search query.
(Question: Is this more of just a search query design?)

Alternatives

• Determine if there are "alternatives" of empty states or if these are entirely separate things and could rather just be referenced in the docs if needed because they are related.

(Note: At first glance, these seem like different patterns and not part of empty states.

Onboarding experience
(Question: Isn't this more of like "Walkme"?. For onboarding situations, things will probably be empty, which would result in an empty state, but that seems like its just a first time use case instead and not an onboarding experience.)
Starter content
Education content
Search best match