Internationalized Docs about website

[jamiebuilds]

@devongovett I would recommend Crowdin so that we can have them automatically synced and have a whole tool for managing them.

I can set this up at some point.

For now just create folders with the different languages and I'll migrate them later:

/en/*.md
/cn/*.md
/ko/*.md

[lcxfs1991]

I will add a dropdown tonight.

[lcxfs1991]

Due to poilcy issue, we need to take a few time to register customized domain at Chinese Gov. So could we add a cname first?

[lcxfs1991]

Plesae try to add CNAME:

cn.parceljs.org.cdn.dnsv1.com

[jamiebuilds]

Could we just host the Chinese docs within this project?

[lcxfs1991]

Sure. We cold host a copy within this project and another will be hosted within a Chinese cdn speedup server.

[lcxfs1991]

You know due to policy issue, Github maybe sometimes down...............

[jamiebuilds]

The website isn't hosted on GitHub pages, we can make sure that it's on a service that is available globally.

[lcxfs1991]

great. So shall the Chinese docs be deployed using Zeit Now? Or any other solutions?

[devongovett]

@lcxfs1991 this is awesome, thanks for your work on it! Want to make a PR with your translations? Maybe we can have subdomains deployed with zeit for the translations, e.g. cn.parceljs.org etc.

[lcxfs1991]

Awesome. What shall I do to deploy the site with zeit?

[devongovett]

we'll take care of that. zeit is already used to deploy the main site

[devongovett]

see also #35 for korean.

What's the best way to maintain these so that they don't diverge?

[albinotonnina]

@thejameskyle I read your article about Crowdin and what you did with Babel, looks like the way to go!

_{Sent with GitHawk}

[devongovett]

I have set up the site to support translations. See #39.

There are subdomains for each translation:

• https://en.parceljs.org/
• https://ko.parceljs.org/

The top level domain https://parceljs.org/ will attempt to detect the browser language using the "Accept-Language" header, and serve that language.

[lcxfs1991]

@devongovett What about Chinese site?

[lcxfs1991]

should I put docs under 'website/src/i18n' ?

[devongovett]

@lcxfs1991 yes, that would be awesome!

[lcxfs1991]

I will do it tonight. thx!

…

On Fri, Dec 15, 2017 at 10:58 AM, Devon Govett ***@***.***> wrote: @lcxfs1991 <https://github.com/lcxfs1991> yes, that would be awesome! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#28 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADMXrvJoWVsQemuUgdtbNu1zd23qLayfks5tAeBFgaJpZM4Q6yAz> .

-- First Honor Graduate, The Chinese University of Hong Kong Developer, Tencent AlloyTeam Email: [email protected] Hong Kong Tel: [phone] Shenzhen Tel: [phone]

[devongovett]

Maybe you can work with @zhenyong who also did a translation https://github.com/zhenyong/parcel-website/tree/gh-pages

[lcxfs1991]

I know him. He is also in a group of docshina.org which is an org to localize open source project.

…

On Fri, Dec 15, 2017 at 11:01 AM, Devon Govett ***@***.***> wrote: Maybe you can work with @zhenyong <https://github.com/zhenyong> who also did a translation https://github.com/zhenyong/parcel-website/tree/gh-pages — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#28 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADMXruBm2zFJbss6uGhtkdFhHcXU5H2Iks5tAeD3gaJpZM4Q6yAz> .

-- First Honor Graduate, The Chinese University of Hong Kong Developer, Tencent AlloyTeam Email: [email protected] Hong Kong Tel: [phone] Shenzhen Tel: [phone]

[zhenyong]

Awesome!
@lcxfs1991 feel free to contact me to work together if need. ^_^

[lcxfs1991]

@devongovett please check
#42

[brandon93s]

Closing, as we've successful established a pattern for i18n docs and the community has delivered numerous languages! As mentioned above - a management platform, such as Crowdin, would be beneficial at some point.