-
-
Notifications
You must be signed in to change notification settings - Fork 32.7k
[docs] Clarify MUI Base != Base UI (1/2) #46978
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
base: v6.x
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,7 +6,7 @@ export default function App() { | |
<div className="box"> | ||
<h1>Base UI + Create React App scaffold (TypeScript)</h1> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Looks like some of the titles (and directories) still say "Base UI." Honestly I think we should just remove these examples entirely. We don't want people to use MUI Base so we shouldn't give them boilerplates to start with. As long as MUI Base exists it will continue to confuse some people looking for Base UI. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah yes, let's fix this. As for use case of those examples, I only see making it easier to report regressions for people migrating from MUI Base to Base UI. It's in the v6.x branch, so it's mostly hidden. |
||
<div className="item"> | ||
<a href="https://mui.com/base-ui/">Base UI</a> is a library of unstyled React UI components | ||
<a href="https://v6.mui.com/base-ui/getting-started/">MUI Base</a> is a library of unstyled React UI components | ||
which includes prebuilt components with production-ready functionality, along with low-level | ||
hooks for transferring that functionality to other components. | ||
</div> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be helpful to add (legacy) to these examples for extra clarity? I don't have a strong opinion so feel free to use or discard.