-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[docs] Set up Crowdin for MUI X docs #4948
Comments
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. |
I missed the motivation to have opened this issue. It was because of mui/material-ui#32399 (comment) Also agree that the ROI is debatable. We need to see how many users use the translated docs in Portuguese or Chinese. |
This issue is no longer relevant since we disabled translated docs in #6560 |
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: