[docs] Update "Unstyled" sections to point to new Base UI package

[mapache-salvaje]

Related page

https://mui.com/material-ui/react-select/#unstyled

Kind of issue

Other

Issue description

Material UI components with Base UI equivalents have an "Unstyled" section in their component docs to direct users to the latter if they need them. With mui/base-ui now replacing the older legacy package in the material-ui repo, these links and descriptions should be updated to point to the new library.

The only question is when to do it. ASAP? Or should it coincide with a later milestone for Base UI—beta or stable release?

Search keywords: unstyled, base ui, docs

[oliviertassinari]

The only question is when to do it. ASAP? Or should it coincide with a later milestone for Base UI—beta or stable release?

It feels like ASAP. Reasoning:

• We link to a legacy version. We can't have this. Either we remove all links or we link to the most up-to-date version.
• If we remove all links, won't we undeserve users? The ones that want more customization freedom?
• If we link the new Base UI, we will get users coming and reporting issues, and experiencing what might not be amazing, yet. But it seems still better than going with linking nothing or linking the old Base UI.

[mapache-salvaje]

It feels like ASAP.

That's my thought as well. cc @colmtuite in case you have any thoughts or preferences about when to move forward with this.

[oliviertassinari]

Per https://mui-org.slack.com/archives/C02P87NQLJC/p1734608624843609, I think that we could turn this issue into an umbrella issue. Current steps we see:

• 1. Update our repo social preview: https://github.com/mui/base-ui/settings
• 4. Change any remaining "Base UI" text or anchor text to "MUI Base". Helping the branding messaging to talk about the two different versions. This seems the simplest, by following the npm names.
• 5. Add a deprecation warning to every page of https://mui.com/base-ui/*. Link to the new component's page.
• 3. Delete all links from mui.com/* pointing to https://mui.com/base-ui/*
• 8. Create content to communicate the change. The bare minimum seems a blog post. Great is a guide to explains how to do that migration, so we lose as few users as possible in the switch.
• 2. Delete https://mui.com/base-ui/, the marketing page. Instead, add a 301 to link the page to one in https://base-ui.com/.
• 7. Email our mailing list announcing the launch of Base UI, explaining the @mui/base deprecation, and encouraging migration. Using content in 8.
• 6. Deprecate the @mui/base npm package. Use the blog post of 8. for people who wants to learn more.
• 9. Rename the /examples/ to match the name.
• 10. Once Base UI has more downloads that MUI Base. At least remove 3/4 of the current MUI Base /examples/ from the codebase. No much more purpose.

[colmtuite]

Updated task list

• Delete all links from mui.com/* that point to https://mui.com/base-ui/ or https://mui.com/base-ui/*, unless they exist within https://mui.com/base-ui/*.
• Add a 301 to redirect https://mui.com/base-ui/ to https://base-ui.com. [docs] 301 redirect /base-ui to base-ui.com #45061
• Change any remaining "Base UI" text to "MUI Base". [docs] Rename "Base UI" to "MUI Base" in all text #45060
• Add a deprecation warning to every page of https://mui.com/base-ui/*. The warning message should be located at the very top of the main content. For component pages that have a new Base UI counterpart, add a link to the new component's page. For component pages or utility pages that don't have a new Base UI counterpart, just link to the homepage. [docs] Add @mui/base deprecation callout #45030