[docs] Fix 301 link to Base UI #40396
Merged
+88
−80
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not the cleanest solution but it works to solve
https://app.ahrefs.com/site-audit/3524616/99/data-explorer?columns=pageRating%2Curl%2Ctraffic%2ChttpCode%2CredirectChainUrls%2CisRedirectLoop%2CincomingAllLinks%2CincomingRedirect%2Corigin&filterId=808b08e88c934ee19e04fdec4ed87a5a&issueId=c64d12c1-d0f4-11e7-8ed1-001e67ed4656&sorting=-pageRating
Extracted in #40531
Off-topic. When it comes to my own use of the components, the UX before #35938 likely work better with my workflows. Now, some would clearly prefer the new UX. Still, I think that it means that for the new approach to have a higher chance of winning, we have to fill the gaps with the older one:
material-ui/docs/translations/translations.json
Line 305 in 48251ab
Off-topic
Extracted in #40532
@alexfauquette I wonder if it would make sense to format more the HTML of the API pages, with h4, h3 so Google can more easily return relevant search results.
I have tried searching for the description of props on Google, can't really find helpful results. Maybe it's not a common workflow though, I don't recall ever trying this in the past as a user.