You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should set up the repo in Crowndin and update the page to redirect to the correct dashboard when on a MUI X page. This may require a contribution in the core repo too. Apart from adding the Crowndin GitHub Action, the crowndin.yml must also be created. Docs: https://support.crowdin.com/github-crowdin-action/
Examples 🌈
No response
Motivation 🔦
Allow the community to send translations.
Order ID 💳 (optional)
No response
The text was updated successfully, but these errors were encountered:
The translation on MUI Core are kind of broken. I believe that the root cause is that the community is not translating the docs fast enough to catch up with our changes there.
On MUI X, I believe we will face a couple of challenges too, some of our API pages are custom made (not using a shared infra with the main repo), not designed with internationalization in mind.
I think that the important question we need to answer is: "Is is worth translating the documentation?" I don't think that we have ever taken the problem seriously, so never attempted to solve the problem properly. It would likely take 12 months of continuous investment to see if the ROI is positive or negative.
Duplicates
Latest version
Summary 💡
The button to edit the page (or translate the page) is redirecting to the MUI Core dashboard: https://translate.mui.com/project/material-ui-docs/
We should set up the repo in Crowndin and update the page to redirect to the correct dashboard when on a MUI X page. This may require a contribution in the core repo too. Apart from adding the Crowndin GitHub Action, the
crowndin.yml
must also be created. Docs: https://support.crowdin.com/github-crowdin-action/Examples 🌈
No response
Motivation 🔦
Allow the community to send translations.
Order ID 💳 (optional)
No response
The text was updated successfully, but these errors were encountered: