From 88d7db08f51c290c0f187b23237d110fadc11d5d Mon Sep 17 00:00:00 2001 From: camperbot Date: Tue, 31 Oct 2023 10:06:21 -0700 Subject: [PATCH] chore(i18n,docs): processed translations (#52172) --- .../authors-analytics-manual.md | 4 +- .../codebase-best-practices.md | 2 +- .../how-to-catch-outgoing-emails-locally.md | 2 +- .../how-to-contribute-to-the-codebase.md | 4 +- .../how-to-enable-new-languages.md | 12 ++-- .../how-to-help-with-video-challenges.md | 2 +- .../how-to-open-a-pull-request.md | 6 +- .../how-to-proofread-files.md | 4 +- .../how-to-setup-freecodecamp-locally.md | 8 +-- ...o-setup-freecodecamp-mobile-app-locally.md | 10 +-- .../chinese-traditional/how-to-setup-wsl.md | 2 +- .../how-to-use-docker-on-windows-home.md | 2 +- .../how-to-work-on-coding-challenges.md | 4 +- .../how-to-work-on-localized-client-webapp.md | 6 +- .../how-to-work-on-practice-projects.md | 4 +- ...-to-work-on-tutorials-that-use-coderoad.md | 6 +- .../language-lead-handbook.md | 2 +- .../chinese-traditional/moderator-handbook.md | 4 +- .../chinese-traditional/reply-templates.md | 4 +- .../troubleshooting-development-issues.md | 4 +- docs/i18n/chinese/authors-analytics-manual.md | 4 +- docs/i18n/chinese/codebase-best-practices.md | 2 +- .../how-to-catch-outgoing-emails-locally.md | 2 +- .../how-to-contribute-to-the-codebase.md | 4 +- .../chinese/how-to-enable-new-languages.md | 12 ++-- .../how-to-help-with-video-challenges.md | 2 +- .../chinese/how-to-open-a-pull-request.md | 6 +- docs/i18n/chinese/how-to-proofread-files.md | 4 +- .../how-to-setup-freecodecamp-locally.md | 8 +-- ...o-setup-freecodecamp-mobile-app-locally.md | 10 +-- docs/i18n/chinese/how-to-setup-wsl.md | 2 +- .../how-to-use-docker-on-windows-home.md | 2 +- .../how-to-work-on-coding-challenges.md | 4 +- .../how-to-work-on-localized-client-webapp.md | 6 +- .../how-to-work-on-practice-projects.md | 4 +- ...-to-work-on-tutorials-that-use-coderoad.md | 6 +- docs/i18n/chinese/language-lead-handbook.md | 2 +- docs/i18n/chinese/moderator-handbook.md | 4 +- docs/i18n/chinese/reply-templates.md | 4 +- .../troubleshooting-development-issues.md | 4 +- docs/i18n/espanol/authors-analytics-manual.md | 4 +- docs/i18n/espanol/codebase-best-practices.md | 2 +- .../how-to-catch-outgoing-emails-locally.md | 2 +- .../how-to-contribute-to-the-codebase.md | 4 +- .../espanol/how-to-enable-new-languages.md | 12 ++-- .../how-to-help-with-video-challenges.md | 2 +- .../espanol/how-to-open-a-pull-request.md | 6 +- docs/i18n/espanol/how-to-proofread-files.md | 4 +- .../how-to-setup-freecodecamp-locally.md | 8 +-- ...o-setup-freecodecamp-mobile-app-locally.md | 10 +-- docs/i18n/espanol/how-to-setup-wsl.md | 2 +- .../how-to-use-docker-on-windows-home.md | 2 +- .../how-to-work-on-coding-challenges.md | 4 +- .../how-to-work-on-localized-client-webapp.md | 6 +- .../how-to-work-on-practice-projects.md | 4 +- ...-to-work-on-tutorials-that-use-coderoad.md | 6 +- docs/i18n/espanol/language-lead-handbook.md | 2 +- docs/i18n/espanol/moderator-handbook.md | 4 +- docs/i18n/espanol/reply-templates.md | 4 +- .../troubleshooting-development-issues.md | 4 +- docs/i18n/german/authors-analytics-manual.md | 4 +- docs/i18n/german/codebase-best-practices.md | 2 +- .../how-to-catch-outgoing-emails-locally.md | 2 +- .../how-to-contribute-to-the-codebase.md | 4 +- .../german/how-to-enable-new-languages.md | 12 ++-- .../how-to-help-with-video-challenges.md | 2 +- .../i18n/german/how-to-open-a-pull-request.md | 6 +- docs/i18n/german/how-to-proofread-files.md | 4 +- .../how-to-setup-freecodecamp-locally.md | 8 +-- ...o-setup-freecodecamp-mobile-app-locally.md | 10 +-- docs/i18n/german/how-to-setup-wsl.md | 2 +- .../how-to-use-docker-on-windows-home.md | 2 +- .../how-to-work-on-coding-challenges.md | 4 +- .../how-to-work-on-localized-client-webapp.md | 6 +- .../how-to-work-on-practice-projects.md | 4 +- ...-to-work-on-tutorials-that-use-coderoad.md | 6 +- docs/i18n/german/language-lead-handbook.md | 2 +- docs/i18n/german/moderator-handbook.md | 4 +- docs/i18n/german/reply-templates.md | 4 +- .../troubleshooting-development-issues.md | 4 +- docs/i18n/italian/authors-analytics-manual.md | 4 +- docs/i18n/italian/codebase-best-practices.md | 2 +- .../how-to-catch-outgoing-emails-locally.md | 2 +- .../how-to-contribute-to-the-codebase.md | 4 +- .../italian/how-to-enable-new-languages.md | 12 ++-- .../how-to-help-with-video-challenges.md | 2 +- .../italian/how-to-open-a-pull-request.md | 6 +- docs/i18n/italian/how-to-proofread-files.md | 4 +- .../how-to-setup-freecodecamp-locally.md | 8 +-- ...o-setup-freecodecamp-mobile-app-locally.md | 10 +-- docs/i18n/italian/how-to-setup-wsl.md | 2 +- .../how-to-use-docker-on-windows-home.md | 2 +- .../how-to-work-on-coding-challenges.md | 4 +- .../how-to-work-on-localized-client-webapp.md | 6 +- .../how-to-work-on-practice-projects.md | 4 +- ...-to-work-on-tutorials-that-use-coderoad.md | 6 +- docs/i18n/italian/language-lead-handbook.md | 2 +- docs/i18n/italian/moderator-handbook.md | 4 +- docs/i18n/italian/reply-templates.md | 4 +- .../troubleshooting-development-issues.md | 4 +- .../i18n/japanese/authors-analytics-manual.md | 4 +- docs/i18n/japanese/codebase-best-practices.md | 2 +- .../how-to-catch-outgoing-emails-locally.md | 2 +- .../how-to-contribute-to-the-codebase.md | 4 +- .../japanese/how-to-enable-new-languages.md | 12 ++-- .../how-to-help-with-video-challenges.md | 2 +- .../japanese/how-to-open-a-pull-request.md | 6 +- docs/i18n/japanese/how-to-proofread-files.md | 4 +- .../how-to-setup-freecodecamp-locally.md | 8 +-- ...o-setup-freecodecamp-mobile-app-locally.md | 10 +-- docs/i18n/japanese/how-to-setup-wsl.md | 2 +- .../how-to-use-docker-on-windows-home.md | 2 +- .../how-to-work-on-coding-challenges.md | 4 +- .../how-to-work-on-localized-client-webapp.md | 6 +- .../how-to-work-on-practice-projects.md | 4 +- ...-to-work-on-tutorials-that-use-coderoad.md | 6 +- docs/i18n/japanese/language-lead-handbook.md | 2 +- docs/i18n/japanese/moderator-handbook.md | 4 +- docs/i18n/japanese/reply-templates.md | 4 +- .../troubleshooting-development-issues.md | 4 +- .../portuguese/authors-analytics-manual.md | 4 +- .../portuguese/how-to-enable-new-languages.md | 2 +- .../how-to-help-with-video-challenges.md | 2 +- .../portuguese/how-to-open-a-pull-request.md | 4 +- .../i18n/portuguese/how-to-proofread-files.md | 2 +- docs/i18n/portuguese/how-to-setup-wsl.md | 2 +- .../how-to-work-on-coding-challenges.md | 62 +++++++++---------- .../how-to-work-on-practice-projects.md | 2 +- docs/i18n/portuguese/moderator-handbook.md | 2 +- docs/i18n/portuguese/reply-templates.md | 2 +- .../troubleshooting-development-issues.md | 2 +- .../ukrainian/how-to-open-a-pull-request.md | 2 +- .../how-to-work-on-coding-challenges.md | 58 ++++++++--------- .../how-to-work-on-practice-projects.md | 2 +- docs/i18n/ukrainian/reply-templates.md | 2 +- 135 files changed, 351 insertions(+), 351 deletions(-) diff --git a/docs/i18n/chinese-traditional/authors-analytics-manual.md b/docs/i18n/chinese-traditional/authors-analytics-manual.md index 221ca725cd9..fa5bbe46392 100644 --- a/docs/i18n/chinese-traditional/authors-analytics-manual.md +++ b/docs/i18n/chinese-traditional/authors-analytics-manual.md @@ -1,10 +1,10 @@ # Authors Analytics Manual -If you are an author with access to the publication's Google Analytics Property (News), you can use this guide to view your articles engagement and search for articles by publication language. +If you are an author with access to the publication's Google Analytics Property (News), you can use this guide to view your article engagement and search for articles by publication language. ## Search by Language -To search for engagement reports by a specific language: +To search for engagement reports in a specific language: ![Image - Show steps to search by language on googla analytics](https://contribute.freecodecamp.org/images/google-analytics/search-by-language.png) diff --git a/docs/i18n/chinese-traditional/codebase-best-practices.md b/docs/i18n/chinese-traditional/codebase-best-practices.md index 3a0a50e17ae..a2253ffb3b3 100644 --- a/docs/i18n/chinese-traditional/codebase-best-practices.md +++ b/docs/i18n/chinese-traditional/codebase-best-practices.md @@ -161,7 +161,7 @@ The `api/` tests are split into two parts: Unit tests isolate a single function or component. The tests do not need mocking, but will require fixtures. -The unit tests are located in a new file adjacent the file exporting that being tested: +The unit tests are located in a new file adjacent to the file exporting that is being tested: ```text api/ diff --git a/docs/i18n/chinese-traditional/how-to-catch-outgoing-emails-locally.md b/docs/i18n/chinese-traditional/how-to-catch-outgoing-emails-locally.md index a4082eacfa4..9346378712c 100644 --- a/docs/i18n/chinese-traditional/how-to-catch-outgoing-emails-locally.md +++ b/docs/i18n/chinese-traditional/how-to-catch-outgoing-emails-locally.md @@ -104,7 +104,7 @@ mailhog ## Using MailHog -Open a new browser tab or window and navigate to [http://localhost:8025](http://localhost:8025) to open your MailHog inbox when the MailHog installation has completed and MailHog is running. +Open a new browser tab or window and navigate to [http://localhost:8025](http://localhost:8025) to open your MailHog inbox when the MailHog installation has been completed and MailHog is running. ## Useful Links diff --git a/docs/i18n/chinese-traditional/how-to-contribute-to-the-codebase.md b/docs/i18n/chinese-traditional/how-to-contribute-to-the-codebase.md index 3ee01e7f9c9..0068611fc50 100644 --- a/docs/i18n/chinese-traditional/how-to-contribute-to-the-codebase.md +++ b/docs/i18n/chinese-traditional/how-to-contribute-to-the-codebase.md @@ -23,7 +23,7 @@ Follow these steps: nothing to commit, working directory clean ``` - If you got different message, then you aren't on main or your working directory isn't clean, resolve any outstanding files/commits and checkout `main`: + If you got a different message, then you aren't on main or your working directory isn't clean, resolve any outstanding files/commits and checkout `main`: ```console git checkout main @@ -55,7 +55,7 @@ Follow these steps: git push origin main --force ``` - You can validate your current main matches the upstream/main by performing a diff: + You can validate that your current main matches the upstream/main by performing a diff: ```console git diff upstream/main diff --git a/docs/i18n/chinese-traditional/how-to-enable-new-languages.md b/docs/i18n/chinese-traditional/how-to-enable-new-languages.md index e83092b17f2..1de91311616 100644 --- a/docs/i18n/chinese-traditional/how-to-enable-new-languages.md +++ b/docs/i18n/chinese-traditional/how-to-enable-new-languages.md @@ -142,7 +142,7 @@ export const rtlLangs = ['']; ### Set Translated SuperBlocks -In the [shared/config/superblocks.ts](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/shared/config/superblocks.ts) file, add the new language to the `notAuditedSuperBlocks` object. This lists all the superblocks which are not fully translated. Add an array of superblocks which have not been fully translated to it. For example: +In the [shared/config/superblocks.ts](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/shared/config/superblocks.ts) file, add the new language to the `notAuditedSuperBlocks` object. This lists all the superblocks which are not fully translated. Add an array of superblocks that have not been fully translated to it. For example: ```js export const notAuditedSuperBlocks: NotAuditedSuperBlocks = { @@ -166,7 +166,7 @@ export const notAuditedSuperBlocks: NotAuditedSuperBlocks = { } ``` -Be sure to only add the superblocks which are **not** fully translated and approved. The translated superblocks will be calculated from this object. When a new superblock is finished being fully translated, remove it from the array for that language. +Be sure to only add the superblocks that are **not** fully translated and approved. The translated superblocks will be calculated from this object. When a new superblock is finished being fully translated, remove it from the array for that language. See the `SuperBlocks` enum at the beginning of the same file for the full list of superblocks. @@ -174,7 +174,7 @@ See the `SuperBlocks` enum at the beginning of the same file for the full list o Next, open the [`client/src/utils/algolia-locale-setup.ts`](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/client/src/utils/algolia-locale-setup.ts) 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 the same values as the `english` object for local testing, replacing the `english` key with your language's `availableLangs` value. +Add an object for your language to the `algoliaIndices` object. You should use the same values as the `english` object for local testing, replacing the `english` key with your language's `availableLangs` value. > [!NOTE] If we have already deployed an instance of news in your target language, you can update the values to reflect the live instance. Otherwise, use the English values. @@ -229,7 +229,7 @@ You don't have to have everything in these 3 files translated at first. It's pos You can replace any URLs that you have corresponding pages ready in your language. -For example, if you have the publication in your language, you can replace the URL for `"news"`. If you want to translate articles listed in the footer links, see [How to Translate Articles in the Footer Links](language-lead-handbook.md#how-to-translate-articles-in-the-footer-links). +For example, if you have a publication in your language, you can replace the URL for `"news"`. If you want to translate articles listed in the footer links, see [How to Translate Articles in the Footer Links](language-lead-handbook.md#how-to-translate-articles-in-the-footer-links). #### `meta-tags.json` @@ -303,7 +303,7 @@ videoLocaleIds: Joi.when('challengeType', { If you would like to test translations locally, before adding them to our main repository - skip the Crowdin workflow changes. Follow the steps for enabling a language, then download the translations from Crowdin and load them into your local code. -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://discord.gg/PRyKn3Vbay), or you can translate the English markdown files locally for testing purposes. +Because the language has not been approved for production, our scripts are not automatically downloading the translations yet. Only staff have access to directly download the translations - you are welcome to reach out to us in our [contributors chat room](https://discord.gg/PRyKn3Vbay), 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. @@ -325,7 +325,7 @@ In [`shared/config/i18n.ts`](https://github.com/freeCodeCamp/freeCodeCamp/blob/m export const hiddenLangs = []; // Remove your language from the array ``` -When this PR is merged and gets deployed, the curriculum in your language will be live. +When this PR is merged and deployed, the curriculum in your language will be live. # Deploying New Languages on `/news` diff --git a/docs/i18n/chinese-traditional/how-to-help-with-video-challenges.md b/docs/i18n/chinese-traditional/how-to-help-with-video-challenges.md index af0695932a9..67e296f0157 100644 --- a/docs/i18n/chinese-traditional/how-to-help-with-video-challenges.md +++ b/docs/i18n/chinese-traditional/how-to-help-with-video-challenges.md @@ -125,7 +125,7 @@ Add/Update the question text under the part that shows: ## --text-- ``` -Add/Update answers (`Answer 1`, `Answer 2`, and so on) under `## --answers--`. Make sure to update the number under `## --video-solution--` with the correct answer number. You can add more possible answers using the same format. The question and answers can be surrounded with quotation marks. +Add/Update answers (`Answer 1`, `Answer 2`, and so on) under `## --answers--`. Make sure to update the number under `## --video-solution--` with the correct answer number. You can add more possible answers using the same format. The questions and answers can be surrounded with quotation marks. ### Question examples diff --git a/docs/i18n/chinese-traditional/how-to-open-a-pull-request.md b/docs/i18n/chinese-traditional/how-to-open-a-pull-request.md index 052b759f846..1157e7439c2 100644 --- a/docs/i18n/chinese-traditional/how-to-open-a-pull-request.md +++ b/docs/i18n/chinese-traditional/how-to-open-a-pull-request.md @@ -140,7 +140,7 @@ When you are working on regular bugs and features on our development branch `mai ### For Upcoming Curriculum and Features -When you are working on features for our upcoming curriculum `next-*` branches, you have to do a cherry pick: +When you are working on features for our upcoming curriculum `next-*` branches, you have to do a `cherry-pick`: 1. Make sure your upstream comes in sync with your local: @@ -151,7 +151,7 @@ When you are working on features for our upcoming curriculum `next-*` branches, git reset --hard upstream/next-python-projects ``` -2. Take backup +2. Take a backup a. Either delete your local branch after taking a backup (if you still have it locally): @@ -169,7 +169,7 @@ When you are working on features for our upcoming curriculum `next-*` branches, git branch -D ``` - b. Or just a backup of your pr branch (if you do not have it locally): + b. Or just a backup of your PR branch (if you do not have it locally): ```console git checkout -b origin/ diff --git a/docs/i18n/chinese-traditional/how-to-proofread-files.md b/docs/i18n/chinese-traditional/how-to-proofread-files.md index 151cdf6a205..6c4eeb4f63e 100644 --- a/docs/i18n/chinese-traditional/how-to-proofread-files.md +++ b/docs/i18n/chinese-traditional/how-to-proofread-files.md @@ -2,7 +2,7 @@ Our proofreading team is responsible for ensuring that translations accurately reflect the source text. We trust our proofreaders to ensure that we have very high quality translations. -All our translations are done by hand, by real humans. Proofreading ensures that there is a consistent tone across our all our translated resources like the curriculum. +All our translations are done by hand, by real humans. Proofreading ensures that there is a consistent tone across all our translated resources like the curriculum. To begin proofreading, visit [our translation platform](https://translate.freecodecamp.org) and login. Select "Go to console" in the top navigation bar to switch from the public view to the workspace view. @@ -49,6 +49,6 @@ Our staff team and community moderators teams are always looking for kind volunt ## Creating a Channel on Chat for a World Language -For the most part we encourage you to use the [contributors chat](https://discord.gg/PRyKn3Vbay) room for all correspondence. However if the team of volunteer translators grows for a certain language, we can consider creating additional break-out channel for the language. +For the most part, we encourage you to use the [contributors chat](https://discord.gg/PRyKn3Vbay) room for all correspondence. However if the team of volunteer translators grows for a certain language, we can consider creating an additional break-out channel for the language. If you are already a proofreader and are interested in having a dedicated channel on our chat servers for a specific language, [fill out this form](https://forms.gle/XU5CyutrYCgDYaVZA). diff --git a/docs/i18n/chinese-traditional/how-to-setup-freecodecamp-locally.md b/docs/i18n/chinese-traditional/how-to-setup-freecodecamp-locally.md index b229521a0f8..b98c69abcf1 100644 --- a/docs/i18n/chinese-traditional/how-to-setup-freecodecamp-locally.md +++ b/docs/i18n/chinese-traditional/how-to-setup-freecodecamp-locally.md @@ -4,7 +4,7 @@ Follow these guidelines for setting up a development environment for freeCodeCam > [!ATTENTION] - freeCodeCamp does not build and run natively on Windows, you will [need to use WSL2](how-to-setup-wsl.md) for a Linux-like setup on Windows. - You can't use Windows Command Prompt, Git Bash or PowerShell to build and run the codebase. - Note that if using Windows, the hardware requirements need to be more than [what we mention](how-to-setup-freecodecamp-locally?id=how-to-prepare-your-local-machine) to accommodate for WSL-based setup. -If you are looking to make a one-off contribution, you should use Gitpod to make changes. The Gitpod setup launches a ready-to-code environment in a few minutes in your web browser. For contributing long-term, we recommend you setup freeCodeCamp on your local machine. +If you are looking to make a one-off contribution, you should use Gitpod to make changes. The Gitpod setup launches a ready-to-code environment in a few minutes in your web browser. To contribute long-term, we recommend you set up freeCodeCamp on your local machine. Here are some pros and cons which should help you decide which option is best for you: @@ -19,9 +19,9 @@ Here are some pros and cons which should help you decide which option is best fo ### How to Prepare a Gitpod Workspace -We have automated the process of installing all the dependencies & tools you will need. With Gitpod you get a free ready-to-code environment in a few minutes, and is useful if you do not have access to computer or want to make one-time changes. +We have automated the process of installing all the dependencies & tools you will need. With Gitpod you get a free ready-to-code environment in a few minutes, and is useful if you do not have access to a computer or want to make one-time changes. -There are various ways to launch an Gitpod workspace: +There are various ways to launch a Gitpod workspace: 1. **(Fastest)** Prepend `gitpod.io/#` in front of any URL from GitHub. @@ -158,7 +158,7 @@ Now that you have downloaded a copy of your fork, you will need to set up an `up You need a reference from your local clone to the `upstream` repository in addition to the `origin` repository. This is so that you can sync changes from the main repository without the requirement of forking and cloning repeatedly. -1. Change directory to the new freeCodeCamp directory: +1. Change the directory to the new freeCodeCamp directory: ```console cd freeCodeCamp diff --git a/docs/i18n/chinese-traditional/how-to-setup-freecodecamp-mobile-app-locally.md b/docs/i18n/chinese-traditional/how-to-setup-freecodecamp-mobile-app-locally.md index 07b11cb8e34..412e7b91137 100644 --- a/docs/i18n/chinese-traditional/how-to-setup-freecodecamp-mobile-app-locally.md +++ b/docs/i18n/chinese-traditional/how-to-setup-freecodecamp-mobile-app-locally.md @@ -44,7 +44,7 @@ Once you have the prerequisites installed, you need to prepare your development [Forking](https://help.github.com/articles/about-forks/) is a step where you get your own copy of the repository (a.k.a _repo_) on GitHub. -This is essential, as it allows you to work on your own copy of freeCodeCamp mobile app on GitHub, or to download (clone) your repository to work on locally. Later, you will be able to request changes to be pulled into the main repository from your fork via a pull request (PR). +This is essential, as it allows you to work on your own copy of the freeCodeCamp mobile app on GitHub, or to download (clone) your repository to work on locally. Later, you will be able to request changes to be pulled into the main repository from your fork via a pull request (PR). > [!TIP] The main repository at `https://github.com/freeCodeCamp/mobile` is often referred to as the `upstream` repository. > @@ -361,14 +361,14 @@ Follow these steps: > [!NOTE] You only need to follow this section if you're modifying the challenge test runner in the mobile app. Otherwise, you can go to the next section on [how to open a pull request](#proposing-a-pull-request-pr). -1. Clone a copy of the [freeCodeCamp repo](https://github.com/freeCodeCamp/freeCodeCamp) locally outside of your local copy of freeCodeCamp mobile repo. Your folder structure should look like this: +1. Clone a copy of the [freeCodeCamp repo](https://github.com/freeCodeCamp/freeCodeCamp) locally outside of your local copy of the freeCodeCamp mobile repo. Your folder structure should look like this: ```console ├── freeCodeCamp ├── mobile ``` -2. Change directory to the freeCodeCamp repo: +2. Change the directory to the freeCodeCamp repo: ```console cd freeCodeCamp @@ -480,7 +480,7 @@ If you are on a different OS and/or are still running into issues, see [getting ### Issues with the UI, build errors, etc. -If you face issues with the UI, or builds errors a cleanup can be useful: +If you face issues with the UI, or build errors a cleanup can be useful: ```console flutter clean @@ -488,7 +488,7 @@ flutter clean ### Issues Installing Dependencies -If you get errors while installing the dependencies, please make sure that you are not in a restricted network or your firewall settings do not prevent you from accessing resources. +If you get errors while installing the dependencies, please make sure that you are not in a restricted network or that your firewall settings do not prevent you from accessing resources. Be patient as the first-time setup can take a while depending on your network bandwidth. diff --git a/docs/i18n/chinese-traditional/how-to-setup-wsl.md b/docs/i18n/chinese-traditional/how-to-setup-wsl.md index 04514807d94..97910f5ab77 100644 --- a/docs/i18n/chinese-traditional/how-to-setup-wsl.md +++ b/docs/i18n/chinese-traditional/how-to-setup-wsl.md @@ -123,7 +123,7 @@ Now that you have installed the pre-requisites, follow [our local setup guide](h > [!WARNING] > -> Please note, at this time the setup for Cypress tests (and related GUI needs) are a work in progress. You should still be able to work on most of the codebase. +> Please note, at this time the setup for Cypress tests (and related GUI needs) is a work in progress. You should still be able to work on most of the codebase. ## Useful Links diff --git a/docs/i18n/chinese-traditional/how-to-use-docker-on-windows-home.md b/docs/i18n/chinese-traditional/how-to-use-docker-on-windows-home.md index f091299dcd9..21438241f8d 100644 --- a/docs/i18n/chinese-traditional/how-to-use-docker-on-windows-home.md +++ b/docs/i18n/chinese-traditional/how-to-use-docker-on-windows-home.md @@ -2,7 +2,7 @@ There are a few pitfalls to be avoided when setting up Docker on Windows Home. First of all, you have to use [Docker Toolbox](https://docs.docker.com/toolbox/toolbox_install_windows/) as Administrator. Unfortunately Windows Home does not support Docker for Windows Desktop, so Toolbox must be used instead. It has to be run as Administrator as the installation uses symlinks, which cannot be created otherwise. -Once you've installed the toolbox, run Docker Quickstart Terminal as Administrator. This will create a `default` virtual machine if it does not already exist. Once that has happened, close the terminal and open VirtualBox (again as Administrator). You should be able to see the `default` machine. The site is quite resource-intensive, so stop the virtual machine and raise the settings as much as you can - memory in particular. It has been confirmed to work with 4GB of ram. +Once you've installed the toolbox, run Docker Quickstart Terminal as Administrator. This will create a `default` virtual machine if it does not already exist. Once that has happened, close the terminal and open VirtualBox (again as Administrator). You should be able to see the `default` machine. The site is quite resource-intensive, so stop the virtual machine and raise the settings as much as you can - memory in particular. It has been confirmed to work with 4GB of RAM. Once you're happy that Docker is working, clone the freeCodeCamp repository to a directory inside `C:\Users`. These directories are shared giving Docker access to the local directories, which it needs during installation. diff --git a/docs/i18n/chinese-traditional/how-to-work-on-coding-challenges.md b/docs/i18n/chinese-traditional/how-to-work-on-coding-challenges.md index 7fb51f7455a..3ecdd2d246e 100644 --- a/docs/i18n/chinese-traditional/how-to-work-on-coding-challenges.md +++ b/docs/i18n/chinese-traditional/how-to-work-on-coding-challenges.md @@ -4,7 +4,7 @@ Our goal is to develop a fun and clear interactive learning experience. Designing interactive coding challenges is difficult. It would be much easier to write a lengthy explanation or to create a video tutorial. But for our core curriculum, we're sticking with what works best for most people - a fully interactive, video game-like experience. -We want campers to achieve a flow state. We want them to build momentum and blast through our curriculum with as few snags as possible. We want them to go into the projects with confidence and gain a wide exposure to programming concepts. +We want campers to achieve a flow state. We want them to build momentum and blast through our curriculum with as few snags as possible. We want them to go into the projects with confidence and gain wide exposure to programming concepts. Note that for Version 7.0 of the freeCodeCamp curriculum, we are moving toward [an entirely project-focused model with a lot more repetition](https://www.freecodecamp.org/news/python-curriculum-is-live/). @@ -554,7 +554,7 @@ b c ``` -And you choose `b`, your new order will be: +If you choose `b`, your new order will be: ```bash a diff --git a/docs/i18n/chinese-traditional/how-to-work-on-localized-client-webapp.md b/docs/i18n/chinese-traditional/how-to-work-on-localized-client-webapp.md index a862f8e6d30..b1f4834855a 100644 --- a/docs/i18n/chinese-traditional/how-to-work-on-localized-client-webapp.md +++ b/docs/i18n/chinese-traditional/how-to-work-on-localized-client-webapp.md @@ -8,13 +8,13 @@ Once you have set up the project locally you should be able to follow this docum 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 to translate 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. ## File Structure -Most of the files for translating the platform are located in the [`client/i18n`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/client/i18n) folder. Each language has a directory within that containing JSON files with the translations. +Most of the files for translating the platform are located in the [`client/i18n`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/client/i18n) folder. Each language has a directory that contains JSON files with the translations. ```console config @@ -55,7 +55,7 @@ Most of the files for translating the platform are located in the [`client/i18n` └── validate-keys.ts ``` -Some of these files are translated on our translation platform (Crowdin) and some are translated or created via PR's on GitHub. +Some of these files are translated on our translation platform (Crowdin) and some are translated or created via PRs on GitHub. **Files translated on our translation platform:** diff --git a/docs/i18n/chinese-traditional/how-to-work-on-practice-projects.md b/docs/i18n/chinese-traditional/how-to-work-on-practice-projects.md index f0caaf64b9f..e3a62924e56 100644 --- a/docs/i18n/chinese-traditional/how-to-work-on-practice-projects.md +++ b/docs/i18n/chinese-traditional/how-to-work-on-practice-projects.md @@ -38,7 +38,7 @@ Clicking this button will add a new step at the end of the project. This step wi #### Create Empty Steps -Enter the number of steps you want to add in the input. Then, clicking the button will create that many empty steps at the end of the project. +Enter the number of steps you want to add in the input. Then, clicking the button will create many empty steps at the end of the project. #### Insert Step @@ -124,7 +124,7 @@ pnpm run delete-step X # where X is the step number to be deleted. ### update-step-titles -A one-off script that automatically updates the frontmatter in a project's markdown files so that they are consistent with the project's meta.json. It ensures that each step's title (and dashedName) match the meta's challengeOrder. +A one-off script that automatically updates the frontmatter in a project's markdown files so that they are consistent with the project's meta.json. It ensures that each step's title (and dashedName) matches the meta's `challengeOrder`. #### How to Run the Script diff --git a/docs/i18n/chinese-traditional/how-to-work-on-tutorials-that-use-coderoad.md b/docs/i18n/chinese-traditional/how-to-work-on-tutorials-that-use-coderoad.md index b4f3ab4a1d9..182565a1ca0 100644 --- a/docs/i18n/chinese-traditional/how-to-work-on-tutorials-that-use-coderoad.md +++ b/docs/i18n/chinese-traditional/how-to-work-on-tutorials-that-use-coderoad.md @@ -56,7 +56,7 @@ If you want to test your changes to `main` after using the above instructions, f - Follow the instructions on the [rdb-alpha repo](https://github.com/freeCodeCamp/rdb-alpha) to run a container - Start the tutorial using the `tutorial.json` file on the new branch -### Reviewing PR's to `main` +### Reviewing PRs to `main` If reviewing a PR that only changes `main` with instructional or grammar issues as described above, the changes in `TUTORIAL.md` should match the changes in `tutorial.json`. @@ -119,11 +119,11 @@ If you have write access to the freeCodeCamp repo, have verified the `CHANGELOG` - Make a PR to `main` on the freeCodeCamp repo - If you are satisfied, merge it or leave it and ask for a review from someone - After the PR is merged, open the tutorial by following the instructions on the [rdb-alpha repo](https://github.com/freeCodeCamp/rdb-alpha) to make sure it's loading properly, and that you can get through a few steps -- Finally, if any PRs for this version exists, close them +- Finally, if any PRs for this version exist, close them ### How to Revert to a Previous Version -- Create a new branch off the latest `main` with `git checkout -b revert/to-version-X.X.X` +- Create a new branch off of the latest `main` with `git checkout -b revert/to-version-X.X.X` - Revert all commits on this branch up to and including the commit of the version after the one you want to revert to. For example, you may have commits that look like this: ``` diff --git a/docs/i18n/chinese-traditional/language-lead-handbook.md b/docs/i18n/chinese-traditional/language-lead-handbook.md index 5ad785ce3fe..113564728ba 100644 --- a/docs/i18n/chinese-traditional/language-lead-handbook.md +++ b/docs/i18n/chinese-traditional/language-lead-handbook.md @@ -339,7 +339,7 @@ In Crowdin, individuate the `User management` on the left-hand side menu. This will open the user management tools, you will be able to see the list of all the users. -Search for the user that will become a proofreader. Use the three dots menu on the user row to open a menu and select "Add to team". The proofreader teams have a standard name of `Proof Readers ()`, you can search the team using the language name. Once you have selected the team, use the "ADD" button at the bottom of the page to finalize the thing. +Search for the user who will become a proofreader. Use the three dots menu on the user row to open a menu and select "Add to team". The proofreader teams have a standard name of `Proof Readers ()`, you can search the team using the language name. Once you have selected the team, use the "ADD" button at the bottom of the page to finalize the thing. The user is now a proofreader. diff --git a/docs/i18n/chinese-traditional/moderator-handbook.md b/docs/i18n/chinese-traditional/moderator-handbook.md index 61e4f636b6d..bbefc6d8b99 100644 --- a/docs/i18n/chinese-traditional/moderator-handbook.md +++ b/docs/i18n/chinese-traditional/moderator-handbook.md @@ -18,7 +18,7 @@ freeCodeCamp 是一個包容的社區，我們需要保持這種狀態。 We have a single [Code of Conduct](https://code-of-conduct.freecodecamp.org) that governs our entire community. 規則越少，就越容易記住。 你可以在[這裏](https://code-of-conduct.freecodecamp.org)閱讀這些規則，並把它們記在心裏。 -> [!NOTE] As a moderator, we would add you to one or more teams on GitHub, our community forums & 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). +> [!NOTE] As a moderator, we would add you to one or more teams on GitHub, our community forums & chat servers. If you are missing access to a platform that you would like to moderate, please [reach out to a staff member](FAQ.md#additional-assistance). ## 管理 GitHub @@ -164,7 +164,7 @@ As a moderator, you help keep our community an enjoyable place for anyone to lea Note that once you are a moderator on the forum, you will start to see blue moderator hints about forum members, like "this is the first time [person] has posted - let's welcome them to the community!" or "[person] hasn't posted in a long time - let's welcome them back." -![A blue text message saying "this is the first time [person] has posted - let's welcome them to the community!](https://i.imgur.com/mPmVgzK.png) +![A blue text message saying "This is the first time [person] has posted - let's welcome them to the community!](https://i.imgur.com/mPmVgzK.png) These are opportunities for you to welcome them and make them feel extra special. You never know which person who's marginally involved may become our next super-helper, helping many other people in their coding journey. Even the slightest kindness may trigger a cascade of good deeds. diff --git a/docs/i18n/chinese-traditional/reply-templates.md b/docs/i18n/chinese-traditional/reply-templates.md index a1a9bbcc41c..d5c5110346b 100644 --- a/docs/i18n/chinese-traditional/reply-templates.md +++ b/docs/i18n/chinese-traditional/reply-templates.md @@ -183,7 +183,7 @@ If the forum members determine there is nothing wrong with your code, you can re Thank you and happy coding. ``` -> When an issue is duplicate of an earlier issue. +> When an issue is a duplicate of an earlier issue. ```markdown Thank you for reporting this issue. @@ -230,7 +230,7 @@ Happy contributing. ```md We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. -Issues labelled with `help wanted` or `first timers only` are open for contributions. +Issues labeled with `help wanted` or `first timers only` are open for contributions. Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. ``` diff --git a/docs/i18n/chinese-traditional/troubleshooting-development-issues.md b/docs/i18n/chinese-traditional/troubleshooting-development-issues.md index 84569c6fbf7..962fd04362c 100644 --- a/docs/i18n/chinese-traditional/troubleshooting-development-issues.md +++ b/docs/i18n/chinese-traditional/troubleshooting-development-issues.md @@ -31,7 +31,7 @@ Use the shortcut pnpm run clean-and-develop ``` -If you continue to face issues with the build, cleaning up the workspace is recommend. +If you continue to face issues with the build, cleaning up the workspace is recommended. Use `git clean` in interactive mode: @@ -50,7 +50,7 @@ git clean -ifdX ## Issues with API, login, Challenge Submissions, etc. -If you can't sign in, and instead you see a banner with an error message that it will be reported to freeCodeCamp, please double-check that your local port `3000` is not in use by a different program. +If you can't sign in, and instead you see a banner with an error message saying that the error will be reported to freeCodeCamp, please double-check that your local port `3000` is not in use by a different program. #### **From Terminal:** ```console diff --git a/docs/i18n/chinese/authors-analytics-manual.md b/docs/i18n/chinese/authors-analytics-manual.md index 221ca725cd9..fa5bbe46392 100644 --- a/docs/i18n/chinese/authors-analytics-manual.md +++ b/docs/i18n/chinese/authors-analytics-manual.md @@ -1,10 +1,10 @@ # Authors Analytics Manual -If you are an author with access to the publication's Google Analytics Property (News), you can use this guide to view your articles engagement and search for articles by publication language. +If you are an author with access to the publication's Google Analytics Property (News), you can use this guide to view your article engagement and search for articles by publication language. ## Search by Language -To search for engagement reports by a specific language: +To search for engagement reports in a specific language: ![Image - Show steps to search by language on googla analytics](https://contribute.freecodecamp.org/images/google-analytics/search-by-language.png) diff --git a/docs/i18n/chinese/codebase-best-practices.md b/docs/i18n/chinese/codebase-best-practices.md index 3a0a50e17ae..a2253ffb3b3 100644 --- a/docs/i18n/chinese/codebase-best-practices.md +++ b/docs/i18n/chinese/codebase-best-practices.md @@ -161,7 +161,7 @@ The `api/` tests are split into two parts: Unit tests isolate a single function or component. The tests do not need mocking, but will require fixtures. -The unit tests are located in a new file adjacent the file exporting that being tested: +The unit tests are located in a new file adjacent to the file exporting that is being tested: ```text api/ diff --git a/docs/i18n/chinese/how-to-catch-outgoing-emails-locally.md b/docs/i18n/chinese/how-to-catch-outgoing-emails-locally.md index b15b0e10474..a4631290c5f 100644 --- a/docs/i18n/chinese/how-to-catch-outgoing-emails-locally.md +++ b/docs/i18n/chinese/how-to-catch-outgoing-emails-locally.md @@ -104,7 +104,7 @@ mailhog ## Using MailHog -Open a new browser tab or window and navigate to [http://localhost:8025](http://localhost:8025) to open your MailHog inbox when the MailHog installation has completed and MailHog is running. +Open a new browser tab or window and navigate to [http://localhost:8025](http://localhost:8025) to open your MailHog inbox when the MailHog installation has been completed and MailHog is running. ## Useful Links diff --git a/docs/i18n/chinese/how-to-contribute-to-the-codebase.md b/docs/i18n/chinese/how-to-contribute-to-the-codebase.md index 3ee01e7f9c9..0068611fc50 100644 --- a/docs/i18n/chinese/how-to-contribute-to-the-codebase.md +++ b/docs/i18n/chinese/how-to-contribute-to-the-codebase.md @@ -23,7 +23,7 @@ Follow these steps: nothing to commit, working directory clean ``` - If you got different message, then you aren't on main or your working directory isn't clean, resolve any outstanding files/commits and checkout `main`: + If you got a different message, then you aren't on main or your working directory isn't clean, resolve any outstanding files/commits and checkout `main`: ```console git checkout main @@ -55,7 +55,7 @@ Follow these steps: git push origin main --force ``` - You can validate your current main matches the upstream/main by performing a diff: + You can validate that your current main matches the upstream/main by performing a diff: ```console git diff upstream/main diff --git a/docs/i18n/chinese/how-to-enable-new-languages.md b/docs/i18n/chinese/how-to-enable-new-languages.md index cd7895ca2eb..1dde283c1a2 100644 --- a/docs/i18n/chinese/how-to-enable-new-languages.md +++ b/docs/i18n/chinese/how-to-enable-new-languages.md @@ -142,7 +142,7 @@ export const rtlLangs = ['']; ### Set Translated SuperBlocks -In the [shared/config/superblocks.ts](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/shared/config/superblocks.ts) file, add the new language to the `notAuditedSuperBlocks` object. This lists all the superblocks which are not fully translated. Add an array of superblocks which have not been fully translated to it. For example: +In the [shared/config/superblocks.ts](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/shared/config/superblocks.ts) file, add the new language to the `notAuditedSuperBlocks` object. This lists all the superblocks which are not fully translated. Add an array of superblocks that have not been fully translated to it. For example: ```js export const notAuditedSuperBlocks: NotAuditedSuperBlocks = { @@ -166,7 +166,7 @@ export const notAuditedSuperBlocks: NotAuditedSuperBlocks = { } ``` -Be sure to only add the superblocks which are **not** fully translated and approved. The translated superblocks will be calculated from this object. When a new superblock is finished being fully translated, remove it from the array for that language. +Be sure to only add the superblocks that are **not** fully translated and approved. The translated superblocks will be calculated from this object. When a new superblock is finished being fully translated, remove it from the array for that language. See the `SuperBlocks` enum at the beginning of the same file for the full list of superblocks. @@ -174,7 +174,7 @@ See the `SuperBlocks` enum at the beginning of the same file for the full list o Next, open the [`client/src/utils/algolia-locale-setup.ts`](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/client/src/utils/algolia-locale-setup.ts) 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 the same values as the `english` object for local testing, replacing the `english` key with your language's `availableLangs` value. +Add an object for your language to the `algoliaIndices` object. You should use the same values as the `english` object for local testing, replacing the `english` key with your language's `availableLangs` value. > [!NOTE] If we have already deployed an instance of news in your target language, you can update the values to reflect the live instance. Otherwise, use the English values. @@ -229,7 +229,7 @@ You don't have to have everything in these 3 files translated at first. It's pos You can replace any URLs that you have corresponding pages ready in your language. -For example, if you have the publication in your language, you can replace the URL for `"news"`. If you want to translate articles listed in the footer links, see [How to Translate Articles in the Footer Links](language-lead-handbook.md#how-to-translate-articles-in-the-footer-links). +For example, if you have a publication in your language, you can replace the URL for `"news"`. If you want to translate articles listed in the footer links, see [How to Translate Articles in the Footer Links](language-lead-handbook.md#how-to-translate-articles-in-the-footer-links). #### `meta-tags.json` @@ -303,7 +303,7 @@ videoLocaleIds: Joi.when('challengeType', { If you would like to test translations locally, before adding them to our main repository - skip the Crowdin workflow changes. Follow the steps for enabling a language, then download the translations from Crowdin and load them into your local code. -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://discord.gg/PRyKn3Vbay), or you can translate the English markdown files locally for testing purposes. +Because the language has not been approved for production, our scripts are not automatically downloading the translations yet. Only staff have access to directly download the translations - you are welcome to reach out to us in our [contributors chat room](https://discord.gg/PRyKn3Vbay), 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. @@ -325,7 +325,7 @@ In [`shared/config/i18n.ts`](https://github.com/freeCodeCamp/freeCodeCamp/blob/m export const hiddenLangs = []; // Remove your language from the array ``` -When this PR is merged and gets deployed, the curriculum in your language will be live. +When this PR is merged and deployed, the curriculum in your language will be live. # Deploying New Languages on `/news` diff --git a/docs/i18n/chinese/how-to-help-with-video-challenges.md b/docs/i18n/chinese/how-to-help-with-video-challenges.md index af0695932a9..67e296f0157 100644 --- a/docs/i18n/chinese/how-to-help-with-video-challenges.md +++ b/docs/i18n/chinese/how-to-help-with-video-challenges.md @@ -125,7 +125,7 @@ Add/Update the question text under the part that shows: ## --text-- ``` -Add/Update answers (`Answer 1`, `Answer 2`, and so on) under `## --answers--`. Make sure to update the number under `## --video-solution--` with the correct answer number. You can add more possible answers using the same format. The question and answers can be surrounded with quotation marks. +Add/Update answers (`Answer 1`, `Answer 2`, and so on) under `## --answers--`. Make sure to update the number under `## --video-solution--` with the correct answer number. You can add more possible answers using the same format. The questions and answers can be surrounded with quotation marks. ### Question examples 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 052b759f846..1157e7439c2 100644 --- a/docs/i18n/chinese/how-to-open-a-pull-request.md +++ b/docs/i18n/chinese/how-to-open-a-pull-request.md @@ -140,7 +140,7 @@ When you are working on regular bugs and features on our development branch `mai ### For Upcoming Curriculum and Features -When you are working on features for our upcoming curriculum `next-*` branches, you have to do a cherry pick: +When you are working on features for our upcoming curriculum `next-*` branches, you have to do a `cherry-pick`: 1. Make sure your upstream comes in sync with your local: @@ -151,7 +151,7 @@ When you are working on features for our upcoming curriculum `next-*` branches, git reset --hard upstream/next-python-projects ``` -2. Take backup +2. Take a backup a. Either delete your local branch after taking a backup (if you still have it locally): @@ -169,7 +169,7 @@ When you are working on features for our upcoming curriculum `next-*` branches, git branch -D ``` - b. Or just a backup of your pr branch (if you do not have it locally): + b. Or just a backup of your PR branch (if you do not have it locally): ```console git checkout -b origin/ diff --git a/docs/i18n/chinese/how-to-proofread-files.md b/docs/i18n/chinese/how-to-proofread-files.md index c7cd85d78b3..8ef0dcab8f6 100644 --- a/docs/i18n/chinese/how-to-proofread-files.md +++ b/docs/i18n/chinese/how-to-proofread-files.md @@ -2,7 +2,7 @@ Our proofreading team is responsible for ensuring that translations accurately reflect the source text. We trust our proofreaders to ensure that we have very high quality translations. -All our translations are done by hand, by real humans. Proofreading ensures that there is a consistent tone across our all our translated resources like the curriculum. +All our translations are done by hand, by real humans. Proofreading ensures that there is a consistent tone across all our translated resources like the curriculum. To begin proofreading, visit [our translation platform](https://translate.freecodecamp.org) and login. Select "Go to console" in the top navigation bar to switch from the public view to the workspace view. @@ -49,6 +49,6 @@ Our staff team and community moderators teams are always looking for kind volunt ## Creating a Channel on Chat for a World Language -For the most part we encourage you to use the [contributors chat](https://discord.gg/PRyKn3Vbay) room for all correspondence. However if the team of volunteer translators grows for a certain language, we can consider creating additional break-out channel for the language. +For the most part, we encourage you to use the [contributors chat](https://discord.gg/PRyKn3Vbay) room for all correspondence. However if the team of volunteer translators grows for a certain language, we can consider creating an additional break-out channel for the language. If you are already a proofreader and are interested in having a dedicated channel on our chat servers for a specific language, [fill out this form](https://forms.gle/XU5CyutrYCgDYaVZA). diff --git a/docs/i18n/chinese/how-to-setup-freecodecamp-locally.md b/docs/i18n/chinese/how-to-setup-freecodecamp-locally.md index b229521a0f8..b98c69abcf1 100644 --- a/docs/i18n/chinese/how-to-setup-freecodecamp-locally.md +++ b/docs/i18n/chinese/how-to-setup-freecodecamp-locally.md @@ -4,7 +4,7 @@ Follow these guidelines for setting up a development environment for freeCodeCam > [!ATTENTION] - freeCodeCamp does not build and run natively on Windows, you will [need to use WSL2](how-to-setup-wsl.md) for a Linux-like setup on Windows. - You can't use Windows Command Prompt, Git Bash or PowerShell to build and run the codebase. - Note that if using Windows, the hardware requirements need to be more than [what we mention](how-to-setup-freecodecamp-locally?id=how-to-prepare-your-local-machine) to accommodate for WSL-based setup. -If you are looking to make a one-off contribution, you should use Gitpod to make changes. The Gitpod setup launches a ready-to-code environment in a few minutes in your web browser. For contributing long-term, we recommend you setup freeCodeCamp on your local machine. +If you are looking to make a one-off contribution, you should use Gitpod to make changes. The Gitpod setup launches a ready-to-code environment in a few minutes in your web browser. To contribute long-term, we recommend you set up freeCodeCamp on your local machine. Here are some pros and cons which should help you decide which option is best for you: @@ -19,9 +19,9 @@ Here are some pros and cons which should help you decide which option is best fo ### How to Prepare a Gitpod Workspace -We have automated the process of installing all the dependencies & tools you will need. With Gitpod you get a free ready-to-code environment in a few minutes, and is useful if you do not have access to computer or want to make one-time changes. +We have automated the process of installing all the dependencies & tools you will need. With Gitpod you get a free ready-to-code environment in a few minutes, and is useful if you do not have access to a computer or want to make one-time changes. -There are various ways to launch an Gitpod workspace: +There are various ways to launch a Gitpod workspace: 1. **(Fastest)** Prepend `gitpod.io/#` in front of any URL from GitHub. @@ -158,7 +158,7 @@ Now that you have downloaded a copy of your fork, you will need to set up an `up You need a reference from your local clone to the `upstream` repository in addition to the `origin` repository. This is so that you can sync changes from the main repository without the requirement of forking and cloning repeatedly. -1. Change directory to the new freeCodeCamp directory: +1. Change the directory to the new freeCodeCamp directory: ```console cd freeCodeCamp diff --git a/docs/i18n/chinese/how-to-setup-freecodecamp-mobile-app-locally.md b/docs/i18n/chinese/how-to-setup-freecodecamp-mobile-app-locally.md index 07b11cb8e34..412e7b91137 100644 --- a/docs/i18n/chinese/how-to-setup-freecodecamp-mobile-app-locally.md +++ b/docs/i18n/chinese/how-to-setup-freecodecamp-mobile-app-locally.md @@ -44,7 +44,7 @@ Once you have the prerequisites installed, you need to prepare your development [Forking](https://help.github.com/articles/about-forks/) is a step where you get your own copy of the repository (a.k.a _repo_) on GitHub. -This is essential, as it allows you to work on your own copy of freeCodeCamp mobile app on GitHub, or to download (clone) your repository to work on locally. Later, you will be able to request changes to be pulled into the main repository from your fork via a pull request (PR). +This is essential, as it allows you to work on your own copy of the freeCodeCamp mobile app on GitHub, or to download (clone) your repository to work on locally. Later, you will be able to request changes to be pulled into the main repository from your fork via a pull request (PR). > [!TIP] The main repository at `https://github.com/freeCodeCamp/mobile` is often referred to as the `upstream` repository. > @@ -361,14 +361,14 @@ Follow these steps: > [!NOTE] You only need to follow this section if you're modifying the challenge test runner in the mobile app. Otherwise, you can go to the next section on [how to open a pull request](#proposing-a-pull-request-pr). -1. Clone a copy of the [freeCodeCamp repo](https://github.com/freeCodeCamp/freeCodeCamp) locally outside of your local copy of freeCodeCamp mobile repo. Your folder structure should look like this: +1. Clone a copy of the [freeCodeCamp repo](https://github.com/freeCodeCamp/freeCodeCamp) locally outside of your local copy of the freeCodeCamp mobile repo. Your folder structure should look like this: ```console ├── freeCodeCamp ├── mobile ``` -2. Change directory to the freeCodeCamp repo: +2. Change the directory to the freeCodeCamp repo: ```console cd freeCodeCamp @@ -480,7 +480,7 @@ If you are on a different OS and/or are still running into issues, see [getting ### Issues with the UI, build errors, etc. -If you face issues with the UI, or builds errors a cleanup can be useful: +If you face issues with the UI, or build errors a cleanup can be useful: ```console flutter clean @@ -488,7 +488,7 @@ flutter clean ### Issues Installing Dependencies -If you get errors while installing the dependencies, please make sure that you are not in a restricted network or your firewall settings do not prevent you from accessing resources. +If you get errors while installing the dependencies, please make sure that you are not in a restricted network or that your firewall settings do not prevent you from accessing resources. Be patient as the first-time setup can take a while depending on your network bandwidth. diff --git a/docs/i18n/chinese/how-to-setup-wsl.md b/docs/i18n/chinese/how-to-setup-wsl.md index 04514807d94..97910f5ab77 100644 --- a/docs/i18n/chinese/how-to-setup-wsl.md +++ b/docs/i18n/chinese/how-to-setup-wsl.md @@ -123,7 +123,7 @@ Now that you have installed the pre-requisites, follow [our local setup guide](h > [!WARNING] > -> Please note, at this time the setup for Cypress tests (and related GUI needs) are a work in progress. You should still be able to work on most of the codebase. +> Please note, at this time the setup for Cypress tests (and related GUI needs) is a work in progress. You should still be able to work on most of the codebase. ## Useful Links diff --git a/docs/i18n/chinese/how-to-use-docker-on-windows-home.md b/docs/i18n/chinese/how-to-use-docker-on-windows-home.md index f091299dcd9..21438241f8d 100644 --- a/docs/i18n/chinese/how-to-use-docker-on-windows-home.md +++ b/docs/i18n/chinese/how-to-use-docker-on-windows-home.md @@ -2,7 +2,7 @@ There are a few pitfalls to be avoided when setting up Docker on Windows Home. First of all, you have to use [Docker Toolbox](https://docs.docker.com/toolbox/toolbox_install_windows/) as Administrator. Unfortunately Windows Home does not support Docker for Windows Desktop, so Toolbox must be used instead. It has to be run as Administrator as the installation uses symlinks, which cannot be created otherwise. -Once you've installed the toolbox, run Docker Quickstart Terminal as Administrator. This will create a `default` virtual machine if it does not already exist. Once that has happened, close the terminal and open VirtualBox (again as Administrator). You should be able to see the `default` machine. The site is quite resource-intensive, so stop the virtual machine and raise the settings as much as you can - memory in particular. It has been confirmed to work with 4GB of ram. +Once you've installed the toolbox, run Docker Quickstart Terminal as Administrator. This will create a `default` virtual machine if it does not already exist. Once that has happened, close the terminal and open VirtualBox (again as Administrator). You should be able to see the `default` machine. The site is quite resource-intensive, so stop the virtual machine and raise the settings as much as you can - memory in particular. It has been confirmed to work with 4GB of RAM. Once you're happy that Docker is working, clone the freeCodeCamp repository to a directory inside `C:\Users`. These directories are shared giving Docker access to the local directories, which it needs during installation. 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 7fb51f7455a..3ecdd2d246e 100644 --- a/docs/i18n/chinese/how-to-work-on-coding-challenges.md +++ b/docs/i18n/chinese/how-to-work-on-coding-challenges.md @@ -4,7 +4,7 @@ Our goal is to develop a fun and clear interactive learning experience. Designing interactive coding challenges is difficult. It would be much easier to write a lengthy explanation or to create a video tutorial. But for our core curriculum, we're sticking with what works best for most people - a fully interactive, video game-like experience. -We want campers to achieve a flow state. We want them to build momentum and blast through our curriculum with as few snags as possible. We want them to go into the projects with confidence and gain a wide exposure to programming concepts. +We want campers to achieve a flow state. We want them to build momentum and blast through our curriculum with as few snags as possible. We want them to go into the projects with confidence and gain wide exposure to programming concepts. Note that for Version 7.0 of the freeCodeCamp curriculum, we are moving toward [an entirely project-focused model with a lot more repetition](https://www.freecodecamp.org/news/python-curriculum-is-live/). @@ -554,7 +554,7 @@ b c ``` -And you choose `b`, your new order will be: +If you choose `b`, your new order will be: ```bash a 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 a862f8e6d30..b1f4834855a 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 @@ -8,13 +8,13 @@ Once you have set up the project locally you should be able to follow this docum 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 to translate 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. ## File Structure -Most of the files for translating the platform are located in the [`client/i18n`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/client/i18n) folder. Each language has a directory within that containing JSON files with the translations. +Most of the files for translating the platform are located in the [`client/i18n`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/client/i18n) folder. Each language has a directory that contains JSON files with the translations. ```console config @@ -55,7 +55,7 @@ Most of the files for translating the platform are located in the [`client/i18n` └── validate-keys.ts ``` -Some of these files are translated on our translation platform (Crowdin) and some are translated or created via PR's on GitHub. +Some of these files are translated on our translation platform (Crowdin) and some are translated or created via PRs on GitHub. **Files translated on our translation 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 f0caaf64b9f..e3a62924e56 100644 --- a/docs/i18n/chinese/how-to-work-on-practice-projects.md +++ b/docs/i18n/chinese/how-to-work-on-practice-projects.md @@ -38,7 +38,7 @@ Clicking this button will add a new step at the end of the project. This step wi #### Create Empty Steps -Enter the number of steps you want to add in the input. Then, clicking the button will create that many empty steps at the end of the project. +Enter the number of steps you want to add in the input. Then, clicking the button will create many empty steps at the end of the project. #### Insert Step @@ -124,7 +124,7 @@ pnpm run delete-step X # where X is the step number to be deleted. ### update-step-titles -A one-off script that automatically updates the frontmatter in a project's markdown files so that they are consistent with the project's meta.json. It ensures that each step's title (and dashedName) match the meta's challengeOrder. +A one-off script that automatically updates the frontmatter in a project's markdown files so that they are consistent with the project's meta.json. It ensures that each step's title (and dashedName) matches the meta's `challengeOrder`. #### How to Run the Script diff --git a/docs/i18n/chinese/how-to-work-on-tutorials-that-use-coderoad.md b/docs/i18n/chinese/how-to-work-on-tutorials-that-use-coderoad.md index b4f3ab4a1d9..182565a1ca0 100644 --- a/docs/i18n/chinese/how-to-work-on-tutorials-that-use-coderoad.md +++ b/docs/i18n/chinese/how-to-work-on-tutorials-that-use-coderoad.md @@ -56,7 +56,7 @@ If you want to test your changes to `main` after using the above instructions, f - Follow the instructions on the [rdb-alpha repo](https://github.com/freeCodeCamp/rdb-alpha) to run a container - Start the tutorial using the `tutorial.json` file on the new branch -### Reviewing PR's to `main` +### Reviewing PRs to `main` If reviewing a PR that only changes `main` with instructional or grammar issues as described above, the changes in `TUTORIAL.md` should match the changes in `tutorial.json`. @@ -119,11 +119,11 @@ If you have write access to the freeCodeCamp repo, have verified the `CHANGELOG` - Make a PR to `main` on the freeCodeCamp repo - If you are satisfied, merge it or leave it and ask for a review from someone - After the PR is merged, open the tutorial by following the instructions on the [rdb-alpha repo](https://github.com/freeCodeCamp/rdb-alpha) to make sure it's loading properly, and that you can get through a few steps -- Finally, if any PRs for this version exists, close them +- Finally, if any PRs for this version exist, close them ### How to Revert to a Previous Version -- Create a new branch off the latest `main` with `git checkout -b revert/to-version-X.X.X` +- Create a new branch off of the latest `main` with `git checkout -b revert/to-version-X.X.X` - Revert all commits on this branch up to and including the commit of the version after the one you want to revert to. For example, you may have commits that look like this: ``` diff --git a/docs/i18n/chinese/language-lead-handbook.md b/docs/i18n/chinese/language-lead-handbook.md index 5ad785ce3fe..113564728ba 100644 --- a/docs/i18n/chinese/language-lead-handbook.md +++ b/docs/i18n/chinese/language-lead-handbook.md @@ -339,7 +339,7 @@ In Crowdin, individuate the `User management` on the left-hand side menu. This will open the user management tools, you will be able to see the list of all the users. -Search for the user that will become a proofreader. Use the three dots menu on the user row to open a menu and select "Add to team". The proofreader teams have a standard name of `Proof Readers ()`, you can search the team using the language name. Once you have selected the team, use the "ADD" button at the bottom of the page to finalize the thing. +Search for the user who will become a proofreader. Use the three dots menu on the user row to open a menu and select "Add to team". The proofreader teams have a standard name of `Proof Readers ()`, you can search the team using the language name. Once you have selected the team, use the "ADD" button at the bottom of the page to finalize the thing. The user is now a proofreader. diff --git a/docs/i18n/chinese/moderator-handbook.md b/docs/i18n/chinese/moderator-handbook.md index e273ae517c0..b648f5d6a4a 100644 --- a/docs/i18n/chinese/moderator-handbook.md +++ b/docs/i18n/chinese/moderator-handbook.md @@ -18,7 +18,7 @@ freeCodeCamp 是一个包容的社区，我们需要保持这种状态。 We have a single [Code of Conduct](https://code-of-conduct.freecodecamp.org) that governs our entire community. 规则越少，就越容易记住。 你可以在[这里](https://code-of-conduct.freecodecamp.org)阅读这些规则，并把它们记在心里。 -> [!NOTE] As a moderator, we would add you to one or more teams on GitHub, our community forums & 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). +> [!NOTE] As a moderator, we would add you to one or more teams on GitHub, our community forums & chat servers. If you are missing access to a platform that you would like to moderate, please [reach out to a staff member](FAQ.md#additional-assistance). ## 管理 GitHub @@ -164,7 +164,7 @@ As a moderator, you help keep our community an enjoyable place for anyone to lea Note that once you are a moderator on the forum, you will start to see blue moderator hints about forum members, like "this is the first time [person] has posted - let's welcome them to the community!" or "[person] hasn't posted in a long time - let's welcome them back." -![A blue text message saying "this is the first time [person] has posted - let's welcome them to the community!](https://i.imgur.com/mPmVgzK.png) +![A blue text message saying "This is the first time [person] has posted - let's welcome them to the community!](https://i.imgur.com/mPmVgzK.png) These are opportunities for you to welcome them and make them feel extra special. You never know which person who's marginally involved may become our next super-helper, helping many other people in their coding journey. Even the slightest kindness may trigger a cascade of good deeds. diff --git a/docs/i18n/chinese/reply-templates.md b/docs/i18n/chinese/reply-templates.md index a1a9bbcc41c..d5c5110346b 100644 --- a/docs/i18n/chinese/reply-templates.md +++ b/docs/i18n/chinese/reply-templates.md @@ -183,7 +183,7 @@ If the forum members determine there is nothing wrong with your code, you can re Thank you and happy coding. ``` -> When an issue is duplicate of an earlier issue. +> When an issue is a duplicate of an earlier issue. ```markdown Thank you for reporting this issue. @@ -230,7 +230,7 @@ Happy contributing. ```md We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. -Issues labelled with `help wanted` or `first timers only` are open for contributions. +Issues labeled with `help wanted` or `first timers only` are open for contributions. Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. ``` diff --git a/docs/i18n/chinese/troubleshooting-development-issues.md b/docs/i18n/chinese/troubleshooting-development-issues.md index 84569c6fbf7..962fd04362c 100644 --- a/docs/i18n/chinese/troubleshooting-development-issues.md +++ b/docs/i18n/chinese/troubleshooting-development-issues.md @@ -31,7 +31,7 @@ Use the shortcut pnpm run clean-and-develop ``` -If you continue to face issues with the build, cleaning up the workspace is recommend. +If you continue to face issues with the build, cleaning up the workspace is recommended. Use `git clean` in interactive mode: @@ -50,7 +50,7 @@ git clean -ifdX ## Issues with API, login, Challenge Submissions, etc. -If you can't sign in, and instead you see a banner with an error message that it will be reported to freeCodeCamp, please double-check that your local port `3000` is not in use by a different program. +If you can't sign in, and instead you see a banner with an error message saying that the error will be reported to freeCodeCamp, please double-check that your local port `3000` is not in use by a different program. #### **From Terminal:** ```console diff --git a/docs/i18n/espanol/authors-analytics-manual.md b/docs/i18n/espanol/authors-analytics-manual.md index 5c5ec80e5d4..09ba1bc2a90 100644 --- a/docs/i18n/espanol/authors-analytics-manual.md +++ b/docs/i18n/espanol/authors-analytics-manual.md @@ -1,10 +1,10 @@ # Manual para Autores de Google Analytics -Si usted es un autor con acceso a la propiedad noticias de Google Analytics, use esta guía para ver la sección para encontrar tus artículos de compromiso, y buscar artículos por idioma de publicación. +If you are an author with access to the publication's Google Analytics Property (News), you can use this guide to view your article engagement and search for articles by publication language. ## Búsqueda por Idioma -Para buscar noticias de engagement por un idioma específico: +To search for engagement reports in a specific language: ![Imagen - Muestra pasos para buscar por idioma en Google Analytics](https://contribute.freecodecamp.org/images/google-analytics/search-by-language.png) diff --git a/docs/i18n/espanol/codebase-best-practices.md b/docs/i18n/espanol/codebase-best-practices.md index 502e1d6430d..b85bc52e0c5 100644 --- a/docs/i18n/espanol/codebase-best-practices.md +++ b/docs/i18n/espanol/codebase-best-practices.md @@ -161,7 +161,7 @@ The `api/` tests are split into two parts: Unit tests isolate a single function or component. The tests do not need mocking, but will require fixtures. -The unit tests are located in a new file adjacent the file exporting that being tested: +The unit tests are located in a new file adjacent to the file exporting that is being tested: ```text api/ diff --git a/docs/i18n/espanol/how-to-catch-outgoing-emails-locally.md b/docs/i18n/espanol/how-to-catch-outgoing-emails-locally.md index 5aebf304cf6..d0fc01e9c1b 100644 --- a/docs/i18n/espanol/how-to-catch-outgoing-emails-locally.md +++ b/docs/i18n/espanol/how-to-catch-outgoing-emails-locally.md @@ -104,7 +104,7 @@ Comienza a [usar MailHog](#using-mailhog). ## Usando MailHog -Open a new browser tab or window and navigate to [http://localhost:8025](http://localhost:8025) to open your MailHog inbox when the MailHog installation has completed and MailHog is running. +Open a new browser tab or window and navigate to [http://localhost:8025](http://localhost:8025) to open your MailHog inbox when the MailHog installation has been completed and MailHog is running. ## Enlaces útiles diff --git a/docs/i18n/espanol/how-to-contribute-to-the-codebase.md b/docs/i18n/espanol/how-to-contribute-to-the-codebase.md index 3ae4069f985..e98d3c3b91a 100644 --- a/docs/i18n/espanol/how-to-contribute-to-the-codebase.md +++ b/docs/i18n/espanol/how-to-contribute-to-the-codebase.md @@ -23,7 +23,7 @@ Sigue estos pasos: nothing to commit, working directory clean ``` - Si obtuviste un resultado distinto, no estás en la rama main o tu directorio de trabajo no está limpio. Resolvé cualquier confirmación o archivo pendiente y cambia a ` main `: + If you got a different message, then you aren't on main or your working directory isn't clean, resolve any outstanding files/commits and checkout `main`: ```console git checkout main @@ -55,7 +55,7 @@ Sigue estos pasos: git push origin main --force ``` - Podes validar que tu main actual concuerda con el upstream/main a través del comando diff: + You can validate that your current main matches the upstream/main by performing a diff: ```console git diff upstream/main diff --git a/docs/i18n/espanol/how-to-enable-new-languages.md b/docs/i18n/espanol/how-to-enable-new-languages.md index dffc34f6992..ab0386772eb 100644 --- a/docs/i18n/espanol/how-to-enable-new-languages.md +++ b/docs/i18n/espanol/how-to-enable-new-languages.md @@ -142,7 +142,7 @@ export const rtlLangs = ['']; ### Set Translated SuperBlocks -In the [shared/config/superblocks.ts](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/shared/config/superblocks.ts) file, add the new language to the `notAuditedSuperBlocks` object. This lists all the superblocks which are not fully translated. Add an array of superblocks which have not been fully translated to it. For example: +In the [shared/config/superblocks.ts](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/shared/config/superblocks.ts) file, add the new language to the `notAuditedSuperBlocks` object. This lists all the superblocks which are not fully translated. Add an array of superblocks that have not been fully translated to it. For example: ```js export const notAuditedSuperBlocks: NotAuditedSuperBlocks = { @@ -166,7 +166,7 @@ export const notAuditedSuperBlocks: NotAuditedSuperBlocks = { } ``` -Be sure to only add the superblocks which are **not** fully translated and approved. The translated superblocks will be calculated from this object. When a new superblock is finished being fully translated, remove it from the array for that language. +Be sure to only add the superblocks that are **not** fully translated and approved. The translated superblocks will be calculated from this object. When a new superblock is finished being fully translated, remove it from the array for that language. See the `SuperBlocks` enum at the beginning of the same file for the full list of superblocks. @@ -174,7 +174,7 @@ See the `SuperBlocks` enum at the beginning of the same file for the full list o Next, open the [`client/src/utils/algolia-locale-setup.ts`](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/client/src/utils/algolia-locale-setup.ts) file. Estos datos son utilizados por la barra de búsqueda que carga artículos de `/news`. Si bien es poco probable que vayas a probar esta funcionalidad, lea falta de datos para tu lenguaje puede llevarle a errores al intentar construir el código base localmente. -Agrega un objeto para al objeto `algoliaIndices`. Deberñias usar los mismos valores del objeto `english` para pruebas locales, remplazando la clave `english` con el valor `avalaibleLangs` para tu idioma. +Agrega un objeto para al objeto `algoliaIndices`. You should use the same values as the `english` object for local testing, replacing the `english` key with your language's `availableLangs` value. > [!NOTE] Si ya hemos desplegado una instancia de noticias en tu destino de idioma, puedes actualizar los valores para reflejar la instancia real. De lo contracio, use los valores del inglés. @@ -229,7 +229,7 @@ You don't have to have everything in these 3 files translated at first. It's pos You can replace any URLs that you have corresponding pages ready in your language. -For example, if you have the publication in your language, you can replace the URL for `"news"`. If you want to translate articles listed in the footer links, see [How to Translate Articles in the Footer Links](language-lead-handbook.md#how-to-translate-articles-in-the-footer-links). +For example, if you have a publication in your language, you can replace the URL for `"news"`. If you want to translate articles listed in the footer links, see [How to Translate Articles in the Footer Links](language-lead-handbook.md#how-to-translate-articles-in-the-footer-links). #### `meta-tags.json` @@ -303,7 +303,7 @@ videoLocaleIds: Joi.when('challengeType', { Si desea probar las traducciones localmente, antes de añadirlas a nuestro repositorio principal, salte los cambios del flujo de trabajo de Crowdin. Siga los pasos para activar un idioma, luego descargue las traducciones de Crowdin y cargue las traducciones en su código local. -Como el lenguaje no ha sido aprovado para producción, nuestros scripts aún no descargan las traducciones de manera automática. Sólo el personal tiene acceso a la descarga directa de traducciones. Eres bienvenido a comunicarte con nosotros en nuestra [contributors chat room](https://discord.gg/PRyKn3Vbay), o puedes traducir los archivos markdown localmente con razones de testeo. +Como el lenguaje no ha sido aprovado para producción, nuestros scripts aún no descargan las traducciones de manera automática. Only staff have access to directly download the translations - you are welcome to reach out to us in our [contributors chat room](https://discord.gg/PRyKn3Vbay), or you can translate the English markdown files locally for testing purposes. Una vez que poseas los archivos, necesitarás colocarlos en el directorio correcto. Para los desafíos de currículum, deberías colocar las carpetas de certificación (i.e. `01-responsive-web-design`) dentro del directorio `curriculum/challenges/{lang}`. Para nuestras traducciones al Dothraki, deberia ser `curriculum/challenges/dothraki`. La traducción del cliente `.json` archivos irá al directorio `client/i18n/locales/{lang}`. @@ -325,7 +325,7 @@ In [`shared/config/i18n.ts`](https://github.com/freeCodeCamp/freeCodeCamp/blob/m export const hiddenLangs = []; // Remove your language from the array ``` -When this PR is merged and gets deployed, the curriculum in your language will be live. +When this PR is merged and deployed, the curriculum in your language will be live. # Deploying New Languages on `/news` diff --git a/docs/i18n/espanol/how-to-help-with-video-challenges.md b/docs/i18n/espanol/how-to-help-with-video-challenges.md index b9aa80b9916..50038173fa0 100644 --- a/docs/i18n/espanol/how-to-help-with-video-challenges.md +++ b/docs/i18n/espanol/how-to-help-with-video-challenges.md @@ -125,7 +125,7 @@ Agrega/Actualiza el texto de la pregunta debajo de la parte que dice: ## --text-- ``` -Añade/Actualiza las respuestas (`Answer 1`, `Answer 2`, y así) debajo de `## --answers--`. Asegúrate de actualizar el número debajo de ` ## --video-solution-- ` con el número de respuesta correcto. Puede añadir más respuestas posibles usando el mismo formato. La pregunta y las respuestas pueden estar rodeadas de comillas. +Añade/Actualiza las respuestas (`Answer 1`, `Answer 2`, y así) debajo de `## --answers--`. Asegúrate de actualizar el número debajo de ` ## --video-solution-- ` con el número de respuesta correcto. Puede añadir más respuestas posibles usando el mismo formato. The questions and answers can be surrounded with quotation marks. ### Ejemplos de preguntas 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 9549250e245..8d2bf79ec35 100644 --- a/docs/i18n/espanol/how-to-open-a-pull-request.md +++ b/docs/i18n/espanol/how-to-open-a-pull-request.md @@ -140,7 +140,7 @@ When you are working on regular bugs and features on our development branch `mai ### For Upcoming Curriculum and Features -When you are working on features for our upcoming curriculum `next-*` branches, you have to do a cherry pick: +When you are working on features for our upcoming curriculum `next-*` branches, you have to do a `cherry-pick`: 1. Make sure your upstream comes in sync with your local: @@ -151,7 +151,7 @@ When you are working on features for our upcoming curriculum `next-*` branches, git reset --hard upstream/next-python-projects ``` -2. Take backup +2. Take a backup a. Either delete your local branch after taking a backup (if you still have it locally): @@ -169,7 +169,7 @@ When you are working on features for our upcoming curriculum `next-*` branches, git branch -D ``` - b. Or just a backup of your pr branch (if you do not have it locally): + b. Or just a backup of your PR branch (if you do not have it locally): ```console git checkout -b origin/ diff --git a/docs/i18n/espanol/how-to-proofread-files.md b/docs/i18n/espanol/how-to-proofread-files.md index bfde5edc3d5..2a0646781f7 100644 --- a/docs/i18n/espanol/how-to-proofread-files.md +++ b/docs/i18n/espanol/how-to-proofread-files.md @@ -2,7 +2,7 @@ Nuestro equipo de revisión es responsable de garantizar que las traducciones reflejen con precisión el texto original. Confiamos en nuestro equipo de revisión para asegurarnos de que tenemos traducciones de muy alta calidad. -Todas nuestras traducciones están hechas a mano, por humanos reales. La revisión garantiza que haya un tono coherente en todos nuestros recursos traducidos, como el plan de estudios. +Todas nuestras traducciones están hechas a mano, por humanos reales. Proofreading ensures that there is a consistent tone across all our translated resources like the curriculum. Para comenzar a revisar, visita [nuestra plataforma de traducción](https://translate.freecodecamp.org) e inicia sesión. Selecciona "Ir a la consola" en la barra de navegación superior para cambiar de la vista pública a la vista de espacio de trabajo. @@ -50,6 +50,6 @@ Nuestro equipo de personal y de moderadores de la comunidad buscan constantement ## Creating a Channel on Chat for a World Language -Mayormente, te recomendamos que utilices la sala de chat de [contribuidores](https://discord.gg/PRyKn3Vbay) para toda la correspondencia. Sin embargo, si el equipo de traductores voluntarios crece para un idioma determinado, podemos considerar la creación de un canal de escape adicional para el idioma. +For the most part, we encourage you to use the [contributors chat](https://discord.gg/PRyKn3Vbay) room for all correspondence. However if the team of volunteer translators grows for a certain language, we can consider creating an additional break-out channel for the language. Si ya eres un revisor y estás interesado en tener un canal dedicado en nuestros servidores de chat para un idioma específico, [completa este formulario](https://forms.gle/XU5CyutrYCgDYaVZA). diff --git a/docs/i18n/espanol/how-to-setup-freecodecamp-locally.md b/docs/i18n/espanol/how-to-setup-freecodecamp-locally.md index e0a970c4e80..b9def84613c 100644 --- a/docs/i18n/espanol/how-to-setup-freecodecamp-locally.md +++ b/docs/i18n/espanol/how-to-setup-freecodecamp-locally.md @@ -4,7 +4,7 @@ Sigue estas directrices para configurar un entorno de desarrollo para freeCodeCa > [!ATTENTION] - freeCodeCamp does not build and run natively on Windows, you will [need to use WSL2](how-to-setup-wsl.md) for a Linux-like setup on Windows. - You can't use Windows Command Prompt, Git Bash or PowerShell to build and run the codebase. - Note that if using Windows, the hardware requirements need to be more than [what we mention](how-to-setup-freecodecamp-locally?id=how-to-prepare-your-local-machine) to accommodate for WSL-based setup. -Si deseas hacer una contribución puntual, debes utilizar Gitpod para realizar cambios. La configuración de Gitpod lanza un entorno listo para codificar en pocos minutos en tu navegador web. Para contribuir a largo plazo, te recomendamos que instales freeCodeCamp en tu máquina local. +Si deseas hacer una contribución puntual, debes utilizar Gitpod para realizar cambios. La configuración de Gitpod lanza un entorno listo para codificar en pocos minutos en tu navegador web. To contribute long-term, we recommend you set up freeCodeCamp on your local machine. Estos son algunos pros y contras que deberían ayudarte a decidir cuál es la mejor opción para ti: @@ -19,9 +19,9 @@ Estos son algunos pros y contras que deberían ayudarte a decidir cuál es la me ### How to Prepare a Gitpod Workspace -Hemos automatizado el proceso de instalación de todas las dependencias & herramientas que necesitarás. With Gitpod you get a free ready-to-code environment in a few minutes, and is useful if you do not have access to computer or want to make one-time changes. +Hemos automatizado el proceso de instalación de todas las dependencias & herramientas que necesitarás. With Gitpod you get a free ready-to-code environment in a few minutes, and is useful if you do not have access to a computer or want to make one-time changes. -There are various ways to launch an Gitpod workspace: +There are various ways to launch a Gitpod workspace: 1. **(Más rápido)** Añade `gitpod.io/#` a cualquier URL de GitHub. @@ -158,7 +158,7 @@ Now that you have downloaded a copy of your fork, you will need to set up an `up You need a reference from your local clone to the `upstream` repository in addition to the `origin` repository. This is so that you can sync changes from the main repository without the requirement of forking and cloning repeatedly. -1. Change directory to the new freeCodeCamp directory: +1. Change the directory to the new freeCodeCamp directory: ```console cd freeCodeCamp diff --git a/docs/i18n/espanol/how-to-setup-freecodecamp-mobile-app-locally.md b/docs/i18n/espanol/how-to-setup-freecodecamp-mobile-app-locally.md index 018d1525def..6f8e50cfd07 100644 --- a/docs/i18n/espanol/how-to-setup-freecodecamp-mobile-app-locally.md +++ b/docs/i18n/espanol/how-to-setup-freecodecamp-mobile-app-locally.md @@ -44,7 +44,7 @@ Una vez que estén instalados los requisitos previos, hay que preparar el entorn [Fork](https://help.github.com/articles/about-forks/) es un paso donde consigues tu propia copia del repositorio (conocido como _repo_) en GitHub. -Esto es esencial, te permite trabajar en tu propia copia de la app móvil de freeCodeCamp en GitHub, o descargar (clonar) tu repositorio para trabajar localmente. Más adelant, podrás solicitar cambios para que se muestren en el repositorio principal de tu "fork" (bifurcación) a través de una "pull request" (PR). +This is essential, as it allows you to work on your own copy of the freeCodeCamp mobile app on GitHub, or to download (clone) your repository to work on locally. Más adelant, podrás solicitar cambios para que se muestren en el repositorio principal de tu "fork" (bifurcación) a través de una "pull request" (PR). > [!TIP] El repositorio principal en `https://github.com/freeCodeCamp/mobile` es frecuentemente conocido como el repositorio `upstream`. > @@ -361,14 +361,14 @@ Sigue estos pasos: > [!NOTE] You only need to follow this section if you're modifying the challenge test runner in the mobile app. Otherwise, you can go to the next section on [how to open a pull request](#proposing-a-pull-request-pr). -1. Clone a copy of the [freeCodeCamp repo](https://github.com/freeCodeCamp/freeCodeCamp) locally outside of your local copy of freeCodeCamp mobile repo. Your folder structure should look like this: +1. Clone a copy of the [freeCodeCamp repo](https://github.com/freeCodeCamp/freeCodeCamp) locally outside of your local copy of the freeCodeCamp mobile repo. Your folder structure should look like this: ```console ├── freeCodeCamp ├── mobile ``` -2. Change directory to the freeCodeCamp repo: +2. Change the directory to the freeCodeCamp repo: ```console cd freeCodeCamp @@ -480,7 +480,7 @@ Si estás en un sistema operativo diferente y/o todavía tienes problemas, consu ### Problemas con la interfaz de usuario, fuentes, errores de compilación, etc. -Si tienes problemas con la interfaz de usuario, o errores de compilación, una limpieza puede ser útil: +If you face issues with the UI, or build errors a cleanup can be useful: ```console flutter clean @@ -488,7 +488,7 @@ flutter clean ### Issues Installing Dependencies -Si obtienes errores al instalar las dependencias, por favor asegúrate de que no estés en una red restringida o que tu configuración de firewall no te impida acceder a los recursos. +If you get errors while installing the dependencies, please make sure that you are not in a restricted network or that your firewall settings do not prevent you from accessing resources. Be patient as the first-time setup can take a while depending on your network bandwidth. diff --git a/docs/i18n/espanol/how-to-setup-wsl.md b/docs/i18n/espanol/how-to-setup-wsl.md index a3a59f7ac38..0421a40a3e0 100644 --- a/docs/i18n/espanol/how-to-setup-wsl.md +++ b/docs/i18n/espanol/how-to-setup-wsl.md @@ -123,7 +123,7 @@ Now that you have installed the pre-requisites, follow [our local setup guide](h > [!WARNING] > -> Please note, at this time the setup for Cypress tests (and related GUI needs) are a work in progress. Aún así deberías poder trabajar en la mayor parte del código base. +> Please note, at this time the setup for Cypress tests (and related GUI needs) is a work in progress. Aún así deberías poder trabajar en la mayor parte del código base. ## Enlaces útiles diff --git a/docs/i18n/espanol/how-to-use-docker-on-windows-home.md b/docs/i18n/espanol/how-to-use-docker-on-windows-home.md index d6337155b1f..75a3fc8108b 100644 --- a/docs/i18n/espanol/how-to-use-docker-on-windows-home.md +++ b/docs/i18n/espanol/how-to-use-docker-on-windows-home.md @@ -2,7 +2,7 @@ Hay unas cuantas dificultades que debes evitar al configurar Docker en Windows Home. En primer lugar, tienes que utilizar [Docker Toolbox](https://docs.docker.com/toolbox/toolbox_install_windows/) como administrador. Desafortunadamente, Windows Home no soporta Docker para Windows Desktop, por lo que se debe utilizar Toolbox en su lugar. Tiene que ejecutarse como Administrador, ya que la instalación utiliza enlaces simbólicos, los cuales no se pueden crear de otra manera. -Una vez instalado Toolbox, ejecute Docker Quickstart Terminal como Administrador. Esto creará una máquina virtual `default` (predeterminada) si no existía anteriormente. Una vez que esto haya ocurrido, cierra la terminal y abre VirtualBox (otra vez como Administrador). Debes ser capaz de ver la máquina `default`. El sitio es bastante intensivo en recursos, así que detén la máquina virtual y aumenta la configuración tanto como puedas, especialmente la memoria. Se ha confirmado que trabaja con 4GB de ram. +Una vez instalado Toolbox, ejecute Docker Quickstart Terminal como Administrador. Esto creará una máquina virtual `default` (predeterminada) si no existía anteriormente. Una vez que esto haya ocurrido, cierra la terminal y abre VirtualBox (otra vez como Administrador). Debes ser capaz de ver la máquina `default`. El sitio es bastante intensivo en recursos, así que detén la máquina virtual y aumenta la configuración tanto como puedas, especialmente la memoria. It has been confirmed to work with 4GB of RAM. Una vez que estés contento de que Docker está funcionando, clona el repositorio freeCodeCamp en un directorio dentro de `C:\Users`. Estos directorios son compartidos dándole acceso a Docker a los directorios locales que necesita durante la instalación. 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 356ecc9460c..503b5eef683 100644 --- a/docs/i18n/espanol/how-to-work-on-coding-challenges.md +++ b/docs/i18n/espanol/how-to-work-on-coding-challenges.md @@ -4,7 +4,7 @@ Nuestro objetivo es desarrollar una experiencia de aprendizaje interactiva y div Diseñar desafíos de codificación interactivos es difícil. Sería mucho más fácil escribir una explicación larga o crear un tutorial en vídeo. Pero para nuestro plan de estudios, estamos aferrándonos a lo que mejor funciona para la mayoría de la gente - una experiencia totalmente interactiva y de videojuegos. -Queremos que los campistas entren en un estado de flujo. Queremos que generen impulso y exploten a través de nuestro plan de estudios con el menor número de trabas posible. Queremos que ingresen en los proyectos con confianza y se expongan ampliamente a los conceptos de programación. +Queremos que los campistas entren en un estado de flujo. Queremos que generen impulso y exploten a través de nuestro plan de estudios con el menor número de trabas posible. We want them to go into the projects with confidence and gain wide exposure to programming concepts. Ten en cuenta que para la versión 7.0 del plan de estudios gratuito, estamos avanzando hacia [un modelo totalmente orientado al proyecto con mucha más repetición](https://www.freecodecamp.org/news/python-curriculum-is-live/). @@ -558,7 +558,7 @@ b c ``` -And you choose `b`, your new order will be: +If you choose `b`, your new order will be: ```bash a 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 d9109885765..114d8e53c4c 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 @@ -8,13 +8,13 @@ Once you have set up the project locally you should be able to follow this docum Esto podría ser útil cuando se está trabajando en una función que se dirige específicamente a algo que implica la localización, y requiere que valides, por ejemplo, la etiqueta de un botón en un idioma diferente. -> [!TIP] No necesitas seguir este documento para traducir el currículo de freeCodeCamp o para contribuir con la documentación. En su lugar, lee [esta guia](how-to-translate-files.md). +> [!TIP] You do not need to follow this document to translate freeCodeCamp's curriculum or contributing documentation. En su lugar, lee [esta guia](how-to-translate-files.md). Veamos cómo funcionan los marcos de trabajo y las herramientas de i18n. ## Estructura de archivos -Most of the files for translating the platform are located in the [`client/i18n`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/client/i18n) folder. Cada idioma tiene una carpeta dentro que contiene archivos JSON con las traducciones. +Most of the files for translating the platform are located in the [`client/i18n`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/client/i18n) folder. Each language has a directory that contains JSON files with the translations. ```console config @@ -55,7 +55,7 @@ Most of the files for translating the platform are located in the [`client/i18n` └── validate-keys.ts ``` -Some of these files are translated on our translation platform (Crowdin) and some are translated or created via PR's on GitHub. +Some of these files are translated on our translation platform (Crowdin) and some are translated or created via PRs on GitHub. **Archivos traducidos en nuestra plataforma de traducción:** 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 775fa5793e1..be9948678ec 100644 --- a/docs/i18n/espanol/how-to-work-on-practice-projects.md +++ b/docs/i18n/espanol/how-to-work-on-practice-projects.md @@ -38,7 +38,7 @@ Clicking this button will add a new step at the end of the project. This step wi #### Create Empty Steps -Enter the number of steps you want to add in the input. Then, clicking the button will create that many empty steps at the end of the project. +Enter the number of steps you want to add in the input. Then, clicking the button will create many empty steps at the end of the project. #### Insert Step @@ -124,7 +124,7 @@ pnpm run delete-step X # where X is the step number to be deleted. ### update-step-titles -A one-off script that automatically updates the frontmatter in a project's markdown files so that they are consistent with the project's meta.json. It ensures that each step's title (and dashedName) match the meta's challengeOrder. +A one-off script that automatically updates the frontmatter in a project's markdown files so that they are consistent with the project's meta.json. It ensures that each step's title (and dashedName) matches the meta's `challengeOrder`. #### How to Run the Script diff --git a/docs/i18n/espanol/how-to-work-on-tutorials-that-use-coderoad.md b/docs/i18n/espanol/how-to-work-on-tutorials-that-use-coderoad.md index 6b95d1f6fd8..e6fc215be38 100644 --- a/docs/i18n/espanol/how-to-work-on-tutorials-that-use-coderoad.md +++ b/docs/i18n/espanol/how-to-work-on-tutorials-that-use-coderoad.md @@ -56,7 +56,7 @@ Si deseas probar sus cambios en `main` después de seguir las instrucciones ante - Siga las instrucciones del [rdb-alpha repo](https://github.com/freeCodeCamp/rdb-alpha) para ejecutar un contenedor - Comienza el tutorial usando el archivo `tutorial.json` en la nueva rama -### Revisiando las relaciones públicas en `main` +### Reviewing PRs to `main` Si revisa un PR que solo cambia `main` con problemas de instrucción o gramática como se describe anteriormente, los cambios en `TUTORIAL.md` deberían coincidir con los cambios en `tutorial.json`. @@ -119,11 +119,11 @@ Si tienes acceso de escritura al repo de freeCodeCamp, has verificado los archiv - Hacer un PR a `main` en el repositorio freeCodeCamp - Si estás satisfecho, fusionalo o déjalo y pide una reseña a alguien - Después de fusionar las relaciones públicas, abra el tutorial siguiendo las instrucciones en el repositorio [rdb-alpha](https://github.com/freeCodeCamp/rdb-alpha) para asegurarse de que está cargando correctamente, y que usted puede pasar unos pasos -- Finalmente, si existe algún PRs para esta versión, ciérrelos +- Finally, if any PRs for this version exist, close them ### How to Revert to a Previous Version -- Crea una nueva rama desde la última `main` con `git checkout -b revert/to-version-X.X.X` +- Create a new branch off of the latest `main` with `git checkout -b revert/to-version-X.X.X` - Revertir todos los commits en esta rama hasta e incluyendo el commit de la versión después del que desea revertir. Por ejemplo, puede haber commits que se vean así: ``` diff --git a/docs/i18n/espanol/language-lead-handbook.md b/docs/i18n/espanol/language-lead-handbook.md index 2f0f4c3bde9..846b6669217 100644 --- a/docs/i18n/espanol/language-lead-handbook.md +++ b/docs/i18n/espanol/language-lead-handbook.md @@ -339,7 +339,7 @@ In Crowdin, individuate the `User management` on the left-hand side menu. This will open the user management tools, you will be able to see the list of all the users. -Search for the user that will become a proofreader. Use the three dots menu on the user row to open a menu and select "Add to team". The proofreader teams have a standard name of `Proof Readers ()`, you can search the team using the language name. Once you have selected the team, use the "ADD" button at the bottom of the page to finalize the thing. +Search for the user who will become a proofreader. Use the three dots menu on the user row to open a menu and select "Add to team". The proofreader teams have a standard name of `Proof Readers ()`, you can search the team using the language name. Once you have selected the team, use the "ADD" button at the bottom of the page to finalize the thing. The user is now a proofreader. diff --git a/docs/i18n/espanol/moderator-handbook.md b/docs/i18n/espanol/moderator-handbook.md index 0457e22cc74..af77665e62c 100644 --- a/docs/i18n/espanol/moderator-handbook.md +++ b/docs/i18n/espanol/moderator-handbook.md @@ -18,7 +18,7 @@ freeCodeCamp es una comunidad inclusiva y necesitamos mantenerla de esa manera. Tenemos un solo [Código de Conducta](https://code-of-conduct.freecodecamp.org) que gobierna toda nuestra comunidad. Cuantas menos reglas, mas fácil serán de recordar. Puedes leerlas y memorizarlas [aquí](https://code-of-conduct.freecodecamp.org). -> [!NOTE] As a moderator, we would add you to one or more teams on GitHub, our community forums & chat servers. Si no tienes acceso a una plataforma que te gustaría moderar, por favor [ponte en contacto con uno de los miembros del personal](FAQ.md#additional-assistance). +> [!NOTE] As a moderator, we would add you to one or more teams on GitHub, our community forums & chat servers. If you are missing access to a platform that you would like to moderate, please [reach out to a staff member](FAQ.md#additional-assistance). ## Moderando GitHub @@ -164,7 +164,7 @@ As a moderator, you help keep our community an enjoyable place for anyone to lea Note that once you are a moderator on the forum, you will start to see blue moderator hints about forum members, like "this is the first time [person] has posted - let's welcome them to the community!" or "[person] hasn't posted in a long time - let's welcome them back." -![A blue text message saying "this is the first time [person] has posted - let's welcome them to the community!](https://i.imgur.com/mPmVgzK.png) +![A blue text message saying "This is the first time [person] has posted - let's welcome them to the community!](https://i.imgur.com/mPmVgzK.png) These are opportunities for you to welcome them and make them feel extra special. You never know which person who's marginally involved may become our next super-helper, helping many other people in their coding journey. Even the slightest kindness may trigger a cascade of good deeds. diff --git a/docs/i18n/espanol/reply-templates.md b/docs/i18n/espanol/reply-templates.md index a1a9bbcc41c..d5c5110346b 100644 --- a/docs/i18n/espanol/reply-templates.md +++ b/docs/i18n/espanol/reply-templates.md @@ -183,7 +183,7 @@ If the forum members determine there is nothing wrong with your code, you can re Thank you and happy coding. ``` -> When an issue is duplicate of an earlier issue. +> When an issue is a duplicate of an earlier issue. ```markdown Thank you for reporting this issue. @@ -230,7 +230,7 @@ Happy contributing. ```md We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. -Issues labelled with `help wanted` or `first timers only` are open for contributions. +Issues labeled with `help wanted` or `first timers only` are open for contributions. Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. ``` diff --git a/docs/i18n/espanol/troubleshooting-development-issues.md b/docs/i18n/espanol/troubleshooting-development-issues.md index 05f88f56c49..8d720305c2c 100644 --- a/docs/i18n/espanol/troubleshooting-development-issues.md +++ b/docs/i18n/espanol/troubleshooting-development-issues.md @@ -31,7 +31,7 @@ Use el atajo pnpm run clean-and-develop ``` -Si continúa enfrentándose a problemas con la construcción, se recomienda limpiar el espacio de trabajo. +If you continue to face issues with the build, cleaning up the workspace is recommended. Use `git clean` en modo interactivo: @@ -50,7 +50,7 @@ git clean -ifdX ## Issues with API, login, Challenge Submissions, etc. -Si no puedes iniciar sesión, y en cambio ves un banner con un mensaje de error de que será reportado a freeCodeCamp, por favor, verifique otra vez de que tu puerto local `3000` no esté en uso por un programa diferente. +If you can't sign in, and instead you see a banner with an error message saying that the error will be reported to freeCodeCamp, please double-check that your local port `3000` is not in use by a different program. #### **From Terminal:** ```console diff --git a/docs/i18n/german/authors-analytics-manual.md b/docs/i18n/german/authors-analytics-manual.md index 221ca725cd9..fa5bbe46392 100644 --- a/docs/i18n/german/authors-analytics-manual.md +++ b/docs/i18n/german/authors-analytics-manual.md @@ -1,10 +1,10 @@ # Authors Analytics Manual -If you are an author with access to the publication's Google Analytics Property (News), you can use this guide to view your articles engagement and search for articles by publication language. +If you are an author with access to the publication's Google Analytics Property (News), you can use this guide to view your article engagement and search for articles by publication language. ## Search by Language -To search for engagement reports by a specific language: +To search for engagement reports in a specific language: ![Image - Show steps to search by language on googla analytics](https://contribute.freecodecamp.org/images/google-analytics/search-by-language.png) diff --git a/docs/i18n/german/codebase-best-practices.md b/docs/i18n/german/codebase-best-practices.md index ae276c1d570..58c162476ee 100644 --- a/docs/i18n/german/codebase-best-practices.md +++ b/docs/i18n/german/codebase-best-practices.md @@ -161,7 +161,7 @@ The `api/` tests are split into two parts: Unit tests isolate a single function or component. The tests do not need mocking, but will require fixtures. -The unit tests are located in a new file adjacent the file exporting that being tested: +The unit tests are located in a new file adjacent to the file exporting that is being tested: ```text api/ diff --git a/docs/i18n/german/how-to-catch-outgoing-emails-locally.md b/docs/i18n/german/how-to-catch-outgoing-emails-locally.md index 442d705bab3..db50735dd79 100644 --- a/docs/i18n/german/how-to-catch-outgoing-emails-locally.md +++ b/docs/i18n/german/how-to-catch-outgoing-emails-locally.md @@ -104,7 +104,7 @@ Starte [mit der Nutzung von MailHog](#using-mailhog). ## MailHog verwenden -Open a new browser tab or window and navigate to [http://localhost:8025](http://localhost:8025) to open your MailHog inbox when the MailHog installation has completed and MailHog is running. +Open a new browser tab or window and navigate to [http://localhost:8025](http://localhost:8025) to open your MailHog inbox when the MailHog installation has been completed and MailHog is running. ## Nützliche Links diff --git a/docs/i18n/german/how-to-contribute-to-the-codebase.md b/docs/i18n/german/how-to-contribute-to-the-codebase.md index 3ee01e7f9c9..0068611fc50 100644 --- a/docs/i18n/german/how-to-contribute-to-the-codebase.md +++ b/docs/i18n/german/how-to-contribute-to-the-codebase.md @@ -23,7 +23,7 @@ Follow these steps: nothing to commit, working directory clean ``` - If you got different message, then you aren't on main or your working directory isn't clean, resolve any outstanding files/commits and checkout `main`: + If you got a different message, then you aren't on main or your working directory isn't clean, resolve any outstanding files/commits and checkout `main`: ```console git checkout main @@ -55,7 +55,7 @@ Follow these steps: git push origin main --force ``` - You can validate your current main matches the upstream/main by performing a diff: + You can validate that your current main matches the upstream/main by performing a diff: ```console git diff upstream/main diff --git a/docs/i18n/german/how-to-enable-new-languages.md b/docs/i18n/german/how-to-enable-new-languages.md index 0d19c2424d9..a588bc04cf5 100644 --- a/docs/i18n/german/how-to-enable-new-languages.md +++ b/docs/i18n/german/how-to-enable-new-languages.md @@ -142,7 +142,7 @@ export const rtlLangs = ['']; ### Set Translated SuperBlocks -In the [shared/config/superblocks.ts](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/shared/config/superblocks.ts) file, add the new language to the `notAuditedSuperBlocks` object. This lists all the superblocks which are not fully translated. Add an array of superblocks which have not been fully translated to it. For example: +In the [shared/config/superblocks.ts](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/shared/config/superblocks.ts) file, add the new language to the `notAuditedSuperBlocks` object. This lists all the superblocks which are not fully translated. Add an array of superblocks that have not been fully translated to it. For example: ```js export const notAuditedSuperBlocks: NotAuditedSuperBlocks = { @@ -166,7 +166,7 @@ export const notAuditedSuperBlocks: NotAuditedSuperBlocks = { } ``` -Be sure to only add the superblocks which are **not** fully translated and approved. The translated superblocks will be calculated from this object. When a new superblock is finished being fully translated, remove it from the array for that language. +Be sure to only add the superblocks that are **not** fully translated and approved. The translated superblocks will be calculated from this object. When a new superblock is finished being fully translated, remove it from the array for that language. See the `SuperBlocks` enum at the beginning of the same file for the full list of superblocks. @@ -174,7 +174,7 @@ See the `SuperBlocks` enum at the beginning of the same file for the full list o Next, open the [`client/src/utils/algolia-locale-setup.ts`](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/client/src/utils/algolia-locale-setup.ts) file. Diese Daten werden für die Suchleiste verwendet, die `/news `-Artikel lädt. Es ist zwar unwahrscheinlich, dass du diese Funktion testen wirst, aber das Fehlen der Daten für deine Sprache kann zu Fehlern führen, wenn du versuchst, die Codebasis lokal zu erstellen. -Füge ein Objekt für deine Sprache zum `algoliaIndices`-Objekt hinzu. Du solltest die gleichen Werte wie das `english`-Objekt für lokale Tests verwenden, indem du den `english`-Schlüssel durch den `availableLangs`-Wert deiner Sprache ersetzt. +Füge ein Objekt für deine Sprache zum `algoliaIndices`-Objekt hinzu. You should use the same values as the `english` object for local testing, replacing the `english` key with your language's `availableLangs` value. > [!NOTE] Wenn wir bereits eine Instanz von news in deiner Zielsprache bereitgestellt haben, kannst du die Werte aktualisieren, damit sie die Live-Instanz widerspiegeln. Andernfalls verwendest du die englischen Werte. @@ -229,7 +229,7 @@ You don't have to have everything in these 3 files translated at first. It's pos You can replace any URLs that you have corresponding pages ready in your language. -For example, if you have the publication in your language, you can replace the URL for `"news"`. If you want to translate articles listed in the footer links, see [How to Translate Articles in the Footer Links](language-lead-handbook.md#how-to-translate-articles-in-the-footer-links). +For example, if you have a publication in your language, you can replace the URL for `"news"`. If you want to translate articles listed in the footer links, see [How to Translate Articles in the Footer Links](language-lead-handbook.md#how-to-translate-articles-in-the-footer-links). #### `meta-tags.json` @@ -303,7 +303,7 @@ videoLocaleIds: Joi.when('challengeType', { Wenn du Übersetzungen lokal testen möchtest, bevor du sie zu unserem main-Repository hinzufügst, kannst du die Änderungen am Crowdin-Workflow überspringen. Folge den Schritten zur Aktivierung einer Sprache, lade dann die Übersetzungen von Crowdin herunter und lade sie in deinen lokalen Code. -Da die Sprache noch nicht für die Produktion freigegeben wurde, laden unsere Skripte die Übersetzungen noch nicht automatisch herunter. Nur Mitarbeiter haben die Möglichkeit, die Übersetzungen direkt herunterzuladen - Du kannst uns gerne in unserem ["Contributors" Chatraum](https://discord.gg/PRyKn3Vbay) ansprechen, oder du kannst die englischen Markdown-Dateien lokal zu Testzwecken übersetzen. +Da die Sprache noch nicht für die Produktion freigegeben wurde, laden unsere Skripte die Übersetzungen noch nicht automatisch herunter. Only staff have access to directly download the translations - you are welcome to reach out to us in our [contributors chat room](https://discord.gg/PRyKn3Vbay), or you can translate the English markdown files locally for testing purposes. Sobald du die Dateien hast, musst du sie im richtigen Verzeichnis ablegen. Für die Studienplanaufgaben solltest du die Zertifizierungsordner (z.B. `01-responsive-web-design`) in das Verzeichnis `curriculum/challenges/{lang}` ablegen. Für unsere Dothraki-Übersetzungen wäre dies `curriculum/challenges/dothraki`. Die Client-Übersetzungsdateien `.json` werden im Verzeichnis `client/i18n/locales/{lang}` abgelegt. @@ -325,7 +325,7 @@ In [`shared/config/i18n.ts`](https://github.com/freeCodeCamp/freeCodeCamp/blob/m export const hiddenLangs = []; // Remove your language from the array ``` -When this PR is merged and gets deployed, the curriculum in your language will be live. +When this PR is merged and deployed, the curriculum in your language will be live. # Neue Sprachen auf `/news` bereitstellen diff --git a/docs/i18n/german/how-to-help-with-video-challenges.md b/docs/i18n/german/how-to-help-with-video-challenges.md index 292f2ab3050..11f65b461f8 100644 --- a/docs/i18n/german/how-to-help-with-video-challenges.md +++ b/docs/i18n/german/how-to-help-with-video-challenges.md @@ -119,7 +119,7 @@ Füge den Fragetext unter dem angezeigten Teil hinzu bzw. aktualisiere ihn: ## --text-- ``` -Füge Antworten (`Answer 1`, `Answer 2`, und so weiter) unter `## --answers--` hinzu bzw. aktualisiere sie. Achte darauf, dass du die Nummer unter `## --video-solution--` mit der richtigen Antwortnummer aktualisierst. Du kannst weitere mögliche Antworten hinzufügen, indem du das gleiche Format verwendest. Die Fragen und Antworten können in Anführungszeichen gesetzt werden. +Füge Antworten (`Answer 1`, `Answer 2`, und so weiter) unter `## --answers--` hinzu bzw. aktualisiere sie. Achte darauf, dass du die Nummer unter `## --video-solution--` mit der richtigen Antwortnummer aktualisierst. Du kannst weitere mögliche Antworten hinzufügen, indem du das gleiche Format verwendest. The questions and answers can be surrounded with quotation marks. ### Fragebeispiele diff --git a/docs/i18n/german/how-to-open-a-pull-request.md b/docs/i18n/german/how-to-open-a-pull-request.md index c80746b2a42..f3cb9a40565 100644 --- a/docs/i18n/german/how-to-open-a-pull-request.md +++ b/docs/i18n/german/how-to-open-a-pull-request.md @@ -140,7 +140,7 @@ Wenn du an regulären Bugs und Features auf unserem Entwicklungszweig `main` arb ### For Upcoming Curriculum and Features -Wenn du an Funktionen für unseren kommenden `next-*`-Branch arbeitest, musst du Rosinenpickerei betreiben: +When you are working on features for our upcoming curriculum `next-*` branches, you have to do a `cherry-pick`: 1. Achte darauf, dass dein Upstream mit deinem Local übereinstimmt: @@ -151,7 +151,7 @@ Wenn du an Funktionen für unseren kommenden `next-*`-Branch arbeitest, musst du git reset --hard upstream/next-python-projects ``` -2. Backup erstellen +2. Take a backup a. Entweder löschst du deinen lokalen Branch, nachdem du ein Backup gemacht hast (wenn du ihn noch lokal hast): @@ -169,7 +169,7 @@ Wenn du an Funktionen für unseren kommenden `next-*`-Branch arbeitest, musst du git branch -D ``` - b. Oder einfach ein Backup deines PR-Branch (wenn du ihn nicht lokal hast): + b. Or just a backup of your PR branch (if you do not have it locally): ```console git checkout -b origin/ diff --git a/docs/i18n/german/how-to-proofread-files.md b/docs/i18n/german/how-to-proofread-files.md index 94f540affed..4eb3d48f496 100644 --- a/docs/i18n/german/how-to-proofread-files.md +++ b/docs/i18n/german/how-to-proofread-files.md @@ -2,7 +2,7 @@ Unser Korrekturleseteam ist dafür verantwortlich, dass die Übersetzungen den Ausgangstext genau wiedergeben. Wir vertrauen darauf, dass unsere Korrekturleserinnen und -leser dafür sorgen, dass wir qualitativ hochwertige Übersetzungen erhalten. -Alle unsere Übersetzungen werden von Hand erstellt, von echten Menschen. Durch das Korrekturlesen wird sichergestellt, dass alle unsere übersetzten Ressourcen wie der Studienplan einen einheitlichen Wortlaut aufweisen. +Alle unsere Übersetzungen werden von Hand erstellt, von echten Menschen. Proofreading ensures that there is a consistent tone across all our translated resources like the curriculum. Um mit dem Korrekturlesen zu beginnen, besuche [unsere Übersetzungsplattform](https://translate.freecodecamp.org) und logge dich ein. Wähle "Go to console" in der oberen Navigationsleiste, um von der öffentlichen Ansicht zur Ansicht des Arbeitsbereichs zu wechseln. @@ -49,6 +49,6 @@ Unser Mitarbeiterteam und unsere Community-Moderatoren sind immer auf der Suche ## Creating a Channel on Chat for a World Language -In der Regel empfehlen wir dir, den [Contributors Chat](https://discord.gg/PRyKn3Vbay) für die gesamte Kommunikation zu nutzen. Wenn jedoch das Team der freiwilligen Übersetzer für eine bestimmte Sprache wächst, können wir in Erwägung ziehen, einen zusätzlichen Break-Out-Channel für diese Sprache einzurichten. +For the most part, we encourage you to use the [contributors chat](https://discord.gg/PRyKn3Vbay) room for all correspondence. However if the team of volunteer translators grows for a certain language, we can consider creating an additional break-out channel for the language. Wenn du bereits Korrekturleser/in bist und Interesse an einem eigenen Kanal auf unseren Chatservern für eine bestimmte Sprache hast, [fülle dieses Formular aus](https://forms.gle/XU5CyutrYCgDYaVZA). diff --git a/docs/i18n/german/how-to-setup-freecodecamp-locally.md b/docs/i18n/german/how-to-setup-freecodecamp-locally.md index de6214b2a3a..7a8278c130a 100644 --- a/docs/i18n/german/how-to-setup-freecodecamp-locally.md +++ b/docs/i18n/german/how-to-setup-freecodecamp-locally.md @@ -4,7 +4,7 @@ Follow these guidelines for setting up a development environment for freeCodeCam > [!ATTENTION] - freeCodeCamp does not build and run natively on Windows, you will [need to use WSL2](how-to-setup-wsl.md) for a Linux-like setup on Windows. - You can't use Windows Command Prompt, Git Bash or PowerShell to build and run the codebase. - Note that if using Windows, the hardware requirements need to be more than [what we mention](how-to-setup-freecodecamp-locally?id=how-to-prepare-your-local-machine) to accommodate for WSL-based setup. -If you are looking to make a one-off contribution, you should use Gitpod to make changes. The Gitpod setup launches a ready-to-code environment in a few minutes in your web browser. For contributing long-term, we recommend you setup freeCodeCamp on your local machine. +If you are looking to make a one-off contribution, you should use Gitpod to make changes. The Gitpod setup launches a ready-to-code environment in a few minutes in your web browser. To contribute long-term, we recommend you set up freeCodeCamp on your local machine. Here are some pros and cons which should help you decide which option is best for you: @@ -19,9 +19,9 @@ Here are some pros and cons which should help you decide which option is best fo ### How to Prepare a Gitpod Workspace -We have automated the process of installing all the dependencies & tools you will need. With Gitpod you get a free ready-to-code environment in a few minutes, and is useful if you do not have access to computer or want to make one-time changes. +We have automated the process of installing all the dependencies & tools you will need. With Gitpod you get a free ready-to-code environment in a few minutes, and is useful if you do not have access to a computer or want to make one-time changes. -There are various ways to launch an Gitpod workspace: +There are various ways to launch a Gitpod workspace: 1. **(Fastest)** Prepend `gitpod.io/#` in front of any URL from GitHub. @@ -158,7 +158,7 @@ Now that you have downloaded a copy of your fork, you will need to set up an `up You need a reference from your local clone to the `upstream` repository in addition to the `origin` repository. This is so that you can sync changes from the main repository without the requirement of forking and cloning repeatedly. -1. Change directory to the new freeCodeCamp directory: +1. Change the directory to the new freeCodeCamp directory: ```console cd freeCodeCamp diff --git a/docs/i18n/german/how-to-setup-freecodecamp-mobile-app-locally.md b/docs/i18n/german/how-to-setup-freecodecamp-mobile-app-locally.md index 02e0cc57824..4053ab814de 100644 --- a/docs/i18n/german/how-to-setup-freecodecamp-mobile-app-locally.md +++ b/docs/i18n/german/how-to-setup-freecodecamp-mobile-app-locally.md @@ -44,7 +44,7 @@ Sobald du die notwendigen Ressourcen installiert hast, musst du deine Entwicklun [Forking](https://help.github.com/articles/about-forks/) ist ein Schritt, bei dem du deine eigene Kopie des Repositorys (auch bekannt als _Repo_) auf GitHub erhältst. -Dies ist wichtig, da es dir ermöglicht, an deiner eigenen Kopie der freeCodeCamp mobile App auf GitHub zu arbeiten oder dein Repository herunterzuladen (zu klonen), um lokal daran zu arbeiten. Später kannst du über einen Pull Request (PR) beantragen, dass Änderungen aus deinem Fork in das Haupt-Repository gezogen werden. +This is essential, as it allows you to work on your own copy of the freeCodeCamp mobile app on GitHub, or to download (clone) your repository to work on locally. Später kannst du über einen Pull Request (PR) beantragen, dass Änderungen aus deinem Fork in das Haupt-Repository gezogen werden. > [!TIP] Das Haupt-Repository unter `https://github.com/freeCodeCamp/mobile` wird oft als `upstream`-Repository bezeichnet. > @@ -361,14 +361,14 @@ Folge diesen Schritten: > [!NOTE] You only need to follow this section if you're modifying the challenge test runner in the mobile app. Otherwise, you can go to the next section on [how to open a pull request](#proposing-a-pull-request-pr). -1. Clone a copy of the [freeCodeCamp repo](https://github.com/freeCodeCamp/freeCodeCamp) locally outside of your local copy of freeCodeCamp mobile repo. Your folder structure should look like this: +1. Clone a copy of the [freeCodeCamp repo](https://github.com/freeCodeCamp/freeCodeCamp) locally outside of your local copy of the freeCodeCamp mobile repo. Your folder structure should look like this: ```console ├── freeCodeCamp ├── mobile ``` -2. Change directory to the freeCodeCamp repo: +2. Change the directory to the freeCodeCamp repo: ```console cd freeCodeCamp @@ -480,7 +480,7 @@ Wenn du mit einem anderen Betriebssystem arbeitest und/oder immer noch Probleme ### Probleme mit der Benutzeroberfläche, Build-Fehler usw. -Wenn du Probleme mit der Benutzeroberfläche oder Build-Fehler hast, kann eine Bereinigung nützlich sein: +If you face issues with the UI, or build errors a cleanup can be useful: ```console flutter clean @@ -488,7 +488,7 @@ flutter clean ### Issues Installing Dependencies -Wenn du bei der Installation der Abhängigkeiten Fehler erhältst, vergewissere dich bitte, dass du dich nicht in einem eingeschränkten Netzwerk befindest oder dass deine Firewall-Einstellungen den Zugriff auf die Ressourcen nicht verhindern. +If you get errors while installing the dependencies, please make sure that you are not in a restricted network or that your firewall settings do not prevent you from accessing resources. Be patient as the first-time setup can take a while depending on your network bandwidth. diff --git a/docs/i18n/german/how-to-setup-wsl.md b/docs/i18n/german/how-to-setup-wsl.md index ff9a22e0d15..043ac27c754 100644 --- a/docs/i18n/german/how-to-setup-wsl.md +++ b/docs/i18n/german/how-to-setup-wsl.md @@ -123,7 +123,7 @@ Now that you have installed the pre-requisites, follow [our local setup guide](h > [!WARNING] > -> Please note, at this time the setup for Cypress tests (and related GUI needs) are a work in progress. Du solltest immer noch in der Lage sein, an den meisten Teilen der Codebasis zu arbeiten. +> Please note, at this time the setup for Cypress tests (and related GUI needs) is a work in progress. Du solltest immer noch in der Lage sein, an den meisten Teilen der Codebasis zu arbeiten. ## Nützliche Links diff --git a/docs/i18n/german/how-to-use-docker-on-windows-home.md b/docs/i18n/german/how-to-use-docker-on-windows-home.md index 3725959da94..d234b1ab6d8 100644 --- a/docs/i18n/german/how-to-use-docker-on-windows-home.md +++ b/docs/i18n/german/how-to-use-docker-on-windows-home.md @@ -2,7 +2,7 @@ Bei der Einrichtung von Docker unter Windows Home gibt es einige Fallstricke, die du vermeiden solltest. Als erstes musst du die [Docker Toolbox](https://docs.docker.com/toolbox/toolbox_install_windows/) als Administrator verwenden. Leider unterstützt Windows Home kein Docker für Windows Desktop, sodass stattdessen Toolbox verwendet werden muss. Es muss als Administrator ausgeführt werden, da die Installation Symlinks verwendet, die sonst nicht erstellt werden können. -Sobald du die Toolbox installiert hast, führe das Docker Quickstart Terminal als Administrator aus. Damit wird eine `default` virtuelle Maschine erstellt, wenn sie noch nicht existiert. Wenn das geschehen ist, schließe das Terminal und öffne VirtualBox (wieder als Administrator). Du solltest die `default` Maschine sehen können. Die Website ist ziemlich ressourcenintensiv, also halte die virtuelle Maschine an und erhöhe die Einstellungen so weit wie möglich - vor allem den Arbeitsspeicher. Es wurde bestätigt, dass sie mit 4 GB Arbeitsspeicher funktioniert. +Sobald du die Toolbox installiert hast, führe das Docker Quickstart Terminal als Administrator aus. Damit wird eine `default` virtuelle Maschine erstellt, wenn sie noch nicht existiert. Wenn das geschehen ist, schließe das Terminal und öffne VirtualBox (wieder als Administrator). Du solltest die `default` Maschine sehen können. Die Website ist ziemlich ressourcenintensiv, also halte die virtuelle Maschine an und erhöhe die Einstellungen so weit wie möglich - vor allem den Arbeitsspeicher. It has been confirmed to work with 4GB of RAM. Wenn du sicher bist, dass Docker funktioniert, klone das freeCodeCamp Repository in ein Verzeichnis innerhalb von `C:\Users`. Diese Verzeichnisse werden gemeinsam genutzt, so dass Docker Zugriff auf die lokalen Verzeichnisse hat, die es während der Installation benötigt. diff --git a/docs/i18n/german/how-to-work-on-coding-challenges.md b/docs/i18n/german/how-to-work-on-coding-challenges.md index dd226ea7ab6..47bd1b62eac 100644 --- a/docs/i18n/german/how-to-work-on-coding-challenges.md +++ b/docs/i18n/german/how-to-work-on-coding-challenges.md @@ -4,7 +4,7 @@ Unser Ziel ist es, ein unterhaltsames und voll interaktives Lernerlebnis zu entw Sich interaktive Programmieraufgaben auszudenken ist schwierig. Es wäre viel einfacher, eine ausführliche Erklärung zu schreiben oder ein Video-Tutorial zu erstellen. Aber für unseren Hauptstudienplan bleiben wir bei dem, was für die meisten Menschen am besten funktioniert - ein vollständig interaktives, videospielähnliches Erlebnis. -Wir wollen, dass die Teilnehmer einen Flow-Zustand erreichen. Wir wollen, dass sie in Schwung kommen und so schnell wie möglich Fortschritte in unserem Studienplan machen. Wir wollen, dass sie mit Selbstvertrauen in die Projekte gehen und einen umfassenden Einblick in Programmierkonzepte bekommen. +Wir wollen, dass die Teilnehmer einen Flow-Zustand erreichen. Wir wollen, dass sie in Schwung kommen und so schnell wie möglich Fortschritte in unserem Studienplan machen. We want them to go into the projects with confidence and gain wide exposure to programming concepts. Beachte, dass wir für Version 7.0 des freeCodeCamp-Studienplan zu einem [vollständig projektorientierten Modell mit viel mehr Wiederholungen](https://www.freecodecamp.org/news/python-curriculum-is-live/) übergehen. @@ -553,7 +553,7 @@ b c ``` -And you choose `b`, your new order will be: +If you choose `b`, your new order will be: ```bash a diff --git a/docs/i18n/german/how-to-work-on-localized-client-webapp.md b/docs/i18n/german/how-to-work-on-localized-client-webapp.md index 358d3a004ee..1205002cfac 100644 --- a/docs/i18n/german/how-to-work-on-localized-client-webapp.md +++ b/docs/i18n/german/how-to-work-on-localized-client-webapp.md @@ -8,13 +8,13 @@ Once you have set up the project locally you should be able to follow this docum Das kann hilfreich sein, wenn du an einem Feature arbeitest, das speziell auf die Lokalisierung abzielt und du zum Beispiel die Beschriftung eines Buttons in einer anderen Sprache validieren musst. -> [!TIP] Du musst dieses Dokument nicht befolgen, um den Studienplan von freeCodeCamp zu übersetzen oder etwas zur Dokumentation beizusteuern. Lies stattdessen [diesen Leitfaden hier](how-to-translate-files.md). +> [!TIP] You do not need to follow this document to translate freeCodeCamp's curriculum or contributing documentation. Lies stattdessen [diesen Leitfaden hier](how-to-translate-files.md). Wir wollen verstehen, wie die i18n-Frameworks und -Werkzeuge funktionieren. ## Dateistruktur -Most of the files for translating the platform are located in the [`client/i18n`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/client/i18n) folder. Für jede Sprache gibt es ein Verzeichnis, das JSON-Dateien mit den Übersetzungen enthält. +Most of the files for translating the platform are located in the [`client/i18n`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/client/i18n) folder. Each language has a directory that contains JSON files with the translations. ```console config @@ -55,7 +55,7 @@ Most of the files for translating the platform are located in the [`client/i18n` └── validate-keys.ts ``` -Some of these files are translated on our translation platform (Crowdin) and some are translated or created via PR's on GitHub. +Some of these files are translated on our translation platform (Crowdin) and some are translated or created via PRs on GitHub. **Dateien, die auf unserer Übersetzungsplattform übersetzt wurden:** diff --git a/docs/i18n/german/how-to-work-on-practice-projects.md b/docs/i18n/german/how-to-work-on-practice-projects.md index 178c7a6096c..81a9ef61602 100644 --- a/docs/i18n/german/how-to-work-on-practice-projects.md +++ b/docs/i18n/german/how-to-work-on-practice-projects.md @@ -38,7 +38,7 @@ Clicking this button will add a new step at the end of the project. This step wi #### Create Empty Steps -Enter the number of steps you want to add in the input. Then, clicking the button will create that many empty steps at the end of the project. +Enter the number of steps you want to add in the input. Then, clicking the button will create many empty steps at the end of the project. #### Insert Step @@ -124,7 +124,7 @@ pnpm run delete-step X # where X is the step number to be deleted. ### update-step-titles -A one-off script that automatically updates the frontmatter in a project's markdown files so that they are consistent with the project's meta.json. It ensures that each step's title (and dashedName) match the meta's challengeOrder. +A one-off script that automatically updates the frontmatter in a project's markdown files so that they are consistent with the project's meta.json. It ensures that each step's title (and dashedName) matches the meta's `challengeOrder`. #### How to Run the Script diff --git a/docs/i18n/german/how-to-work-on-tutorials-that-use-coderoad.md b/docs/i18n/german/how-to-work-on-tutorials-that-use-coderoad.md index e89ed15b1dd..f372fdd9ff1 100644 --- a/docs/i18n/german/how-to-work-on-tutorials-that-use-coderoad.md +++ b/docs/i18n/german/how-to-work-on-tutorials-that-use-coderoad.md @@ -56,7 +56,7 @@ Wenn du deine Änderungen an `main` nach den obigen Anweisungen testen willst, b - Befolge die Anweisungen auf dem [rdb-alpha Repo](https://github.com/freeCodeCamp/rdb-alpha), um einen Container zu starten - Starte das Tutorial mit der `tutorial.json` Datei auf dem neuen Branch -### Überprüfen von PRs für `main` +### Reviewing PRs to `main` Wenn du einen PR überprüfst, der nur `main` ändert und dabei wie oben beschrieben didaktische oder grammatikalische Probleme behandelt, sollten die Änderungen in `TUTORIAL.md` mit den Änderungen in `tutorial.json` übereinstimmen. @@ -119,11 +119,11 @@ Wenn du Schreibzugriff auf das freeCodeCamp-Repository hast, die Dateien `CHANGE - Erstelle einen PR zu `main` auf dem freeCodeCamp Repo - Wenn du zufrieden bist, füge es zusammen oder lass es und bitte um eine Überprüfung von jemandem - Nachdem der PR zusammengeführt wurde, öffne das Tutorial, indem du den Anweisungen im [rdb-alpha repo](https://github.com/freeCodeCamp/rdb-alpha) folgst, um sicherzustellen, dass es richtig geladen wird und du einige Schritte durchlaufen kannst -- Wenn es bereits PRs für diese Version gibt, schließe sie +- Finally, if any PRs for this version exist, close them ### How to Revert to a Previous Version -- Erstelle einen neuen Branch vom neuesten `main` mit `git checkout -b revert/to-version-X.X.X` +- Create a new branch off of the latest `main` with `git checkout -b revert/to-version-X.X.X` - Mach alle Commits in diesem Branch rückgängig, bis einschließlich des Commits der Version, die auf die Version folgt, zu der du zurückkehren willst. Du könntest zum Beispiel Commits haben, die wie folgt aussehen: ``` diff --git a/docs/i18n/german/language-lead-handbook.md b/docs/i18n/german/language-lead-handbook.md index 9cf7aa55a0c..4208ef8e599 100644 --- a/docs/i18n/german/language-lead-handbook.md +++ b/docs/i18n/german/language-lead-handbook.md @@ -339,7 +339,7 @@ In Crowdin, individuate the `User management` on the left-hand side menu. Dadurch wird die Benutzerverwaltung geöffnet, in der du die Liste aller Benutzer sehen kannst. -Search for the user that will become a proofreader. Verwende das Menü mit den drei Punkten in der Benutzerzeile, um ein Menü zu öffnen und wähle "Add to team". Die Korrekturleserteams haben den Standardnamen `Proof Readers()`, du kannst das Team über den Namen der Sprache suchen. Wenn du das Team ausgewählt hast, benutze den Button "ADD" unten auf der Seite, um den Vorgang abzuschließen. +Search for the user who will become a proofreader. Verwende das Menü mit den drei Punkten in der Benutzerzeile, um ein Menü zu öffnen und wähle "Add to team". Die Korrekturleserteams haben den Standardnamen `Proof Readers()`, du kannst das Team über den Namen der Sprache suchen. Wenn du das Team ausgewählt hast, benutze den Button "ADD" unten auf der Seite, um den Vorgang abzuschließen. Der Benutzer ist jetzt ein Korrekturleser. diff --git a/docs/i18n/german/moderator-handbook.md b/docs/i18n/german/moderator-handbook.md index ff9560ad2c6..3037b20aad0 100644 --- a/docs/i18n/german/moderator-handbook.md +++ b/docs/i18n/german/moderator-handbook.md @@ -18,7 +18,7 @@ Das freeCodeCamp ist eine inklusive Community, und das soll auch so bleiben. We have a single [Code of Conduct](https://code-of-conduct.freecodecamp.org) that governs our entire community. Je weniger Regeln, desto einfacher ist es, sich sie zu merken. Du kannst die Regeln [hier](https://code-of-conduct.freecodecamp.org) lesen und sie dir einprägen. -> [!NOTE] As a moderator, we would add you to one or more teams on GitHub, our community forums & 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). +> [!NOTE] As a moderator, we would add you to one or more teams on GitHub, our community forums & chat servers. If you are missing access to a platform that you would like to moderate, please [reach out to a staff member](FAQ.md#additional-assistance). ## GitHub moderieren @@ -164,7 +164,7 @@ As a moderator, you help keep our community an enjoyable place for anyone to lea Note that once you are a moderator on the forum, you will start to see blue moderator hints about forum members, like "this is the first time [person] has posted - let's welcome them to the community!" or "[person] hasn't posted in a long time - let's welcome them back." -![A blue text message saying "this is the first time [person] has posted - let's welcome them to the community!](https://i.imgur.com/mPmVgzK.png) +![A blue text message saying "This is the first time [person] has posted - let's welcome them to the community!](https://i.imgur.com/mPmVgzK.png) These are opportunities for you to welcome them and make them feel extra special. You never know which person who's marginally involved may become our next super-helper, helping many other people in their coding journey. Even the slightest kindness may trigger a cascade of good deeds. diff --git a/docs/i18n/german/reply-templates.md b/docs/i18n/german/reply-templates.md index a1a9bbcc41c..d5c5110346b 100644 --- a/docs/i18n/german/reply-templates.md +++ b/docs/i18n/german/reply-templates.md @@ -183,7 +183,7 @@ If the forum members determine there is nothing wrong with your code, you can re Thank you and happy coding. ``` -> When an issue is duplicate of an earlier issue. +> When an issue is a duplicate of an earlier issue. ```markdown Thank you for reporting this issue. @@ -230,7 +230,7 @@ Happy contributing. ```md We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. -Issues labelled with `help wanted` or `first timers only` are open for contributions. +Issues labeled with `help wanted` or `first timers only` are open for contributions. Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. ``` diff --git a/docs/i18n/german/troubleshooting-development-issues.md b/docs/i18n/german/troubleshooting-development-issues.md index 84569c6fbf7..962fd04362c 100644 --- a/docs/i18n/german/troubleshooting-development-issues.md +++ b/docs/i18n/german/troubleshooting-development-issues.md @@ -31,7 +31,7 @@ Use the shortcut pnpm run clean-and-develop ``` -If you continue to face issues with the build, cleaning up the workspace is recommend. +If you continue to face issues with the build, cleaning up the workspace is recommended. Use `git clean` in interactive mode: @@ -50,7 +50,7 @@ git clean -ifdX ## Issues with API, login, Challenge Submissions, etc. -If you can't sign in, and instead you see a banner with an error message that it will be reported to freeCodeCamp, please double-check that your local port `3000` is not in use by a different program. +If you can't sign in, and instead you see a banner with an error message saying that the error will be reported to freeCodeCamp, please double-check that your local port `3000` is not in use by a different program. #### **From Terminal:** ```console diff --git a/docs/i18n/italian/authors-analytics-manual.md b/docs/i18n/italian/authors-analytics-manual.md index c1e2936ea44..a2fb6c5eb13 100644 --- a/docs/i18n/italian/authors-analytics-manual.md +++ b/docs/i18n/italian/authors-analytics-manual.md @@ -1,10 +1,10 @@ # Manuale Analytics per gli autori -Se sei un autore con accesso alla proprietà Google Analytics della pubblicazione (News), puoi utilizzare questa guida per visualizzare l'impatto degli articoli e cercare gli articoli per lingua di pubblicazione. +If you are an author with access to the publication's Google Analytics Property (News), you can use this guide to view your article engagement and search for articles by publication language. ## Cercare per lingua -Per cercare rapporti di engagement per una lingua specifica: +To search for engagement reports in a specific language: ![Immagine - Mostra i passaggi per cercare per lingua su google analytics](https://contribute.freecodecamp.org/images/google-analytics/search-by-language.png) diff --git a/docs/i18n/italian/codebase-best-practices.md b/docs/i18n/italian/codebase-best-practices.md index 3e374c8482e..6358c9a4470 100644 --- a/docs/i18n/italian/codebase-best-practices.md +++ b/docs/i18n/italian/codebase-best-practices.md @@ -161,7 +161,7 @@ The `api/` tests are split into two parts: Unit tests isolate a single function or component. The tests do not need mocking, but will require fixtures. -The unit tests are located in a new file adjacent the file exporting that being tested: +The unit tests are located in a new file adjacent to the file exporting that is being tested: ```text api/ diff --git a/docs/i18n/italian/how-to-catch-outgoing-emails-locally.md b/docs/i18n/italian/how-to-catch-outgoing-emails-locally.md index 28afa3aeda2..2b4bf118506 100644 --- a/docs/i18n/italian/how-to-catch-outgoing-emails-locally.md +++ b/docs/i18n/italian/how-to-catch-outgoing-emails-locally.md @@ -104,7 +104,7 @@ Inizia a [usare MailHog](#using-mailhog). ## Usare Mailhog -Apri una nuova scheda o finestra del browser e vai su [http://localhost:8025](http://localhost:8025) per aprire l'inbox di MailHog dopo che l'installazione è stata completata e MailHog è in esecuzione. +Open a new browser tab or window and navigate to [http://localhost:8025](http://localhost:8025) to open your MailHog inbox when the MailHog installation has been completed and MailHog is running. ## Link Utili diff --git a/docs/i18n/italian/how-to-contribute-to-the-codebase.md b/docs/i18n/italian/how-to-contribute-to-the-codebase.md index 113da69802c..d7e75023484 100644 --- a/docs/i18n/italian/how-to-contribute-to-the-codebase.md +++ b/docs/i18n/italian/how-to-contribute-to-the-codebase.md @@ -23,7 +23,7 @@ Segui questi passaggi: nothing to commit, working directory clean ``` - Se ottieni un messaggio diverso, allora non sei sul main oppure la cartella di lavoro non è pulita, quindi risolvi tutti i file/commit in sospeso e fai il checkout su `main`: + If you got a different message, then you aren't on main or your working directory isn't clean, resolve any outstanding files/commits and checkout `main`: ```console git checkout main @@ -55,7 +55,7 @@ Segui questi passaggi: git push origin main --force ``` - Puoi controllare che il tuo main attuale corrisponda con upstream/main facendo un diff: + You can validate that your current main matches the upstream/main by performing a diff: ```console git diff upstream/main diff --git a/docs/i18n/italian/how-to-enable-new-languages.md b/docs/i18n/italian/how-to-enable-new-languages.md index 05f8df5233b..02bf8ae543d 100644 --- a/docs/i18n/italian/how-to-enable-new-languages.md +++ b/docs/i18n/italian/how-to-enable-new-languages.md @@ -142,7 +142,7 @@ export const rtlLangs = ['']; ### Set Translated SuperBlocks -In the [shared/config/superblocks.ts](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/shared/config/superblocks.ts) file, add the new language to the `notAuditedSuperBlocks` object. This lists all the superblocks which are not fully translated. Add an array of superblocks which have not been fully translated to it. For example: +In the [shared/config/superblocks.ts](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/shared/config/superblocks.ts) file, add the new language to the `notAuditedSuperBlocks` object. This lists all the superblocks which are not fully translated. Add an array of superblocks that have not been fully translated to it. For example: ```js export const notAuditedSuperBlocks: NotAuditedSuperBlocks = { @@ -166,7 +166,7 @@ export const notAuditedSuperBlocks: NotAuditedSuperBlocks = { } ``` -Be sure to only add the superblocks which are **not** fully translated and approved. The translated superblocks will be calculated from this object. When a new superblock is finished being fully translated, remove it from the array for that language. +Be sure to only add the superblocks that are **not** fully translated and approved. The translated superblocks will be calculated from this object. When a new superblock is finished being fully translated, remove it from the array for that language. See the `SuperBlocks` enum at the beginning of the same file for the full list of superblocks. @@ -174,7 +174,7 @@ See the `SuperBlocks` enum at the beginning of the same file for the full list o Next, open the [`client/src/utils/algolia-locale-setup.ts`](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/client/src/utils/algolia-locale-setup.ts) file. Questi dati sono usati dalla barra di ricerca che carica gli articoli in `/news`. Anche se è poco probabile che tu stia testando questa funzione, se questi dati mancano per la tua lingua possono esserci degli errori nel costruire il codebase localmente. -Aggiungi un oggetto per la tua lingua all'oggetto `algoliaIndices`. Dovresti usare gli stessi valori dell'oggetto `english` per testare in locale, sostituendo la chiave `english` con il valore della tua lingua in `availableLangs`. +Aggiungi un oggetto per la tua lingua all'oggetto `algoliaIndices`. You should use the same values as the `english` object for local testing, replacing the `english` key with your language's `availableLangs` value. > [!NOTE] Se abbiamo già distribuito un'istanza della pubblicazione nella tua lingua target, puoi aggiornare i valori così da rispecchiare le istanze live. Altrimenti, usa i valori della pubblicazione inglese. @@ -229,7 +229,7 @@ You don't have to have everything in these 3 files translated at first. It's pos You can replace any URLs that you have corresponding pages ready in your language. -For example, if you have the publication in your language, you can replace the URL for `"news"`. If you want to translate articles listed in the footer links, see [How to Translate Articles in the Footer Links](language-lead-handbook.md#how-to-translate-articles-in-the-footer-links). +For example, if you have a publication in your language, you can replace the URL for `"news"`. If you want to translate articles listed in the footer links, see [How to Translate Articles in the Footer Links](language-lead-handbook.md#how-to-translate-articles-in-the-footer-links). #### `meta-tags.json` @@ -303,7 +303,7 @@ videoLocaleIds: Joi.when('challengeType', { Se desideri testare le traduzioni localmente, prima di aggiungerle al nostro repository principale - salta i cambiamenti delle procedure di Crowdin. Segui i passaggi per abilitare una lingua, quindi scarica le traduzioni da Crowdin e caricale nel tuo codice locale. -Poiché la lingua non è ancora stata approvata per la produzione, i nostri script non scaricheranno automaticamente le traduzioni. Solo lo staff ha accesso al download diretto delle traduzioni - sei il benvenuto a rivolgerti a noi attraverso la [chat room per i contributori](https://discord.gg/PRyKn3Vbay), o puoi tradurre i file markdown inglesi per le esigenze di test. +Poiché la lingua non è ancora stata approvata per la produzione, i nostri script non scaricheranno automaticamente le traduzioni. Only staff have access to directly download the translations - you are welcome to reach out to us in our [contributors chat room](https://discord.gg/PRyKn3Vbay), or you can translate the English markdown files locally for testing purposes. Una volta che avrai i file, li dovrai mettere nelle cartelle giuste. Per le sfide del curriculum, dovresti mettere le cartelle dei certificati (ad esempio `01-responsive-web-design`) nella cartella `curriculum/challenges/{lang}`. Per la nostra traduzione in Dothraki, sarebbe `curriculum/challenges/dothraki`. I file `.json` con le traduzioni del client vanno nella cartella `client/i18n/locales/{lang}`. @@ -325,7 +325,7 @@ In [`shared/config/i18n.ts`](https://github.com/freeCodeCamp/freeCodeCamp/blob/m export const hiddenLangs = []; // Remove your language from the array ``` -When this PR is merged and gets deployed, the curriculum in your language will be live. +When this PR is merged and deployed, the curriculum in your language will be live. # Rilasciare nuove lingue su `/learn` diff --git a/docs/i18n/italian/how-to-help-with-video-challenges.md b/docs/i18n/italian/how-to-help-with-video-challenges.md index 2464adb7b50..e208b419ac2 100644 --- a/docs/i18n/italian/how-to-help-with-video-challenges.md +++ b/docs/i18n/italian/how-to-help-with-video-challenges.md @@ -126,7 +126,7 @@ Aggiungi/Cambia il testo della domanda sotto la parte che dice: ## --text-- ``` -Add/Update answers (`Answer 1`, `Answer 2`, and so on) sotto `## --answers--`. Assicurati di aggiornare il numero sotto `## --video-solution--` con il numero della risposta corretta. Puoi aggiungere altre possibili domande seguendo lo stesso formato. Le domande e le risposte possono essere racchiuse tra virgolette. +Add/Update answers (`Answer 1`, `Answer 2`, and so on) sotto `## --answers--`. Assicurati di aggiornare il numero sotto `## --video-solution--` con il numero della risposta corretta. Puoi aggiungere altre possibili domande seguendo lo stesso formato. The questions and answers can be surrounded with quotation marks. ### Esempi di domande diff --git a/docs/i18n/italian/how-to-open-a-pull-request.md b/docs/i18n/italian/how-to-open-a-pull-request.md index 0039fa5cebc..048e95f85e5 100644 --- a/docs/i18n/italian/how-to-open-a-pull-request.md +++ b/docs/i18n/italian/how-to-open-a-pull-request.md @@ -140,7 +140,7 @@ Quando stai lavorando su normali bug e funzionalità sul nostro ramo di sviluppo ### For Upcoming Curriculum and Features -Quando stai lavorando su funzionalità dei rami `next-*` del nuovo curriculum, devi fare un cherry pick: +When you are working on features for our upcoming curriculum `next-*` branches, you have to do a `cherry-pick`: 1. Assicurati che il tuo upstream sia sincronizzato con il tuo repository locale: @@ -151,7 +151,7 @@ Quando stai lavorando su funzionalità dei rami `next-*` del nuovo curriculum, d git reset --hard upstream/next-python-projects ``` -2. Fai un backup +2. Take a backup a. Elimina il ramo locale dopo aver effettuato un backup (se lo hai ancora localmente): @@ -169,7 +169,7 @@ Quando stai lavorando su funzionalità dei rami `next-*` del nuovo curriculum, d git branch -D ``` - b. O solo un backup del ramo pr (se non lo hai localmente): + b. Or just a backup of your PR branch (if you do not have it locally): ```console git checkout -b origin/ diff --git a/docs/i18n/italian/how-to-proofread-files.md b/docs/i18n/italian/how-to-proofread-files.md index 65cec644433..41214ddf28e 100644 --- a/docs/i18n/italian/how-to-proofread-files.md +++ b/docs/i18n/italian/how-to-proofread-files.md @@ -2,7 +2,7 @@ Il nostro team di revisione è responsabile di controllare che le traduzioni riflettano accuratamente il testo originale. Ci affidiamo ai revisori per avere delle traduzioni di alta qualità. -Tutte le nostre traduzioni sono fatte a mano, da veri esseri umani. La revisione assicura che ci sia un tono consistente su tutte le nostre risorse tradotte, come ad esempio il curriculum. +Tutte le nostre traduzioni sono fatte a mano, da veri esseri umani. Proofreading ensures that there is a consistent tone across all our translated resources like the curriculum. Per iniziare a revisionare visita [la nostra piattaforma di traduzione](https://translate.freecodecamp.org) e fai il login. Seleziona "Go to console" nella barra di navigazione in alto per passare da public view a workspace view. @@ -49,6 +49,6 @@ Il nostro staff e i moderatori della community sono sempre alla ricerca di volon ## Creating a Channel on Chat for a World Language -Per la maggior parte, incoraggiamo l'uso della [chat room per i contributori](https://discord.gg/PRyKn3Vbay) per tutte le comunicazioni. Ma se il team di volontari per una certa lingua cresce, possiamo considerare di creare un canale aggiuntivo per la lingua. +For the most part, we encourage you to use the [contributors chat](https://discord.gg/PRyKn3Vbay) room for all correspondence. However if the team of volunteer translators grows for a certain language, we can consider creating an additional break-out channel for the language. Se sei un proofreader e sei interessato ad avere un canale dedicato sul server di chat per una specifica lingua, [compila questo modulo](https://forms.gle/XU5CyutrYCgDYaVZA). diff --git a/docs/i18n/italian/how-to-setup-freecodecamp-locally.md b/docs/i18n/italian/how-to-setup-freecodecamp-locally.md index ae2780c7d62..ed0ce32ca31 100644 --- a/docs/i18n/italian/how-to-setup-freecodecamp-locally.md +++ b/docs/i18n/italian/how-to-setup-freecodecamp-locally.md @@ -4,7 +4,7 @@ Follow these guidelines for setting up a development environment for freeCodeCam > [!ATTENTION] - freeCodeCamp does not build and run natively on Windows, you will [need to use WSL2](how-to-setup-wsl.md) for a Linux-like setup on Windows. - You can't use Windows Command Prompt, Git Bash or PowerShell to build and run the codebase. - Note that if using Windows, the hardware requirements need to be more than [what we mention](how-to-setup-freecodecamp-locally?id=how-to-prepare-your-local-machine) to accommodate for WSL-based setup. -If you are looking to make a one-off contribution, you should use Gitpod to make changes. The Gitpod setup launches a ready-to-code environment in a few minutes in your web browser. For contributing long-term, we recommend you setup freeCodeCamp on your local machine. +If you are looking to make a one-off contribution, you should use Gitpod to make changes. The Gitpod setup launches a ready-to-code environment in a few minutes in your web browser. To contribute long-term, we recommend you set up freeCodeCamp on your local machine. Here are some pros and cons which should help you decide which option is best for you: @@ -19,9 +19,9 @@ Here are some pros and cons which should help you decide which option is best fo ### How to Prepare a Gitpod Workspace -We have automated the process of installing all the dependencies & tools you will need. With Gitpod you get a free ready-to-code environment in a few minutes, and is useful if you do not have access to computer or want to make one-time changes. +We have automated the process of installing all the dependencies & tools you will need. With Gitpod you get a free ready-to-code environment in a few minutes, and is useful if you do not have access to a computer or want to make one-time changes. -There are various ways to launch an Gitpod workspace: +There are various ways to launch a Gitpod workspace: 1. **(Fastest)** Prepend `gitpod.io/#` in front of any URL from GitHub. @@ -158,7 +158,7 @@ Now that you have downloaded a copy of your fork, you will need to set up an `up You need a reference from your local clone to the `upstream` repository in addition to the `origin` repository. This is so that you can sync changes from the main repository without the requirement of forking and cloning repeatedly. -1. Cambia la directory nella nuova directory freeCodeCamp: +1. Change the directory to the new freeCodeCamp directory: ```console cd freeCodeCamp diff --git a/docs/i18n/italian/how-to-setup-freecodecamp-mobile-app-locally.md b/docs/i18n/italian/how-to-setup-freecodecamp-mobile-app-locally.md index fd94d084e44..2b477febefb 100644 --- a/docs/i18n/italian/how-to-setup-freecodecamp-mobile-app-locally.md +++ b/docs/i18n/italian/how-to-setup-freecodecamp-mobile-app-locally.md @@ -44,7 +44,7 @@ Una volta che avrai installato i prerequisiti, dovrai preparare il tuo ambiente Fare il [fork](https://help.github.com/articles/about-forks/) è il passaggio grazie a cui ottieni la tua copia del repository (_repo_) su GitHub. -Questo è essenziale, in quanto consente di lavorare sulla propria copia dell'app di freeCodeCamp su GitHub, o di scaricare (clonare) il tuo repository per lavorare localmente. Più tardi, potrai richiedere che le tue modifiche siano integrate (pull) nel repository principale dal tuo fork tramite una pull request (PR). +This is essential, as it allows you to work on your own copy of the freeCodeCamp mobile app on GitHub, or to download (clone) your repository to work on locally. Più tardi, potrai richiedere che le tue modifiche siano integrate (pull) nel repository principale dal tuo fork tramite una pull request (PR). > [!TIP] Il repository principale su `https://github.com/freeCodeCamp/mobile` è spesso indicato come il repository `upstream`. > @@ -361,14 +361,14 @@ Segui questi passaggi: > [!NOTE] You only need to follow this section if you're modifying the challenge test runner in the mobile app. Otherwise, you can go to the next section on [how to open a pull request](#proposing-a-pull-request-pr). -1. Clone a copy of the [freeCodeCamp repo](https://github.com/freeCodeCamp/freeCodeCamp) locally outside of your local copy of freeCodeCamp mobile repo. Your folder structure should look like this: +1. Clone a copy of the [freeCodeCamp repo](https://github.com/freeCodeCamp/freeCodeCamp) locally outside of your local copy of the freeCodeCamp mobile repo. Your folder structure should look like this: ```console ├── freeCodeCamp ├── mobile ``` -2. Change directory to the freeCodeCamp repo: +2. Change the directory to the freeCodeCamp repo: ```console cd freeCodeCamp @@ -480,7 +480,7 @@ Se sei su un sistema operativo diverso e/o continui ad avere dei problemi, visit ### Problemi con UI, errori di build, ecc. -Se si verificano problemi con l'interfaccia utente o errori di compilazione, una pulizia potrebbe essere utile: +If you face issues with the UI, or build errors a cleanup can be useful: ```console flutter clean @@ -488,7 +488,7 @@ flutter clean ### Issues Installing Dependencies -Se incontri degli errori durante l'installazione delle dipendenze, assicurati di non essere in una rete ristretta o che le impostazioni del tuo firewall non ti impediscono di accedere alle risorse. +If you get errors while installing the dependencies, please make sure that you are not in a restricted network or that your firewall settings do not prevent you from accessing resources. Be patient as the first-time setup can take a while depending on your network bandwidth. diff --git a/docs/i18n/italian/how-to-setup-wsl.md b/docs/i18n/italian/how-to-setup-wsl.md index 9bdce44e71c..29180621f37 100644 --- a/docs/i18n/italian/how-to-setup-wsl.md +++ b/docs/i18n/italian/how-to-setup-wsl.md @@ -123,7 +123,7 @@ Now that you have installed the pre-requisites, follow [our local setup guide](h > [!WARNING] > -> Please note, at this time the setup for Cypress tests (and related GUI needs) are a work in progress. Dovresti essere comunque in grado di lavorare sulla maggior parte del codebase. +> Please note, at this time the setup for Cypress tests (and related GUI needs) is a work in progress. Dovresti essere comunque in grado di lavorare sulla maggior parte del codebase. ## Link Utili diff --git a/docs/i18n/italian/how-to-use-docker-on-windows-home.md b/docs/i18n/italian/how-to-use-docker-on-windows-home.md index 49746a0cae1..303fe4116eb 100644 --- a/docs/i18n/italian/how-to-use-docker-on-windows-home.md +++ b/docs/i18n/italian/how-to-use-docker-on-windows-home.md @@ -2,7 +2,7 @@ Ci sono alcuni pericoli da evitare quando si setta Docker su Windows Home. Per prima cosa devi usare [Docker Toolbox](https://docs.docker.com/toolbox/toolbox_install_windows/) come amministratore. Purtroppo Windows Home non supporta Docker per Windows Desktop, quindi deve essere usata la Toolbox. Essa deve essere eseguita come Amministratore in quanto l'installazione utilizza collegamenti simbolici che non possono essere creati altrimenti. -Dopo aver installato la toolbox, esegui Docker Quickstart Terminal come amministratore. Questo creerà una virtual machine di `default`, se ancora non esiste. Dopo averlo fatto, chiudi il terminale e apri VirtualBox (ancora come Amministratore). Dovresti essere in grado di vedere la macchina di `default`. Il sito richiede molte risorse, quindi ferma la virtual machine e alza le impostazioni per quanto puoi, soprattutto la memoria. È stato confermato che lavora con 4GB di ram. +Dopo aver installato la toolbox, esegui Docker Quickstart Terminal come amministratore. Questo creerà una virtual machine di `default`, se ancora non esiste. Dopo averlo fatto, chiudi il terminale e apri VirtualBox (ancora come Amministratore). Dovresti essere in grado di vedere la macchina di `default`. Il sito richiede molte risorse, quindi ferma la virtual machine e alza le impostazioni per quanto puoi, soprattutto la memoria. It has been confirmed to work with 4GB of RAM. Una volta che sarai felice perché Docker sta funzionando, clona il repository di freeCodeCamp in una directory all'interno di `C:\Users`. Queste directory sono condivise dando a Docker accesso alle directory locali, di cui ha bisogno durante l'installazione. diff --git a/docs/i18n/italian/how-to-work-on-coding-challenges.md b/docs/i18n/italian/how-to-work-on-coding-challenges.md index c1f97ffb0e3..6a1c1f549ae 100644 --- a/docs/i18n/italian/how-to-work-on-coding-challenges.md +++ b/docs/i18n/italian/how-to-work-on-coding-challenges.md @@ -4,7 +4,7 @@ Il nostro obiettivo è quello di sviluppare un'esperienza di apprendimento inter Progettare le sfide di programmazione interattiva è difficile. Sarebbe molto più facile scrivere una spiegazione lunga o creare un video tutorial. Ma per il nostro curriculum di base, ci atteniamo a ciò che funziona meglio per la maggior parte delle persone - un'esperienza completamente interattiva, come il videogioco. -Vogliamo che i camper raggiungano uno stato di flusso. Vogliamo che costruiscano slancio e sfondino attraverso il nostro curriculum con il minor numero di intoppi possibile. Vogliamo che entrino nei progetti con fiducia e che si espongano ampiamente ai concetti di programmazione. +Vogliamo che i camper raggiungano uno stato di flusso. Vogliamo che costruiscano slancio e sfondino attraverso il nostro curriculum con il minor numero di intoppi possibile. We want them to go into the projects with confidence and gain wide exposure to programming concepts. Nota che per la versione 7.0 del curriculum freeCodeCamp, ci stiamo muovendo verso [un modello interamente orientato al progetto con molta più ripetizione](https://www.freecodecamp.org/news/python-curriculum-is-live/). @@ -554,7 +554,7 @@ b c ``` -And you choose `b`, your new order will be: +If you choose `b`, your new order will be: ```bash a diff --git a/docs/i18n/italian/how-to-work-on-localized-client-webapp.md b/docs/i18n/italian/how-to-work-on-localized-client-webapp.md index 69152283811..890e4dfdd6f 100644 --- a/docs/i18n/italian/how-to-work-on-localized-client-webapp.md +++ b/docs/i18n/italian/how-to-work-on-localized-client-webapp.md @@ -8,13 +8,13 @@ Once you have set up the project locally you should be able to follow this docum Questo può essere utile quando stai lavorando su una caratteristica che riguarda specificatamente qualcosa che coinvolge la localizzazione e ti richiede ad esempio l'etichetta di un bottone in una lingua diversa. -> [!TIP] Non hai bisogno di seguire questo documento per tradurre il curriculum di freeCodeCamp o per contribuire alla documentazione. Invece, leggi [questa guida](how-to-translate-files.md). +> [!TIP] You do not need to follow this document to translate freeCodeCamp's curriculum or contributing documentation. Invece, leggi [questa guida](how-to-translate-files.md). Andiamo a vedere come funzionano il framework e gli strumenti. ## Struttura dei file -Most of the files for translating the platform are located in the [`client/i18n`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/client/i18n) folder. Ogni lingua ha una directory al suo interno che contiene file JSON con le traduzioni. +Most of the files for translating the platform are located in the [`client/i18n`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/client/i18n) folder. Each language has a directory that contains JSON files with the translations. ```console config @@ -55,7 +55,7 @@ Most of the files for translating the platform are located in the [`client/i18n` └── validate-keys.ts ``` -Some of these files are translated on our translation platform (Crowdin) and some are translated or created via PR's on GitHub. +Some of these files are translated on our translation platform (Crowdin) and some are translated or created via PRs on GitHub. **File tradotti con la nostra piattaforma di traduzione:** diff --git a/docs/i18n/italian/how-to-work-on-practice-projects.md b/docs/i18n/italian/how-to-work-on-practice-projects.md index de7c7c44bae..1c4cae7a57f 100644 --- a/docs/i18n/italian/how-to-work-on-practice-projects.md +++ b/docs/i18n/italian/how-to-work-on-practice-projects.md @@ -38,7 +38,7 @@ Cliccando questo pulsante aggiungerai un nuovo step alla fine del progetto. Ques #### Creare step vuoti -Inserisci nell'input il numero di step che vuoi aggiungere. Poi, cliccando sul pulsante verrà creato il numero di step desiderati alla fine del progetto. +Inserisci nell'input il numero di step che vuoi aggiungere. Then, clicking the button will create many empty steps at the end of the project. #### Inserire uno step @@ -124,7 +124,7 @@ pnpm run delete-step X # dove X è il numero dello step da eliminare. ### update-step-titles -Uno script una tantum che aggiorna automaticamente il frontmatter nei file di markdown di un progetto in modo che siano coerenti con il progetto meta.json. Fa in modo che il titolo di ogni step (e dashedName) corrisponda al challengeOrder in meta. +Uno script una tantum che aggiorna automaticamente il frontmatter nei file di markdown di un progetto in modo che siano coerenti con il progetto meta.json. It ensures that each step's title (and dashedName) matches the meta's `challengeOrder`. #### How to Run the Script diff --git a/docs/i18n/italian/how-to-work-on-tutorials-that-use-coderoad.md b/docs/i18n/italian/how-to-work-on-tutorials-that-use-coderoad.md index 83f38e97857..424ab3c17b1 100644 --- a/docs/i18n/italian/how-to-work-on-tutorials-that-use-coderoad.md +++ b/docs/i18n/italian/how-to-work-on-tutorials-that-use-coderoad.md @@ -56,7 +56,7 @@ Se vuoi testare i tuoi cambiamenti a `main` dopo aver usato le istruzioni preced - Segui le istruzioni nel repo [rdb-alpha repo](https://github.com/freeCodeCamp/rdb-alpha) per creare un contenitore - Inizia il tutorial usando `tutorial.json` nel nuovo branch -### Revisionare PR a `main` +### Reviewing PRs to `main` Se stai revisionando un PR che fa cambiamenti a `main`solo con istruzioni o errori di grammatica come descritto sopra, i cambiamenti in `TUTORIAL.md` devono combaciare con i cambiamenti in `tutorial.json`. @@ -119,11 +119,11 @@ Se hai permessi di scrittura al repo di freeCodeCamp, hai verificato i file `CHA - Fai un PR a `main` sul repo di freeCodeCamp - Se sei soddisfatto, fai il merge, o lascialo e chiedi una review da parte di qualcun altro - Dopo che è stato fatto il merge del PR, apri il tutotial seguendo le istruzioni nel [repo rdb-alpha](https://github.com/freeCodeCamp/rdb-alpha) per assicurarti che si carichi come si deve e che puoi procedere per qualche step -- Infine, se esistono PR per questa versione, chiudile +- Finally, if any PRs for this version exist, close them ### How to Revert to a Previous Version -- Crea un nuovo branch dal `main` più recente con `git checkout -b revert/to-version-X.X.X` +- Create a new branch off of the latest `main` with `git checkout -b revert/to-version-X.X.X` - Fai il revert di tutti i commit di questo branch fino a e includendo il commit della versione successiva a quella a cui vuoi tornare. Per esempio, se hai dei commit tipo questi: ``` diff --git a/docs/i18n/italian/language-lead-handbook.md b/docs/i18n/italian/language-lead-handbook.md index d451699fa58..65cd321b142 100644 --- a/docs/i18n/italian/language-lead-handbook.md +++ b/docs/i18n/italian/language-lead-handbook.md @@ -339,7 +339,7 @@ In Crowdin, individuate the `User management` on the left-hand side menu. Aprirà gli strumenti di gestione degli utenti e sarai in grado di vedere la lista di tutti gli utenti. -Search for the user that will become a proofreader. Utilizzare il menu a tre punti nella riga dell'utente per aprire un menu e selezionare "Add to team". I team di revisori hanno il nome standard di `Proof Readers ()`, puoi cercare il team usando il nome della lingua. Una volta selezionato il team, utilizza il pulsante "ADD" in fondo alla pagina per finalizzare il processo. +Search for the user who will become a proofreader. Utilizzare il menu a tre punti nella riga dell'utente per aprire un menu e selezionare "Add to team". I team di revisori hanno il nome standard di `Proof Readers ()`, puoi cercare il team usando il nome della lingua. Una volta selezionato il team, utilizza il pulsante "ADD" in fondo alla pagina per finalizzare il processo. L'utente ora è un revisore. diff --git a/docs/i18n/italian/moderator-handbook.md b/docs/i18n/italian/moderator-handbook.md index aae1c37fee7..743f2ed4b09 100644 --- a/docs/i18n/italian/moderator-handbook.md +++ b/docs/i18n/italian/moderator-handbook.md @@ -18,7 +18,7 @@ freeCodeCamp è una comunità inclusiva ed è necessario lasciarla così. Abbiamo un singolo [Codice di Condotta](https://code-of-conduct.freecodecamp.org) per gestire tutta la nostra comunità. Meno sono le regole, più facile sarà ricordarle. Puoi leggere queste regole e impegnarti a ricordarle [qui](https://code-of-conduct.freecodecamp.org). -> [!NOTE] As a moderator, we would add you to one or more teams on GitHub, our community forums & chat servers. Se ti manca l'accesso a una piattaforma che vorresti moderare, per favore [contatta un membro dello staff](FAQ.md#assistenza-aggiuntiva). +> [!NOTE] As a moderator, we would add you to one or more teams on GitHub, our community forums & chat servers. If you are missing access to a platform that you would like to moderate, please [reach out to a staff member](FAQ.md#additional-assistance). ## Moderare GitHub @@ -164,7 +164,7 @@ As a moderator, you help keep our community an enjoyable place for anyone to lea Note that once you are a moderator on the forum, you will start to see blue moderator hints about forum members, like "this is the first time [person] has posted - let's welcome them to the community!" or "[person] hasn't posted in a long time - let's welcome them back." -![A blue text message saying "this is the first time [person] has posted - let's welcome them to the community!](https://i.imgur.com/mPmVgzK.png) +![A blue text message saying "This is the first time [person] has posted - let's welcome them to the community!](https://i.imgur.com/mPmVgzK.png) These are opportunities for you to welcome them and make them feel extra special. You never know which person who's marginally involved may become our next super-helper, helping many other people in their coding journey. Even the slightest kindness may trigger a cascade of good deeds. diff --git a/docs/i18n/italian/reply-templates.md b/docs/i18n/italian/reply-templates.md index a1a9bbcc41c..d5c5110346b 100644 --- a/docs/i18n/italian/reply-templates.md +++ b/docs/i18n/italian/reply-templates.md @@ -183,7 +183,7 @@ If the forum members determine there is nothing wrong with your code, you can re Thank you and happy coding. ``` -> When an issue is duplicate of an earlier issue. +> When an issue is a duplicate of an earlier issue. ```markdown Thank you for reporting this issue. @@ -230,7 +230,7 @@ Happy contributing. ```md We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. -Issues labelled with `help wanted` or `first timers only` are open for contributions. +Issues labeled with `help wanted` or `first timers only` are open for contributions. Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. ``` diff --git a/docs/i18n/italian/troubleshooting-development-issues.md b/docs/i18n/italian/troubleshooting-development-issues.md index 1aacf9c00b8..da424cf322c 100644 --- a/docs/i18n/italian/troubleshooting-development-issues.md +++ b/docs/i18n/italian/troubleshooting-development-issues.md @@ -31,7 +31,7 @@ Usa la scorciatoia pnpm run clean-and-develop ``` -Se continui a incontrare problemi con il build, è consigliato ripulire lo spazio di lavoro. +If you continue to face issues with the build, cleaning up the workspace is recommended. Usa `git clean` in modalità interattiva: @@ -50,7 +50,7 @@ git clean -ifdX ## Issues with API, login, Challenge Submissions, etc. -Se non riesci ad accedere e invece vedi un banner con un messaggio di errore che verrà segnalato a freeCodeCamp, ti preghiamo di controllare che la porta locale `3000` non sia utilizzata da un programma diverso. +If you can't sign in, and instead you see a banner with an error message saying that the error will be reported to freeCodeCamp, please double-check that your local port `3000` is not in use by a different program. #### **From Terminal:** ```console diff --git a/docs/i18n/japanese/authors-analytics-manual.md b/docs/i18n/japanese/authors-analytics-manual.md index 221ca725cd9..fa5bbe46392 100644 --- a/docs/i18n/japanese/authors-analytics-manual.md +++ b/docs/i18n/japanese/authors-analytics-manual.md @@ -1,10 +1,10 @@ # Authors Analytics Manual -If you are an author with access to the publication's Google Analytics Property (News), you can use this guide to view your articles engagement and search for articles by publication language. +If you are an author with access to the publication's Google Analytics Property (News), you can use this guide to view your article engagement and search for articles by publication language. ## Search by Language -To search for engagement reports by a specific language: +To search for engagement reports in a specific language: ![Image - Show steps to search by language on googla analytics](https://contribute.freecodecamp.org/images/google-analytics/search-by-language.png) diff --git a/docs/i18n/japanese/codebase-best-practices.md b/docs/i18n/japanese/codebase-best-practices.md index dd2dbc791fb..0dc019736d0 100644 --- a/docs/i18n/japanese/codebase-best-practices.md +++ b/docs/i18n/japanese/codebase-best-practices.md @@ -161,7 +161,7 @@ The `api/` tests are split into two parts: Unit tests isolate a single function or component. The tests do not need mocking, but will require fixtures. -The unit tests are located in a new file adjacent the file exporting that being tested: +The unit tests are located in a new file adjacent to the file exporting that is being tested: ```text api/ diff --git a/docs/i18n/japanese/how-to-catch-outgoing-emails-locally.md b/docs/i18n/japanese/how-to-catch-outgoing-emails-locally.md index 1966b072412..292b8caf094 100644 --- a/docs/i18n/japanese/how-to-catch-outgoing-emails-locally.md +++ b/docs/i18n/japanese/how-to-catch-outgoing-emails-locally.md @@ -104,7 +104,7 @@ mailhog ## MailHog の使用 -Open a new browser tab or window and navigate to [http://localhost:8025](http://localhost:8025) to open your MailHog inbox when the MailHog installation has completed and MailHog is running. +Open a new browser tab or window and navigate to [http://localhost:8025](http://localhost:8025) to open your MailHog inbox when the MailHog installation has been completed and MailHog is running. ## 有用なリンク diff --git a/docs/i18n/japanese/how-to-contribute-to-the-codebase.md b/docs/i18n/japanese/how-to-contribute-to-the-codebase.md index 3ee01e7f9c9..0068611fc50 100644 --- a/docs/i18n/japanese/how-to-contribute-to-the-codebase.md +++ b/docs/i18n/japanese/how-to-contribute-to-the-codebase.md @@ -23,7 +23,7 @@ Follow these steps: nothing to commit, working directory clean ``` - If you got different message, then you aren't on main or your working directory isn't clean, resolve any outstanding files/commits and checkout `main`: + If you got a different message, then you aren't on main or your working directory isn't clean, resolve any outstanding files/commits and checkout `main`: ```console git checkout main @@ -55,7 +55,7 @@ Follow these steps: git push origin main --force ``` - You can validate your current main matches the upstream/main by performing a diff: + You can validate that your current main matches the upstream/main by performing a diff: ```console git diff upstream/main diff --git a/docs/i18n/japanese/how-to-enable-new-languages.md b/docs/i18n/japanese/how-to-enable-new-languages.md index 00d643a7c6e..dd214464d05 100644 --- a/docs/i18n/japanese/how-to-enable-new-languages.md +++ b/docs/i18n/japanese/how-to-enable-new-languages.md @@ -142,7 +142,7 @@ export const rtlLangs = ['']; ### Set Translated SuperBlocks -In the [shared/config/superblocks.ts](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/shared/config/superblocks.ts) file, add the new language to the `notAuditedSuperBlocks` object. This lists all the superblocks which are not fully translated. Add an array of superblocks which have not been fully translated to it. For example: +In the [shared/config/superblocks.ts](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/shared/config/superblocks.ts) file, add the new language to the `notAuditedSuperBlocks` object. This lists all the superblocks which are not fully translated. Add an array of superblocks that have not been fully translated to it. For example: ```js export const notAuditedSuperBlocks: NotAuditedSuperBlocks = { @@ -166,7 +166,7 @@ export const notAuditedSuperBlocks: NotAuditedSuperBlocks = { } ``` -Be sure to only add the superblocks which are **not** fully translated and approved. The translated superblocks will be calculated from this object. When a new superblock is finished being fully translated, remove it from the array for that language. +Be sure to only add the superblocks that are **not** fully translated and approved. The translated superblocks will be calculated from this object. When a new superblock is finished being fully translated, remove it from the array for that language. See the `SuperBlocks` enum at the beginning of the same file for the full list of superblocks. @@ -174,7 +174,7 @@ See the `SuperBlocks` enum at the beginning of the same file for the full list o Next, open the [`client/src/utils/algolia-locale-setup.ts`](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/client/src/utils/algolia-locale-setup.ts) 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 the same values as the `english` object for local testing, replacing the `english` key with your language's `availableLangs` value. +Add an object for your language to the `algoliaIndices` object. You should use the same values as the `english` object for local testing, replacing the `english` key with your language's `availableLangs` value. > [!NOTE] If we have already deployed an instance of news in your target language, you can update the values to reflect the live instance. Otherwise, use the English values. @@ -229,7 +229,7 @@ You don't have to have everything in these 3 files translated at first. It's pos You can replace any URLs that you have corresponding pages ready in your language. -For example, if you have the publication in your language, you can replace the URL for `"news"`. If you want to translate articles listed in the footer links, see [How to Translate Articles in the Footer Links](language-lead-handbook.md#how-to-translate-articles-in-the-footer-links). +For example, if you have a publication in your language, you can replace the URL for `"news"`. If you want to translate articles listed in the footer links, see [How to Translate Articles in the Footer Links](language-lead-handbook.md#how-to-translate-articles-in-the-footer-links). #### `meta-tags.json` @@ -303,7 +303,7 @@ videoLocaleIds: Joi.when('challengeType', { If you would like to test translations locally, before adding them to our main repository - skip the Crowdin workflow changes. Follow the steps for enabling a language, then download the translations from Crowdin and load them into your local code. -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://discord.gg/PRyKn3Vbay), or you can translate the English markdown files locally for testing purposes. +Because the language has not been approved for production, our scripts are not automatically downloading the translations yet. Only staff have access to directly download the translations - you are welcome to reach out to us in our [contributors chat room](https://discord.gg/PRyKn3Vbay), 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. @@ -325,7 +325,7 @@ In [`shared/config/i18n.ts`](https://github.com/freeCodeCamp/freeCodeCamp/blob/m export const hiddenLangs = []; // Remove your language from the array ``` -When this PR is merged and gets deployed, the curriculum in your language will be live. +When this PR is merged and deployed, the curriculum in your language will be live. # Deploying New Languages on `/news` diff --git a/docs/i18n/japanese/how-to-help-with-video-challenges.md b/docs/i18n/japanese/how-to-help-with-video-challenges.md index f6a8168330d..9e84541877a 100644 --- a/docs/i18n/japanese/how-to-help-with-video-challenges.md +++ b/docs/i18n/japanese/how-to-help-with-video-challenges.md @@ -125,7 +125,7 @@ Answer 2 ## --text-- ``` -`## --answers--` の下に回答を追加 / 更新してください (`Answer 1`、`Answer 2` など)。 `## -video-solution--` の下にある番号を正解の番号に更新してください。 同じ形式で、他の回答も追加できます。 質問と回答は引用符で囲むことができます。 +`## --answers--` の下に回答を追加 / 更新してください (`Answer 1`、`Answer 2` など)。 `## -video-solution--` の下にある番号を正解の番号に更新してください。 同じ形式で、他の回答も追加できます。 The questions and answers can be surrounded with quotation marks. ### 質問の例 diff --git a/docs/i18n/japanese/how-to-open-a-pull-request.md b/docs/i18n/japanese/how-to-open-a-pull-request.md index 9d976a6278b..63eb5d2e101 100644 --- a/docs/i18n/japanese/how-to-open-a-pull-request.md +++ b/docs/i18n/japanese/how-to-open-a-pull-request.md @@ -140,7 +140,7 @@ When you are working on regular bugs and features on our development branch `mai ### For Upcoming Curriculum and Features -When you are working on features for our upcoming curriculum `next-*` branches, you have to do a cherry pick: +When you are working on features for our upcoming curriculum `next-*` branches, you have to do a `cherry-pick`: 1. Make sure your upstream comes in sync with your local: @@ -151,7 +151,7 @@ When you are working on features for our upcoming curriculum `next-*` branches, git reset --hard upstream/next-python-projects ``` -2. Take backup +2. Take a backup a. Either delete your local branch after taking a backup (if you still have it locally): @@ -169,7 +169,7 @@ When you are working on features for our upcoming curriculum `next-*` branches, git branch -D ``` - b. Or just a backup of your pr branch (if you do not have it locally): + b. Or just a backup of your PR branch (if you do not have it locally): ```console git checkout -b origin/ diff --git a/docs/i18n/japanese/how-to-proofread-files.md b/docs/i18n/japanese/how-to-proofread-files.md index 2635a3350a5..d6bba257bde 100644 --- a/docs/i18n/japanese/how-to-proofread-files.md +++ b/docs/i18n/japanese/how-to-proofread-files.md @@ -2,7 +2,7 @@ 校正チームは、翻訳文が原文を正確に反映するようにする責任があります。 私たちは、非常に高い品質の翻訳文を提供してくれる校正者を信頼しています。 -翻訳はすべて実際の人間が作業しています。 校正により、カリキュラムなどの翻訳リソース全体で一貫したトーンが保証されます。 +翻訳はすべて実際の人間が作業しています。 Proofreading ensures that there is a consistent tone across all our translated resources like the curriculum. 校正を始めるには、[翻訳プラットフォーム](https://translate.freecodecamp.org) にアクセスしてログインします。 上部ナビゲーションバーで「コンソールに移動」を選択し、パブリックビューからワークスペースビューに切り替えます。 @@ -49,6 +49,6 @@ ## Creating a Channel on Chat for a World Language -ほとんどの場合、すべての連絡に [「contributors」](https://discord.gg/PRyKn3Vbay) チャンネルを使用することをお勧めします。 しかし、ある言語のボランティア翻訳者のチームが成長した場合、その言語のブレイクアウトチャンネルを追加することを検討します。 +For the most part, we encourage you to use the [contributors chat](https://discord.gg/PRyKn3Vbay) room for all correspondence. However if the team of volunteer translators grows for a certain language, we can consider creating an additional break-out channel for the language. 既に校正者であり、特定の言語のためのチャットサーバーに専用チャンネルを持つことに興味がある場合、[このフォーム](https://forms.gle/XU5CyutrYCgDYaVZA) に記入します。 diff --git a/docs/i18n/japanese/how-to-setup-freecodecamp-locally.md b/docs/i18n/japanese/how-to-setup-freecodecamp-locally.md index b80b6306de4..5251b9e7bc0 100644 --- a/docs/i18n/japanese/how-to-setup-freecodecamp-locally.md +++ b/docs/i18n/japanese/how-to-setup-freecodecamp-locally.md @@ -4,7 +4,7 @@ Follow these guidelines for setting up a development environment for freeCodeCam > [!ATTENTION] - freeCodeCamp does not build and run natively on Windows, you will [need to use WSL2](how-to-setup-wsl.md) for a Linux-like setup on Windows. - You can't use Windows Command Prompt, Git Bash or PowerShell to build and run the codebase. - Note that if using Windows, the hardware requirements need to be more than [what we mention](how-to-setup-freecodecamp-locally?id=how-to-prepare-your-local-machine) to accommodate for WSL-based setup. -If you are looking to make a one-off contribution, you should use Gitpod to make changes. The Gitpod setup launches a ready-to-code environment in a few minutes in your web browser. For contributing long-term, we recommend you setup freeCodeCamp on your local machine. +If you are looking to make a one-off contribution, you should use Gitpod to make changes. The Gitpod setup launches a ready-to-code environment in a few minutes in your web browser. To contribute long-term, we recommend you set up freeCodeCamp on your local machine. Here are some pros and cons which should help you decide which option is best for you: @@ -19,9 +19,9 @@ Here are some pros and cons which should help you decide which option is best fo ### How to Prepare a Gitpod Workspace -We have automated the process of installing all the dependencies & tools you will need. With Gitpod you get a free ready-to-code environment in a few minutes, and is useful if you do not have access to computer or want to make one-time changes. +We have automated the process of installing all the dependencies & tools you will need. With Gitpod you get a free ready-to-code environment in a few minutes, and is useful if you do not have access to a computer or want to make one-time changes. -There are various ways to launch an Gitpod workspace: +There are various ways to launch a Gitpod workspace: 1. **(Fastest)** Prepend `gitpod.io/#` in front of any URL from GitHub. @@ -158,7 +158,7 @@ Now that you have downloaded a copy of your fork, you will need to set up an `up You need a reference from your local clone to the `upstream` repository in addition to the `origin` repository. This is so that you can sync changes from the main repository without the requirement of forking and cloning repeatedly. -1. Change directory to the new freeCodeCamp directory: +1. Change the directory to the new freeCodeCamp directory: ```console cd freeCodeCamp diff --git a/docs/i18n/japanese/how-to-setup-freecodecamp-mobile-app-locally.md b/docs/i18n/japanese/how-to-setup-freecodecamp-mobile-app-locally.md index 07b11cb8e34..412e7b91137 100644 --- a/docs/i18n/japanese/how-to-setup-freecodecamp-mobile-app-locally.md +++ b/docs/i18n/japanese/how-to-setup-freecodecamp-mobile-app-locally.md @@ -44,7 +44,7 @@ Once you have the prerequisites installed, you need to prepare your development [Forking](https://help.github.com/articles/about-forks/) is a step where you get your own copy of the repository (a.k.a _repo_) on GitHub. -This is essential, as it allows you to work on your own copy of freeCodeCamp mobile app on GitHub, or to download (clone) your repository to work on locally. Later, you will be able to request changes to be pulled into the main repository from your fork via a pull request (PR). +This is essential, as it allows you to work on your own copy of the freeCodeCamp mobile app on GitHub, or to download (clone) your repository to work on locally. Later, you will be able to request changes to be pulled into the main repository from your fork via a pull request (PR). > [!TIP] The main repository at `https://github.com/freeCodeCamp/mobile` is often referred to as the `upstream` repository. > @@ -361,14 +361,14 @@ Follow these steps: > [!NOTE] You only need to follow this section if you're modifying the challenge test runner in the mobile app. Otherwise, you can go to the next section on [how to open a pull request](#proposing-a-pull-request-pr). -1. Clone a copy of the [freeCodeCamp repo](https://github.com/freeCodeCamp/freeCodeCamp) locally outside of your local copy of freeCodeCamp mobile repo. Your folder structure should look like this: +1. Clone a copy of the [freeCodeCamp repo](https://github.com/freeCodeCamp/freeCodeCamp) locally outside of your local copy of the freeCodeCamp mobile repo. Your folder structure should look like this: ```console ├── freeCodeCamp ├── mobile ``` -2. Change directory to the freeCodeCamp repo: +2. Change the directory to the freeCodeCamp repo: ```console cd freeCodeCamp @@ -480,7 +480,7 @@ If you are on a different OS and/or are still running into issues, see [getting ### Issues with the UI, build errors, etc. -If you face issues with the UI, or builds errors a cleanup can be useful: +If you face issues with the UI, or build errors a cleanup can be useful: ```console flutter clean @@ -488,7 +488,7 @@ flutter clean ### Issues Installing Dependencies -If you get errors while installing the dependencies, please make sure that you are not in a restricted network or your firewall settings do not prevent you from accessing resources. +If you get errors while installing the dependencies, please make sure that you are not in a restricted network or that your firewall settings do not prevent you from accessing resources. Be patient as the first-time setup can take a while depending on your network bandwidth. diff --git a/docs/i18n/japanese/how-to-setup-wsl.md b/docs/i18n/japanese/how-to-setup-wsl.md index 8be500abc73..0777f99233e 100644 --- a/docs/i18n/japanese/how-to-setup-wsl.md +++ b/docs/i18n/japanese/how-to-setup-wsl.md @@ -123,7 +123,7 @@ Now that you have installed the pre-requisites, follow [our local setup guide](h > [!WARNING] > -> Please note, at this time the setup for Cypress tests (and related GUI needs) are a work in progress. それでも、ほとんどのコードベースで作業できるはずです。 +> Please note, at this time the setup for Cypress tests (and related GUI needs) is a work in progress. それでも、ほとんどのコードベースで作業できるはずです。 ## 有用なリンク diff --git a/docs/i18n/japanese/how-to-use-docker-on-windows-home.md b/docs/i18n/japanese/how-to-use-docker-on-windows-home.md index 894849be357..78d905c0c2c 100644 --- a/docs/i18n/japanese/how-to-use-docker-on-windows-home.md +++ b/docs/i18n/japanese/how-to-use-docker-on-windows-home.md @@ -2,7 +2,7 @@ Windows Home で Docker を設定する際に避けるべき落とし穴がいくつかあります。 まず、[Docker Toolbox](https://docs.docker.com/toolbox/toolbox_install_windows/) を管理者として使用する必要があります。 残念ながら、Windows Home は Docker for Windows Desktop をサポートしていないため、代わりに Toolbox を使用する必要があります。 インストールでシンボリックリンクを使用するため、管理者として実行する必要があります。 -Toolbox をインストールしたら、管理者として Docker Quickstart Terminal を実行します。 既存の仮想マシンが存在しない場合は、`default` 仮想マシンが作成されます その後、ターミナルを閉じて (再び管理者として) VirtualBoxを開きます。 `default` マシンが表示されます。 サイトはかなりリソースが多いので、仮想マシンを停止し、できるだけメモリの容量を増やしてください。 4GBの RAM で動作することが確認されています。 +Toolbox をインストールしたら、管理者として Docker Quickstart Terminal を実行します。 既存の仮想マシンが存在しない場合は、`default` 仮想マシンが作成されます その後、ターミナルを閉じて (再び管理者として) VirtualBoxを開きます。 `default` マシンが表示されます。 サイトはかなりリソースが多いので、仮想マシンを停止し、できるだけメモリの容量を増やしてください。 It has been confirmed to work with 4GB of RAM. Docker が正常に動作していることを確認したら、freeCodeCamp リポジトリを `C:\Users` 内のディレクトリにクローンします。 これらのディレクトリは共有され、インストール中に必要なローカルディレクトリに Docker アクセスを提供します。 diff --git a/docs/i18n/japanese/how-to-work-on-coding-challenges.md b/docs/i18n/japanese/how-to-work-on-coding-challenges.md index ddb36a3dd66..d75ce0e093f 100644 --- a/docs/i18n/japanese/how-to-work-on-coding-challenges.md +++ b/docs/i18n/japanese/how-to-work-on-coding-challenges.md @@ -4,7 +4,7 @@ インタラクティブなコーディングチャレンジの設計は難しいです。 長い説明を書いたり、ビデオチュートリアルを作成したりする方がはるかに簡単です。 しかし、私たちのコアカリキュラムは、多くの人にとって最適なものに固執しています。完全にインタラクティブでビデオゲームのような体験です。 -私たちはキャンパーにフロー状態を体験してほしいのです。 勢いをつけて大きな支障なくカリキュラムを突破してほしいと思っています。 自信を持ってプロジェクトに参加し、プログラミングの概念に広く触れてほしいと考えています。 +私たちはキャンパーにフロー状態を体験してほしいのです。 勢いをつけて大きな支障なくカリキュラムを突破してほしいと思っています。 We want them to go into the projects with confidence and gain wide exposure to programming concepts. freeCodeCamp カリキュラムのバージョン 7.0 では、[多くの繰り返しを伴うプロジェクトに焦点を当てたモデル](https://www.freecodecamp.org/news/python-curriculum-is-live/) に移行しています。 @@ -554,7 +554,7 @@ b c ``` -And you choose `b`, your new order will be: +If you choose `b`, your new order will be: ```bash a diff --git a/docs/i18n/japanese/how-to-work-on-localized-client-webapp.md b/docs/i18n/japanese/how-to-work-on-localized-client-webapp.md index 22e0b2fd566..81577cdd4fa 100644 --- a/docs/i18n/japanese/how-to-work-on-localized-client-webapp.md +++ b/docs/i18n/japanese/how-to-work-on-localized-client-webapp.md @@ -8,13 +8,13 @@ Once you have set up the project locally you should be able to follow this docum これは、ローカライゼーションを含むものを対象にし、例えば別の言語でボタンラベルを検証する必要がある機能に関して作業している場合に役立ちます。 -> [!TIP] freeCodeCamp のカリキュラムやコントリビューションドキュメントを翻訳するために、このドキュメントに従う必要はありません。 代わりに、[このガイド](how-to-translate-files.md) をお読みください。 +> [!TIP] You do not need to follow this document to translate freeCodeCamp's curriculum or contributing documentation. 代わりに、[このガイド](how-to-translate-files.md) をお読みください。 i18n フレームワークとツールがどのように機能するかを理解しましょう。 ## ファイル構成 -Most of the files for translating the platform are located in the [`client/i18n`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/client/i18n) folder. 各言語には、翻訳付きの JSON ファイルを含むディレクトリがあります。 +Most of the files for translating the platform are located in the [`client/i18n`](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/client/i18n) folder. Each language has a directory that contains JSON files with the translations. ```console config @@ -55,7 +55,7 @@ Most of the files for translating the platform are located in the [`client/i18n` └── validate-keys.ts ``` -Some of these files are translated on our translation platform (Crowdin) and some are translated or created via PR's on GitHub. +Some of these files are translated on our translation platform (Crowdin) and some are translated or created via PRs on GitHub. **翻訳プラットフォーム上で翻訳されたファイル:** diff --git a/docs/i18n/japanese/how-to-work-on-practice-projects.md b/docs/i18n/japanese/how-to-work-on-practice-projects.md index d5f913de8ee..c62354b6e41 100644 --- a/docs/i18n/japanese/how-to-work-on-practice-projects.md +++ b/docs/i18n/japanese/how-to-work-on-practice-projects.md @@ -38,7 +38,7 @@ Clicking this button will add a new step at the end of the project. This step wi #### Create Empty Steps -Enter the number of steps you want to add in the input. Then, clicking the button will create that many empty steps at the end of the project. +Enter the number of steps you want to add in the input. Then, clicking the button will create many empty steps at the end of the project. #### Insert Step @@ -124,7 +124,7 @@ pnpm run delete-step X # where X is the step number to be deleted. ### update-step-titles -A one-off script that automatically updates the frontmatter in a project's markdown files so that they are consistent with the project's meta.json. It ensures that each step's title (and dashedName) match the meta's challengeOrder. +A one-off script that automatically updates the frontmatter in a project's markdown files so that they are consistent with the project's meta.json. It ensures that each step's title (and dashedName) matches the meta's `challengeOrder`. #### How to Run the Script diff --git a/docs/i18n/japanese/how-to-work-on-tutorials-that-use-coderoad.md b/docs/i18n/japanese/how-to-work-on-tutorials-that-use-coderoad.md index 2ed60c22bac..86039f04bd2 100644 --- a/docs/i18n/japanese/how-to-work-on-tutorials-that-use-coderoad.md +++ b/docs/i18n/japanese/how-to-work-on-tutorials-that-use-coderoad.md @@ -56,7 +56,7 @@ Each of the freeCodeCamp tutorials that use CodeRoad has its own repo under the - [rdb-alpha repo](https://github.com/freeCodeCamp/rdb-alpha) の手順に従ってコンテナを実行します。 - 新しいブランチの `tutorial.json` ファイルを使用してチュートリアルを開始します。 -### `main` の PR をレビューする +### Reviewing PRs to `main` 上述のように、指示もしくは文法問題に関わる `main` のみを変更する PR をレビューする場合、`TUTORIAL.md` の変更は、`tutorial.json` の変更と一致する必要があります。 @@ -119,11 +119,11 @@ freeCodeCamp リポジトリへの書き込みアクセス権を有しており - freeCodeCamp リポジトリで `main` にPRを作成します。 - 問題がない場合は、それをマージするか残して、レビューを依頼します。 - PR がマージされた後、[rdb-alpha repo](https://github.com/freeCodeCamp/rdb-alpha) の指示に従ってチュートリアルを開き、正しく読み込まれていることと、いくつかのステップが実行できることを確認します。 -- 最後に、このバージョンの PR が存在する場合は、それらをクローズします。 +- Finally, if any PRs for this version exist, close them ### How to Revert to a Previous Version -- `git checkout -b revert/to-version-X.X.X` で、最新 `main` の新しいブランチを作成します。 +- Create a new branch off of the latest `main` with `git checkout -b revert/to-version-X.X.X` - このブランチにおいて、元に戻したいバージョン以降のコミットをすべて元に戻します。 例えば、次のようなコミットです。 ``` diff --git a/docs/i18n/japanese/language-lead-handbook.md b/docs/i18n/japanese/language-lead-handbook.md index 5ad785ce3fe..113564728ba 100644 --- a/docs/i18n/japanese/language-lead-handbook.md +++ b/docs/i18n/japanese/language-lead-handbook.md @@ -339,7 +339,7 @@ In Crowdin, individuate the `User management` on the left-hand side menu. This will open the user management tools, you will be able to see the list of all the users. -Search for the user that will become a proofreader. Use the three dots menu on the user row to open a menu and select "Add to team". The proofreader teams have a standard name of `Proof Readers ()`, you can search the team using the language name. Once you have selected the team, use the "ADD" button at the bottom of the page to finalize the thing. +Search for the user who will become a proofreader. Use the three dots menu on the user row to open a menu and select "Add to team". The proofreader teams have a standard name of `Proof Readers ()`, you can search the team using the language name. Once you have selected the team, use the "ADD" button at the bottom of the page to finalize the thing. The user is now a proofreader. diff --git a/docs/i18n/japanese/moderator-handbook.md b/docs/i18n/japanese/moderator-handbook.md index ab7b465fc35..032be8c3dd3 100644 --- a/docs/i18n/japanese/moderator-handbook.md +++ b/docs/i18n/japanese/moderator-handbook.md @@ -18,7 +18,7 @@ freeCodeCamp は包括的なコミュニティであり、それを維持する We have a single [Code of Conduct](https://code-of-conduct.freecodecamp.org) that governs our entire community. ルールは少ないほど、覚えやすいものです。 [こちら](https://code-of-conduct.freecodecamp.org) にあるルールを読み、記憶に留めておいてください。 -> [!NOTE] As a moderator, we would add you to one or more teams on GitHub, our community forums & 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). +> [!NOTE] As a moderator, we would add you to one or more teams on GitHub, our community forums & chat servers. If you are missing access to a platform that you would like to moderate, please [reach out to a staff member](FAQ.md#additional-assistance). ## GitHub をモデレートする @@ -164,7 +164,7 @@ As a moderator, you help keep our community an enjoyable place for anyone to lea Note that once you are a moderator on the forum, you will start to see blue moderator hints about forum members, like "this is the first time [person] has posted - let's welcome them to the community!" or "[person] hasn't posted in a long time - let's welcome them back." -![A blue text message saying "this is the first time [person] has posted - let's welcome them to the community!](https://i.imgur.com/mPmVgzK.png) +![A blue text message saying "This is the first time [person] has posted - let's welcome them to the community!](https://i.imgur.com/mPmVgzK.png) These are opportunities for you to welcome them and make them feel extra special. You never know which person who's marginally involved may become our next super-helper, helping many other people in their coding journey. Even the slightest kindness may trigger a cascade of good deeds. diff --git a/docs/i18n/japanese/reply-templates.md b/docs/i18n/japanese/reply-templates.md index a1a9bbcc41c..d5c5110346b 100644 --- a/docs/i18n/japanese/reply-templates.md +++ b/docs/i18n/japanese/reply-templates.md @@ -183,7 +183,7 @@ If the forum members determine there is nothing wrong with your code, you can re Thank you and happy coding. ``` -> When an issue is duplicate of an earlier issue. +> When an issue is a duplicate of an earlier issue. ```markdown Thank you for reporting this issue. @@ -230,7 +230,7 @@ Happy contributing. ```md We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. -Issues labelled with `help wanted` or `first timers only` are open for contributions. +Issues labeled with `help wanted` or `first timers only` are open for contributions. Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. ``` diff --git a/docs/i18n/japanese/troubleshooting-development-issues.md b/docs/i18n/japanese/troubleshooting-development-issues.md index 84569c6fbf7..962fd04362c 100644 --- a/docs/i18n/japanese/troubleshooting-development-issues.md +++ b/docs/i18n/japanese/troubleshooting-development-issues.md @@ -31,7 +31,7 @@ Use the shortcut pnpm run clean-and-develop ``` -If you continue to face issues with the build, cleaning up the workspace is recommend. +If you continue to face issues with the build, cleaning up the workspace is recommended. Use `git clean` in interactive mode: @@ -50,7 +50,7 @@ git clean -ifdX ## Issues with API, login, Challenge Submissions, etc. -If you can't sign in, and instead you see a banner with an error message that it will be reported to freeCodeCamp, please double-check that your local port `3000` is not in use by a different program. +If you can't sign in, and instead you see a banner with an error message saying that the error will be reported to freeCodeCamp, please double-check that your local port `3000` is not in use by a different program. #### **From Terminal:** ```console diff --git a/docs/i18n/portuguese/authors-analytics-manual.md b/docs/i18n/portuguese/authors-analytics-manual.md index 10d616e762c..d97dbfbe4d4 100644 --- a/docs/i18n/portuguese/authors-analytics-manual.md +++ b/docs/i18n/portuguese/authors-analytics-manual.md @@ -1,10 +1,10 @@ # Manual de análise dos autores -Se você é um autor com acesso à Propriedade do Google Analytics da publicação (editorial), pode usar este guia para visualizar o engajamento de seus artigos e pesquisar artigos no idioma da publicação. +Se você é um autor com acesso à Propriedade do Google Analytics da publicação (editorial), pode usar este guia para visualizar o engajamento do seu artigo e pesquisar artigos no idioma da publicação. ## Pesquisar por idioma -Para procurar relatórios de engajamento por um idioma específico: +Para procurar relatórios de engajamento em um idioma específico: ![Imagem - Mostrar etapas para pesquisar por idioma no Google Analytics](https://contribute.freecodecamp.org/images/google-analytics/search-by-language.png) diff --git a/docs/i18n/portuguese/how-to-enable-new-languages.md b/docs/i18n/portuguese/how-to-enable-new-languages.md index 71229b3671c..43c8f756c22 100644 --- a/docs/i18n/portuguese/how-to-enable-new-languages.md +++ b/docs/i18n/portuguese/how-to-enable-new-languages.md @@ -229,7 +229,7 @@ Você não precisa ter tudo nestes 3 arquivos traduzidos no começo. É possíve Você pode substituir qualquer URL que tenha páginas correspondentes prontas no seu idioma. -Por exemplo, se você tiver a publicação no seu idioma, você pode substituir o URL para `"news"`. Se quiser traduzir artigos listados nos links de rodapé, consulte [Como traduzir artigos nos links de rodapé](language-lead-handbook.md#how-to-translate-articles-in-the-footer-links). +Por exemplo, se você tiver uma publicação no seu idioma, você pode substituir o URL para `"news"`. Se quiser traduzir artigos listados nos links de rodapé, consulte [Como traduzir artigos nos links de rodapé](language-lead-handbook.md#how-to-translate-articles-in-the-footer-links). #### `meta-tags.json` diff --git a/docs/i18n/portuguese/how-to-help-with-video-challenges.md b/docs/i18n/portuguese/how-to-help-with-video-challenges.md index 0d347002da0..ee73876c8c4 100644 --- a/docs/i18n/portuguese/how-to-help-with-video-challenges.md +++ b/docs/i18n/portuguese/how-to-help-with-video-challenges.md @@ -125,7 +125,7 @@ Adicione/atualize o texto da pergunta sob a parte que diz: ## --text-- ``` -Adicione/Atualize (`Answer 1`, `Answer 2`, e assim por diante) sob `## --answers--`. Confirme se o número sob `## --video-solution--` seja o número da resposta correta. Você pode adicionar mais respostas possíveis usando o mesmo formato. Tanto a pergunta quanto as respostas podem estar entre aspas. +Adicione/Atualize (`Answer 1`, `Answer 2`, e assim por diante) sob `## --answers--`. Confirme se o número sob `## --video-solution--` seja o número da resposta correta. Você pode adicionar mais respostas possíveis usando o mesmo formato. Tanto as perguntas quanto as respostas podem estar entre aspas. ### Exemplos de perguntas 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 837596a395d..393b18e3e76 100644 --- a/docs/i18n/portuguese/how-to-open-a-pull-request.md +++ b/docs/i18n/portuguese/how-to-open-a-pull-request.md @@ -140,7 +140,7 @@ Quando se está trabalhando em erros normais e funcionalidades no seu branch `ma ### Para o próximo currículo e próximas funcionalidades -Quando você estiver trabalhando em funcionalidades para nossos próximos branches `next-*` de currículo, você tem que fazer um cherry pick: +Quando você estiver trabalhando em funcionalidades para nossos próximos branches `next-*` de currículo, você tem que fazer um `cherry-pick`: 1. Certifique-se de que seu upstream esteja sincronizado com seu local: @@ -169,7 +169,7 @@ Quando você estiver trabalhando em funcionalidades para nossos próximos branch git branch -D ``` - b. Ou apenas faça um backup do seu branch de pr (se você não o tem localmente): + b. Ou apenas faça um backup do seu branch de PR (se você não o tem localmente): ```console git checkout -b origin/ diff --git a/docs/i18n/portuguese/how-to-proofread-files.md b/docs/i18n/portuguese/how-to-proofread-files.md index 77a584a603a..b1309a888d5 100644 --- a/docs/i18n/portuguese/how-to-proofread-files.md +++ b/docs/i18n/portuguese/how-to-proofread-files.md @@ -2,7 +2,7 @@ Nossa equipe de revisão é responsável por garantir que as traduções reflitam com exatidão o texto original. Confiamos em nossos revisores para que tenhamos traduções de alta qualidade. -Todas as nossas traduções são feitas a mão, por humanos reais. A revisão mantém um tom consistente em todos os nossos recursos traduzidos, como o currículo. +Todas as nossas traduções são feitas a mão, por humanos reais. A revisão mantém um tom consistente em todos os recursos traduzidos, como o currículo. Para iniciar a revisão, visite [nossa plataforma de tradução](https://translate.freecodecamp.org) e faça o login. Selecione "Go to console" na barra de navegação superior para mudar da visualização pública para a visualização do espaço de trabalho. diff --git a/docs/i18n/portuguese/how-to-setup-wsl.md b/docs/i18n/portuguese/how-to-setup-wsl.md index 1bf53ec2e25..aaa3d6577aa 100644 --- a/docs/i18n/portuguese/how-to-setup-wsl.md +++ b/docs/i18n/portuguese/how-to-setup-wsl.md @@ -123,7 +123,7 @@ Agora que você instalou os pré-requisitos, siga [nosso guia de instalação lo > [!WARNING] > -> Por favor note que, neste momento, a configuração para testes do Cypress (e necessidades relacionadas à GUI) são um trabalho em andamento. Você ainda deve ser capaz de trabalhar na maior parte do código. +> Por favor note que, neste momento, a configuração para testes do Cypress (e necessidades relacionadas à GUI) é um trabalho em andamento. Você ainda deve ser capaz de trabalhar na maior parte do código. ## Links Úteis 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 cfc58274399..2e933957c1c 100644 --- a/docs/i18n/portuguese/how-to-work-on-coding-challenges.md +++ b/docs/i18n/portuguese/how-to-work-on-coding-challenges.md @@ -463,13 +463,13 @@ Antes de [criar um pull request](how-to-open-a-pull-request.md) para suas modifi pnpm run test:curriculum ``` -2. To test single challenge, you can use it challenge id with following command +2. Para testar um único desafio, você pode usar o id do desafio com o seguinte comando ``` FCC_CHALLENGE_ID=646cf6cbca98e258da65c979 pnpm run test:curriculum ``` -3. You can also test a block or a superblock of challenges with these commands +3. Você também pode testar um bloco ou superbloco de desafios com esses comandos ``` FCC_BLOCK='Basic HTML and HTML5' pnpm run test:curriculum @@ -479,43 +479,43 @@ FCC_BLOCK='Basic HTML and HTML5' pnpm run test:curriculum FCC_SUPERBLOCK='responsive-web-design' pnpm run test:curriculum ``` -You are also able to test challenges by title by performing the following steps: +Você também pode testar desafios por título utilizando as seguintes etapas: -1. Switch to the `curriculum` directory: +1. Mude para o diretório `curriculum`: ``` cd curriculum ``` -2. Run the following for each challenge file for which you have changed (replacing `challenge-title-goes-here` with the full title of the challenge): +2. Execute o comando a seguir para cada arquivo de desafio no qual você fez alteraçõess (substituindo `challenge-title-goes-here` com o título completo do desafio): ``` - pnpm run test -- -g challenge-title-goes-here + pnpm run test -- -g titulo-do-desafio-aqui ``` > [!TIP] -> You can set the environment variable `LOCALE` in the `.env` to the language of the challenge(s) you need to test. +> Você pode definir a váriavel de ambiente `LOCALE` no arquivo `.env` para o idioma do(s) desafio(s) que você precisa testar. > -> The currently accepted values are `english` and `chinese`, with `english` being set by default. +> Os valores aceitos de momento são `english` e `chinese`, com `english` sendo o valor padrão. -## Proposing a Pull Request (PR) +## Propondo um Pull Request (PR) -After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). +Depois de fazer o commit de suas alterações, confira aqui [como abrir um Pull Request](how-to-open-a-pull-request.md). -## Useful Links +## Links úteis -Creating and Editing Challenges: +Criação e edição de desafios: -1. [Challenge types](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/client/utils/challenge-types.js#L1-L13) - what the numeric challenge type values mean (enum). +1. [Tipos de desafio](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/client/utils/challenge-types.js#L1-L13) - o que significam os valores do tipo de desafio numérico (enum). -2. [Contributing to FreeCodeCamp - Writing ES6 Challenge Tests](https://www.youtube.com/watch?v=iOdD84OSfAE#t=2h49m55s) - a video following [Ethan Arrowood](https://twitter.com/ArrowoodTech) as he contributes to the old version of the curriculum. +2. [Contribuindo para o FreeCodeCamp - Escrevendo testes para desafios de ES6](https://www.youtube.com/watch?v=iOdD84OSfAE#t=2h49m55s) - um vídeo que acompanha [Ethan Arrowood](https://twitter.com/ArrowoodTech) durante sua contribuição para a versão antiga do currículo. -## Helper Scripts +## Scripts auxiliares > [!NOTE] -> If you are working with the step-based challenges, refer to the [Work on Practice Projects](how-to-work-on-practice-projects.md) section. +> Se estiver trabalhando com os desafios baseados em passos, consulte a seção [Trabalho com projetos práticos](how-to-work-on-practice-projects.md). -There are a few helper scripts that can be used to manage the challenges in a block. Note that these commands should all be run in the block directory. For example: +Existem alguns scripts auxiliares que podem ser usados para gerenciar os desafios em um bloco. Observe que todos esses comandos devem ser executados no diretório do bloco. Por exemplo: ```bash cd curriculum/challenges/english/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting @@ -523,33 +523,33 @@ cd curriculum/challenges/english/02-javascript-algorithms-and-data-structures/ba ### Adicionar um novo desafio -To add a new challenge at the end of a block, call the script: +Para adicionar um novo desafio no final de um bloco, chame o script: ```bash pnpm run create-next-challenge ``` -This will prompt you for the challenge information and create the challenge file, updating the `meta.json` file with the new challenge information. +Ele solicitará a informação do desafio e criará o arquivo de desafio, atualizando o arquivo `meta.json` com as novas informações de desafio. ### Excluir um desafio -To delete a challenge, call the script: +Para excluir um desafio, chame o script: ```bash pnpm run delete-challenge ``` -This will prompt you to select which challenge should be deleted, then delete the file and update the `meta.json` file to remove the challenge from the order. +Ele solicitará que você selecione qual desafio deve ser excluído. Em seguida, excluirá o arquivo e atualizará o arquivo `meta.json` para remover o desafio da ordem. ### Inserir um desafio -To insert a challenge before an existing challenge, call the script: +Para inserir um desafio antes de um desafio existente, chame o script: ```bash pnpm run insert-challenge ``` -This will prompt you for the challenge information, then for the challenge to insert before. For example, if your choices are: +Ele solicitará a informação do desafio e, em seguida, o desafio será inserido antes do desafio informado. Por exemplo, se suas escolhas forem: ```bash a @@ -557,37 +557,37 @@ b c ``` -And you choose `b`, your new order will be: +Se você escolher `b`, a nova ordem será: ```bash a -new challenge +novo desafio b c ``` ### Atualizar a ordem dos desafios -If you need to manually re-order the challenges, call the script: +Se você precisar reordenar manualmente os desafios, chame o script: ```bash pnpm run update-challenge-order ``` -This will take you through an interactive process to select the order of the challenges. +Ele vai orientá-lo através de um processo interativo para selecionar a ordem dos desafios. ## Solução de problemas ### Loop infinito detectado -If you see the following error in the console while previewing a challenge: +Se você ver o seguinte erro no console ao pré-visualizar um desafio: ```text Potential infinite loop detected on line ... ``` -This means that the loop-protect plugin has found a long-running loop or recursive function. If your challenge needs to do that (e.g. it contains an event loop that is supposed to run indefinitely), then you can prevent the plugin from being used in the preview. To do so, add `disableLoopProtectPreview: true` to the block's `meta.json` file. +Isso significa que o plug-in de proteção de loops encontrou um loop de longa duração ou uma função recursiva. Se o desafio precisar fazer isso (por exemplo, contém um loop de eventos que deve ser executado indefinidamente), então você pode impedir que o plug-in seja usado na visualização. Para fazer isso, adicione `disableLoopProtectPreview: true` ao arquivo `meta.json` do bloco. -If your tests are computationally intensive, then you may see this error when they run. If this happens then you can add `disableLoopProtectTests: true` to the block's `meta.json` file. +Se os testes demandam muitos cálculos, você poderá ver esse erro quando eles forem executados. Se isso acontecer, adicione `disableLoopProtectPreview: true` ao arquivo `meta.json` do bloco. -It's not typically necessary to have both set to true, so only set them as needed. +Normalmente, não é necessário ter os dois definidos como true, Defina-os, apenas, conforme necessário. 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 1104c1818c9..e28588e0829 100644 --- a/docs/i18n/portuguese/how-to-work-on-practice-projects.md +++ b/docs/i18n/portuguese/how-to-work-on-practice-projects.md @@ -124,7 +124,7 @@ pnpm run delete-step X #, onde X é o número do passo a ser excluído. ### update-step-titles -Um script único que atualiza automaticamente a frontmatter nos arquivos markdown de um projeto para que eles sejam consistentes com o meta.json do projeto. Garante que o título de cada passo (e seu dashedName) correspondam ao challengeOrder do arquivo meta. +Um script único que atualiza automaticamente a frontmatter nos arquivos markdown de um projeto para que eles sejam consistentes com o meta.json do projeto. Garante que o título de cada passo (e seu dashedName) corresponda ao `challengeOrder` do arquivo meta. #### Como executar o script diff --git a/docs/i18n/portuguese/moderator-handbook.md b/docs/i18n/portuguese/moderator-handbook.md index 0350daa7192..81f8cc6a4c9 100644 --- a/docs/i18n/portuguese/moderator-handbook.md +++ b/docs/i18n/portuguese/moderator-handbook.md @@ -164,7 +164,7 @@ Como moderador, você ajuda a manter nossa comunidade um lugar agradável para q Note que, ao se tornar um moderador no fórum, você vai começar a ver dicas azuis sobre os membros do fórum, como "esta é a primeira vez que [person] postou - vamos dar as boas-vindas à comunidade!" ou "[person] não postou há muito tempo - vamos recebê-lo de volta." -![Uma mensagem de texto azul dizendo "esta é a primeira vez que [person] postou - vamos dar as boas-vindas à comunidade!](https://i.imgur.com/mPmVgzK.png) +![Uma mensagem de texto azul dizendo "Esta é a primeira vez que [person] postou - vamos dar as boas-vindas à comunidade!](https://i.imgur.com/mPmVgzK.png) São oportunidades para você recebê-lo(a) e fazê-lo(a) sentir-se mais especial. Nunca se sabe quais pessoas que estão pouco envolvidas e que podem ser nossos próximos superajudantes, ajudando muitas outras pessoas na sua jornada de programação. Mesmo a menor bondade pode desencadear várias boas ações. diff --git a/docs/i18n/portuguese/reply-templates.md b/docs/i18n/portuguese/reply-templates.md index 36f1ffca4c9..de90619e4e9 100644 --- a/docs/i18n/portuguese/reply-templates.md +++ b/docs/i18n/portuguese/reply-templates.md @@ -230,7 +230,7 @@ Happy contributing. ```md We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. -Issues labelled with `help wanted` or `first timers only` are open for contributions. +Issues labeled with `help wanted` or `first timers only` are open for contributions. Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. ``` diff --git a/docs/i18n/portuguese/troubleshooting-development-issues.md b/docs/i18n/portuguese/troubleshooting-development-issues.md index 7285df2608b..412073c1799 100644 --- a/docs/i18n/portuguese/troubleshooting-development-issues.md +++ b/docs/i18n/portuguese/troubleshooting-development-issues.md @@ -50,7 +50,7 @@ git clean -ifdX ## Problemas com API, login, envio de desafios, etc. -Se você não conseguir fazer o login e se vir um banner com uma mensagem de erro dizendo que isso será reportado ao freeCodeCamp, verifique novamente se a porta local `3000` não está em uso por um programa diferente. +Se você não conseguir fazer o login e se vir um banner com uma mensagem de erro dizendo que o erro será reportado ao freeCodeCamp, verifique novamente se a porta local `3000` não está em uso por um programa diferente. #### **A partir do Terminal:** ```console diff --git a/docs/i18n/ukrainian/how-to-open-a-pull-request.md b/docs/i18n/ukrainian/how-to-open-a-pull-request.md index 07c191c614c..d813640b3cc 100644 --- a/docs/i18n/ukrainian/how-to-open-a-pull-request.md +++ b/docs/i18n/ukrainian/how-to-open-a-pull-request.md @@ -140,7 +140,7 @@ ### Майбутня навчальна програма та функціональності -Коли ви працюєте над функціональностями для майбутньої навчальної програми на гілках `next-*`, потрібно виконати команду cherry pick: +Коли ви працюєте над функціональностями для майбутньої навчальної програми на гілках `next-*`, потрібно виконати команду `cherry-pick`: 1. Переконайтесь, що upstream синхронізовано з локальною гілкою: diff --git a/docs/i18n/ukrainian/how-to-work-on-coding-challenges.md b/docs/i18n/ukrainian/how-to-work-on-coding-challenges.md index 1a59c5c058c..903e038bdcf 100644 --- a/docs/i18n/ukrainian/how-to-work-on-coding-challenges.md +++ b/docs/i18n/ukrainian/how-to-work-on-coding-challenges.md @@ -460,13 +460,13 @@ function myFunc() { pnpm run test:curriculum ``` -2. To test single challenge, you can use it challenge id with following command +2. Щоб перевірити окреме завдання, використайте його id з цією командою ``` FCC_CHALLENGE_ID=646cf6cbca98e258da65c979 pnpm run test:curriculum ``` -3. You can also test a block or a superblock of challenges with these commands +3. Ви можете перевірити блок або суперблок завдань за допомогою цих команд ``` FCC_BLOCK='Basic HTML and HTML5' pnpm run test:curriculum @@ -476,43 +476,43 @@ FCC_BLOCK='Basic HTML and HTML5' pnpm run test:curriculum FCC_SUPERBLOCK='responsive-web-design' pnpm run test:curriculum ``` -You are also able to test challenges by title by performing the following steps: +Ви також можете перевірити завдання за заголовками, виконавши такі кроки: -1. Switch to the `curriculum` directory: +1. Перейдіть до каталогу `curriculum`: ``` cd curriculum ``` -2. Run the following for each challenge file for which you have changed (replacing `challenge-title-goes-here` with the full title of the challenge): +2. Виконайте цю команду для кожного файлу завдання, до якого ви внесли зміни (замінивши `challenge-title-goes-here` на повну назву завдання): ``` pnpm run test -- -g challenge-title-goes-here ``` > [!TIP] -> You can set the environment variable `LOCALE` in the `.env` to the language of the challenge(s) you need to test. +> Ви можете встановити змінну середовища `LOCALE` у `.env` на мову завдань, які потрібно протестувати. > -> The currently accepted values are `english` and `chinese`, with `english` being set by default. +> Наразі прийнятними значеннями є `english` та `chinese` (`english` за замовчуванням). -## Proposing a Pull Request (PR) +## Відкриття запиту на злиття (PR) -After you've committed your changes, check here for [how to open a Pull Request](how-to-open-a-pull-request.md). +Як тільки ви затвердили свої зміни, див. [як відкрити запит на злиття](how-to-open-a-pull-request.md). -## Useful Links +## Корисні посилання -Creating and Editing Challenges: +Створення та редагування завдань: -1. [Challenge types](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/client/utils/challenge-types.js#L1-L13) - what the numeric challenge type values mean (enum). +1. [Види завдань](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/client/utils/challenge-types.js#L1-L13) — що означають числові значення завдань (перелік). -2. [Contributing to FreeCodeCamp - Writing ES6 Challenge Tests](https://www.youtube.com/watch?v=iOdD84OSfAE#t=2h49m55s) - a video following [Ethan Arrowood](https://twitter.com/ArrowoodTech) as he contributes to the old version of the curriculum. +2. [Внесок до FreeCodeCamp: написання тестів до завдань ES6](https://www.youtube.com/watch?v=iOdD84OSfAE#t=2h49m55s) — відео [Ітана Арровуда](https://twitter.com/ArrowoodTech) про його внесок до старої версії навчальної програми. -## Helper Scripts +## Допоміжні скрипти > [!NOTE] -> If you are working with the step-based challenges, refer to the [Work on Practice Projects](how-to-work-on-practice-projects.md) section. +> Якщо ви працюєте над покроковими завданнями, див. розділ щодо [роботи над практичними проєктами](how-to-work-on-practice-projects.md). -There are a few helper scripts that can be used to manage the challenges in a block. Note that these commands should all be run in the block directory. For example: +Існує декілька допоміжних скриптів, які можна використовувати для завдань у блоці. Зверніть увагу, що ці команди потрібно виконувати у каталозі блоків. Наприклад: ```bash cd curriculum/challenges/english/02-javascript-algorithms-and-data-structures/basic-algorithm-scripting @@ -520,33 +520,33 @@ cd curriculum/challenges/english/02-javascript-algorithms-and-data-structures/ba ### Додати нове завдання -To add a new challenge at the end of a block, call the script: +Щоб додати нове завдання в кінці блоку, викличте скрипт: ```bash pnpm run create-next-challenge ``` -This will prompt you for the challenge information and create the challenge file, updating the `meta.json` file with the new challenge information. +Це допоможе отримати інформацію про завдання та створити файл з завданням, оновивши файл `meta.json` новою інформацією про завдання. ### Видалити завдання -To delete a challenge, call the script: +Щоб видалити завдання, викличте скрипт: ```bash pnpm run delete-challenge ``` -This will prompt you to select which challenge should be deleted, then delete the file and update the `meta.json` file to remove the challenge from the order. +Це допоможе обрати потрібне завдання, видалити файл та оновити файл `meta.json`, щоб видалити завдання з порядку. ### Вставити завдання -To insert a challenge before an existing challenge, call the script: +Щоб вставити завдання перед наявним завданням, викличте скрипт: ```bash pnpm run insert-challenge ``` -This will prompt you for the challenge information, then for the challenge to insert before. For example, if your choices are: +Це допоможе отримати інформацію про нове завдання, а також про наявне завдання. Наприклад, якщо варіанти такі: ```bash a @@ -554,7 +554,7 @@ b c ``` -And you choose `b`, your new order will be: +Якщо оберете `b`, то новим порядком буде: ```bash a @@ -565,26 +565,26 @@ c ### Оновити порядок завдань -If you need to manually re-order the challenges, call the script: +Якщо вам потрібно змінити порядок завдань вручну, викличте скрипт: ```bash pnpm run update-challenge-order ``` -This will take you through an interactive process to select the order of the challenges. +Він проведе вас через інтерактивний процес, який допоможе впорядкувати завдання. ## Розв’язання проблем розробки ### Виявлено нескінченний цикл -If you see the following error in the console while previewing a challenge: +Якщо ви бачите цю помилку в консолі під час попереднього перегляду завдання: ```text Potential infinite loop detected on line ... ``` -This means that the loop-protect plugin has found a long-running loop or recursive function. If your challenge needs to do that (e.g. it contains an event loop that is supposed to run indefinitely), then you can prevent the plugin from being used in the preview. To do so, add `disableLoopProtectPreview: true` to the block's `meta.json` file. +Це означає, що плагін для захисту циклу знайшов довгий цикл або рекурсивну функцію. Якщо ваше завдання передбачає їх (тобто містить нескінченний цикл), ви можете запобігти використанню плагіну в попередньому перегляді. Для цього додайте `disableLoopProtectPreview: true` до файлу блоку `meta.json`. -If your tests are computationally intensive, then you may see this error when they run. If this happens then you can add `disableLoopProtectTests: true` to the block's `meta.json` file. +Якщо ваші тести інтенсивно обчислюються, ви можете побачити цю помилку під час запуску. Якщо це відбувається, додайте `disableLoopProtectTests: true` до файлу блоку `meta.json`. -It's not typically necessary to have both set to true, so only set them as needed. +Значенням обох необов’язково має бути true, тому налаштовуйте їх лише за потреби. diff --git a/docs/i18n/ukrainian/how-to-work-on-practice-projects.md b/docs/i18n/ukrainian/how-to-work-on-practice-projects.md index 152244488a7..1aa4efd72ce 100644 --- a/docs/i18n/ukrainian/how-to-work-on-practice-projects.md +++ b/docs/i18n/ukrainian/how-to-work-on-practice-projects.md @@ -124,7 +124,7 @@ pnpm run delete-step X # де X є номером кроку, який потр ### update-step-titles -Це разовий скрипт, який автоматично оновлює початковий матеріал у файлах розмітки проєкту, щоб вони відповідали meta.json. Він гарантує, що заголовки кроків (та dashedName) відповідають challengeOrder. +Це разовий скрипт, який автоматично оновлює початковий матеріал у файлах розмітки проєкту, щоб вони відповідали meta.json. Він гарантує, що заголовки кроків (та dashedName) відповідають `challengeOrder`. #### Як запустити скрипт diff --git a/docs/i18n/ukrainian/reply-templates.md b/docs/i18n/ukrainian/reply-templates.md index ba7d53edb3e..27fe7a8889b 100644 --- a/docs/i18n/ukrainian/reply-templates.md +++ b/docs/i18n/ukrainian/reply-templates.md @@ -230,7 +230,7 @@ Happy contributing. ```md We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. -Issues labelled with `help wanted` or `first timers only` are open for contributions. +Issues labeled with `help wanted` or `first timers only` are open for contributions. Please make sure you read [our guidelines for contributing](https://contribute.freecodecamp.org/#/). We prioritize contributors following the instructions in our guide. Join us in [our chat room](https://discord.gg/PRyKn3Vbay) or [the forum](https://forum.freecodecamp.org/c/contributors/3) if you need help contributing - our community will be happy to assist you. ```