Merged
Conversation
jdmcleod
approved these changes
Feb 16, 2026
Collaborator
|
Did you update the readme? |
Member
Author
|
@jdmcleod Did now |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Tabs components provide show/hide behavior for connecting buttons to areas of content on a page.
The goal was to have extremely easy to implement and customize components. With that goal in mind, they are meant to be light, composable, and not opinionated. This allows them to provide functionality while fitting into whatever design system or application you may already have without requiring significant style modifications.
[ ] Improve documentation on usage@jdmcleod Would be good to standardize on documentation this across all components but doesn't need to hold this up at the moment.tabs-demo.mov