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

Cards: Composability analysis #6617

Open
7 tasks
Tracked by #6614
RichKummer opened this issue Dec 18, 2024 · 0 comments
Open
7 tasks
Tracked by #6614

Cards: Composability analysis #6617

RichKummer opened this issue Dec 18, 2024 · 0 comments

Comments

@RichKummer
Copy link

RichKummer commented Dec 18, 2024

Now that you’re more familiar with the component/pattern, we can start to think about the different pieces for composability.

  • Identify existing areas of the component that we might consider swapping out. For example, might an adopter want to swap another component from an existing one?
    • Ex. Tearsheet has header actions that can appear across from the header. What might adopters want to use there? What sort of guidance would we need?
  • Identify if we would want to add any net new areas that the adopter could swap another component in.
    • Ex. Tearsheet has a header that could use a main slot below the description for larger components. What could adopters use here?
  • Were there other areas of opportunity uncovered in the previous sprint?
  • As you’re analyzing for slots/composibility, are there other design updates we should consider?
  • Consider accessibility here. Try tabbing through the component in Storybook. Try VoiceOver on your Macbook to see how/if the audio announces the key parts of the component.
  • If it's useful, feel free to jump into Figma and play around with some ideas for composibility/flexibility.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog 🌋
Development

No branches or pull requests

1 participant