[docs] Fix 404 links to MUI X API

[oliviertassinari]

The issue was raised by Moz.com

Try to navigate to the data grid API from the v5 documentation, it fails.

• Before: https://mui.com/api/css-baseline/
• After: https://deploy-preview-28176--material-ui.netlify.app/api/css-baseline/

TIL prefetch doesn't work between zones: https://nextjs.org/docs/advanced-features/multi-zones, confirmed in vercel/next.js#4419 (comment).

[mui-pr-bot]

No bundle size changes

Generated by 🚫 dangerJS against 0afab4f

[eps1lon]

This breaks the following sort() and map().

Could you go back and check if this worked when the pages were added?

[oliviertassinari]

This breaks the following sort() and map().

@eps1lon This logic is shallow, it's not applied on the nested array I have modified.

Could you go back and check if this worked when the pages were added?

I had a look at the history. It was broken when introduced. To be more precise. It got done correctly in #26477, targeting the v4 branch. Then I cherry-picked the same changes in the v5 branch, but I didn't account for #23586, so it broke.

[eps1lon]

I had a look at the history. It was broken when introduced.

So how was it tested when introduce and how did you test it now?

[oliviertassinari]

@mnajdova I have changed the approach, this logic will soon be removed once we isolate the different documentation, similarly to how react-aria has its own space https://react-spectrum.adobe.com/react-aria/ vs. https://react-spectrum.adobe.com/react-spectrum/index.html

Soon or later @danilo-leal will figure out a great solution. So, to keep things simple, I have copied and pasted the logic of MUI X. I think that we can call it a day.

---

So how was it tested when introduce

@eps1lon It was tested on the branch of v4 (master), it wasn't on v5 (next).

how did you test it now

It can be reviewed by opening the Before and After links of the issue's description and making sure the href won't point to a 404

https://mui.com/api/css-baseline/