-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
[material-ui][docs] Standardize all references to Material Design 3 (M3) #40903
[material-ui][docs] Standardize all references to Material Design 3 (M3) #40903
Conversation
docs/data/material/guides/material-3-components/material-3-components.md
Outdated
Show resolved
Hide resolved
docs/data/material/guides/material-3-components/material-3-components.md
Show resolved
Hide resolved
The |
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.
Thanks for tackling this @samuelsycamore 😊
Regarding "Material You" and "MD3" mentions in @mui/material-next
, we should standardize them as well.
docs/data/material/guides/material-3-components/material-3-components.md
Show resolved
Hide resolved
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.
Looks great to me! 🤙
Raised in this comment thread: #40446 (comment)
(From https://developer.android.com/codelabs/jetpack-compose-theming#0)
This PR replaces mentions of "Material 3" and "MD3" with either "Material Design 3" or "M3."
Though "Material 3" might be considered an acceptable synonym, I think it's overly confusing in our context. (Are we talking about Material UI v3?). We should err on the side of clarifying that we're talking about Material Design most of the time; after first mention, I think M3 works well to maintain that clarity.
I removed the names of the components from the headers in the component demo docs because they just felt redundant. The search experience could be better, but that's something we should address with the design of the search results if we want to improve it.
I've also done some rewriting of the
@mui/material-next
docs to reflect the changes to the release schedule (since M3 is coming in v7, not v6).