Add Chinese version of website

[laziobird]

Desired feature or idea.
What would you like to see happen?
There are many developers who are always focus on OpenTelemetry in China. 😊
We already have a Chinese project in OpenTelemetry GitHub : https://github.com/open-telemetry/docs-cn.
As a maintainer, i try a better way to spread OpenTelemetry in China.
Our community team want to contribute the Chinese official documents in OpenTelemetry.io . I suggest that whether we can add a link in OpenTelemetry.io , which is from the Chinese official introduction project https://github.com/open-telemetry/docs-cn.

Additional context
Anything else you can think about that would be helpful.
I think it is a good way to preach the Technology of OpenTelemetry Observability and bring everyone's more passions in China community . I have already communicated with Ted for the topic ，and he is very nice and suggested me to file an issue .
Looking forward your suggestion too.

---

Tasks

• [zh] Add zh version of homepage #4341
• [infra] Adjust site config etc in preparation for multilingual support #4443
• @laziobird @windsonsea et al., please confirm that these edits of mine were ok:
  Edit(@chalin 2024/05/13): I'm marking subtasks below as ok, given [zh] Add zh version of homepage #4341 (comment) and that [zh] Minor translation update of zh version homepage #4470 has been approved; if this isn't the case submit a follow up PR. Thanks!
  • [zh] Add zh version of homepage #4341 (comment)
  • [zh] Add zh version of homepage #4341 (comment)
• Publish Chinese homepage in production! 🎉 - [zh] Show Chinese homepage in production #4477
• [zh] Add a first docs page #4478

Followup items:

• Moving remaining items to: Improved i18n support #4467

[cartermp]

Wow, this is a really great initiative. I think we'd have to discuss what it would mean to have a Chinese version of the site, or at least the site's content.

I can see in the repo you linked that there's content there that summarizes some of the concepts in a different way than we do in this repo. That's both fantastic and a bit of a challenge -- we may need to work out a plan to merge content so that both the Chinese and English versions have the same content.

Some topics that come to mind that we'd have to work out:

• Differences in content and how to move forward with that
• How to handle site maintenance
• How to adjust a contribution flow - for example, someone contributes content in English, how do we port to Chinese?
• Multiple SIGs?

@chalin and @svrnm how would you like to proceed?

[chalin]

My first thoughts & comments:

• As you probably know, Hugo + Docsy have support for multilingual sites.
• We anticipated that other languages would come along and put the English docs under content/en already.
• As a trial, we could mount the docs-cn under content/cn as is, and enable the (natural) language version menu.

I think that there are two main ways to approach this. One is to just mount docs-cn as is (with it's different structure), but ideally, both language versions should have the same structure because we'll then be able to setup the cn version of the docs to fall back to the en version when no cn page is present. That way, both sets of docs have all the pages, supporting an incremental translation of the docs.

[svrnm]

Hey @laziobird , thanks! I agree with @cartermp that this is a great initiative and definitely something we should have, so we need to discuss the how we can have it, as @chalin outlined it already.

I agree with @chalin that ideally the two should have the same structure (and maybe even live out of the same repo?), I see us having more languages in the future so we should start with a good practice now.

@laziobird would you be able to attend one of our SIG meetings, there is one today at 10 am PST, not sure if this works for you? Otherwise we can discuss it async via the slack channel

[laziobird]

Hey @laziobird , thanks! I agree with @cartermp that this is a great initiative and definitely something we should have, so we need to discuss the how we can have it, as @chalin outlined it already.

I agree with @chalin that ideally the two should have the same structure (and maybe even live out of the same repo?), I see us having more languages in the future so we should start with a good practice now.

@laziobird would you be able to attend one of our SIG meetings, there is one today at 10 am PST, not sure if this works for you? Otherwise we can discuss it async via the slack channel

@svrnm Thanks for your invitation ！I probably can't attend this meetings , i hope to discuss it async via the slack channel continue . I would like to attend next SIG meeting though my English speaking and listening are a little poor ，if you don't mind this . 😊

[svrnm]

@laziobird no worries, I understand that. We can keep it async here or in the slack, whatever you prefer.

[laziobird]

My first thoughts & comments:

• As you probably know, Hugo + Docsy have support for multilingual sites.
• We anticipated that other languages would come along and put the English docs under content/en already.
• As a trial, we could mount the docs-cn under content/cn as is, and enable the (natural) language version menu.

I think that there are two main ways to approach this. One is to just mount docs-cn as is (with it's different structure), but ideally, both language versions should have the same structure because we'll then be able to setup the cn version of the docs to fall back to the en version when no cn page is present. That way, both sets of docs have all the pages, supporting an incremental translation of the docs.

I very agree it . It is necessary to keep the uniform structure . I would like to be open to support cn version of the docs .

[laziobird]

We see a good example : istio
This is en version
https://istio.io/latest/
This is cn version
https://istio.io/latest/zh/docs/
You know , number of documents is big , and sometime they are changed frequently.
Maybe we can translate the core and main documents first , that give a fast way to preach OpenTelemetry in Chinese community and encourage all members to distribute some contents. These contributors who are response for translating must understand OpenTelemetry and Observability much more .
So we need some time and patience . 😊

[svrnm]

@laziobird what we need to continue with this, is an understanding of how many people are there who are willing to help building the chinese version? We need a critical mass of people, who are willing to help with that, to be sure that we can maintain and run this long term, since the existing maintainers are not able to help with that.

Maybe we can translate the core and main documents first ,

Yes, I think there are some pages which are more important than others (https://opentelemetry.io/, https://opentelemetry.io/docs/concepts/, https://opentelemetry.io/docs/getting-started/ are the ones that should be there first, then the getting started for collector & all languages, etc., that's at least my suggestion)

[Petrie]

@laziobird Is there any recent progress on this topic?
As a native Chinese speaker, I would be delighted to contribute to the creation of a Chinese version.

[laziobird]

@laziobird Is there any recent progress on this topic? As a native Chinese speaker, I would be delighted to contribute to the creation of a Chinese version.

Hi:
Petrie, you can join in the slack channel https://join.slack.com/t/opentelemetry-china/shared_invite/zt-1rzmuyguc-N9DI692M4aa4AlmYr1vfdA . And we can communicate with each other deeply if you are interesting with this plan . My account is 蒋志伟 in slack .