Skip to content
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.

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

[Empty States] resolve outstanding design spec decisions #4384

Open
7 of 11 tasks
Tracked by #17553
laurenmrice opened this issue Dec 4, 2024 · 1 comment
Open
7 of 11 tasks
Tracked by #17553

[Empty States] resolve outstanding design spec decisions #4384

laurenmrice opened this issue Dec 4, 2024 · 1 comment

Comments

@laurenmrice
Copy link
Member

laurenmrice commented Dec 4, 2024

Acceptance criteria

There are a few design decisions below that still need to resolved for Empty states. It would be good to have these in order before finalizing website documentation guidance and this may help inform us if this is defined as a component or pattern.


Text and illustration alignment

  • Create a final stance of when text and illustrations of empty states are left or centered aligned.
    • Note: I believe the workgroup was saying to just always center align in every scenario instead of being choosy to make the guidelines easier and more straightforward. Need to confirm this direction.
  • When can you have both text and illustration and when should you only have text? Are there any considerations of when to use one or the other? Should it always be consistent if you have multiple empty states in one page?

Buttons and links

  • How many buttons should be included in an empty state? Does this depend on the component the empty state is on? Is it bad to have multiple call to action buttons in one empty state scenario that are different styles of buttons?
  • Should we allow links?

Text max width

  • Finalize a text max width across different components for empty states. We have decided it for data table,but what about smaller spaces, like in cards or side panels?

Types of empty state

  • Determine if empty states should be categorised and, if so, define the types (e.g., First Use, No Data, Error States).
  • Decide if First Use and Error States should be considered as empty states or treated separately.

Are there any more?

In parallel:

  • Go through the Slack threads.
  • Refer to Tracey's pagination workstream.

Playback

  • Playback decisions to design team and get feedback.
  • Playback decisions to workgroup and get feedback.
Copy link
Contributor

github-actions bot commented Dec 4, 2024

Thank you for submitting a feature request. Your proposal is open and will soon be triaged by the Carbon team.

If your proposal is accepted and the Carbon team has bandwidth they will take on the issue, or else request you or other volunteers from the community to work on this issue.

@laurenmrice laurenmrice transferred this issue from carbon-design-system/carbon Dec 4, 2024
@laurenmrice laurenmrice moved this from Triage to Next ➡ in Roadmap Dec 4, 2024
@laurenmrice laurenmrice moved this to ⏱ Backlog in Design System Dec 4, 2024
@sstrubberg sstrubberg removed this from Roadmap Dec 5, 2024
@laurenmrice laurenmrice added this to the 2024 Q4 milestone Dec 6, 2024
@laurenmrice laurenmrice moved this from ⏱ Backlog to 🏗 In Progress in Design System Dec 11, 2024
@laurenmrice laurenmrice removed their assignment Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🏗 In Progress
Development

No branches or pull requests

2 participants