[docs] Clarify MUI Base != Base UI (2/2) #46979
Open
Conversation
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
oliviertassinari
force-pushed
the
clearify-mui-base-2
branch
from
76980ab to
b9f2ef9
Compare
oliviertassinari
added
docs
Netlify deploy previewhttps://deploy-preview-46979--material-ui.netlify.app/ Bundle size report
|
oliviertassinari
force-pushed
the
clearify-mui-base-2
branch
2 times, most recently
from
cab9487 to
60e2fab
Compare
oliviertassinari
changed the title
oliviertassinari
force-pushed
the
clearify-mui-base-2
branch
from
60e2fab to
78d315a
Compare
mapache-salvaje
changed the title
| @@ -1,22 +1,22 @@ | |||
| --- | |||
| title: An exciting year ahead for Base UI | |||
| title: An exciting year ahead for MUI Base: Base UI | |||
There was a problem hiding this comment.
this article is about Base UI, though?
There was a problem hiding this comment.
We rewrote the history, we said that what we were working on since 2021 was MUI Base, and we rebranded to Base UI late 2024.
So at the time this was written, early 2024, it was still MUI Base.
| That made a lot of sense in the beginning because we didn't intend for MUI Base to be a standalone product at the time. | ||
| As a result of this early decision, we've seen that some developers are hesitant to try it out because of the apparent association with Material Design. | ||
| Rest assured that Base UI _is_ a standalone library, and it doesn't come packaged with _any_ default styles or themes. | ||
| Rest assured that MUI Base _is_ a standalone library, and it doesn't come packaged with _any_ default styles or themes. |
There was a problem hiding this comment.
This text is extremely confusing. Very few readers will be able to make sense of Base UI vs MUI Base in this context, and I can't imagine many people are reading this blog in late 2025 anyway. I don't think it's worthwhile to bother with edits like this. If you think the blog post is going to confuse people, I think it should just be removed.
There was a problem hiding this comment.
I can't imagine many people are reading this blog in late 2025 anyway.
The problem is that this blog post shows up when searching on Google for Base UI vs MUI Base.
This text is extremely confusing.
What is confusing?
There was a problem hiding this comment.
A few thoughts:
- Many users still don't understand that MUI != Material UI. Even as someone who has firsthand knowledge of the history of Base UI, I had a hard time making sense of this text. The names are so similar, it's hard to keep track of which is which, and it's not clear as a reader why it matters.
- A blog post with the slug
/base-ui-2025-planswould quickly and easily outrank this post in a google search and it would be much simpler for users to comprehend - plans have changed, here's the latest news- then we could add a note at the top of the 2024 blog post to let users know there have been significant updates that they can read about in the newer post
- In the absence of a new blog post, it would still make more sense to just add a callout to the top of this post to note that it's outdated and plans have changed
- In general I'm not a fan of "rewriting history" in this way - at best it's confusing for users, and it leaves us with the burden of dozens of outdated timely posts to consider revising every few months
- this is why publishers differentiate between "timely" content and "evergreen" content - the timely stuff isn't worth your time to constantly update when things change, and if it's confusing or misleading then it's best to just delete
- if we want evergreen content on this topic, we should create a post called something like
/mui-base-vs-base-ui-comparisonto address it directly
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.
Same as #46978 but for a different base branch.