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
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.
The text was updated successfully, but these errors were encountered:
Now that you’re more familiar with the component/pattern, we can start to think about the different pieces for composability.
The text was updated successfully, but these errors were encountered: