[handbook] Add choosing-components guide and table layout#4308
Open
CiscoFran10 wants to merge 3 commits intomui:masterfrom
Open
[handbook] Add choosing-components guide and table layout#4308CiscoFran10 wants to merge 3 commits intomui:masterfrom
CiscoFran10 wants to merge 3 commits intomui:masterfrom
Conversation
Made-with: Cursor
commit: |
Bundle size report
Check out the code infra dashboard for more information about this PR. |
✅ Deploy Preview for base-ui ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Draft / feature concept (DO NOT MERGE)
This PR adds a Choosing the right component handbook page to help developers pick the right Base UI component by use case.
https://deploy-preview-4308--base-ui.netlify.app/react/handbook/choosing-components
I've seen this come up a lot: devs opening issues and asking in Discord which component to use (e.g. Select vs Combobox, Dialog vs Popover, when to use Tooltip vs Toast). This is an attempt to address that with a single reference page that groups components by purpose and includes short "key differences" so people can decide without digging through every doc.
Why it's a draft / proposal
I know the Base UI team is working on a new design for the docs. This is not meant to be the final solution, just a concrete proposal you can:
I wanted to put the idea and a minimal implementation out there so it can be discussed and, if useful, implemented in a better way as part of the new docs. Happy to iterate or close in favor of a different approach.