diff --git a/docs/i18n/chinese/FAQ.md b/docs/i18n/chinese/FAQ.md index 39c0fdf71c..412520742c 100644 --- a/docs/i18n/chinese/FAQ.md +++ b/docs/i18n/chinese/FAQ.md @@ -8,7 +8,7 @@ Yes - You can contribute to any of the 30+ languages we have enabled on our tran We have the user contributed translations live in Chinese (中文) and Spanish (Español). We intend to localize freeCodeCamp into several major world languages. You can read all about this in our [announcement here](https://www.freecodecamp.org/news/world-language-translation-effort). -If you are interested in contributing to translations please makes sure you [read this guide](/how-to-translate-files) first. +If you are interested in contributing to translations please makes sure you [read this guide](how-to-translate-files.md) first. ### How can I report a new bug? diff --git a/docs/i18n/chinese/codebase-best-practices.md b/docs/i18n/chinese/codebase-best-practices.md index 0653a85904..80481a0a35 100644 --- a/docs/i18n/chinese/codebase-best-practices.md +++ b/docs/i18n/chinese/codebase-best-practices.md @@ -2,7 +2,7 @@ ## General JavaScript -In most cases, our [linter](how-to-setup-freecodecamp-locally?id=follow-these-steps-to-get-your-development-environment-ready) will warn of any formatting which goes against this codebase's preferred practice. +In most cases, our [linter](how-to-setup-freecodecamp-locally.md#follow-these-steps-to-get-your-development-environment-ready) will warn of any formatting which goes against this codebase's preferred practice. It is encouraged to use functional components over class-based components. diff --git a/docs/i18n/chinese/how-to-open-a-pull-request.md b/docs/i18n/chinese/how-to-open-a-pull-request.md index d9b942ee9b..f096e7e13b 100644 --- a/docs/i18n/chinese/how-to-open-a-pull-request.md +++ b/docs/i18n/chinese/how-to-open-a-pull-request.md @@ -2,7 +2,7 @@ A pull request (PR) enables you to send changes from your fork on GitHub to freeCodeCamp.org's main repository. Once you are done making changes to the code, you can follow these guidelines to open a PR. -> [!NOTE] Your PR should be in English. See [here](https://contribute.freecodecamp.org/#/index?id=translations) for how to contribute translations. +> [!NOTE] Your PR should be in English. See [here](index.md#translations) for how to contribute translations. ## Prepare a good PR title @@ -68,7 +68,7 @@ Some examples of good PRs titles would be: - This is very important when making changes that are not just edits to text content like documentation or a challenge description. Examples of changes that need local testing include JavaScript, CSS, or HTML which could change the functionality or layout of a page. - - If your PR affects the behaviour of a page it should be accompanied by corresponding [Cypress integration tests](/how-to-add-cypress-tests). + - If your PR affects the behaviour of a page it should be accompanied by corresponding [Cypress integration tests](how-to-add-cypress-tests.md). ## Feedback on pull requests @@ -78,7 +78,7 @@ Our moderators will now take a look and leave you feedback. Please be patient wi And as always, feel free to ask questions on the ['Contributors' category on our forum](https://forum.freecodecamp.org/c/contributors) or [the contributors chat room](https://chat.freecodecamp.org/channel/contributors). -> [!TIP] If you are to be contributing more pull requests, we recommend you read the [making changes and syncing](https://contribute.freecodecamp.org/#/how-to-setup-freecodecamp-locally?id=making-changes-locally) guidelines to avoid having to delete your fork. +> [!TIP] If you are to be contributing more pull requests, we recommend you read the [making changes and syncing](how-to-setup-freecodecamp-locally.md#making-changes-locally) guidelines to avoid having to delete your fork. ## Conflicts on a pull request diff --git a/docs/i18n/chinese/how-to-proofread-files.md b/docs/i18n/chinese/how-to-proofread-files.md index d862d03973..1116dc9360 100644 --- a/docs/i18n/chinese/how-to-proofread-files.md +++ b/docs/i18n/chinese/how-to-proofread-files.md @@ -14,7 +14,7 @@ You should see the list of projects you have been granted access to. Select the You should now see the list of available files. Choose your file by selecting the `Proofread` button on the right of that file, then choosing `Proofreading` from the drop-down menu that appears. -> [!NOTE] 如果你在工作区视图（workspace view）中，但想要[翻译文件](./how-to-translate-files.md)，而不是校对文件，那么你可以从下拉菜单中选择 `Crowdsourcing`。 +> [!NOTE] If you are in this workspace view, but want to work on [translating a file](how-to-translate-files.md) instead of proofreading, you may select `Crowdsourcing` from the dropdown menu instead. ## 校对译文 diff --git a/docs/i18n/chinese/how-to-setup-freecodecamp-locally.md b/docs/i18n/chinese/how-to-setup-freecodecamp-locally.md index 462a02621f..7d74162552 100644 --- a/docs/i18n/chinese/how-to-setup-freecodecamp-locally.md +++ b/docs/i18n/chinese/how-to-setup-freecodecamp-locally.md @@ -14,7 +14,7 @@ Start by installing the prerequisite software for your operating system. We primarily support development on Linux and Unix-based systems. Our staff and community contributors regularly work with the codebase using tools installed on Ubuntu and macOS. -We also support Windows 10 via WSL2, which you can prepare by [reading this guide](/how-to-setup-wsl). +We also support Windows 10 via WSL2, which you can prepare by [reading this guide](how-to-setup-wsl.md). Some community members also develop on Windows 10 natively with Git for Windows (Git Bash), and other tools installed on Windows. We do not have official support for such a setup at this time, we recommend using WSL2 instead. diff --git a/docs/i18n/chinese/how-to-setup-wsl.md b/docs/i18n/chinese/how-to-setup-wsl.md index eccdf07ec5..00588667cd 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 [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. +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](how-to-setup-freecodecamp-locally.md) to work with freeCodeCamp on Windows running a WSL distro like Ubuntu. ## Enable WSL @@ -119,7 +119,7 @@ npm install -g npm@latest ## Set up freeCodeCamp locally -Now that you have installed the pre-requisites, follow [our local setup guide](https://contribute.freecodecamp.org/#/how-to-setup-freecodecamp-locally) to clone, install and setup freeCodeCamp locally on your machine. +Now that you have installed the pre-requisites, follow [our local setup guide](how-to-setup-freecodecamp-locally.md) to clone, install and setup freeCodeCamp locally on your machine. > [!WARNING] > diff --git a/docs/i18n/chinese/how-to-work-on-coding-challenges.md b/docs/i18n/chinese/how-to-work-on-coding-challenges.md index 9bf379c2ca..f671bb00a6 100644 --- a/docs/i18n/chinese/how-to-work-on-coding-challenges.md +++ b/docs/i18n/chinese/how-to-work-on-coding-challenges.md @@ -476,7 +476,7 @@ You are also able to test one challenge individually by performing the following ``` npm run test -- -g challenge-title-goes-here ``` -Once you have verified that each challenge you've worked on passes the tests, [please create a pull request](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/docs/how-to-open-a-pull-request.md). +Once you have verified that each challenge you've worked on passes the tests, [please create a pull request](how-to-open-a-pull-request.md). > [!TIP] You can set the environment variable `LOCALE` in the `.env` to the language of the challenge(s) you need to test. > diff --git a/docs/i18n/chinese/how-to-work-on-localized-client-webapp.md b/docs/i18n/chinese/how-to-work-on-localized-client-webapp.md index 8425ead979..73ec325f42 100644 --- a/docs/i18n/chinese/how-to-work-on-localized-client-webapp.md +++ b/docs/i18n/chinese/how-to-work-on-localized-client-webapp.md @@ -2,13 +2,13 @@ The react based client web app that powers our learning platform is built using Gatsby. It is translated into various world languages using [react-i18next](https://react.i18next.com/) and [i18next](https://www.i18next.com/). -You can learn more about setting up the client application locally for development by following [our local setup guide here](/how-to-setup-freecodecamp-locally). By default the application is available only in English. +You can learn more about setting up the client application locally for development by following [our local setup guide here](how-to-setup-freecodecamp-locally.md). By default the application is available only in English. Once you have setup the project locally you should be able to follow this documentation to run the client in the language of your choice from the list of available languages. This could be helpful when you are working on a feature that specifically targets something that involves localization, and requires you to validate for instance a button's label in a different language. -> [!TIP] You do not need to follow this document for translating freeCodeCamp's curriculum or contributing documentation. Read [this guide here](./how-to-translate-files.md) instead. +> [!TIP] You do not need to follow this document for translating freeCodeCamp's curriculum or contributing documentation. Read [this guide here](how-to-translate-files.md) instead. Let's understand how the i18n frameworks and tooling work. @@ -67,7 +67,7 @@ Some of these files are translated on our translation platform (Crowdin), some a - The `intro.json` file contains the key-value pairs for the introduction text on the certification pages. - If you want to add/update translations for the keys please [read this guide here](/how-to-translate-files.md). + If you want to add/update translations for the keys please [read this guide here](how-to-translate-files.md). **Files NOT translated on our translations platform:** diff --git a/docs/i18n/chinese/how-to-work-on-practice-projects.md b/docs/i18n/chinese/how-to-work-on-practice-projects.md index 8b57f216eb..16782c1977 100644 --- a/docs/i18n/chinese/how-to-work-on-practice-projects.md +++ b/docs/i18n/chinese/how-to-work-on-practice-projects.md @@ -12,7 +12,7 @@ If you want to create new steps, the following tools simplify that process. A one-off script that will automatically add the next step based on the last step numbered as `part-xxx.md` where `xxx` represents the 3-digit step number of the last step. The challenge seed code will use the previous step's challenge seed code with the editable region markers (ERMs) removed. -**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps). +**Note:** This script also runs [reorder-steps](#reorder-steps). ### How to run script: @@ -27,7 +27,7 @@ npm run create-next-step A one-off script that automatically adds a specified number of steps at a specific starting step number. The challenge seed code for all steps created will be empty. -**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps). +**Note:** This script also runs [reorder-steps](#reorder-steps). ### How to run script: @@ -42,7 +42,7 @@ npm run create-empty-steps start=X num=Y # where X is the starting step number a A one-off script that automatically adds a new step between two existing consecutive steps. The challenge seed code will use the existing starting step's challenge seed code with the editable region markers (ERMs) removed. -**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps). +**Note:** This script also runs [reorder-steps](#reorder-steps). ### How to run script: diff --git a/docs/i18n/chinese/index.md b/docs/i18n/chinese/index.md index 05745f4ce0..19260c4b1f 100644 --- a/docs/i18n/chinese/index.md +++ b/docs/i18n/chinese/index.md @@ -10,7 +10,7 @@ - 帮助我们修复 freeCodeCamp.org 的[学习平台](#learning-platform)中的 bug 。 - [帮助我们翻译](#translations) freeCodeCamp.org 的内容为各种语言。 -我们在这里回答了贡献者最常见的一些问题：[有关贡献者的 FAQ](/FAQ.md). +We answer the most common questions about contributing [in our contributor FAQ](FAQ.md). ## 课程 diff --git a/docs/i18n/chinese/moderator-handbook.md b/docs/i18n/chinese/moderator-handbook.md index a1762f28e5..4c5e6407b3 100644 --- a/docs/i18n/chinese/moderator-handbook.md +++ b/docs/i18n/chinese/moderator-handbook.md @@ -18,7 +18,7 @@ freeCodeCamp is an inclusive community, and we need to keep it that way. We have a single code of conduct that governs our entire community. The fewer the rules, the easier they are to remember. You can read those rules and commit them to memory [here](https://code-of-conduct.freecodecamp.org). -> [!NOTE] As a moderator we would add you to one or more teams on GitHub, our community forum(s) & chat servers. If you are missing access on a platform that you would like to moderate please [reach out to a staff member](/FAQ?id=additional-assistance). +> [!NOTE] As a moderator we would add you to one or more teams on GitHub, our community forum(s) & chat servers. If you are missing access on a platform that you would like to moderate please [reach out to a staff member](FAQ.md#additional-assistance). ## Moderating GitHub @@ -39,7 +39,7 @@ You can help us organize and triage the issue reports by applying labels from [t Please pay special attention to the labels `"help wanted"` and `"first timers only"`. These are to be added to threads that you think can be opened up to potential contributors for making a pull request. -A `"first timer only"` label should be applied to a trivial issue (ex. a typo fix) and should include additional information. You can use this [reply template](/moderator-handbook?id=first-timer-only-issues) for triage. +A `"first timer only"` label should be applied to a trivial issue (ex. a typo fix) and should include additional information. You can use this [reply template](moderator-handbook.md#first-timer-only-issues) for triage. #### Closing Stale, Outdated, Inactive Issues and Pull Requests @@ -49,7 +49,7 @@ A `"first timer only"` label should be applied to a trivial issue (ex. a typo fi - If the contributor asks for additional assistance or even time, the above can be relaxed and revisited after a response is given. In any case, the mods should use their best judgment to resolve the outstanding PR's status. -> [!TIP] We recommend you use this list of standard [reply templates](https://contribute.freecodecamp.org/#/moderator-handbook?id=reply-templates) while triaging issues. +> [!TIP] We recommend you use this list of standard [reply templates](moderator-handbook.md#reply-templates) while triaging issues. ### Moderating Pull Requests @@ -63,7 +63,7 @@ Pull Requests (PRs) are how contributors submit changes to freeCodeCamp's reposi You can also review these right on GitHub and decide whether to merge them. We need to be a bit more careful about these because millions of people will encounter this text as they work through the freeCodeCamp curriculum. Does the pull request make the text more clear without making it much longer? Are the edits relevant and not overly pedantic? Remember that our goal is for challenges to be as clear and as short as possible. They aren't the place for obscure details. Contributors may try to add links to resources to the challenges. - You can close invalid pull requests and reply to them with these [reply templates](https://contribute.freecodecamp.org/#/moderator-handbook?id=closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). If the change looks good, please ensure to leave an approval with a "LGTM" comment. Once a pull request gets at least two approvals (including yours) from the moderators or the dev-team, you can go ahead and merge it. @@ -75,7 +75,7 @@ Pull Requests (PRs) are how contributors submit changes to freeCodeCamp's reposi Some contributors may try to add additional tests to cover pedantic corner-cases. We need to be careful to not make the challenge too complicated. These challenges and their tests should be as simple and intuitive as possible. Aside from the algorithm challenges and interview prep section, learners should be able to solve each challenge within about 2 minutes. - You can close invalid pull requests and reply to them with these [reply templates](https://contribute.freecodecamp.org/#/moderator-handbook?id=closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). If the change looks good, please ensure to leave an approval with a "LGTM" comment. Once a pull request gets at least two approvals (including yours) from the moderators or the dev-team, you can go ahead and merge it. @@ -142,7 +142,7 @@ Often, a pull request will be low effort. You can usually tell this immediately There are also situations where the contributor is trying to add a link to their website, include a library they created, or have a frivolous edit that doesn't help anyone but themselves. -You can close invalid pull requests and reply to them with these [reply templates](https://contribute.freecodecamp.org/#/moderator-handbook?id=closing-invalid-pull-requests). +You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). #### Other guidelines for Moderators on GitHub @@ -387,7 +387,7 @@ Once you resolve these issues, we will be able to review your PR and merge it. --- -Feel free to reference the [contributing guidelines](https://contribute.freecodecamp.org/#/how-to-work-on-coding-challenges?id=testing-challenges) for instructions on running the CI build locally. ✅ +Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ ``` ### Syncing Fork diff --git a/docs/i18n/espanol/FAQ.md b/docs/i18n/espanol/FAQ.md index d3e0daa4f9..6199daa215 100644 --- a/docs/i18n/espanol/FAQ.md +++ b/docs/i18n/espanol/FAQ.md @@ -8,7 +8,7 @@ Yes - You can contribute to any of the 30+ languages we have enabled on our tran We have the user contributed translations live in Chinese (中文) and Spanish (Español). We intend to localize freeCodeCamp into several major world languages. You can read all about this in our [announcement here](https://www.freecodecamp.org/news/world-language-translation-effort). -If you are interested in contributing to translations please makes sure you [read this guide](/how-to-translate-files) first. +If you are interested in contributing to translations please makes sure you [read this guide](how-to-translate-files.md) first. ### ¿Cómo puedo reportar un nuevo error? diff --git a/docs/i18n/espanol/codebase-best-practices.md b/docs/i18n/espanol/codebase-best-practices.md index 0653a85904..80481a0a35 100644 --- a/docs/i18n/espanol/codebase-best-practices.md +++ b/docs/i18n/espanol/codebase-best-practices.md @@ -2,7 +2,7 @@ ## General JavaScript -In most cases, our [linter](how-to-setup-freecodecamp-locally?id=follow-these-steps-to-get-your-development-environment-ready) will warn of any formatting which goes against this codebase's preferred practice. +In most cases, our [linter](how-to-setup-freecodecamp-locally.md#follow-these-steps-to-get-your-development-environment-ready) will warn of any formatting which goes against this codebase's preferred practice. It is encouraged to use functional components over class-based components. diff --git a/docs/i18n/espanol/how-to-open-a-pull-request.md b/docs/i18n/espanol/how-to-open-a-pull-request.md index f0e812773c..1ee1e99425 100644 --- a/docs/i18n/espanol/how-to-open-a-pull-request.md +++ b/docs/i18n/espanol/how-to-open-a-pull-request.md @@ -2,7 +2,7 @@ Una pull request (PR) le permite enviar cambios desde su bifurcación en GitHub al repositorio principal de freeCodeCamp.org. Una vez que haya hecho cambios en el código, puede seguir estas pautas para abrir un PR. -> [!NOTE] Tu PR debe ser en inglés. See [here](https://contribute.freecodecamp.org/#/index?id=translations) for how to contribute translations. +> [!NOTE] Tu PR debe ser en inglés. See [here](index.md#translations) for how to contribute translations. ## Prepara un buen título para tu PR @@ -68,7 +68,7 @@ Algunos ejemplos de buenos títulos para PRs serían: - Esto es muy importante cuando se hagan cambios que no sean solo ediciones del contenido de texto como documentación o una descripción de un desafío. Ejemplos de los cambios que necesitan pruebas en el entorno local incluyen JavaScript, CSS o HTML que podrían cambiar la funcionalidad o el diseño de una página. - - Si tu PR afecta el comportamiento de una página, debe ir acompañada de la correspondiente [pruebas de integración de Cypress](/how-to-add-cypress-tests). + - If your PR affects the behaviour of a page it should be accompanied by corresponding [Cypress integration tests](how-to-add-cypress-tests.md). ## Comentarios sobre pull requests @@ -78,7 +78,7 @@ Nuestros moderadores ahora echarán un vistazo y te dejarán tus comentarios. Po Y como siempre, siéntete libre de preguntar en la [categoría de 'Contribuidores' de nuestro foro](https://forum.freecodecamp.org/c/contributors) o [en la sala de chat de contribuidores](https://chat.freecodecamp.org/channel/contributors). -> [!TIP] Si quieres contribuir con más PRs, te recomendamos que leas las directrices ["haciendo cambios y sincronizando"](https://contribute.freecodecamp.org/#/how-to-setup-freecodecamp-locally?id=making-changes-locally) para evitar la necesidad de borrar tu bifurcación. +> [!TIP] If you are to be contributing more pull requests, we recommend you read the [making changes and syncing](how-to-setup-freecodecamp-locally.md#making-changes-locally) guidelines to avoid having to delete your fork. ## Conflicto en un pull request diff --git a/docs/i18n/espanol/how-to-proofread-files.md b/docs/i18n/espanol/how-to-proofread-files.md index daecc0d687..0aa1e435b6 100644 --- a/docs/i18n/espanol/how-to-proofread-files.md +++ b/docs/i18n/espanol/how-to-proofread-files.md @@ -14,7 +14,7 @@ You should see the list of projects you have been granted access to. Select the You should now see the list of available files. Choose your file by selecting the `Proofread` button on the right of that file, then choosing `Proofreading` from the drop-down menu that appears. -> [!NOTE] Si estás en la vista "workspace" pero quieres trabajar en [traducir un archivo](./how-to-translate-files.md) en lugar de corregirlo, puedes seleccionar la opción `Crowdsourcing` del menú desplegable. +> [!NOTE] If you are in this workspace view, but want to work on [translating a file](how-to-translate-files.md) instead of proofreading, you may select `Crowdsourcing` from the dropdown menu instead. ## Revisar traducciones diff --git a/docs/i18n/espanol/how-to-setup-freecodecamp-locally.md b/docs/i18n/espanol/how-to-setup-freecodecamp-locally.md index 664417c89a..f0f90866bb 100644 --- a/docs/i18n/espanol/how-to-setup-freecodecamp-locally.md +++ b/docs/i18n/espanol/how-to-setup-freecodecamp-locally.md @@ -14,7 +14,7 @@ Comience instalando el software de requisitos previos para su sistema operativo. Apoyamos principalmente el desarrollo en sistemas basados en Linux y Unix. Nuestro personal y los colaboradores de la comunidad trabajan regularmente con el código base utilizando herramientas instaladas en Ubuntu y macOS. -También soportamos Windows 10 a través de WSL2, que puedes preparar [leyendo esta guía](/how-to-setup-wsl). +We also support Windows 10 via WSL2, which you can prepare by [reading this guide](how-to-setup-wsl.md). Algunos miembros de la comunidad también desarrollan en Windows 10 nativamente con Git for Windows (Git Bash), y otras herramientas instaladas en Windows. No tenemos soporte oficial para dicha configuración en este momento, así que recomendamos usar WSL2 en su lugar. diff --git a/docs/i18n/espanol/how-to-setup-wsl.md b/docs/i18n/espanol/how-to-setup-wsl.md index 5a9fdc8a07..ea40be4bff 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. 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. +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](how-to-setup-freecodecamp-locally.md) to work with freeCodeCamp on Windows running a WSL distro like Ubuntu. ## Habilitar WSL @@ -119,7 +119,7 @@ npm install -g npm@latest ## Configurar freeCodeCamp localmente -Now that you have installed the pre-requisites, follow [our local setup guide](https://contribute.freecodecamp.org/#/how-to-setup-freecodecamp-locally) to clone, install and setup freeCodeCamp locally on your machine. +Now that you have installed the pre-requisites, follow [our local setup guide](how-to-setup-freecodecamp-locally.md) to clone, install and setup freeCodeCamp locally on your machine. > [!WARNING] > diff --git a/docs/i18n/espanol/how-to-work-on-coding-challenges.md b/docs/i18n/espanol/how-to-work-on-coding-challenges.md index d8579f4ec2..fc6e430b35 100644 --- a/docs/i18n/espanol/how-to-work-on-coding-challenges.md +++ b/docs/i18n/espanol/how-to-work-on-coding-challenges.md @@ -476,7 +476,7 @@ You are also able to test one challenge individually by performing the following ``` npm run test -- -g challenge-title-goes-here ``` -Once you have verified that each challenge you've worked on passes the tests, [please create a pull request](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/docs/how-to-open-a-pull-request.md). +Once you have verified that each challenge you've worked on passes the tests, [please create a pull request](how-to-open-a-pull-request.md). > [!TIP] You can set the environment variable `LOCALE` in the `.env` to the language of the challenge(s) you need to test. > diff --git a/docs/i18n/espanol/how-to-work-on-localized-client-webapp.md b/docs/i18n/espanol/how-to-work-on-localized-client-webapp.md index 8425ead979..73ec325f42 100644 --- a/docs/i18n/espanol/how-to-work-on-localized-client-webapp.md +++ b/docs/i18n/espanol/how-to-work-on-localized-client-webapp.md @@ -2,13 +2,13 @@ The react based client web app that powers our learning platform is built using Gatsby. It is translated into various world languages using [react-i18next](https://react.i18next.com/) and [i18next](https://www.i18next.com/). -You can learn more about setting up the client application locally for development by following [our local setup guide here](/how-to-setup-freecodecamp-locally). By default the application is available only in English. +You can learn more about setting up the client application locally for development by following [our local setup guide here](how-to-setup-freecodecamp-locally.md). By default the application is available only in English. Once you have setup the project locally you should be able to follow this documentation to run the client in the language of your choice from the list of available languages. This could be helpful when you are working on a feature that specifically targets something that involves localization, and requires you to validate for instance a button's label in a different language. -> [!TIP] You do not need to follow this document for translating freeCodeCamp's curriculum or contributing documentation. Read [this guide here](./how-to-translate-files.md) instead. +> [!TIP] You do not need to follow this document for translating freeCodeCamp's curriculum or contributing documentation. Read [this guide here](how-to-translate-files.md) instead. Let's understand how the i18n frameworks and tooling work. @@ -67,7 +67,7 @@ Some of these files are translated on our translation platform (Crowdin), some a - The `intro.json` file contains the key-value pairs for the introduction text on the certification pages. - If you want to add/update translations for the keys please [read this guide here](/how-to-translate-files.md). + If you want to add/update translations for the keys please [read this guide here](how-to-translate-files.md). **Files NOT translated on our translations platform:** diff --git a/docs/i18n/espanol/how-to-work-on-practice-projects.md b/docs/i18n/espanol/how-to-work-on-practice-projects.md index 8b57f216eb..16782c1977 100644 --- a/docs/i18n/espanol/how-to-work-on-practice-projects.md +++ b/docs/i18n/espanol/how-to-work-on-practice-projects.md @@ -12,7 +12,7 @@ If you want to create new steps, the following tools simplify that process. A one-off script that will automatically add the next step based on the last step numbered as `part-xxx.md` where `xxx` represents the 3-digit step number of the last step. The challenge seed code will use the previous step's challenge seed code with the editable region markers (ERMs) removed. -**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps). +**Note:** This script also runs [reorder-steps](#reorder-steps). ### How to run script: @@ -27,7 +27,7 @@ npm run create-next-step A one-off script that automatically adds a specified number of steps at a specific starting step number. The challenge seed code for all steps created will be empty. -**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps). +**Note:** This script also runs [reorder-steps](#reorder-steps). ### How to run script: @@ -42,7 +42,7 @@ npm run create-empty-steps start=X num=Y # where X is the starting step number a A one-off script that automatically adds a new step between two existing consecutive steps. The challenge seed code will use the existing starting step's challenge seed code with the editable region markers (ERMs) removed. -**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps). +**Note:** This script also runs [reorder-steps](#reorder-steps). ### How to run script: diff --git a/docs/i18n/espanol/index.md b/docs/i18n/espanol/index.md index 51469bb979..1863bb7cc8 100644 --- a/docs/i18n/espanol/index.md +++ b/docs/i18n/espanol/index.md @@ -10,7 +10,7 @@ Eres bienvenido a: - Ayúdanos a corregir errores en la [plataforma de aprendizaje](#learning-platform) de freeCodeCamp.org. - [Ayúdanos a traducir](#translations) freeCodeCamp.org a idiomas del mundo. -Respondemos a las preguntas más comunes sobre cómo contribuir [en nuestras preguntas frecuentes del contribuidor](/FAQ.md). +We answer the most common questions about contributing [in our contributor FAQ](FAQ.md). ## Plan de estudios diff --git a/docs/i18n/espanol/moderator-handbook.md b/docs/i18n/espanol/moderator-handbook.md index cff51d56ab..1a02fb2d93 100644 --- a/docs/i18n/espanol/moderator-handbook.md +++ b/docs/i18n/espanol/moderator-handbook.md @@ -18,7 +18,7 @@ freeCodeCamp is an inclusive community, and we need to keep it that way. We have a single code of conduct that governs our entire community. The fewer the rules, the easier they are to remember. You can read those rules and commit them to memory [here](https://code-of-conduct.freecodecamp.org). -> [!NOTE] As a moderator we would add you to one or more teams on GitHub, our community forum(s) & chat servers. If you are missing access on a platform that you would like to moderate please [reach out to a staff member](/FAQ?id=additional-assistance). +> [!NOTE] As a moderator we would add you to one or more teams on GitHub, our community forum(s) & chat servers. If you are missing access on a platform that you would like to moderate please [reach out to a staff member](FAQ.md#additional-assistance). ## Moderando GitHub @@ -39,7 +39,7 @@ You can help us organize and triage the issue reports by applying labels from [t Please pay special attention to the labels `"help wanted"` and `"first timers only"`. These are to be added to threads that you think can be opened up to potential contributors for making a pull request. -A `"first timer only"` label should be applied to a trivial issue (ex. a typo fix) and should include additional information. You can use this [reply template](/moderator-handbook?id=first-timer-only-issues) for triage. +A `"first timer only"` label should be applied to a trivial issue (ex. a typo fix) and should include additional information. You can use this [reply template](moderator-handbook.md#first-timer-only-issues) for triage. #### Closing Stale, Outdated, Inactive Issues and Pull Requests @@ -49,7 +49,7 @@ A `"first timer only"` label should be applied to a trivial issue (ex. a typo fi - If the contributor asks for additional assistance or even time, the above can be relaxed and revisited after a response is given. In any case, the mods should use their best judgment to resolve the outstanding PR's status. -> [!TIP] We recommend you use this list of standard [reply templates](https://contribute.freecodecamp.org/#/moderator-handbook?id=reply-templates) while triaging issues. +> [!TIP] We recommend you use this list of standard [reply templates](moderator-handbook.md#reply-templates) while triaging issues. ### Moderating Pull Requests @@ -63,7 +63,7 @@ Pull Requests (PRs) are how contributors submit changes to freeCodeCamp's reposi You can also review these right on GitHub and decide whether to merge them. We need to be a bit more careful about these because millions of people will encounter this text as they work through the freeCodeCamp curriculum. Does the pull request make the text more clear without making it much longer? Are the edits relevant and not overly pedantic? Remember that our goal is for challenges to be as clear and as short as possible. They aren't the place for obscure details. Contributors may try to add links to resources to the challenges. - You can close invalid pull requests and reply to them with these [reply templates](https://contribute.freecodecamp.org/#/moderator-handbook?id=closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). If the change looks good, please ensure to leave an approval with a "LGTM" comment. Once a pull request gets at least two approvals (including yours) from the moderators or the dev-team, you can go ahead and merge it. @@ -75,7 +75,7 @@ Pull Requests (PRs) are how contributors submit changes to freeCodeCamp's reposi Some contributors may try to add additional tests to cover pedantic corner-cases. We need to be careful to not make the challenge too complicated. These challenges and their tests should be as simple and intuitive as possible. Aside from the algorithm challenges and interview prep section, learners should be able to solve each challenge within about 2 minutes. - You can close invalid pull requests and reply to them with these [reply templates](https://contribute.freecodecamp.org/#/moderator-handbook?id=closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). If the change looks good, please ensure to leave an approval with a "LGTM" comment. Once a pull request gets at least two approvals (including yours) from the moderators or the dev-team, you can go ahead and merge it. @@ -142,7 +142,7 @@ Often, a pull request will be low effort. You can usually tell this immediately There are also situations where the contributor is trying to add a link to their website, include a library they created, or have a frivolous edit that doesn't help anyone but themselves. -You can close invalid pull requests and reply to them with these [reply templates](https://contribute.freecodecamp.org/#/moderator-handbook?id=closing-invalid-pull-requests). +You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). #### Otras pautas para moderadores en GitHub @@ -387,7 +387,7 @@ Once you resolve these issues, we will be able to review your PR and merge it. --- -Feel free to reference the [contributing guidelines](https://contribute.freecodecamp.org/#/how-to-work-on-coding-challenges?id=testing-challenges) for instructions on running the CI build locally. ✅ +Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ ``` ### Syncing Fork diff --git a/docs/i18n/italian/FAQ.md b/docs/i18n/italian/FAQ.md index 7bc8ac6689..fd7d2dc83e 100644 --- a/docs/i18n/italian/FAQ.md +++ b/docs/i18n/italian/FAQ.md @@ -8,7 +8,7 @@ Sì, puoi contribuire a ognuna delle oltre 30 lingue abilitate sulla nostra piat Abbiamo già live le traduzioni fatte dagli utenti per cinese (中文), spagnolo (Español) e italiano. Abbiamo intenzione di localizzare freeCodeCamp nelle lingue più usate nel mondo. Puoi leggere tutto su questo argomento nel nostro [annuncio](https://www.freecodecamp.org/news/world-language-translation-effort). -Se sei interessato a contribuire alla traduzione per favore assicurati di [!TIP] Ti consigliamo di usare questa lista di [modelli di risposta](https://contribute.freecodecamp.org/#/moderator-handbook?id=reply-templates) mentre smisti le issue. +> [!TIP] We recommend you use this list of standard [reply templates](moderator-handbook.md#reply-templates) while triaging issues. ### Moderare le pull request @@ -63,7 +63,7 @@ Le pull request (PR) sono il modo in cui i contributori sottopongono cambiamenti Puoi anche farne la revisione direttamente su GitHub e decidere se fare il merge. Dobbiamo fare un po' attenzione su questo perché milioni di persone incontreranno questo testo lavorando sul curriculum di freeCodeCamp. La pull request rende il testo più chiaro senza allungarlo troppo? Le modifiche sono rilevanti e non troppo pedanti? Ricorda che il nostro obbiettivo è che le sfide siano più chiare e più corte possibile. Non sono il luogo per dettagli incomprensibili. I contributori possono provare ad aggiungere link e risorse alle sfide. - Puoi chiudere le pull request non valide e rispondervi con questi [modelli di risposta](https://contribute.freecodecamp.org/#/moderator-handbook?id=closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). Se la modifica va bene, assicurati di lasciare un'approvazione con un commento "LGTM". Una volta che una pull request riceve almeno due approvazioni (inclusa la tua) dai moderatori o dal dev-team, puoi procedere e farne il merge. @@ -75,7 +75,7 @@ Le pull request (PR) sono il modo in cui i contributori sottopongono cambiamenti Alcuni contributori potrebbero provare ad aggiungere test addizionali per coprire casi limite pedanti. Dobbiamo fare attenzione a non rendere le sfide troppo complicate. Queste sfide e i loro test dovrebbero essere più semplici e intuitivi possibile. Ad eccezione delle sfide sugli algoritmi e della sezione di preparazione al colloquio di lavoro, gli studenti dovrebbero essere in grado di risolvere ogni sfida entro due minuti. - Puoi chiudere le pull request non valide e rispondervi con questi [modelli di risposta](https://contribute.freecodecamp.org/#/moderator-handbook?id=closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). Se la modifica va bene, assicurati di lasciare un'approvazione con un commento "LGTM". Una volta che una pull request ha ricevuto almeno due approvazioni (inclusa la tua) dai moderatori o dal dev-team, puoi procedere e farne il merge. @@ -142,7 +142,7 @@ Spesso una pull request avrà richiesto uno sforzo minimo. Puoi capirlo immediat Ci sono anche situazioni in cui il contributore sta cercando di aggiungere un collegamento al proprio sito Web, includere una libreria che ha creato o apportare una modifica frivola che non aiuta nessuno tranne se stesso. -Puoi chiudere le pull request non valide e rispondere con questi [modelli di risposta](https://contribute.freecodecamp.org/#/moderator-handbook?id=closing-invalid-pull-requests). +You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). #### Altre linee guida per i Moderatori su GitHub @@ -388,7 +388,7 @@ Once you resolve these issues, we will be able to review your PR and merge it. --- -Feel free to reference the [contributing guidelines](https://contribute.freecodecamp.org/#/how-to-work-on-coding-challenges?id=testing-challenges) for instructions on running the CI build locally. ✅ +Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ ``` ### Sincronizzare le fork diff --git a/docs/i18n/portuguese/FAQ.md b/docs/i18n/portuguese/FAQ.md index 1945ccbb1e..d0b5c47444 100644 --- a/docs/i18n/portuguese/FAQ.md +++ b/docs/i18n/portuguese/FAQ.md @@ -8,7 +8,7 @@ Sim. Você pode contribuir com qualquer um dos mais de 30 idiomas disponíveis e Temos as traduções de chinês (中文) e espanhol (Español) no ar. Pretendemos traduzir o freeCodeCamp para vários idiomas. Você pode ler mais sobre isso em nosso [anúncio aqui](https://www.freecodecamp.org/news/world-language-translation-effort). -Se você está interessado em contribuir com as traduções, certifique-se de [ler este guia](/how-to-translate-files) primeiro. +If you are interested in contributing to translations please makes sure you [read this guide](how-to-translate-files.md) first. ### Como posso relatar um novo erro? diff --git a/docs/i18n/portuguese/codebase-best-practices.md b/docs/i18n/portuguese/codebase-best-practices.md index 57dc29d176..56ba0566b9 100644 --- a/docs/i18n/portuguese/codebase-best-practices.md +++ b/docs/i18n/portuguese/codebase-best-practices.md @@ -2,7 +2,7 @@ ## JavaScript em geral -Na maioria dos casos, nosso [linter](how-to-setup-freecodecamp-locally?id=follow-these-steps-to-get-your-development-environment-ready) avisará sobre qualquer formatação que contradiga as práticas recomendadas desta base de código. +In most cases, our [linter](how-to-setup-freecodecamp-locally.md#follow-these-steps-to-get-your-development-environment-ready) will warn of any formatting which goes against this codebase's preferred practice. Recomendamos o uso de componentes funcionais em vez de componentes baseados em classes. diff --git a/docs/i18n/portuguese/how-to-add-cypress-tests.md b/docs/i18n/portuguese/how-to-add-cypress-tests.md index c222edf432..8103d40e5f 100644 --- a/docs/i18n/portuguese/how-to-add-cypress-tests.md +++ b/docs/i18n/portuguese/how-to-add-cypress-tests.md @@ -12,7 +12,7 @@ Para aprender como escrever testes Cypress ou 'specs', por favor confira a [docu ## Como executar testes -> [!NOTE] If using GitPod, please see [Cypress-GitPod Setup](/how-to-add-cypress-tests#cypress-gitpod-setup) +> [!NOTE] Se estiver usando o GitPod, consulte a [configuração do Cypress-GitPod](/how-to-add-cypress-tests#cypress-gitpod-setup) ### 1. Veja se as aplicações de cliente e MongoDB estão executando diff --git a/docs/i18n/portuguese/how-to-open-a-pull-request.md b/docs/i18n/portuguese/how-to-open-a-pull-request.md index ff4755b02e..7514e488c5 100644 --- a/docs/i18n/portuguese/how-to-open-a-pull-request.md +++ b/docs/i18n/portuguese/how-to-open-a-pull-request.md @@ -2,7 +2,7 @@ Um pull request (PR) permite que você envie alterações do seu fork do GitHub para o repositório principal do freeCodeCamp.org. Depois de terminar de fazer alterações no código, você pode seguir essas diretrizes para abrir um PR. -> [!NOTE] Seu PR deve estar em inglês. Veja [aqui](https://contribute.freecodecamp.org/#/index?id=translations) como contribuir com traduções. +> [!NOTE] Seu PR deve estar em inglês. See [here](index.md#translations) for how to contribute translations. ## Prepare um bom título para o PR @@ -68,7 +68,7 @@ Alguns exemplos de bons títulos de PRs seriam: - Isso é muito importante quando se está fazendo mudanças que não são apenas edições no conteúdo do texto como a documentação ou descrição de um desafio. Exemplos de mudanças que precisam ser testadas localmente incluem JavaScript, CSS ou HTML que podem mudar a funcionalidade ou aparência de uma página. - - Se seu PR afeta o comportamento de uma página ele deve estar acompanhado pelo correspondente [teste de integração Cypress](/how-to-add-cypress-tests). + - If your PR affects the behaviour of a page it should be accompanied by corresponding [Cypress integration tests](how-to-add-cypress-tests.md). ## Comentários nos pull requests @@ -78,7 +78,7 @@ Nossos moderadores vão dar uma olhada e deixar um comentário para você. Seja E como sempre, fique à vontade em perguntar na [categoria 'Contribuidores' do fórum](https://forum.freecodecamp.org/c/contributors) ou [no chat dos contribuidores](https://chat.freecodecamp.org/channel/contributors). -> [!TIP] Se você vai contribuir com mais pull requests, recomendamos ler as diretrizes sobre [fazer mudanças e sincronizá-las](https://contribute.freecodecamp.org/#/how-to-setup-freecodecamp-locally?id=making-changes-locally) para evitar o apagamento de seu fork. +> [!TIP] If you are to be contributing more pull requests, we recommend you read the [making changes and syncing](how-to-setup-freecodecamp-locally.md#making-changes-locally) guidelines to avoid having to delete your fork. ## Conflitos em um pull request diff --git a/docs/i18n/portuguese/how-to-proofread-files.md b/docs/i18n/portuguese/how-to-proofread-files.md index e5b252f1dd..f0e6281c4a 100644 --- a/docs/i18n/portuguese/how-to-proofread-files.md +++ b/docs/i18n/portuguese/how-to-proofread-files.md @@ -14,7 +14,7 @@ Você deve ver a lista de projetos aos quais foi concedido acesso. Selecione o p Agora você deve ver a lista de arquivos disponíveis. Escolha seu arquivo selecionando o botão `Proofread` à direita do arquivo, depois escolha `Proofreading` no menu que aparece. -> [!NOTE] Se você estiver nesta visão de espaço de trabalho, mas quiser [traduzir um arquivo](./how-to-translate-files.md) em vez de revisar, você pode selecionar `Crowdsourcing` no menu suspenso. +> [!NOTE] If you are in this workspace view, but want to work on [translating a file](how-to-translate-files.md) instead of proofreading, you may select `Crowdsourcing` from the dropdown menu instead. ## Traduções revisadas diff --git a/docs/i18n/portuguese/how-to-setup-freecodecamp-locally.md b/docs/i18n/portuguese/how-to-setup-freecodecamp-locally.md index 8ccbf6521d..2ea9f0825f 100644 --- a/docs/i18n/portuguese/how-to-setup-freecodecamp-locally.md +++ b/docs/i18n/portuguese/how-to-setup-freecodecamp-locally.md @@ -14,7 +14,7 @@ Comece instalando o software pré-requisito para seu sistema operacional. Apoiamos principalmente o desenvolvimento em sistemas Linux e Unix. Nossa equipe e colaboradores da comunidade trabalham regularmente com a base de código usando ferramentas instaladas no Ubuntu e no macOS. -Também suportamos o Windows 10 via WSL2, que você pode preparar [lendo este guia](/how-to-setup-wsl). +We also support Windows 10 via WSL2, which you can prepare by [reading this guide](how-to-setup-wsl.md). Alguns membros da comunidade também desenvolvem no Windows 10 nativamente com Git para Windows (Git Bash), e outras ferramentas instaladas no Windows. Neste momento, não dispomos de apoio oficial para esse tipo de instalações, recomendamos que se utilize WSL2. diff --git a/docs/i18n/portuguese/how-to-setup-wsl.md b/docs/i18n/portuguese/how-to-setup-wsl.md index fa31f354a6..d86387540c 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 para Windows**: Veja os respectivos requisitos para [Windows 10 Pro](https://docs.docker.com/docker-for-windows/install/#system-requirements) e [Windows 10 Home](https://docs.docker.com/docker-for-windows/install-windows-home/#system-requirements) -Este guia abrange algumas etapas comuns sobre a instalação do WSL2. Uma vez resolvidos alguns dos problemas comuns com o WSL2, você deve seguir o nosso [guia de instalação local](https://contribute.freecodecamp.org/#/how-to-setup-freecodecamp-locally) para trabalhar com o freeCodeCamp no Windows executando uma distro WSL como o Ubuntu. +Este guia abrange algumas etapas comuns sobre a instalação do WSL2. Once some of the common issues with WSL2 are addressed, you should be able to follow [this local setup guide](how-to-setup-freecodecamp-locally.md) to work with freeCodeCamp on Windows running a WSL distro like Ubuntu. ## Ative o WSL @@ -119,7 +119,7 @@ npm install -g npm@latest ## Configure localmente o freeCodeCamp -Agora que você instalou os pré-requisitos, siga [nosso guia de instalação local](https://contribute.freecodecamp.org/#/how-to-setup-freecodecamp-locally) para clonar, instalar e configurar o freeCodeCamp em sua máquina. +Now that you have installed the pre-requisites, follow [our local setup guide](how-to-setup-freecodecamp-locally.md) to clone, install and setup freeCodeCamp locally on your machine. > [!WARNING] > diff --git a/docs/i18n/portuguese/how-to-work-on-coding-challenges.md b/docs/i18n/portuguese/how-to-work-on-coding-challenges.md index b286d6912f..bbbced15fe 100644 --- a/docs/i18n/portuguese/how-to-work-on-coding-challenges.md +++ b/docs/i18n/portuguese/how-to-work-on-coding-challenges.md @@ -479,7 +479,7 @@ Você também é capaz de testar um desafio individualmente seguindo as seguinte ``` npm run test -- -g challenge-title-goes-here ``` -Quando você verificar que cada desafio modificado passou nos testes, [crie um pull request](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/docs/how-to-open-a-pull-request.md). +Once you have verified that each challenge you've worked on passes the tests, [please create a pull request](how-to-open-a-pull-request.md). > [!TIP] Você pode definir a variável de ambiente `LOCALE` no `.env` no idioma do(s) desafio(s) que precisa testar. > diff --git a/docs/i18n/portuguese/how-to-work-on-localized-client-webapp.md b/docs/i18n/portuguese/how-to-work-on-localized-client-webapp.md index b563f39946..e302d458f4 100644 --- a/docs/i18n/portuguese/how-to-work-on-localized-client-webapp.md +++ b/docs/i18n/portuguese/how-to-work-on-localized-client-webapp.md @@ -2,13 +2,13 @@ O nosso cliente web app com base em React que alimenta nossa plataforma de aprendizado foi criado usando o Gatsby. Ele é traduzido em vários idiomas do mundo todo usando [react-i18next](https://react.i18next.com/) e [i18next](https://www.i18next.com/). -Você pode aprender mais sobre configurar o cliente localmente para desenvolvimento seguindo [nosso guia de configuração aqui](/how-to-setup-freecodecamp-locally). Por padrão, a aplicação está disponível somente em inglês. +You can learn more about setting up the client application locally for development by following [our local setup guide here](how-to-setup-freecodecamp-locally.md). Por padrão, a aplicação está disponível somente em inglês. Assim que você tiver o projeto configurado localmente, você poderá seguir essa documentação para rodar o cliente no idioma de sua escolha a partir de uma lista de idiomas disponíveis. Isso pode ser de grande ajuda quando você estiver trabalhando em uma nova feature que envolva tradução, em especial, e que necessite que você valide, por exemplo, uma label de botão em um idioma diferente. -> [!TIP] Você não precisa seguir esse documento para traduzir o currículo do freeCodeCamp ou contribuir com a documentação. Em vez disso, leia [esse guia aqui](./how-to-translate-files.md). +> [!TIP] Você não precisa seguir esse documento para traduzir o currículo do freeCodeCamp ou contribuir com a documentação. Read [this guide here](how-to-translate-files.md) instead. Vamos entender como o framework i18n e suas ferramentas funcionam. @@ -67,7 +67,7 @@ Alguns desses arquivos estão traduzidos na nossa plataforma de tradução (Crow - O arquivo `intro.json` contém os pares chave-valor para o texto de introdução nas páginas de certificação. - Se você deseja adicionar/atualizar traduções para as chaves, [leia este guia aqui](/how-to-translate-files.md). + If you want to add/update translations for the keys please [read this guide here](how-to-translate-files.md). **Arquivos NÃO traduzidos na nossa plataforma de tradução:** diff --git a/docs/i18n/portuguese/how-to-work-on-practice-projects.md b/docs/i18n/portuguese/how-to-work-on-practice-projects.md index ae303bb356..3a463e9cee 100644 --- a/docs/i18n/portuguese/how-to-work-on-practice-projects.md +++ b/docs/i18n/portuguese/how-to-work-on-practice-projects.md @@ -12,7 +12,7 @@ Se você quer criar novos passos, as ferramentas a seguir vão simplificar o pro Um script único que automaticamente adiciona um novo passo baseado no último passo numerado como `part-xxx.md` onde `xxx` representa o número de 3 dígitos do último passo. O código inicial de desafio usará o código inicial de desafio da etapa anterior com os marcadores de região editáveis ​​(ERMs) removidos. -**Observação:** Esse script também executa [reorder-steps](how-to-work-on-practice-projects#reorder-steps). +**Note:** This script also runs [reorder-steps](#reorder-steps). ### Como executar esse script: @@ -27,7 +27,7 @@ npm run create-next-step Um script único que adiciona automaticamente um número especificado de passos começando a partir de um número específico. O código seed de todos os passos criados estarão vazios. -**Observação:** Esse script também executa [reorder-steps](how-to-work-on-practice-projects#reorder-steps). +**Note:** This script also runs [reorder-steps](#reorder-steps). ### Como executar esse script: @@ -42,7 +42,7 @@ npm run create-empty-steps start=X num=Y # onde X é o número do passo onde dev Um único script que automaticamente adiciona passos entre dois passos consecutivos. O código inicial do desafio usará o código inicial do desafio da etapa inicial existente com os marcadores de região editáveis ​​(ERMs) removidos. -**Observação:** Esse script também executa [reorder-steps](how-to-work-on-practice-projects#reorder-steps). +**Note:** This script also runs [reorder-steps](#reorder-steps). ### Como executar esse script: diff --git a/docs/i18n/portuguese/index.md b/docs/i18n/portuguese/index.md index 594fa0f2d6..02edc694dd 100644 --- a/docs/i18n/portuguese/index.md +++ b/docs/i18n/portuguese/index.md @@ -10,7 +10,7 @@ Fique à vontade para: - Nos ajudar a corrigir bugs na [plataforma de aprendizado](#plataforma-de-aprendizado) do freeCodeCamp.org. - [Nos ajudar a traduzir](#tradu%c3%a7%c3%b5es) freeCodeCamp.org para vários idiomas. -Respondemos às perguntas mais comuns sobre como contribuir [no nosso FAQ do colaborador](/FAQ.md). +We answer the most common questions about contributing [in our contributor FAQ](FAQ.md). ## Currículo diff --git a/docs/i18n/portuguese/moderator-handbook.md b/docs/i18n/portuguese/moderator-handbook.md index 1e4159f6ff..c5d7a7339f 100644 --- a/docs/i18n/portuguese/moderator-handbook.md +++ b/docs/i18n/portuguese/moderator-handbook.md @@ -18,7 +18,7 @@ O freeCodeCamp é uma comunidade inclusiva e temos de mantê-la assim. Temos um código de conduta único que rege toda a nossa comunidade. Quanto menos regras, mais fáceis elas são de lembrar. Você pode ler essas regras e guardá-las na memória [aqui](https://code-of-conduct.freecodecamp.org). -> [!NOTE] Como moderador, nós adicionaríamos você a um ou mais times no GitHub, nos nossos fóruns comunitários e nos servidores de chat. Caso você não tenha acesso a uma plataforma que queira moderar, [entre em contato com um membro da equipe](/FAQ?id=additional-assistance). +> [!NOTE] Como moderador, nós adicionaríamos você a um ou mais times no GitHub, nos nossos fóruns comunitários e nos servidores de chat. If you are missing access on a platform that you would like to moderate please [reach out to a staff member](FAQ.md#additional-assistance). ## Moderando no GitHub @@ -39,7 +39,7 @@ Você pode nos ajudar a organizar e moderar issues usando etiquetas [dessa lista Preste atenção especial às etiquetas `"help wanted"` e `"first timers only"`. Elas devem ser adicionadas aos tópicos que você considere que possam ser abertos aos potenciais contribuidores para realizar um "pull request". -Uma etiqueta `"first timer only"` deve ser aplicada a uma issue trivial (ex.: consertar um erro de digitação) e deve incluir informações adicionais. Você pode usar esse [modelo de resposta](/moderator-handbook?id=first-timer-only-issues). +Uma etiqueta `"first timer only"` deve ser aplicada a uma issue trivial (ex.: consertar um erro de digitação) e deve incluir informações adicionais. You can use this [reply template](moderator-handbook.md#first-timer-only-issues) for triage. #### Fechando issues e pull requests parados, desatualizados ou inativos @@ -49,7 +49,7 @@ Uma etiqueta `"first timer only"` deve ser aplicada a uma issue trivial (ex.: co - Se o criador do PR pedir assistência adicional ou mais tempo, as regras acima podem ser revistas após uma resposta. Em todo caso, os moderadores devem usar o melhor julgamento para resolverem o estado do PR. -> [!TIP] Recomendamos usar essa lista de [modelos de resposta](https://contribute.freecodecamp.org/#/moderator-handbook?id=reply-templates) padrão enquanto estiver monitorando issues. +> [!TIP] We recommend you use this list of standard [reply templates](moderator-handbook.md#reply-templates) while triaging issues. ### Moderando pull requests @@ -63,7 +63,7 @@ Pull Requests (PRs) são como os colaboradores enviam alterações para o reposi Você também pode revisar isso diretamente no GitHub e decidir fazer merge ou não. Precisamos ter um pouco mais de cuidado com relação a isso, pois milhões de pessoas encontrarão este texto enquanto usam o currículo do freeCodeCamp. O pull request deixa o texto mais claro sem deixá-lo muito mais longo? As edições são relevantes e não são excessivamente pedantes? Lembre-se que nosso objetivo é que os desafios sejam mais claros e curtos dentro do possível. Não são o lugar para detalhes obscuros. Os contribuidores talvez tentem adicionar links para recursos dos desafios. - Você pode fechar pull requests inválidos e respondê-los com esses [modelos de resposta](https://contribute.freecodecamp.org/#/moderator-handbook?id=closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). Se as mudanças parecem boas, por favor aprove-as comentando "LGTM". Uma vez que um pull request tiver pelo menos duas aprovações (incluindo a sua) dos moderadores ou equipe de desenvolvedores, você pode fazer o merge. @@ -75,7 +75,7 @@ Pull Requests (PRs) são como os colaboradores enviam alterações para o reposi Alguns contribuidores podem tentar adicionar mais testes para cobrir casos confusos pedantes. Precisamos ter cuidado para não deixarmos o desafio muito complicado. Esses desafios e seus testes devem ser simples e intuitivos na medida do possível. Além dos desafios de algoritmo e a seção de preparação para entrevistas, os estudantes devem ser capazes de resolver cada desafio em aproximadamente 2 minutos. - Você pode fechar pull requests inválidos e respondê-los com esses [modelos de resposta](https://contribute.freecodecamp.org/#/moderator-handbook?id=closing-invalid-pull-requests). + You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). Se as mudanças parecem boas, por favor aprove-as comentando "LGTM". Uma vez que um pull request tiver pelo menos duas aprovações (incluindo a sua) dos moderadores ou equipe de desenvolvedores, você pode fazer o merge. @@ -142,7 +142,7 @@ Muitas vezes, um pull request será obviamente de baixo esforço. Muitas vezes, Há também situações em que o colaborador está tentando adicionar um link para o seu próprio site, incluir uma biblioteca que criou, ou tem uma edição frívola que não serve para ajudar ninguém, exceto a si mesmo. -Você pode fechar pull requests inválidos e respondê-los com esses [modelos de resposta](https://contribute.freecodecamp.org/#/moderator-handbook?id=closing-invalid-pull-requests). +You can close invalid pull requests and reply to them with these [reply templates](moderator-handbook.md#closing-invalid-pull-requests). #### Outras diretrizes para moderadores no GitHub @@ -387,8 +387,7 @@ Assim que você resolver essas issues, nós poderemos rever seu PR e fazer o mer --- -Fique à vontade para recorrer às [diretrizes de contribuição] -(https://contribute.freecodecamp.org/#/how-to-work-on-coding-challenges?id=testing-challenges) para ver instruções sobre como executar o build de CI localmente. ✅ +Feel free to reference the [contributing guidelines](how-to-work-on-coding-challenges.md#testing-challenges) for instructions on running the CI build locally. ✅ ``` ### Sincronização dos forks