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
What do you think about translating the site to the other languages? Do you have plan or direction for this? I really want to contribute by translating the site into Turkish.
I have already contributed the translations of some open source repositories . Let me answer you questions based on my experiences;
What happens if there are changes?
You can either have a manual process (I mean notifying maintainers on every update) or use a tool for this. I have used GitLocalize in some of the projects I involved in. This decision depends on the infrastructure decision.
General infrastructure
One way for managing translations is to ask people to use their forked repositories. You will link them form your main repository or from the site. They have to generate the static sites like you do in the main repository. In this way, handling changes are totally responsibility of the fork repository maintainers. This not the best way for me. For example, Hacker Laws repository manages some of the translations in this way. I am the one maintaining the Turkish repository and I can say that handling the changes are not easy in this way.
Second way is to create a language based folder structure on the main repository. Ask people to maintain the translations on the main repository. The localized static site is generated by you and linked directly from the site by letting user to select the language. For example, PHP - The Wrong Way is a good example for that.
I also involved the translation of Open Source Guides which has the second way infrastructure and it can be accepted as a success story. They generate the static site by using localized content from separate folders.
Woah, GitLocalize sounds super useful. This may not be so hard with it :). I'll think about this more and maybe play around with GitLocalize this weekend, thank you
The tutorial is awesome. And I've translated it into simplified Chinese, the link is https://makefiletutorial.vercel.app. Please help yourself if needed.
Reacted by Lan, wanyzh, 高君, Chase Lambert, Alwin Arrasyid, Yujian Zhang and zhoutz
The tutorial is awesome. And I've translated it into simplified Chinese, the link is https://makefiletutorial.vercel.app. Please help yourself if needed.
Haha, I'm a beginner and I've translated the tutorial in Chinese in halfway and you had done.xD.
The tutorial is awesome. And I've translated it into simplified Chinese, the link is https://makefiletutorial.vercel.app. Please help yourself if needed.
Haha, I'm a beginner and I've translated the tutorial in Chinese in halfway and you had done.xD.
I can also contribute with a Hebrew translation. Some tweaks might need to be implemented for RTL scripts (I can do that), as well as connected scripts like Hindi or Arabic.
Activity
chaselambda commentedon Feb 15, 2021
Oh I appreciate the offer! Hmm, the issue is I don't have any great immediate ideas on how to go about doing the translations. Some thoughts:
Are there success stories you know of that talk about simple static website translations and maintenance?
umutphp commentedon Feb 16, 2021
Hi @theicfire,
I have already contributed the translations of some open source repositories . Let me answer you questions based on my experiences;
What happens if there are changes?
You can either have a manual process (I mean notifying maintainers on every update) or use a tool for this. I have used GitLocalize in some of the projects I involved in. This decision depends on the infrastructure decision.
General infrastructure
One way for managing translations is to ask people to use their forked repositories. You will link them form your main repository or from the site. They have to generate the static sites like you do in the main repository. In this way, handling changes are totally responsibility of the fork repository maintainers. This not the best way for me. For example, Hacker Laws repository manages some of the translations in this way. I am the one maintaining the Turkish repository and I can say that handling the changes are not easy in this way.
Second way is to create a language based folder structure on the main repository. Ask people to maintain the translations on the main repository. The localized static site is generated by you and linked directly from the site by letting user to select the language. For example, PHP - The Wrong Way is a good example for that.
I also involved the translation of Open Source Guides which has the second way infrastructure and it can be accepted as a success story. They generate the static site by using localized content from separate folders.
chaselambda commentedon Feb 16, 2021
Woah, GitLocalize sounds super useful. This may not be so hard with it :). I'll think about this more and maybe play around with GitLocalize this weekend, thank you
gavinliu6 commentedon Jun 11, 2021
The tutorial is awesome. And I've translated it into simplified Chinese, the link is https://makefiletutorial.vercel.app. Please help yourself if needed.
crisjumbo commentedon Sep 14, 2021
@theicfire congratulations for the tutorial. It is just amazing !!
I would love also to contribute in the Spanish translation. Let me know :D
klaygomes commentedon Sep 23, 2021
If this idea go ahead, I would like to maintain the Brazilian Portuguese version.
BreakingLead commentedon Mar 16, 2022
Haha, I'm a beginner and I've translated the tutorial in Chinese in halfway and you had done.xD.
BreakingLead commentedon Mar 16, 2022
Haha, I'm a beginner and I've translated the tutorial in Chinese in halfway and you had done.xD.
zhuzhzh commentedon Sep 25, 2022
@gavinliu6 I don't know you've done it. I did it again.
amosbarsinai commentedon Jan 28, 2026
I can also contribute with a Hebrew translation. Some tweaks might need to be implemented for RTL scripts (I can do that), as well as connected scripts like Hindi or Arabic.