i18n(pages): add Russian (ru) locale to the documentation site

[lizhengfeng101]

Summary

Our documentation website (pages/) currently supports English, Chinese, and Japanese. The project README already has a Russian translation (README.ru-RU.md), but the docs site does not yet have a Russian locale. We are looking for a native Russian speaker to help us add and maintain Russian translations.

Scope

The following English docs need to be translated into Russian under pages/src/content/docs/ru/:

• quickstart.md
• installation.md
• configuration.md
• cli-reference.md
• architecture.md
• review-rules.md
• tools.md
• mcp.md
• viewer.md
• telemetry.md
• faq.md
• contributing.md
• integrations/ci.md
• integrations/claude-code.md
• integrations/delegate.md
• integrations/agent-skill.md

Additionally, you will need to register the ru locale in the site configuration (see how zh and ja are registered in pages/src/content/docs/index.ts).

Requirements

• Native Russian speaker preferred — natural, idiomatic Russian rather than machine translation
• Keep technical terms (CLI flags, API names, config keys) in their original English form
• Maintain consistent terminology throughout all pages
• Follow the existing structure of other locale directories (en/, zh/, ja/)

Ongoing Maintenance

This is not a one-time task. As the English documentation evolves, the Russian translation will need to be kept in sync. The contributor who takes this on should be willing to periodically update the Russian docs when the English source changes. We will tag the contributor on relevant PRs for awareness.

How to Get Started

1. Look at pages/src/content/docs/ja/ or pages/src/content/docs/zh/ as reference for how existing translations are structured
2. Create a pages/src/content/docs/ru/ directory
3. Start with quickstart.md and installation.md — submit a PR for review
4. Continue with the remaining pages in follow-up PRs (one PR per 2–4 pages is ideal)

Notes

• You don't need to translate everything in one PR — incremental contributions are welcome
• If you're unsure about how to translate a specific concept, open a discussion or leave a comment
• AI-assisted translation is acceptable as a starting draft, but must be reviewed and refined by a native speaker

[chethanuk]

Let me give it a try..

[lizhengfeng101]

Hey @chethanuk, thanks for jumping in! 🙌

Just a heads-up — this one ideally needs a native Russian speaker since it involves ongoing translation maintenance and we want the docs to feel natural to Russian-speaking users. Are you a native speaker by any chance?

Either way, I really appreciate how active you've been — your contributions have been fantastic. If you're looking for more to work on, I'd love to point you toward some of the meatier issues where your skills would really shine. Just let me know!

[chethanuk]

Oh - Then lets better wait for someone else - in last project had used i18n + LLM to do - so thought will give it a try..

[lizhengfeng101]

Thanks for understanding, @chethanuk! Let's wait a bit and see if a native Russian speaker shows up. In the meantime, I've sent you an email at chethanuk@outlook.com to chat further. 🙏

[chethanuk]

you an email at chethanuk@outlook.com to chat further

Just read thank you :)