[docs] Feedback on Toolpad Core mention in MUI templates

[prakhargupta1]

Related page

https://mui.com/material-ui/getting-started/templates/#toolpad-core-beta

Issue description

Feedback on mui/material-ui#44415

• 1. These redirects should be in Toolpad repository.
• 2. Wrong light mode image size. DOM attributes should match asset.
• 3. https://github.com/mui/material-ui/pull/44415/files#diff-6c8074cc0cbdc7ebecdca83a8bffea83d4b53608423228e56f0acbf9e050de80R27 to be moved inside callout.
• 4. http, we should use https [docs] Add Toolpad Core template link material-ui#44415 (comment).
• 5. Move Vercel hosting to MUI org https://vercel.com/mui org. Invitation link in https://mui-org.slack.com/archives/C02P87NQLJC/p1734475618481449?thread_ts=1734455390.083609&cid=C02P87NQLJC

[bharatkashyap]

1. These redirects should be in Toolpad repository.

I added these redirects on the Toolpad docs website but that alone wasn't enough to make the https://mui.com level redirection work: https://mui.com/toolpad/core/templates/nextjs-dashboard still returned a 404 page.

2. Wrong light mode image size.
   Note: I rechecked the dark and light images, and the size is same. I can't figure out what's wrong.

👍🏻

3. https://github.com/mui/material-ui/pull/44415/files#diff-6c8074cc0cbdc7ebecdca83a8bffea83d4b53608423228e56f0acbf9e050de80R27 to be moved under callout.

It's already under the callout, isnt it?

[prakhargupta1]

It's already under the callout, isnt it?

Sorry, I think it was that the callout should be below: 'If you see any room for improvement, please feel free to open an issue or a pull request on GitHub.'

@oliviertassinari can you confirm?

[oliviertassinari]

1. I added these redirects on the Toolpad docs website but that alone wasn't enough to make the https://mui.com/ level redirection work: https://mui.com/toolpad/core/templates/nextjs-dashboard still returned a 404 page.

Right ok, I didn't realize this was a 200. I thought it was a 3XX. In this case, this makes sense. https://docs.netlify.com/routing/redirects/rewrites-proxies/ explains why. We would need to pay more.

By default, we limit internal rewrites to one “hop” — you cannot proxy from Netlify SiteA to Netlify SiteB to Netlify SiteC in a single request. This limitation may be amended for customers on a case-by-case basis. Contact support for more information.

---

3. It's already under the callout, isnt it?

What if it was inside the callout?

---

I have added a new point 5. for Vercel hosting, so we use an org account.

[github-actions]

This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.