docs: add Russian translation

[dragomano]

Added localization: Russian

• Added translated website/docs/ru pages
• Updated website/i18n.json
• Updated website/rspress.config.ts
• Updated website/tsconfig.json

Found issues

Incorrect word wrapping:

How to fix:

.rp-overview-group__item__title {
    word-break: break-all; // <= it should be removed

[Timeless0911]

Thank you for contributing the Russian documentation translation to the project. This demonstrates your strong support for the Rspress project, and we greatly value your contribution.

Currently, our main challenge is a shortage of team members, making it difficult to maintain multilingual documentation stably and long-term. To ensure accuracy and synchronized updates, we currently only maintain both Chinese and English versions of the documentation in the repository to guarantee information quality and consistency.

However, we would greatly appreciate extending i18n capabilities to the built-in text of the project. If it's convenient for you, you could submit a PR to modify DEFAULT_I18N_TEXT.ts to enhance built-in i18n support for Russian.

Thank you again for your contribution!

[dragomano]

I'm not quite sure I understood correctly. Do you only need the translation of the DEFAULT_I18N_TEXT.ts file from this PR, and nothing else?

In that case, is there an option to specify a link to an external repository for a particular language?

[Timeless0911]

Do you only need the translation of the DEFAULT_I18N_TEXT.ts file from this PR, and nothing else?

Yeah, that's correct.

In that case, is there an option to specify a link to an external repository for a particular language?

Since Rspress v2 is currently in the RC stage with actively documentation development, with numerous changes, now is not a good time for initial translation of other languages.

Specify a link to an external repository is the approach we can achieve in the future. However, this requires building a workflow that synchronizes changes to the main repository and automatically translates them to ensure real-time document updates. Otherwise, the authors of external repositories would need to sync the docs updates frequently which is crazy.

[Karibash]

I’m not a member of the Rstack team, but based on my general experience with open source projects, I’d like to share a bit of context that might help.

Once code is merged into the Rspress repository, it becomes something the Rstack team is responsible for maintaining. That means if there are typos, wording improvements, or new documentation pages added in the future, they also need to keep the Russian version accurate and up to date.

Additionally, Rstack doesn’t only maintain Rspress; they also look after projects like Rspack and Rsbuild. If only Rspress officially supported Russian, it might feel a bit inconsistent, and other Russian-speaking users might start asking for Russian support in Rspack and Rsbuild as well. Without native Russian speakers on the team, that could quickly become difficult for them to sustain.

In many open source projects, for changes as large and impactful as adding a new language, maintainers usually prefer to discuss things in an issue before a PR is opened. That way, everyone can confirm whether the change fits their long-term plans and maintenance capacity. It’s really unfortunate when someone spends time on a big PR and it ends up being closed, so this kind of discussion up front can help avoid that situation for both contributors and maintainers.

[dragomano]

Regarding localization synchronization: you could set up exporting the English source files to Crowdin, or implement some kind of tracker similar to what Starlight does.