chore(i18n,docs): update translations (#42429)

docs/i18n/chinese/_sidebar.md

@@ -8,6 +8,7 @@
   - [Work on video challenges](how-to-help-with-video-challenges.md)
   - [Work on the news theme](how-to-work-on-the-news-theme.md)
   - [Work on the docs theme](how-to-work-on-the-docs-theme.md)
+  - [Work on practice projects](how-to-work-on-practice-projects.md)
 - **Translation Contribution**
   - [Work on translating resources](how-to-translate-files.md)
   - [Work on proofreading translations](how-to-proofread-files.md)

docs/i18n/chinese/how-to-work-on-coding-challenges.md

@@ -29,6 +29,9 @@ Before you work on the curriculum, you would need to set up some tooling to help
 
 - Edit the files on GitHub's interface by clicking the pencil icon for the corresponding file. While this is the quickest way, It is **not recommended**, because you are unable to test your changes on GitHub. If our maintainers conclude that the changes you made need to be tested locally, you would need to follow the methods above instead.
 
+### How to work on practice projects
+
+The practice projects have some additional tooling to help create new projects and steps.  To read more, see [these docs](how-to-work-on-practice-projects.md)
 ## Challenge Template
 
 ````md

docs/i18n/chinese/how-to-work-on-practice-projects.md

@@ -0,0 +1,123 @@
+# How to Work on Practice Projects
+
+The `tools/challenge-helper-scripts` folder contains tools to help facilitate the creation and maintenance of the freeCodeCamp project-based curriculum.
+
+## Create a new project
+
+Run `npm run create-project`. This opens up a command line ui that guides you through the process. Once that has finished, there should be a new challenge in the English curriculum that you can use for the first step of the project. For example, if you created a project called `test-project` in the Responsive Web Design certification, it would be in `curriculum/challenges/english/01-responsive-web-design/test-project`.
+
+If you want to create new steps, the following tools simplify that process.
+
+## create-next-step
+
+A one-off script that will automatically add the next step based on the last step numbered as `part-xxx.md` where `xxx` represents the 3-digit step number of the last step. The challenge seed code will use the previous step's challenge seed code with the editable region markers (ERMs) removed.
+
+**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps).
+
+### How to run script:
+
+1. Change to the directory of the project.
+2. Run the following npm command:
+
+```bash
+npm run create-next-step
+```
+
+## create-empty-steps
+
+A one-off script that automatically adds a specified number of steps at a specific starting step number. The challenge seed code for all steps created will be empty.
+
+**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps).
+
+### How to run script:
+
+1. Change to the directory of the project.
+2. Run the following npm command:
+
+```bash
+npm run create-empty-steps start=X num=Y # where X is the starting step number and Y is the number of steps to create.
+```
+
+## create-step-between
+
+A one-off script that automatically adds a new step between two existing consecutive steps. The challenge seed code will use the existing starting step's challenge seed code with the editable region markers (ERMs) removed.
+
+**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps).
+
+### How to run script:
+
+1. Change to the directory of the project.
+2. Run the following npm command:
+
+```bash
+npm run create-step-between start=X # where X is the starting step number
+```
+
+## delete-step
+
+A one-off script that deletes an existing step and then reorders the remaining step files in the project's folder as well as updates the `challengeOrder` property array in the project's `meta.json` with the new order of the steps.
+
+### How to run script
+
+1. Change to the directory of the project.
+2. Run the following npm command:
+
+```bash
+npm run delete-step num=x # where x is the step number to be deleted.
+```
+
+## reorder-steps
+
+A one-off script that automatically reorders the step files in a project's markdown files based on the filename. It also updates the `challengeOrder` property array in the project's `meta.json` with the new order of the steps.
+
+### Working Example
+
+Let's say you start with the following project structure:
+
+```bash
+part-1.md
+part-2.md
+part-3.md
+part-4.md
+part-5.md
+part-6.md
+```
+
+At some point you decide you need to delete `part-2.md`, because that step is no longer needed. Also, you decide to break down `part-4.md` into three steps instead of just one.
+
+To accomplish this restructure, you would need to delete `part-2.md` and then add a `part-4a.md` and a `part-5b.md`. The new folder structure would look like the following:
+
+```bash
+part-001.md
+part-003.md
+part-004.md
+part-004a.md
+part-004b.md
+part-005.md
+part-006.md
+```
+
+You now need the file names to be `part-1.md` through `part-7.md`, because you removed one but gained two more for a net difference of one file. Also, the frontmatter of each file below a deleted step or added step will need to be modified by making the `title` key value match the new step number. For example, after renaming `part-3.md` to `part-2.md`, you would need to change `part-2.md`'s title from `Part 03` to `Part 02`.
+
+See below for the actual project folder changes needed:
+
+```bash
+part-001.md
+part-003.md renamed to part-002.md and title changes to "Part 2"
+part-004.md renames to part-003.md and title changes to "Part 3"
+part-004a.md renames to part-004.md and title changes to "Part 4"
+part-004b.md renames to part-005.md and title changes to "Part 5"
+part-005.md renames to part-006.md and title changes to "Part 6"
+part-006.md renames to part-007.md and title changes to "Part 7"
+```
+
+Along with the above changes, the `challengeOrder` key in the project's `meta.json` file needs to reflect the new step order. This is needed because each step below a step deletion and/or step addition changes the `title` associated with each of the affected step's challenge `id`.
+
+### How to run script
+
+1. Change to the directory of the project.
+2. Run the following npm command:
+
+```bash
+npm run reorder-steps
+```

docs/i18n/espanol/_sidebar.md

@@ -8,6 +8,7 @@
   - [Trabajar en los desafíos de video](how-to-help-with-video-challenges.md)
   - [ Trabajar en el tema de noticias](how-to-work-on-the-news-theme.md)
   - [Trabajar en el tema de docs](how-to-work-on-the-docs-theme.md)
+  - [Work on practice projects](how-to-work-on-practice-projects.md)
 - **Contribución a Traducción**
   - [Work on translating resources](how-to-translate-files.md)
   - [Work on proofreading translations](how-to-proofread-files.md)

docs/i18n/espanol/how-to-work-on-coding-challenges.md

@@ -29,6 +29,9 @@ Antes de trabajar en el plan de estudios, necesitarás configurar algunas herram
 
 - Editar los archivos de la interfaz de GitHub haciendo clic en el icono del lápiz del archivo correspondiente. Aunque esta es la manera más rápida, **no se recomienda**, ya que no puedes probar tus cambios en GitHub. If our maintainers conclude that the changes you made need to be tested locally, you would need to follow the methods above instead.
 
+### How to work on practice projects
+
+The practice projects have some additional tooling to help create new projects and steps.  To read more, see [these docs](how-to-work-on-practice-projects.md)
 ## Plantilla de desafío
 
 ````md
@@ -230,7 +233,7 @@ Proper nouns should use correct capitalization when possible. Below is a list of
 - Node.js
 - El desarrollo de front-end (forma adjetiva con guiones) es cuando estás trabajando en la parte frontal (sin guiones). Lo mismo ocurre con el "back end", "full stack", y muchos otros términos compuestos.
 
-### La regla de los 2 minutos
+### The 2-minute rule
 
 Each challenge should be solvable within 120 seconds by a native English speaker who has completed the challenges leading up to it. This includes the amount of time it takes to read the directions/instructions understand the seeded code, write their code and get all the tests to pass.
 
@@ -243,7 +246,7 @@ The 2-minute rule forces you, the challenge designer, to make your directions co
 
 We track how long it takes for campers to solve changes and use this information to identify challenges that need to be simplified or split.
 
-### Modularidad
+### Modularity
 
 Each challenge should teach exactly one concept, and that concept should be apparent from the challenge's name.
 
@@ -251,7 +254,7 @@ We can reinforce previously covered concepts through repetition and variations -
 
 Our goal is to have thousands of 2-minute challenges. These can flow together and reiterate previously-covered concepts.
 
-### Formateando el texto del desafío
+### Formatting challenge text
 
 Here are specific formatting guidelines for challenge text and examples:
 
@@ -359,7 +362,7 @@ class MyComponent extends React.Component {
 };
 ```
 
-### Traducción de comentarios de código de semilla
+### Translation of seed code comments
 
 There are separate comment dictionaries for each language. The [English version of the comment dictionary](/curriculum/dictionaries/english/comments.js) is the basis for the translations found in the corresponding non-English versions of the files. The non-English version of the Chinese comment dictionary would be located at `/curriculum/dictionaries/chinese/comments.js`.  Each dictionary consists of an array of objects with a unique `id` property and a `text` property.  Only the `text` should be modified to encompass the translation of the corresponding English comment.
 
@@ -378,7 +381,7 @@ Each challenge has a `Get a Hint` button, so a user can access any hints/solutio
 
 If you find a problem with an existing challenge's hints/solutions topic, you can make suggestions in the [contributors category](https://forum.freecodecamp.org/c/contributors) on the forum. Moderators and users with trust level 3 will review the comments and decide whether or not to include the changes in the corresponding hint/solutions topic.
 
-### Añadir nuevos temas de sugerencias/soluciones de Desafío
+### Adding new Challenge hints/solutions Topics
 
 Take the following steps when adding a new challenge hints/solutions related topic.
 
@@ -387,7 +390,7 @@ Take the following steps when adding a new challenge hints/solutions related top
 3. `camperbot` debe ser el dueño de estos temas/posts, así que necesitarás solicitar a un administrador que cambie la propiedad de la publicación principal a `camperbot`.
 4. Una vez creado el nuevo tema, se crea un identificador del tema del foro. Se encuentra al final de la URL del tema del foro. Este id debe añadirse a la parte frontal del archivo de desafío curriculum a través del proceso normal de pull request para el botón `Obtener una pista` para vincular al tema.
 
-### Orientaciones para el contenido de pistas y temas de soluciones
+### Guidelines for content of hints and solutions topics
 
 When proposing a solution for a curriculum challenge related Guide topic, the full code must be added. This includes all the original seed code plus any changes needed to pass all the challenge tests. The following template should be used when creating new hints/solutions topics:
 

docs/i18n/espanol/how-to-work-on-practice-projects.md

@@ -0,0 +1,123 @@
+# How to Work on Practice Projects
+
+The `tools/challenge-helper-scripts` folder contains tools to help facilitate the creation and maintenance of the freeCodeCamp project-based curriculum.
+
+## Create a new project
+
+Run `npm run create-project`. This opens up a command line ui that guides you through the process. Once that has finished, there should be a new challenge in the English curriculum that you can use for the first step of the project. For example, if you created a project called `test-project` in the Responsive Web Design certification, it would be in `curriculum/challenges/english/01-responsive-web-design/test-project`.
+
+If you want to create new steps, the following tools simplify that process.
+
+## create-next-step
+
+A one-off script that will automatically add the next step based on the last step numbered as `part-xxx.md` where `xxx` represents the 3-digit step number of the last step. The challenge seed code will use the previous step's challenge seed code with the editable region markers (ERMs) removed.
+
+**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps).
+
+### How to run script:
+
+1. Change to the directory of the project.
+2. Run the following npm command:
+
+```bash
+npm run create-next-step
+```
+
+## create-empty-steps
+
+A one-off script that automatically adds a specified number of steps at a specific starting step number. The challenge seed code for all steps created will be empty.
+
+**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps).
+
+### How to run script:
+
+1. Change to the directory of the project.
+2. Run the following npm command:
+
+```bash
+npm run create-empty-steps start=X num=Y # where X is the starting step number and Y is the number of steps to create.
+```
+
+## create-step-between
+
+A one-off script that automatically adds a new step between two existing consecutive steps. The challenge seed code will use the existing starting step's challenge seed code with the editable region markers (ERMs) removed.
+
+**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps).
+
+### How to run script:
+
+1. Change to the directory of the project.
+2. Run the following npm command:
+
+```bash
+npm run create-step-between start=X # where X is the starting step number
+```
+
+## delete-step
+
+A one-off script that deletes an existing step and then reorders the remaining step files in the project's folder as well as updates the `challengeOrder` property array in the project's `meta.json` with the new order of the steps.
+
+### How to run script
+
+1. Change to the directory of the project.
+2. Run the following npm command:
+
+```bash
+npm run delete-step num=x # where x is the step number to be deleted.
+```
+
+## reorder-steps
+
+A one-off script that automatically reorders the step files in a project's markdown files based on the filename. It also updates the `challengeOrder` property array in the project's `meta.json` with the new order of the steps.
+
+### Working Example
+
+Let's say you start with the following project structure:
+
+```bash
+part-1.md
+part-2.md
+part-3.md
+part-4.md
+part-5.md
+part-6.md
+```
+
+At some point you decide you need to delete `part-2.md`, because that step is no longer needed. Also, you decide to break down `part-4.md` into three steps instead of just one.
+
+To accomplish this restructure, you would need to delete `part-2.md` and then add a `part-4a.md` and a `part-5b.md`. The new folder structure would look like the following:
+
+```bash
+part-001.md
+part-003.md
+part-004.md
+part-004a.md
+part-004b.md
+part-005.md
+part-006.md
+```
+
+You now need the file names to be `part-1.md` through `part-7.md`, because you removed one but gained two more for a net difference of one file. Also, the frontmatter of each file below a deleted step or added step will need to be modified by making the `title` key value match the new step number. For example, after renaming `part-3.md` to `part-2.md`, you would need to change `part-2.md`'s title from `Part 03` to `Part 02`.
+
+See below for the actual project folder changes needed:
+
+```bash
+part-001.md
+part-003.md renamed to part-002.md and title changes to "Part 2"
+part-004.md renames to part-003.md and title changes to "Part 3"
+part-004a.md renames to part-004.md and title changes to "Part 4"
+part-004b.md renames to part-005.md and title changes to "Part 5"
+part-005.md renames to part-006.md and title changes to "Part 6"
+part-006.md renames to part-007.md and title changes to "Part 7"
+```
+
+Along with the above changes, the `challengeOrder` key in the project's `meta.json` file needs to reflect the new step order. This is needed because each step below a step deletion and/or step addition changes the `title` associated with each of the affected step's challenge `id`.
+
+### How to run script
+
+1. Change to the directory of the project.
+2. Run the following npm command:
+
+```bash
+npm run reorder-steps
+```

docs/i18n/portuguese/_sidebar.md

@@ -8,6 +8,7 @@
   - [Work on video challenges](how-to-help-with-video-challenges.md)
   - [Work on the news theme](how-to-work-on-the-news-theme.md)
   - [Work on the docs theme](how-to-work-on-the-docs-theme.md)
+  - [Work on practice projects](how-to-work-on-practice-projects.md)
 - **Translation Contribution**
   - [Work on translating resources](how-to-translate-files.md)
   - [Work on proofreading translations](how-to-proofread-files.md)

docs/i18n/portuguese/how-to-work-on-coding-challenges.md

@@ -29,6 +29,9 @@ Before you work on the curriculum, you would need to set up some tooling to help
 
 - Edit the files on GitHub's interface by clicking the pencil icon for the corresponding file. While this is the quickest way, It is **not recommended**, because you are unable to test your changes on GitHub. If our maintainers conclude that the changes you made need to be tested locally, you would need to follow the methods above instead.
 
+### How to work on practice projects
+
+The practice projects have some additional tooling to help create new projects and steps.  To read more, see [these docs](how-to-work-on-practice-projects.md)
 ## Challenge Template
 
 ````md

docs/i18n/portuguese/how-to-work-on-practice-projects.md

@@ -0,0 +1,123 @@
+# How to Work on Practice Projects
+
+The `tools/challenge-helper-scripts` folder contains tools to help facilitate the creation and maintenance of the freeCodeCamp project-based curriculum.
+
+## Create a new project
+
+Run `npm run create-project`. This opens up a command line ui that guides you through the process. Once that has finished, there should be a new challenge in the English curriculum that you can use for the first step of the project. For example, if you created a project called `test-project` in the Responsive Web Design certification, it would be in `curriculum/challenges/english/01-responsive-web-design/test-project`.
+
+If you want to create new steps, the following tools simplify that process.
+
+## create-next-step
+
+A one-off script that will automatically add the next step based on the last step numbered as `part-xxx.md` where `xxx` represents the 3-digit step number of the last step. The challenge seed code will use the previous step's challenge seed code with the editable region markers (ERMs) removed.
+
+**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps).
+
+### How to run script:
+
+1. Change to the directory of the project.
+2. Run the following npm command:
+
+```bash
+npm run create-next-step
+```
+
+## create-empty-steps
+
+A one-off script that automatically adds a specified number of steps at a specific starting step number. The challenge seed code for all steps created will be empty.
+
+**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps).
+
+### How to run script:
+
+1. Change to the directory of the project.
+2. Run the following npm command:
+
+```bash
+npm run create-empty-steps start=X num=Y # where X is the starting step number and Y is the number of steps to create.
+```
+
+## create-step-between
+
+A one-off script that automatically adds a new step between two existing consecutive steps. The challenge seed code will use the existing starting step's challenge seed code with the editable region markers (ERMs) removed.
+
+**Note:** This script also runs [reorder-steps](how-to-work-on-practice-projects#reorder-steps).
+
+### How to run script:
+
+1. Change to the directory of the project.
+2. Run the following npm command:
+
+```bash
+npm run create-step-between start=X # where X is the starting step number
+```
+
+## delete-step
+
+A one-off script that deletes an existing step and then reorders the remaining step files in the project's folder as well as updates the `challengeOrder` property array in the project's `meta.json` with the new order of the steps.
+
+### How to run script
+
+1. Change to the directory of the project.
+2. Run the following npm command:
+
+```bash
+npm run delete-step num=x # where x is the step number to be deleted.
+```
+
+## reorder-steps
+
+A one-off script that automatically reorders the step files in a project's markdown files based on the filename. It also updates the `challengeOrder` property array in the project's `meta.json` with the new order of the steps.
+
+### Working Example
+
+Let's say you start with the following project structure:
+
+```bash
+part-1.md
+part-2.md
+part-3.md
+part-4.md
+part-5.md
+part-6.md
+```
+
+At some point you decide you need to delete `part-2.md`, because that step is no longer needed. Also, you decide to break down `part-4.md` into three steps instead of just one.
+
+To accomplish this restructure, you would need to delete `part-2.md` and then add a `part-4a.md` and a `part-5b.md`. The new folder structure would look like the following:
+
+```bash
+part-001.md
+part-003.md
+part-004.md
+part-004a.md
+part-004b.md
+part-005.md
+part-006.md
+```
+
+You now need the file names to be `part-1.md` through `part-7.md`, because you removed one but gained two more for a net difference of one file. Also, the frontmatter of each file below a deleted step or added step will need to be modified by making the `title` key value match the new step number. For example, after renaming `part-3.md` to `part-2.md`, you would need to change `part-2.md`'s title from `Part 03` to `Part 02`.
+
+See below for the actual project folder changes needed:
+
+```bash
+part-001.md
+part-003.md renamed to part-002.md and title changes to "Part 2"
+part-004.md renames to part-003.md and title changes to "Part 3"
+part-004a.md renames to part-004.md and title changes to "Part 4"
+part-004b.md renames to part-005.md and title changes to "Part 5"
+part-005.md renames to part-006.md and title changes to "Part 6"
+part-006.md renames to part-007.md and title changes to "Part 7"
+```
+
+Along with the above changes, the `challengeOrder` key in the project's `meta.json` file needs to reflect the new step order. This is needed because each step below a step deletion and/or step addition changes the `title` associated with each of the affected step's challenge `id`.
+
+### How to run script
+
+1. Change to the directory of the project.
+2. Run the following npm command:
+
+```bash
+npm run reorder-steps
+```