Node.js is a global platform, so this site has many translations. We use Crowdin to translate the Node.js Website

The site's translation into languages other than English is handled by Crowdin translators.

We use next-intl as our Internationalization Library. We recommend reading its documentation for API usage.

1. Request to join the Node.js Website project on Crowdin
2. Select the language you want to translate
3. Start translating

If you have any questions or feedbacks on current translations, you can start a discussion by choosing the "New Topic" and your language from the right dropdown, or a conversation by adding your translators.

Open discussion on the Crowdin project to request a new language. After wait for the language to be added to the project by the Crowdin manager

After that, one of the member of the Node.js Website team should add the new language to the project.

Go on /i18n/config.json and add the new language to the locales array.

Fill the language object with the following fields:

{
  "code": "fr",
  "localName": "Français",
  "name": "French",
  "langDir": "ltr",
  "dateFormat": "DD.MM.YYYY",
  "hrefLang": "fr",
  "enabled": true
}

If you're making a new Component and adding Translation Keys for your Component, they should follow these guidelines:

• Only add the new translation keys on the i18n/locales/en.json file. Crowdin will handle on syncing the files and letting translators know there are new keys to be translated
• The translation keys should have the prefix as the canonical path of your Component. If your Component is components/Common/MyComponent the prefix key should be components.common.myComponent
  • The Translation Key suffix should be easy to understand and semantic. For example, if the key is about "the text of a button that when interacted it copies content to the clipboard", the suffix should probably be copyButton.title. The final translation key would be components.common.myComponent.copyButton.title
  • Translation Keys should be in Camel Case only.
  • The values of each Translation Key should follow the ICU Message Syntax
• All new Translation keys should be added at the bottom of the i18n/locales/en.json file. Since this makes it easier for Translators to notice that there are new Translation keys to be translated.

It's important to mention that we use nested translation keys within the Locale files. This means that if your translation key is components.common.myComponent.something, you should actually define the key and value within:

{
  "components": {
    ...,
    "common": {
      ...,
      "myComponent": {
        "something": "value of translation key"
      }
    }
  }
}

Translation Keys should not be translated during Unit Testing. If your Component uses, for example useTranslations, you should provide the <NextIntlProvider> surrounding your testing-library render logic, or you can create a wrapper for your test. Note that you should not import the English messages to your Unit Test as:

• Unit Testing should test a Component functionality.
• Unit Tests should not rely on text, titles, or string bags, as these texts will change arbitrarily and make the test suite fail.
  • In this case, you should test your component by aria-text, or other aria-* attributes or even by class names or other artifacts.
• Visual Regression Testing is recommended to test how different languages and text appear within a Component.