Please apply suggested changes; see the justification for them. The format follows what our ACM UI has been doing, but with new components added, we need to ensure we keep the UX. 

wolfeallison owns the story, the doc team has raised this issue to her since she is the content designer for ACM and other teams (the doc team had previously stayed on top of these with the UI developers, but can no longer be as proactive on the UI due to bandwidth, so we are thankful for Allison).

She was able to see the build and make suggestions in the following Google doc:

https://docs.google.com/document/d/1BWAptxP0o5m-ot9YaAE8RsRBAF5zVpkBngRu1U6gISs/edit?tab=t.0

The goal is to also have the same empty state experience in onboarding components. If there is more discussion to be had about the suggested content, please contact Allison.  

Description / Background info

This initiative focuses on standardizing the empty state designs within the Advanced Cluster Management (ACM) product to align with the latest PatternFly design guidelines. Empty states are crucial user interface elements that inform users when a list, table, or content area has no items to display. They are an opportunity to provide context, suggest next steps, or guide users towards adding content. Currently, ACM's empty states exhibit inconsistencies in their presentation, messaging, and calls to action across various features. Adhering to PatternFly's established best practices will improve overall UX consistency, reduce cognitive load for users, and enhance the discoverability of features within ACM.

Helpful Links:

• PatternFly Empty State Design Guidelines: https://www.patternfly.org/components/empty-state/design-guidelines

Problem statement:

ACM's current empty state designs are inconsistent across the product, leading to a fragmented user experience, reduced usability, and a missed opportunity to effectively guide users on how to populate empty content areas. We assume that the inconsistency can confuse users, make the product feel less polished, and hinder user adoption, especially for new users who encounter many empty states.

Goals for the work

• Improve UX Consistency: Ensure all empty states within ACM adhere to a unified design language as defined by PatternFly.

• Enhance Usability & Guidance: Provide clear, concise, and actionable guidance to users when they encounter empty states, helping them understand how to populate or interact with features.

Tracking success

• UXD and CCS Team Consensus: Agreement within the OpenShift UXD and CCS team that the updated empty states align with PatternFly guidelines and improve user experience.