You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In recent projects where we've worked on designing complex interfaces for product teams, we found ourselves wishing for a bit more flexibility in the Accordion component, particularly in the header. While we agree that the content of the header should be clearly defined, we'd like to explore the possibility of adding some components that would undoubtedly bring significant value to the component itself. Here's an example of an Accordion with a badge in the header, which could indicate the method by which the API retrieves data for a specific product.
I like it. I think it is a good way to provide additional information.
I took a look to other Design Systems and they provide a similar solution for this.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
In recent projects where we've worked on designing complex interfaces for product teams, we found ourselves wishing for a bit more flexibility in the Accordion component, particularly in the header. While we agree that the content of the header should be clearly defined, we'd like to explore the possibility of adding some components that would undoubtedly bring significant value to the component itself. Here's an example of an Accordion with a badge in the header, which could indicate the method by which the API retrieves data for a specific product.

Thanks!
All reactions