[website] Rename domain to mui.com#28332
Conversation
| /v0.3.2 https://v0.material-ui.com/v0.3.2 | ||
| /v0.3.1 https://v0.material-ui.com/v0.3.1 | ||
| /v0.3.0 https://v0.material-ui.com/v0.3.0 | ||
| /v0.20.0 https://v0.mui.com/v0.20.0 |
There was a problem hiding this comment.
Should we remove these?
There was a problem hiding this comment.
We could, but likely in a different PR for history revision.
| /customization/themes/ /customization/theming/ 301 | ||
| https://v1-5-0.material-ui.com/* https://v1.material-ui.com/:splat 301! | ||
| https://v3-9-0.material-ui.com/* https://v3.material-ui.com/:splat 301! | ||
| https://v1-5-0.mui.com/* https://v1.mui.com/:splat 301! |
There was a problem hiding this comment.
Should we remove these?
There was a problem hiding this comment.
No objections, the context: #16541, likely in a different PR. And likely we need to do the same for some of the v4 versions.
There was a problem hiding this comment.
Alright, will do it in a dedicated PR after the stable release.
|
These look suspicious. Should we change them before going live? |
|
Olivier has to say something about the redirects. I'm not familiar with most of these. Though I can revert the changes to translated markdown files $ git checkout master -- '*-de.md'
$ git checkout master -- '*-es.md'
# etc. |
These redirects are for the v5 docs of the DataGrid. Once we release v5.0.0-beta.0 this week, it will have the same look of the core v5 docs. Previously, we were pointing to https://next--material-ui-x.netlify.app/, but this is our development branch. Then, I created |
|
I could find this page on the matter in the search console: https://search.google.com/search-console/settings/change-address?resource_id=sc-domain%3Amaterial-ui.com For those that don't have access, their "Learn more" points to https://developers.google.com/search/docs/advanced/crawling/site-move-with-url-changes. |
There was a problem hiding this comment.
@mnajdova Looks good
Should we update the netlify instance to publish on the new domain?
I think that we can use the "primary domain" abstraction. In https://app.netlify.com/sites/material-ui-docs/settings/domain
Are the _redirects update correct?
Should we also add a https://material-ui.com/* https://mui.com/:splat 301! redirection?
Publish the previous versions to v[version].mui.com?
This is done automatically by changing the primary domain in Netlify's config.
Update the medium blog post links to point to https://mui.com?
Done. For all the blog posts I could find
Run a SEO crawler once done and fix all the issues coming
We will likely have to wait for being on the main domain
These look suspicious. Should we change them before going live?
@m4theushw Started to answer it. I will complement it by saying that Netlify recommends using the production URL with proxies, it might not work correctly otherwise. We can wait to hit the fan.
| /v0.3.2 https://v0.material-ui.com/v0.3.2 | ||
| /v0.3.1 https://v0.material-ui.com/v0.3.1 | ||
| /v0.3.0 https://v0.material-ui.com/v0.3.0 | ||
| /v0.20.0 https://v0.mui.com/v0.20.0 |
There was a problem hiding this comment.
We could, but likely in a different PR for history revision.
| /customization/themes/ /customization/theming/ 301 | ||
| https://v1-5-0.material-ui.com/* https://v1.material-ui.com/:splat 301! | ||
| https://v3-9-0.material-ui.com/* https://v3.material-ui.com/:splat 301! | ||
| https://v1-5-0.mui.com/* https://v1.mui.com/:splat 301! |
There was a problem hiding this comment.
No objections, the context: #16541, likely in a different PR. And likely we need to do the same for some of the v4 versions.
I've already added it https://github.com/mui-org/material-ui/pull/28332/files#diff-7a0cbac74402caf0e99ba338a9e7c42684580a1f85e149110c3c2ca6e38055afR14 |
|
@oliviertassinari should we also add the following redirects: |
@mnajdova Yeah, makes sense 👍 |



Questions:
_redirectsupdate correct?Other things to do: