diff --git a/docs/i18n/chinese/_sidebar.md b/docs/i18n/chinese/_sidebar.md index 065c82b217..b84070d0fc 100644 --- a/docs/i18n/chinese/_sidebar.md +++ b/docs/i18n/chinese/_sidebar.md @@ -16,6 +16,7 @@ - [Add Cypress tests](how-to-add-cypress-tests.md) - [Work on localized client web app](how-to-work-on-localized-client-webapp.md) - [Catch outgoing emails locally](how-to-catch-outgoing-emails-locally.md) + - [Test translations locally](how-to-test-translations-locally.md) --- diff --git a/docs/i18n/chinese/how-to-setup-wsl.md b/docs/i18n/chinese/how-to-setup-wsl.md index 74db769a80..eccdf07ec5 100644 --- a/docs/i18n/chinese/how-to-setup-wsl.md +++ b/docs/i18n/chinese/how-to-setup-wsl.md @@ -6,7 +6,7 @@ > > **Docker Desktop for Windows**: See respective requirements for [Windows 10 Pro](https://docs.docker.com/docker-for-windows/install/#system-requirements) and [Windows 10 Home](https://docs.docker.com/docker-for-windows/install-windows-home/#system-requirements) -This guide covers some common steps with the setup of WSL2. Once some of the common issues with WSL2 are addressed, you should be able to follow the our local setup guide to work with freeCodeCamp on Windows running a WSL distro like Ubuntu. +This guide covers some common steps with the setup of WSL2. Once some of the common issues with WSL2 are addressed, you should be able to follow [this local setup guide](https://contribute.freecodecamp.org/#/how-to-setup-freecodecamp-locally) to work with freeCodeCamp on Windows running a WSL distro like Ubuntu. ## Enable WSL @@ -32,7 +32,7 @@ Follow the instructions on the [official documentation](https://docs.microsoft.c ## Set up Git -Git comes pre-installed with Ubuntu 18.04, verify that your Git version with `git --version`. +Git comes pre-installed with Ubuntu 18.04, verify your Git version with `git --version`. ```output ~ @@ -54,7 +54,7 @@ You can check these settings by going to Settings > Languages & Frameworks > Nod ## Installing Docker Desktop -**Docker Desktop for Windows** allows you to install and run database and services like MongoDB, NGINX, etc. This is useful to avoid common pitfalls with installing MongoDB or other services directly on Windows or WSL2. +**Docker Desktop for Windows** allows you to install and run databases like MongoDB and other services like NGINX and more. This is useful to avoid common pitfalls with installing MongoDB or other services directly on Windows or WSL2. Follow the instructuction on the [official documentation](https://docs.docker.com/docker-for-windows/install) and install Docker Desktop for your Windows distribution. @@ -64,7 +64,7 @@ There are some minimum hardware requirements for the best experience. Once Docker Desktop is installed, [follow these instructions](https://docs.docker.com/docker-for-windows/wsl) and configure it to use the Ubuntu-18.04 installation as a backend. -This makes it so that the containers run on WSL side instead of running on Windows. You will be able to access the services over `http://localhost` on both Windows and Ubuntu. +This makes it so that the containers run on the WSL side instead of running on Windows. You will be able to access the services over `http://localhost` on both Windows and Ubuntu. ## Install MongoDB from Docker Hub diff --git a/docs/i18n/chinese/how-to-test-translations-locally.md b/docs/i18n/chinese/how-to-test-translations-locally.md new file mode 100644 index 0000000000..30691ae9cc --- /dev/null +++ b/docs/i18n/chinese/how-to-test-translations-locally.md @@ -0,0 +1,131 @@ +# How to Test Translations Locally + +> [!NOTE] This process is not required, but documented in case you would like to preview what your translations will look like. + +If you would like to test your translations on a local instance of the freeCodeCamp `/learn` site, first ensure you have [set up the codebase](how-to-setup-freecodecamp-locally.md). + +## Enabling a Language + +There are a few steps to take in order to allow the codebase to build in your desired language. + +First, visit the `config/i18n/all-langs.js` file to add the language to the available languages list and configure the values. There are four objects here. + +- `availableLangs`: For both the `client` and `curriculum` arrays, add the text name of the language. This is the value that will be used in the `.env` file later. +- `i18nextCodes`: These are the ISO language codes for each language. You will need to add the appropriate ISO code for the language you are enabling. These do need to be unique for each language. +- `langDisplayNames`: These are the display names for the language selector in the navigation menu. +- `langCodes`: These are the language codes used for formatting dates and numbers. These should be Unicode CLDR codes instead of ISO codes. + +As an example, if you wanted to enable Dothraki as a language, your `all-langs.js` objects should look like this: + +```js +const availableLangs = { + client: ['english', 'espanol', 'chinese', 'chinese-traditional', 'dothraki'], + curriculum: ['english', 'espanol', 'chinese', 'chinese-traditional', 'dothraki'] +}; + +const i18nextCodes = { + english: 'en', + espanol: 'es', + chinese: 'zh', + 'chinese-traditional': 'zh-Hant', + 'dothraki': 'mis', +}; + +const langDisplayNames = { + english: 'English', + espanol: 'Español', + chinese: '中文（简体字）', + 'chinese-traditional': '中文（繁體字）', + 'dothraki': 'Dothraki', +}; + +const langCodes = { + english: 'en-US', + espanol: 'es-419', + chinese: 'zh', + 'chinese-traditional': 'zh-Hant', + 'dothraki': 'mis', +}; +``` + +Next, open the `client/src/utils/algolia-locale-setup.js` file. This data is used for the search bar that loads `/news` articles. While it is unlikely that you are going to test this functionality, missing the data for your language can lead to errors when attempting to build the codebase locally. + +Add an object for your language to the `algoliaIndices` object. You should use the values for the `english` object for local testing, replacing the `english` key with your language's `availableLangs` value. + +If you were to add Dothraki: + +```js +const algoliaIndices = { + english: { + name: 'news', + searchPage: 'https://www.freecodecamp.org/news/search/' + }, + espanol: { + name: 'news-es', + searchPage: 'https://www.freecodecamp.org/espanol/news/search/' + }, + chinese: { + name: 'news-zh', + searchPage: 'https://chinese.freecodecamp.org/news/search/' + }, + 'chinese-traditional': { + name: 'news-zh', + searchPage: 'https://chinese.freecodecamp.org/news/search' + }, + dothraki: { + name: 'news', + searchPage: 'https://www.freecodecamp.org/news/search/' + }, +}; +``` + +Next, you will need to tell the client which certifications are translated, and which are still in English. Open the `utils/is-audited.js` file. Within the `auditedCerts`, add a new key with your language's `availableLangs` value. Assign the value of that key to an array containing the *dashed names* for the certifications that have been translated. Refer to the existing data for those dashed names. + +Continuing the work to enable Dothraki - we have translated the first three certifications: + +```js +const auditedCerts = { + espanol: [ + 'responsive-web-design', + 'javascript-algorithms-and-data-structures' + ], + chinese: [ + 'responsive-web-design', + 'javascript-algorithms-and-data-structures', + 'front-end-libraries', + 'data-visualization', + 'apis-and-microservices', + 'quality-assurance' + ], + 'chinese-traditional': [ + 'responsive-web-design', + 'javascript-algorithms-and-data-structures', + 'front-end-libraries', + 'data-visualization', + 'apis-and-microservices', + 'quality-assurance' + ], + 'dothraki': [ + 'responsive-web-design', + 'javascript-algorithms-and-data-structures', + 'front-end-libraries' + ] +}; +``` + +Finally, in your `.env` file, set `CLIENT_LOCALE` and `CURRICULUM_LOCALE` to your new language (use the `availableLangs` value.) + +```txt +CLIENT_LOCALE="dothraki" +CURRICULUM_LOCALE="dothraki" +``` + +## Loading Translations + +Because the language has not been approved for production, our scripts are not automatically downloading the translations yet. Only staff have the access to directly download the translations - you are welcome to reach out to us in our [contributors chat room](https://chat.freecodecamp.org/channel/contributors), or you can translate the English markdown files locally for testing purposes. + +Once you have the files, you will need to place them in the correct directory. For the curriculum challenges, you should place the certification folders (i.e. `01-responsive-web-design`) within the `curriculum/challenges/{lang}` directory. For our Dothraki translations, this would be `curriculum/challenges/dothraki`. The client translation `.json` files will go in the `client/i18n/locales/{lang}` directory. + +Once these are in place, you should be able to run `npm run develop` to view your translated version of freeCodeCamp. + +> [!ATTENTION] While you may perform translations locally for the purpose of testing, we remind everyone that translations should *not* be submitted through GitHub and should only be done through Crowdin. Be sure to reset your local codebase after you are done testing. diff --git a/docs/i18n/espanol/_sidebar.md b/docs/i18n/espanol/_sidebar.md index 3b18297a4a..09bf671231 100644 --- a/docs/i18n/espanol/_sidebar.md +++ b/docs/i18n/espanol/_sidebar.md @@ -16,6 +16,7 @@ - [Agregar pruebas de Cypress](how-to-add-cypress-tests.md) - [Work on localized client web app](how-to-work-on-localized-client-webapp.md) - [Catch outgoing emails locally](how-to-catch-outgoing-emails-locally.md) + - [Test translations locally](how-to-test-translations-locally.md) --- diff --git a/docs/i18n/espanol/how-to-setup-wsl.md b/docs/i18n/espanol/how-to-setup-wsl.md index 768a2a3410..5a9fdc8a07 100644 --- a/docs/i18n/espanol/how-to-setup-wsl.md +++ b/docs/i18n/espanol/how-to-setup-wsl.md @@ -6,7 +6,7 @@ > > **Docker Desktop para Windows**: Vea los requisitos correspondientes para [Windows 10 Pro](https://docs.docker.com/docker-for-windows/install/#system-requirements) y [Windows 10 Home](https://docs.docker.com/docker-for-windows/install-windows-home/#system-requirements) -Esta guía cubre algunos pasos comunes con la configuración de WSL2. Una vez resueltos algunos de los problemas comunes con WSL2, debería ser capaz de seguir nuestra guía de configuración local para trabajar con freeCodeCamp en Windows ejecutando una distribución WSL como Ubuntu. +Esta guía cubre algunos pasos comunes con la configuración de WSL2. Once some of the common issues with WSL2 are addressed, you should be able to follow [this local setup guide](https://contribute.freecodecamp.org/#/how-to-setup-freecodecamp-locally) to work with freeCodeCamp on Windows running a WSL distro like Ubuntu. ## Habilitar WSL @@ -32,7 +32,7 @@ Siga las instrucciones de la [documentación oficial](https://docs.microsoft.com ## Configurar Git -Git viene preinstalado con Ubuntu 18.04, verifique su versión de Git con `git --version`. +Git comes pre-installed with Ubuntu 18.04, verify your Git version with `git --version`. ```output ~ @@ -54,7 +54,7 @@ You can check these settings by going to Settings > Languages & Frameworks > Nod ## Instalando Docker Desktop -**Docker Desktop for Windows** allows you to install and run database and services like MongoDB, NGINX, etc. This is useful to avoid common pitfalls with installing MongoDB or other services directly on Windows or WSL2. +**Docker Desktop for Windows** allows you to install and run databases like MongoDB and other services like NGINX and more. This is useful to avoid common pitfalls with installing MongoDB or other services directly on Windows or WSL2. Follow the instructuction on the [official documentation](https://docs.docker.com/docker-for-windows/install) and install Docker Desktop for your Windows distribution. @@ -64,7 +64,7 @@ There are some minimum hardware requirements for the best experience. Once Docker Desktop is installed, [follow these instructions](https://docs.docker.com/docker-for-windows/wsl) and configure it to use the Ubuntu-18.04 installation as a backend. -This makes it so that the containers run on WSL side instead of running on Windows. You will be able to access the services over `http://localhost` on both Windows and Ubuntu. +This makes it so that the containers run on the WSL side instead of running on Windows. You will be able to access the services over `http://localhost` on both Windows and Ubuntu. ## Instalar MongoDB desde Docker Hub diff --git a/docs/i18n/espanol/how-to-test-translations-locally.md b/docs/i18n/espanol/how-to-test-translations-locally.md new file mode 100644 index 0000000000..30691ae9cc --- /dev/null +++ b/docs/i18n/espanol/how-to-test-translations-locally.md @@ -0,0 +1,131 @@ +# How to Test Translations Locally + +> [!NOTE] This process is not required, but documented in case you would like to preview what your translations will look like. + +If you would like to test your translations on a local instance of the freeCodeCamp `/learn` site, first ensure you have [set up the codebase](how-to-setup-freecodecamp-locally.md). + +## Enabling a Language + +There are a few steps to take in order to allow the codebase to build in your desired language. + +First, visit the `config/i18n/all-langs.js` file to add the language to the available languages list and configure the values. There are four objects here. + +- `availableLangs`: For both the `client` and `curriculum` arrays, add the text name of the language. This is the value that will be used in the `.env` file later. +- `i18nextCodes`: These are the ISO language codes for each language. You will need to add the appropriate ISO code for the language you are enabling. These do need to be unique for each language. +- `langDisplayNames`: These are the display names for the language selector in the navigation menu. +- `langCodes`: These are the language codes used for formatting dates and numbers. These should be Unicode CLDR codes instead of ISO codes. + +As an example, if you wanted to enable Dothraki as a language, your `all-langs.js` objects should look like this: + +```js +const availableLangs = { + client: ['english', 'espanol', 'chinese', 'chinese-traditional', 'dothraki'], + curriculum: ['english', 'espanol', 'chinese', 'chinese-traditional', 'dothraki'] +}; + +const i18nextCodes = { + english: 'en', + espanol: 'es', + chinese: 'zh', + 'chinese-traditional': 'zh-Hant', + 'dothraki': 'mis', +}; + +const langDisplayNames = { + english: 'English', + espanol: 'Español', + chinese: '中文（简体字）', + 'chinese-traditional': '中文（繁體字）', + 'dothraki': 'Dothraki', +}; + +const langCodes = { + english: 'en-US', + espanol: 'es-419', + chinese: 'zh', + 'chinese-traditional': 'zh-Hant', + 'dothraki': 'mis', +}; +``` + +Next, open the `client/src/utils/algolia-locale-setup.js` file. This data is used for the search bar that loads `/news` articles. While it is unlikely that you are going to test this functionality, missing the data for your language can lead to errors when attempting to build the codebase locally. + +Add an object for your language to the `algoliaIndices` object. You should use the values for the `english` object for local testing, replacing the `english` key with your language's `availableLangs` value. + +If you were to add Dothraki: + +```js +const algoliaIndices = { + english: { + name: 'news', + searchPage: 'https://www.freecodecamp.org/news/search/' + }, + espanol: { + name: 'news-es', + searchPage: 'https://www.freecodecamp.org/espanol/news/search/' + }, + chinese: { + name: 'news-zh', + searchPage: 'https://chinese.freecodecamp.org/news/search/' + }, + 'chinese-traditional': { + name: 'news-zh', + searchPage: 'https://chinese.freecodecamp.org/news/search' + }, + dothraki: { + name: 'news', + searchPage: 'https://www.freecodecamp.org/news/search/' + }, +}; +``` + +Next, you will need to tell the client which certifications are translated, and which are still in English. Open the `utils/is-audited.js` file. Within the `auditedCerts`, add a new key with your language's `availableLangs` value. Assign the value of that key to an array containing the *dashed names* for the certifications that have been translated. Refer to the existing data for those dashed names. + +Continuing the work to enable Dothraki - we have translated the first three certifications: + +```js +const auditedCerts = { + espanol: [ + 'responsive-web-design', + 'javascript-algorithms-and-data-structures' + ], + chinese: [ + 'responsive-web-design', + 'javascript-algorithms-and-data-structures', + 'front-end-libraries', + 'data-visualization', + 'apis-and-microservices', + 'quality-assurance' + ], + 'chinese-traditional': [ + 'responsive-web-design', + 'javascript-algorithms-and-data-structures', + 'front-end-libraries', + 'data-visualization', + 'apis-and-microservices', + 'quality-assurance' + ], + 'dothraki': [ + 'responsive-web-design', + 'javascript-algorithms-and-data-structures', + 'front-end-libraries' + ] +}; +``` + +Finally, in your `.env` file, set `CLIENT_LOCALE` and `CURRICULUM_LOCALE` to your new language (use the `availableLangs` value.) + +```txt +CLIENT_LOCALE="dothraki" +CURRICULUM_LOCALE="dothraki" +``` + +## Loading Translations + +Because the language has not been approved for production, our scripts are not automatically downloading the translations yet. Only staff have the access to directly download the translations - you are welcome to reach out to us in our [contributors chat room](https://chat.freecodecamp.org/channel/contributors), or you can translate the English markdown files locally for testing purposes. + +Once you have the files, you will need to place them in the correct directory. For the curriculum challenges, you should place the certification folders (i.e. `01-responsive-web-design`) within the `curriculum/challenges/{lang}` directory. For our Dothraki translations, this would be `curriculum/challenges/dothraki`. The client translation `.json` files will go in the `client/i18n/locales/{lang}` directory. + +Once these are in place, you should be able to run `npm run develop` to view your translated version of freeCodeCamp. + +> [!ATTENTION] While you may perform translations locally for the purpose of testing, we remind everyone that translations should *not* be submitted through GitHub and should only be done through Crowdin. Be sure to reset your local codebase after you are done testing. diff --git a/docs/i18n/portuguese/_sidebar.md b/docs/i18n/portuguese/_sidebar.md index 065c82b217..b84070d0fc 100644 --- a/docs/i18n/portuguese/_sidebar.md +++ b/docs/i18n/portuguese/_sidebar.md @@ -16,6 +16,7 @@ - [Add Cypress tests](how-to-add-cypress-tests.md) - [Work on localized client web app](how-to-work-on-localized-client-webapp.md) - [Catch outgoing emails locally](how-to-catch-outgoing-emails-locally.md) + - [Test translations locally](how-to-test-translations-locally.md) --- diff --git a/docs/i18n/portuguese/how-to-setup-wsl.md b/docs/i18n/portuguese/how-to-setup-wsl.md index 74db769a80..eccdf07ec5 100644 --- a/docs/i18n/portuguese/how-to-setup-wsl.md +++ b/docs/i18n/portuguese/how-to-setup-wsl.md @@ -6,7 +6,7 @@ > > **Docker Desktop for Windows**: See respective requirements for [Windows 10 Pro](https://docs.docker.com/docker-for-windows/install/#system-requirements) and [Windows 10 Home](https://docs.docker.com/docker-for-windows/install-windows-home/#system-requirements) -This guide covers some common steps with the setup of WSL2. Once some of the common issues with WSL2 are addressed, you should be able to follow the our local setup guide to work with freeCodeCamp on Windows running a WSL distro like Ubuntu. +This guide covers some common steps with the setup of WSL2. Once some of the common issues with WSL2 are addressed, you should be able to follow [this local setup guide](https://contribute.freecodecamp.org/#/how-to-setup-freecodecamp-locally) to work with freeCodeCamp on Windows running a WSL distro like Ubuntu. ## Enable WSL @@ -32,7 +32,7 @@ Follow the instructions on the [official documentation](https://docs.microsoft.c ## Set up Git -Git comes pre-installed with Ubuntu 18.04, verify that your Git version with `git --version`. +Git comes pre-installed with Ubuntu 18.04, verify your Git version with `git --version`. ```output ~ @@ -54,7 +54,7 @@ You can check these settings by going to Settings > Languages & Frameworks > Nod ## Installing Docker Desktop -**Docker Desktop for Windows** allows you to install and run database and services like MongoDB, NGINX, etc. This is useful to avoid common pitfalls with installing MongoDB or other services directly on Windows or WSL2. +**Docker Desktop for Windows** allows you to install and run databases like MongoDB and other services like NGINX and more. This is useful to avoid common pitfalls with installing MongoDB or other services directly on Windows or WSL2. Follow the instructuction on the [official documentation](https://docs.docker.com/docker-for-windows/install) and install Docker Desktop for your Windows distribution. @@ -64,7 +64,7 @@ There are some minimum hardware requirements for the best experience. Once Docker Desktop is installed, [follow these instructions](https://docs.docker.com/docker-for-windows/wsl) and configure it to use the Ubuntu-18.04 installation as a backend. -This makes it so that the containers run on WSL side instead of running on Windows. You will be able to access the services over `http://localhost` on both Windows and Ubuntu. +This makes it so that the containers run on the WSL side instead of running on Windows. You will be able to access the services over `http://localhost` on both Windows and Ubuntu. ## Install MongoDB from Docker Hub diff --git a/docs/i18n/portuguese/how-to-test-translations-locally.md b/docs/i18n/portuguese/how-to-test-translations-locally.md new file mode 100644 index 0000000000..30691ae9cc --- /dev/null +++ b/docs/i18n/portuguese/how-to-test-translations-locally.md @@ -0,0 +1,131 @@ +# How to Test Translations Locally + +> [!NOTE] This process is not required, but documented in case you would like to preview what your translations will look like. + +If you would like to test your translations on a local instance of the freeCodeCamp `/learn` site, first ensure you have [set up the codebase](how-to-setup-freecodecamp-locally.md). + +## Enabling a Language + +There are a few steps to take in order to allow the codebase to build in your desired language. + +First, visit the `config/i18n/all-langs.js` file to add the language to the available languages list and configure the values. There are four objects here. + +- `availableLangs`: For both the `client` and `curriculum` arrays, add the text name of the language. This is the value that will be used in the `.env` file later. +- `i18nextCodes`: These are the ISO language codes for each language. You will need to add the appropriate ISO code for the language you are enabling. These do need to be unique for each language. +- `langDisplayNames`: These are the display names for the language selector in the navigation menu. +- `langCodes`: These are the language codes used for formatting dates and numbers. These should be Unicode CLDR codes instead of ISO codes. + +As an example, if you wanted to enable Dothraki as a language, your `all-langs.js` objects should look like this: + +```js +const availableLangs = { + client: ['english', 'espanol', 'chinese', 'chinese-traditional', 'dothraki'], + curriculum: ['english', 'espanol', 'chinese', 'chinese-traditional', 'dothraki'] +}; + +const i18nextCodes = { + english: 'en', + espanol: 'es', + chinese: 'zh', + 'chinese-traditional': 'zh-Hant', + 'dothraki': 'mis', +}; + +const langDisplayNames = { + english: 'English', + espanol: 'Español', + chinese: '中文（简体字）', + 'chinese-traditional': '中文（繁體字）', + 'dothraki': 'Dothraki', +}; + +const langCodes = { + english: 'en-US', + espanol: 'es-419', + chinese: 'zh', + 'chinese-traditional': 'zh-Hant', + 'dothraki': 'mis', +}; +``` + +Next, open the `client/src/utils/algolia-locale-setup.js` file. This data is used for the search bar that loads `/news` articles. While it is unlikely that you are going to test this functionality, missing the data for your language can lead to errors when attempting to build the codebase locally. + +Add an object for your language to the `algoliaIndices` object. You should use the values for the `english` object for local testing, replacing the `english` key with your language's `availableLangs` value. + +If you were to add Dothraki: + +```js +const algoliaIndices = { + english: { + name: 'news', + searchPage: 'https://www.freecodecamp.org/news/search/' + }, + espanol: { + name: 'news-es', + searchPage: 'https://www.freecodecamp.org/espanol/news/search/' + }, + chinese: { + name: 'news-zh', + searchPage: 'https://chinese.freecodecamp.org/news/search/' + }, + 'chinese-traditional': { + name: 'news-zh', + searchPage: 'https://chinese.freecodecamp.org/news/search' + }, + dothraki: { + name: 'news', + searchPage: 'https://www.freecodecamp.org/news/search/' + }, +}; +``` + +Next, you will need to tell the client which certifications are translated, and which are still in English. Open the `utils/is-audited.js` file. Within the `auditedCerts`, add a new key with your language's `availableLangs` value. Assign the value of that key to an array containing the *dashed names* for the certifications that have been translated. Refer to the existing data for those dashed names. + +Continuing the work to enable Dothraki - we have translated the first three certifications: + +```js +const auditedCerts = { + espanol: [ + 'responsive-web-design', + 'javascript-algorithms-and-data-structures' + ], + chinese: [ + 'responsive-web-design', + 'javascript-algorithms-and-data-structures', + 'front-end-libraries', + 'data-visualization', + 'apis-and-microservices', + 'quality-assurance' + ], + 'chinese-traditional': [ + 'responsive-web-design', + 'javascript-algorithms-and-data-structures', + 'front-end-libraries', + 'data-visualization', + 'apis-and-microservices', + 'quality-assurance' + ], + 'dothraki': [ + 'responsive-web-design', + 'javascript-algorithms-and-data-structures', + 'front-end-libraries' + ] +}; +``` + +Finally, in your `.env` file, set `CLIENT_LOCALE` and `CURRICULUM_LOCALE` to your new language (use the `availableLangs` value.) + +```txt +CLIENT_LOCALE="dothraki" +CURRICULUM_LOCALE="dothraki" +``` + +## Loading Translations + +Because the language has not been approved for production, our scripts are not automatically downloading the translations yet. Only staff have the access to directly download the translations - you are welcome to reach out to us in our [contributors chat room](https://chat.freecodecamp.org/channel/contributors), or you can translate the English markdown files locally for testing purposes. + +Once you have the files, you will need to place them in the correct directory. For the curriculum challenges, you should place the certification folders (i.e. `01-responsive-web-design`) within the `curriculum/challenges/{lang}` directory. For our Dothraki translations, this would be `curriculum/challenges/dothraki`. The client translation `.json` files will go in the `client/i18n/locales/{lang}` directory. + +Once these are in place, you should be able to run `npm run develop` to view your translated version of freeCodeCamp. + +> [!ATTENTION] While you may perform translations locally for the purpose of testing, we remind everyone that translations should *not* be submitted through GitHub and should only be done through Crowdin. Be sure to reset your local codebase after you are done testing.