-
-
Notifications
You must be signed in to change notification settings - Fork 32.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] Multi-lingual documentation site #1673
Comments
Hey @Huxpro ! I think it's great that you want to help spread the word about Material-UI in another language. 👍 Yes, the docs project relies on the I see your point about all text being written directly into the .jsx files. In my opinion, the ideal solution would be to consolidate all text strings into a separate module, which can then be What do you think @hai-cea ? |
@shaurya947 Thanks for your reply! I dont wanna bother you guys with that at first ;( |
@Huxpro do you wanna help us? It might be quicker that way :-) To start off, you could submit a PR that modifies the existing documentation site by moving all hard-coded strings into text modules. Let me know if this is something you would like to undertake. |
@shaurya947 Sure. I would like to try it in my free time, after I finish my work with this framework ; ) |
@Huxpro : Are you still planning to go ahead with this? |
@tintin1343 Sorry but im too busy to do that. I'll appreciate sooooo much if someone can accomplish this work. |
@Huxpro : Thanks for replying. I am closing this for now as this is not a pressing issue for us. Whenever you get time to work on this do let us know. We will reopen this. Hope that is alright. |
Hey.
I am a big fan of React, Material Design and now you guys Material-UI.
This components set is so awesome that I wanna do a translation, also build a github pages to help my hometown China.
I am trying to copy
docs
alone, install dependencies and run webpack build but got lots of errors and I finally realized this repo include everything so all the components required are resolved to thesrc
of root instead of tonode_module
..And I am also worried about how to sync updates with your official sites/release, seeing all docs are directly wrote into
.jsx
files, so it may not easy usinggit diff
to checkout diffs.Well..so is there any best practice can help? directly fork the whole repos and output to
gh-pages
branch with onlydocs/build
? (How to do that will a nice npm script..)Looking forward to your reply, thanks
The text was updated successfully, but these errors were encountered: