Archive zh-hans.docs.eslint.org

[mdjermanovic]

What problem do you want to solve?

In the 2025-09-18 TSC meeting, we've agreed to no longer update the zh-hans docs site.

What do you think is the correct solution?

We haven't discussed the next steps yet, so here are some possible to discuss:

1. https://zh-hans.eslint.org/docs/latest/ website: 1) Keep it as-is, or 2) Keep it but add a banner saying it is no longer maintained, with a link to https://eslint.org/docs/latest/, or 3) Redirect requests to https://eslint.org/docs/latest/, or 4) Just remove it. I'd vote for 2).
2. Links to https://zh-hans.eslint.org/docs/latest/. We have links on the org site and the docs site (language selector). I think the org site should link to https://eslint.org/docs/latest/, while on the docs site language should be removed from the language selector.
3. Archive this repo.

Participation

• I am willing to submit a pull request for this change.

Additional comments

No response

[mdjermanovic]

@eslint/eslint-tsc thoughts about next steps?

[lumirlumir]

I have a question: https://github.com/eslint/eslint-jp hasn't been archived and was last updated about nine years ago, so I'm wondering whether eslint-jp should also be considered archived.

---

Personally, I think making the i18n documentation fully community-driven would also be a good approach.

React uses this approach: the React team maintains the ReactJS organization for this purpose. There are over 50 translations available, and each repository is maintained by representatives of the respective language.

[nzakas]

We should archive eslint-jp -- no one's paying attention to that.

Making documentation translating community driven sounds good in theory, but in practice, it's a lot of work and we don't even get that many contributions to the English documentation. On top of that, we'd still need the ESLint team to be involved to merge PRs.

I think the only long-term solution is to have automated translations for the documenation. We have an issue open here:
eslint/eslint#11512

--

@mdjermanovic I think option 2 makes the most sense as well.

[fasttime]

Wow, eslint-jp has one readme file with two commits!

I don't know if it's necessary to remove the Chinese translation from the dropdown selector. Other translations consist of a single yml file (in https://github.com/eslint/eslint.org/tree/main/src/_data/sites) and there is also one for zh-hans. I can't speak about the content, but I guess that yml file should provide translations for most elements on the main page.

I thought we were just going to discontinue this repo but keep the (basic) Chinese translation. So for example a user who opens https://zh-hans.eslint.org/docs/latest/rules/no-restricted-globals would be seeing the current English documentation instead of the outdated Chinese page, same as for the other languages.

[mdjermanovic]

I don't know if it's necessary to remove the Chinese translation from the dropdown selector. Other translations consist of a single yml file (in https://github.com/eslint/eslint.org/tree/main/src/_data/sites) and there is also one for zh-hans. I can't speak about the content, but I guess that yml file should provide translations for most elements on the main page

Sorry for the confusion, I was referring to the dropdown language selector on https://eslint.org/docs/latest/

[fasttime]

I don't know if it's necessary to remove the Chinese translation from the dropdown selector. Other translations consist of a single yml file (in https://github.com/eslint/eslint.org/tree/main/src/_data/sites) and there is also one for zh-hans. I can't speak about the content, but I guess that yml file should provide translations for most elements on the main page

Sorry for the confusion, I was referring to the dropdown language selector on https://eslint.org/docs/latest/

Ah, got it, thanks. I also think that should be removed.

[kecrily]

Personally, I'd prefer to keep it and plan to align it with the English version soon. But it seems the decision has already been made.

[mdjermanovic]

So for example a user who opens https://zh-hans.eslint.org/docs/latest/rules/no-restricted-globals would be seeing the current English documentation instead of the outdated Chinese page, same as for the other languages.

@fasttime that would be option 3 (redirect requests)?

[mdjermanovic]

I've archived the eslint/eslint-jp repository now. Just a note that the repository wasn't intended for the docs, but creating and triaging issues in Japanese.

[fasttime]

So for example a user who opens https://zh-hans.eslint.org/docs/latest/rules/no-restricted-globals would be seeing the current English documentation instead of the outdated Chinese page, same as for the other languages.

@fasttime that would be option 3 (redirect requests)?

Basically yes, except for pages that should have a standard translation like the main page, Team, Donate, etc. Same as for https://fr.eslint.org/, https://fr.eslint.org/team/, https://fr.eslint.org/donate/, etc.