Complex status and flags

[Spark450]

Background

In the open forum session held on February 2nd, designers featured contexts where they had to communicate complex statuses and states using the current badge component. They highlighted the need for a solution that can better accommodate these more complex contexts.

However, addressing this issue may be challenging, and we should approach it with an incremental improvement mindset. It's unrealistic to expect a complete solution immediately, so we should focus on identifying isolated opportunities where the design system can offer high value.

Acceptance criteria

Review “complex” status contexts in the services designed by the following designers to build an understanding of commonalities, differences, and opportunities:

@Mark.Pawson

@Ashley Truong

@Isa Amistad

@Chris Martin (has Miro board for their context)

@Ashifa.Asaria

@Jean-Philippe.Larochelle

Decide on a course of action (here are a few possible paths that can be used singularly or in combination)

Extend the current “Badge” component and docs

Create a “Status” pattern that focuses more on content, usage, and utilization of current components.

Create a “new” component to address challenges

open to other approaches

[Spark450]

Jira issue

[Spark450]

Hey @twjeffery In light of the developments on the workspace pattern I wonder if its worth going back into this one and outlining what we would want enhancements we want to make in development to support this change.