[docs] Redirect NoSsr, Portal and TextareaAutosize to Base UI API page

[ZeeshanTamboli]

• I have followed (at least) the PR section of the contributing guide.

Fixes issue mentioned in comment #37121 (comment)

[mui-bot]

Netlify deploy preview

https://deploy-preview-37175--material-ui.netlify.app/

Bundle size report

No bundle size changes

Generated by 🚫 dangerJS against a45d521

[oliviertassinari]

1. The URL is incorrect. https://deploy-preview-37175--material-ui.netlify.app/material-ui/react-no-ssr/#api links to https://deploy-preview-37175--material-ui.netlify.app/base/api/no-ssr/ which is a 301. It's better than a 404 but it's not correct. It degrades the UX, and wastes some SEO crawl budget, e.g.

Screen.Recording.2023-05-06.at.22.06.14.mov

---

2. We got a 2-3 regressions around the links, this is maybe worth a test case.

[ZeeshanTamboli]

@oliviertassinari

1. The URL is incorrect. https://deploy-preview-37175--material-ui.netlify.app/material-ui/react-no-ssr/#api links to https://deploy-preview-37175--material-ui.netlify.app/base/api/no-ssr/ which is a 301. It's better than a 404 but it's not correct. It degrades the UX, and wastes some SEO crawl budget, e.g.

It at-least is better than adding the API doc manually. If we add the docs manually, the API list can get outdated easily. Anyway, we are going to remove these components from Material UI in the next major release.

2. We got a 2-3 regressions around the links, this is maybe worth a test case.

Added tests.

[mnajdova]

Thanks! Agree, we should fix these urls to point to the correct pages (not use redirects). We probably will need to store somewhere the data about where the API page is shown (we can't create it based on the component name anymore, as the docs lays on some documentation page).

[oliviertassinari]

End to end tests are slow, why not write a test case on the text output of the markdown logic? It would be about x100 faster to run.

Suggested change

await page.goto(`/material-ui/react-${kebabCase(component || '')}/`);

[oliviertassinari]

will need to store somewhere the data about where the API page is shown (we can't create it

The markdown logic runs in a webpack plugin. I guess we could either:

• write the links manually with markdown (there aren't that many cases that are broken like this, maybe 10, to check ahrefs crawl to find them all)
• read the page file, with the API links
• load the logic that generates the page file