Missing Localized Content Despite Language Switch

[Varavchik18]

Issue: Missing Localized Content Despite Language Switch / Mention of Crowdin

Problem

The documentation site (e.g. this page) shows a language switcher, yet it provides no actual translations in any language other than English. This causes user confusion. Although the docs mention the use of Crowdin for localization, it’s unclear if any translations are in progress or if Crowdin is actively used.

Additionally, Ukrainian is mentioned on the official Solana website as a supported/recognized language. It would be beneficial to extend that support here by having Ukrainian as an option on the documentation site — but only if there is actual translated content.

Proposed Solution

1. Confirm whether Crowdin is genuinely being used for localization.
   • If no localization is currently in progress, remove the language switcher to avoid misleading users.
   • If localization is planned or ongoing, share details on where contributors can help (e.g. Crowdin project URL, guidelines, etc.).
2. Consider storing localized content in a folder structure like docs/locales/{locale}, ensuring that each listed language in the switcher matches actual translated files.
3. Include Ukrainian as a valid language option, in line with the official Solana site’s mention of Ukrainian support. I’m ready to assist with translating the docs into Ukrainian and writing contributing guidelines for translators if there’s interest and a clear workflow.

If localization is not a priority or Crowdin isn’t actively used, it might be best to remove the language switcher until translations become available.

[Varavchik18]

any thoughts on this ?

[Varavchik18]

I've finished more deep research and here is the discovered flow how localization is implemented in docs project:

1. Docusaurus has i18n config that provides a possibility to specify the list of supported languages ( populates the dropdown with locales on the page)
2. Integration with crowdin provides as a flow where we downloading the translation from crowdin in a json file that i18n uses for translation.
3. Seems like agave project has only english translation available on a crowdin since like npx docusaurus write-translations generates only one locale folder with translations. And this is the reason why we are not reflecting the changes of selected locale.

Since this issue is ignored for a few weeks I would like to say that the only visible for me solution how to implement multi-language localization support is to provide a public access for crowdin to allow community make a translation for their language.

@HaoranYi @steviez @brooksprumo is that possible , how do you think ?

[steviez]

I'll start by noting that I'm not very familiar with localization "best practices"

With that stated, I'd be hesitant to add anything to the Anza docs that has not been reviewed by Anza. And while Anza does have members who speak multiple languages, translating these would be a large effort and we have many other things currently keeping us busy

If no localization is currently in progress, remove the language switcher to avoid misleading users.

I'm somewhat leaning this way as the "solution"

that the only visible for me solution how to implement multi-language localization support is to provide a public access for crowdin to allow community make a translation for their language.

I'm not exactly sure what you're proposing here, but this seems like a problem waiting to happen. Namely, someone might try to sneak some bad instructions in, and it would be difficult for us (Anza) to detect if we don't natively speak the language.