mirror of
https://github.com/freeCodeCamp/freeCodeCamp.git
synced 2026-05-28 18:26:54 +00:00
chore(i18n,docs): processed translations (#52242)
This commit is contained in:
camperbot
@@ -4,7 +4,7 @@ Ignoring these steps may soil your copy which makes the contributing, maintainin
|
||||
|
||||
## Contributing to the Codebase
|
||||
|
||||
You can now make changes to files and commit your changes to your fork, which you can prepare by reading [how to set up freecodecamp](how-to-setup-freecodecamp-locally.md).
|
||||
You can now make changes to files and commit your changes to your fork, which you can prepare by reading [how to set up freeCodeCamp locally](how-to-setup-freecodecamp-locally.md).
|
||||
|
||||
Follow these steps:
|
||||
|
||||
|
||||
@@ -246,10 +246,11 @@ Next, let's seed the database. In this step, we run the below command that fills
|
||||
pnpm run seed
|
||||
```
|
||||
|
||||
By default, you will be signed in as a new user without any completed certifications. Run the following command if you need to develop with completed certifications:
|
||||
By default, you will be signed in as a new user without any completed certifications. Run the following commands if you need to develop with completed certifications:
|
||||
|
||||
```console
|
||||
pnpm run seed:certified-user
|
||||
pnpm run seed:exams
|
||||
```
|
||||
|
||||
> [!WARNING] Running `pnpm run seed:certified-user` will log you out. You will have to clear your browser cookies and sign in again.
|
||||
@@ -283,5 +284,6 @@ A quick reference to the commands that you will need when working locally.
|
||||
| `pnpm install` | Installs / re-installs all dependencies and bootstraps the different services. |
|
||||
| `pnpm run seed` | Creates authorized test users and inserts them into MongoDB. |
|
||||
| `pnpm run seed:certified-user` | Creates authorized test users with certifications fully completed, and inserts them into MongoDB. |
|
||||
| `pnpm run seed:exams` | Creates exams and inserts them into MongoDB. |
|
||||
| `pnpm run develop` | Starts the freeCodeCamp API Server and Client Applications. |
|
||||
| `pnpm run clean` | Uninstalls all dependencies and cleans up caches. |
|
||||
|
||||
@@ -136,6 +136,14 @@ Solutions are used for the CI tests to ensure that changes to the hints will sti
|
||||
// third solution etc. - Your solutions should be in HTML.
|
||||
```
|
||||
|
||||
# --assignments--
|
||||
|
||||
This will show a checkbox that campers have to check before completing a challenge
|
||||
|
||||
---
|
||||
|
||||
This will show another checkbox that campers have to check before completing a challenge
|
||||
|
||||
# --question--
|
||||
|
||||
These fields are currently used for the multiple-choice Python challenges.
|
||||
@@ -148,6 +156,10 @@ The question text goes here.
|
||||
|
||||
Answer 1
|
||||
|
||||
### --feedback--
|
||||
|
||||
This will be shown as feedback when campers guess this answer
|
||||
|
||||
---
|
||||
|
||||
Answer 2
|
||||
|
||||
@@ -4,7 +4,7 @@ Ignoring these steps may soil your copy which makes the contributing, maintainin
|
||||
|
||||
## Contributing to the Codebase
|
||||
|
||||
You can now make changes to files and commit your changes to your fork, which you can prepare by reading [how to set up freecodecamp](how-to-setup-freecodecamp-locally.md).
|
||||
You can now make changes to files and commit your changes to your fork, which you can prepare by reading [how to set up freeCodeCamp locally](how-to-setup-freecodecamp-locally.md).
|
||||
|
||||
Follow these steps:
|
||||
|
||||
|
||||
@@ -246,10 +246,11 @@ Next, let's seed the database. In this step, we run the below command that fills
|
||||
pnpm run seed
|
||||
```
|
||||
|
||||
By default, you will be signed in as a new user without any completed certifications. Run the following command if you need to develop with completed certifications:
|
||||
By default, you will be signed in as a new user without any completed certifications. Run the following commands if you need to develop with completed certifications:
|
||||
|
||||
```console
|
||||
pnpm run seed:certified-user
|
||||
pnpm run seed:exams
|
||||
```
|
||||
|
||||
> [!WARNING] Running `pnpm run seed:certified-user` will log you out. You will have to clear your browser cookies and sign in again.
|
||||
@@ -283,5 +284,6 @@ A quick reference to the commands that you will need when working locally.
|
||||
| `pnpm install` | Installs / re-installs all dependencies and bootstraps the different services. |
|
||||
| `pnpm run seed` | Creates authorized test users and inserts them into MongoDB. |
|
||||
| `pnpm run seed:certified-user` | Creates authorized test users with certifications fully completed, and inserts them into MongoDB. |
|
||||
| `pnpm run seed:exams` | Creates exams and inserts them into MongoDB. |
|
||||
| `pnpm run develop` | Starts the freeCodeCamp API Server and Client Applications. |
|
||||
| `pnpm run clean` | Uninstalls all dependencies and cleans up caches. |
|
||||
|
||||
@@ -136,6 +136,14 @@ Solutions are used for the CI tests to ensure that changes to the hints will sti
|
||||
// third solution etc. - Your solutions should be in HTML.
|
||||
```
|
||||
|
||||
# --assignments--
|
||||
|
||||
This will show a checkbox that campers have to check before completing a challenge
|
||||
|
||||
---
|
||||
|
||||
This will show another checkbox that campers have to check before completing a challenge
|
||||
|
||||
# --question--
|
||||
|
||||
These fields are currently used for the multiple-choice Python challenges.
|
||||
@@ -148,6 +156,10 @@ The question text goes here.
|
||||
|
||||
Answer 1
|
||||
|
||||
### --feedback--
|
||||
|
||||
This will be shown as feedback when campers guess this answer
|
||||
|
||||
---
|
||||
|
||||
Answer 2
|
||||
|
||||
@@ -4,7 +4,7 @@ Ignorar estos pasos puede empobrecer tu copia lo que hara que el proceso de cont
|
||||
|
||||
## Contribuir a la base del código
|
||||
|
||||
Ya podes hacer modificaciones a los archivos y confimar estos cambios a tu bifurcación, la cual puedes realizar leyendo el tutorial [how to set up freeCodeCamp](how-to-setup-freecodecamp-locally.md).
|
||||
You can now make changes to files and commit your changes to your fork, which you can prepare by reading [how to set up freeCodeCamp locally](how-to-setup-freecodecamp-locally.md).
|
||||
|
||||
Sigue estos pasos:
|
||||
|
||||
|
||||
@@ -246,10 +246,11 @@ Next, let's seed the database. In this step, we run the below command that fills
|
||||
pnpm run seed
|
||||
```
|
||||
|
||||
By default, you will be signed in as a new user without any completed certifications. Run the following command if you need to develop with completed certifications:
|
||||
By default, you will be signed in as a new user without any completed certifications. Run the following commands if you need to develop with completed certifications:
|
||||
|
||||
```console
|
||||
pnpm run seed:certified-user
|
||||
pnpm run seed:exams
|
||||
```
|
||||
|
||||
> [!WARNING] Running `pnpm run seed:certified-user` will log you out. You will have to clear your browser cookies and sign in again.
|
||||
@@ -283,5 +284,6 @@ A quick reference to the commands that you will need when working locally.
|
||||
| `pnpm install` | Installs / re-installs all dependencies and bootstraps the different services. |
|
||||
| `pnpm run seed` | Creates authorized test users and inserts them into MongoDB. |
|
||||
| `pnpm run seed:certified-user` | Creates authorized test users with certifications fully completed, and inserts them into MongoDB. |
|
||||
| `pnpm run seed:exams` | Creates exams and inserts them into MongoDB. |
|
||||
| `pnpm run develop` | Starts the freeCodeCamp API Server and Client Applications. |
|
||||
| `pnpm run clean` | Uninstalls all dependencies and cleans up caches. |
|
||||
|
||||
@@ -142,29 +142,41 @@ Las soluciones se utilizan para las pruebas de CI para garantizar que los cambio
|
||||
// tercera solución, etc. - Sus soluciones deben estar en HTML.
|
||||
```
|
||||
|
||||
# --pregunta--
|
||||
# --assignments--
|
||||
|
||||
Estos campos se utilizan actualmente para los desafíos de Python de opción múltiple.
|
||||
This will show a checkbox that campers have to check before completing a challenge
|
||||
|
||||
---
|
||||
|
||||
This will show another checkbox that campers have to check before completing a challenge
|
||||
|
||||
# --question--
|
||||
|
||||
These fields are currently used for the multiple-choice Python challenges.
|
||||
|
||||
## --text--
|
||||
|
||||
El texto de la pregunta va aquí.
|
||||
The question text goes here.
|
||||
|
||||
## --answers--
|
||||
|
||||
Respuesta 1
|
||||
Answer 1
|
||||
|
||||
### --feedback--
|
||||
|
||||
This will be shown as feedback when campers guess this answer
|
||||
|
||||
---
|
||||
|
||||
Respuesta 2
|
||||
Answer 2
|
||||
|
||||
---
|
||||
|
||||
Más respuestas
|
||||
More answers
|
||||
|
||||
## --video-solution--
|
||||
|
||||
El número de respuestas correctas va aquí.
|
||||
The number for the correct answer goes here.
|
||||
````
|
||||
|
||||
> [!NOTE]
|
||||
@@ -199,7 +211,7 @@ ObjectId("5a474d78df58bafeb3535d34")
|
||||
|
||||
The result is a new id, for example, `5a474d78df58bafeb3535d34` above.
|
||||
|
||||
Una vez que tengas tu id, ponlo en el archivo markdown como el campo `id` en la parte superior, p.ej.
|
||||
Once you have your id, put it into the markdown file as the `id` field at the top, e.g.
|
||||
|
||||
```yml
|
||||
---
|
||||
@@ -209,13 +221,13 @@ título: Título del desafío
|
||||
|
||||
## Nombrando desafíos
|
||||
|
||||
Nombrar cosas es difícil. Lo hemos hecho más fácil imponiendo algunas restricciones.
|
||||
Naming things is hard. We've made it easier by imposing some constraints.
|
||||
|
||||
Todos los títulos del desafío deben ser explícitos y deben seguir este patrón:
|
||||
All challenge titles should be explicit and should follow this pattern:
|
||||
|
||||
\[verb\]\[cláusula del objeto\]
|
||||
\[verb\]\[object clause\]
|
||||
|
||||
Estos son algunos ejemplos de nombres de desafíos:
|
||||
Here are some example challenge names:
|
||||
|
||||
- Utilice Notación en sentido de la derecha para especificar el relleno de un elemento
|
||||
- Condensa arreglos con ".reduce"
|
||||
@@ -223,29 +235,29 @@ Estos son algunos ejemplos de nombres de desafíos:
|
||||
|
||||
## Descripciones/Instrucciones de Desafíos
|
||||
|
||||
Las oraciones deben ser claras y concisas con el menor uso posible de jerga. Si se utiliza, la jerga debe aclararse inmediatamente en español sencillo.
|
||||
Sentences should be clear and concise with minimal jargon. If used, jargon should be immediately defined in plain English.
|
||||
|
||||
Mantenga los párrafos cortos (alrededor de 1-4 oraciones). Es más probable que la gente lea varios párrafos cortos que un muro de texto.
|
||||
Keep paragraphs short (around 1-4 sentences). People are more likely to read several short paragraphs than a wall of text.
|
||||
|
||||
El texto del desafío debe utilizar la segunda persona ("tú") para ayudar a darle un tono de conversación. De esta manera el texto y las instrucciones parecen hablar directamente con el acampador que trabaja a través del desafío. Trate de evitar usar la primera persona ("yo", "nosotros", "déjanos", y "nosotros").
|
||||
Challenge text should use the second person ("you") to help to give it a conversational tone. This way the text and instructions seem to speak directly to the camper working through the challenge. Try to avoid using the first person ("I", "we", "let's", and "us").
|
||||
|
||||
No usar enlaces salientes. Estos interrumpen el flujo. Los campistas no deben tener que googlear nada durante estos desafíos. Si hay recursos de los que piensas que los campistas se beneficiarían, añádelos al artículo relacionado con la guía del desafío.
|
||||
Don't use outbound links. These interrupt the flow. Campers should never have to google anything during these challenges. If there are resources you think campers would benefit from, add them to the challenge's Guide-related article.
|
||||
|
||||
Puedes añadir diagramas si fuera necesario.
|
||||
You can add diagrams if necessary.
|
||||
|
||||
No utilices emojis o emoticonos en desafíos. freeCodeCamp tiene una comunidad global, y el significado cultural de un emoji o emoticono puede ser diferente en distintas partes del mundo. Además, los emojis pueden renderizarse de manera diferente en sistemas diferentes.
|
||||
Don't use emojis or emoticons in challenges. freeCodeCamp has a global community, and the cultural meaning of an emoji or emoticon may be different around the world. Also, emojis can render differently on different systems.
|
||||
|
||||
Los sustantivos adecuados deben usar una capitalización correcta cuando sea posible. A continuación se muestra una lista de palabras como deben aparecer en los desafíos.
|
||||
Proper nouns should use correct capitalization when possible. Below is a list of words as they should appear in the challenges.
|
||||
|
||||
- JavaScript (mayúsculas en "J" y "S" y sin abreviaturas)
|
||||
- Node.js
|
||||
- Aunque a veces sea inexacto, se deben utilizar formularios no separados de 'back-end' y 'front end', ya que se usan más ampliamente.
|
||||
|
||||
### La regla de los 2 minutos
|
||||
### The 2-minute rule
|
||||
|
||||
Cada desafío debe ser resuelto en un plazo de 120 segundos por un hablante nativo de español que haya completado los desafíos que lo preceden. Esto incluye la cantidad de tiempo que se tarda en leer las indicaciones/instrucciones entender el código sembrado, escribir su código y conseguir que todas las pruebas pasen.
|
||||
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.
|
||||
|
||||
Si toma más de dos minutos completar el desafío, tienes dos opciones:
|
||||
If it takes longer than two minutes to complete the challenge, you have two options:
|
||||
|
||||
- Simplificar el desafío, o
|
||||
- Dividir el desafío en dos desafíos.
|
||||
@@ -254,17 +266,17 @@ The 2-minute rule forces you, the challenge designer, to make your directions co
|
||||
|
||||
We track how long it takes for campers to solve challenges and use this information to identify challenges that need to be simplified or split.
|
||||
|
||||
### Modularidad
|
||||
### Modularity
|
||||
|
||||
Cada desafío debe enseñar exactamente un concepto, y ese concepto debe ser evidente por el nombre del reto.
|
||||
Each challenge should teach exactly one concept, and that concept should be apparent from the challenge's name.
|
||||
|
||||
Podemos reforzar los conceptos previamente cubiertos a través de la repetición y las variaciones - por ejemplo, introduciendo los elementos h1 en un desafío, y luego los elementos h3 unos pocos desafíos más tarde.
|
||||
We can reinforce previously covered concepts through repetition and variations - for example, introducing h1 elements in one challenge, then h3 elements a few challenges later.
|
||||
|
||||
Nuestro objetivo es tener miles de desafíos de 2 minutos. Estos pueden fluir juntos y reiterar los conceptos previamente cubiertos.
|
||||
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
|
||||
|
||||
Aquí están las directrices de formato específicas para el texto del desafío y los ejemplos:
|
||||
Here are specific formatting guidelines for challenge text and examples:
|
||||
|
||||
- Las palabras clave del lenguaje van en etiquetas ``. Por ejemplo, nombres de etiquetas HTML o nombres de propiedades CSS.
|
||||
- Las referencias a las partes del código (es decir, funciones, métodos o nombres de variables) deben estar envueltas en etiquetas ``. Ver el ejemplo a continuación:
|
||||
@@ -277,9 +289,9 @@ Usa `parseInt` para convertir la variable `realNumber` en un entero.
|
||||
- Los bloques de código de múltiples líneas **deben estar precedidos por una línea vacía**. La siguiente línea debe comenzar con tres backticks seguidos inmediatamente por uno de los [idiomas soportados](https://prismjs.com/#supported-languages). To complete the code block, you must start a new line that only has three backticks and **another empty line**. Ver el ejemplo a continuación:
|
||||
- El espacio en blanco es importante en Markdown, por lo que le recomendamos que lo haga visible en su editor.
|
||||
|
||||
**Nota:** Si va a utilizar un código de ejemplo en YAML, utilice yaml en lugar de yml para el idioma a la derecha de la comilla inversa.
|
||||
**Note:** If you are going to use an example code in YAML, use `yaml` instead of `yml` for the language to the right of the backticks.
|
||||
|
||||
Lo siguiente es un ejemplo de código:
|
||||
The following is an example of code:
|
||||
|
||||
````md
|
||||
`` `{idioma}
|
||||
@@ -323,13 +335,13 @@ Example of a valid single-line JavaScript comment:
|
||||
// Only change code below this line
|
||||
````
|
||||
|
||||
Ejemplo de un comentario de CSS válido:
|
||||
Example of a valid CSS comment:
|
||||
|
||||
```css
|
||||
/* Only change code above this line */
|
||||
```
|
||||
|
||||
Si un desafío solo tiene un lugar en el que se necesitan cambios de código, utilice los comentarios del siguiente ejemplo para indicar al usuario dónde deben realizarse los cambios.
|
||||
If a challenge only has a single place where code changes are needed, please use the comments in the following example to instruct the user where changes should be made.
|
||||
|
||||
```js
|
||||
var a = 3;
|
||||
@@ -342,7 +354,7 @@ b = 9 + b;
|
||||
c = c + 7;
|
||||
```
|
||||
|
||||
Si un desafío tiene varios lugares donde se espera que el usuario cambie el código (es decir, los desafíos de React)
|
||||
If a challenge has multiple places where the user is expected to change code (i.e. the React challenges)
|
||||
|
||||
```jsx
|
||||
class MyComponent extends React.Component {
|
||||
@@ -375,9 +387,9 @@ class MyComponent extends React.Component {
|
||||
|
||||
### Translation of Seed Code Comments
|
||||
|
||||
Hay diccionarios de comentarios separados para cada idioma. The [English version of the comment dictionary](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/dictionaries/english/comments.json) 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.json`. Cada diccionario consiste en un arreglo de objetos con una propiedad `id` única y una propiedad `text`. Solo debe modificarse el `text` para abarcar la traducción del comentario inglés correspondiente.
|
||||
There are separate comment dictionaries for each language. The [English version of the comment dictionary](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/dictionaries/english/comments.json) 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.json`. 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.
|
||||
|
||||
Algunos comentarios pueden contener una palabra/frase que no debe ser traducida. Por ejemplo, los nombres de las variables o los nombres propios de las bibliotecas, como "React", no deben traducirse. Vea el comentario siguiente como ejemplo. La palabra `myGlobal` no debe traducirse.
|
||||
Some comments may contain a word/phrase that should not be translated. For example, variable names or proper library names like "React" should not be translated. See the comment below as an example. The word `myGlobal` should not be translated.
|
||||
|
||||
```text
|
||||
Declara la variable myGlobal debajo de esta línea
|
||||
@@ -389,11 +401,11 @@ Declara la variable myGlobal debajo de esta línea
|
||||
|
||||
## Consejos y soluciones
|
||||
|
||||
Cada desafío tiene un botón de `Obtener un consejo`, para que un usuario pueda acceder a cualquier pista/solución que haya sido creada para el reto. Los temas de las pistas/soluciones del plan de estudios se encuentran en [nuestro foro](https://forum.freecodecamp.org/c/guide), en la categoría `Guía`.
|
||||
Each challenge has a `Get a Hint` button, so a user can access any hints/solutions which have been created for the challenge. Curriculum hints/solutions topics are located on [our forum](https://forum.freecodecamp.org/c/guide) under the `Guide` category.
|
||||
|
||||
Si encuentras un problema en el tema de pistas/soluciones de un desafío existente, puedes hacer sugerencias en la [categoría de colaboradores](https://forum.freecodecamp.org/c/contributors) del foro. Los moderadores y los usuarios con nivel de confianza 3, revisarán los comentarios y decidirán si se incluyen o no los cambios en el tema de pistas/soluciones correspondiente.
|
||||
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.
|
||||
|
||||
@@ -404,7 +416,7 @@ Take the following steps when adding a new challenge hints/solutions-related top
|
||||
|
||||
### 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. Esto incluye todo el código semilla original más los cambios necesarios para pasar todas las pruebas de desafío. Para crear nuevos temas de pistas/soluciones debe utilizarse la siguiente plantilla:
|
||||
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:
|
||||
|
||||
````md
|
||||
# El nombre del desafío va aquí
|
||||
|
||||
@@ -4,7 +4,7 @@ Ignoring these steps may soil your copy which makes the contributing, maintainin
|
||||
|
||||
## Contributing to the Codebase
|
||||
|
||||
You can now make changes to files and commit your changes to your fork, which you can prepare by reading [how to set up freecodecamp](how-to-setup-freecodecamp-locally.md).
|
||||
You can now make changes to files and commit your changes to your fork, which you can prepare by reading [how to set up freeCodeCamp locally](how-to-setup-freecodecamp-locally.md).
|
||||
|
||||
Follow these steps:
|
||||
|
||||
|
||||
@@ -246,10 +246,11 @@ Next, let's seed the database. In this step, we run the below command that fills
|
||||
pnpm run seed
|
||||
```
|
||||
|
||||
By default, you will be signed in as a new user without any completed certifications. Run the following command if you need to develop with completed certifications:
|
||||
By default, you will be signed in as a new user without any completed certifications. Run the following commands if you need to develop with completed certifications:
|
||||
|
||||
```console
|
||||
pnpm run seed:certified-user
|
||||
pnpm run seed:exams
|
||||
```
|
||||
|
||||
> [!WARNING] Running `pnpm run seed:certified-user` will log you out. You will have to clear your browser cookies and sign in again.
|
||||
@@ -283,5 +284,6 @@ A quick reference to the commands that you will need when working locally.
|
||||
| `pnpm install` | Installs / re-installs all dependencies and bootstraps the different services. |
|
||||
| `pnpm run seed` | Creates authorized test users and inserts them into MongoDB. |
|
||||
| `pnpm run seed:certified-user` | Creates authorized test users with certifications fully completed, and inserts them into MongoDB. |
|
||||
| `pnpm run seed:exams` | Creates exams and inserts them into MongoDB. |
|
||||
| `pnpm run develop` | Starts the freeCodeCamp API Server and Client Applications. |
|
||||
| `pnpm run clean` | Uninstalls all dependencies and cleans up caches. |
|
||||
|
||||
@@ -136,29 +136,41 @@ Lösungen werden für die CI-Tests verwendet, um sicherzustellen, dass Änderung
|
||||
// dritte Lösung usw. - Ihre Lösungen sollten in HTML geschrieben sein.
|
||||
```
|
||||
|
||||
# --assignments--
|
||||
|
||||
This will show a checkbox that campers have to check before completing a challenge
|
||||
|
||||
---
|
||||
|
||||
This will show another checkbox that campers have to check before completing a challenge
|
||||
|
||||
# --question--
|
||||
|
||||
Diese Felder werden derzeit für die Multiple-Choice-Aufgaben in Python verwendet.
|
||||
These fields are currently used for the multiple-choice Python challenges.
|
||||
|
||||
## --text--
|
||||
|
||||
Der Text der Frage steht hier.
|
||||
The question text goes here.
|
||||
|
||||
## --answers--
|
||||
|
||||
Antwort 1
|
||||
Answer 1
|
||||
|
||||
### --feedback--
|
||||
|
||||
This will be shown as feedback when campers guess this answer
|
||||
|
||||
---
|
||||
|
||||
Antwort 2
|
||||
Answer 2
|
||||
|
||||
---
|
||||
|
||||
Weitere Antworten
|
||||
More answers
|
||||
|
||||
## --video-solution--
|
||||
|
||||
Die Nummer für die richtige Antwort steht hier.
|
||||
The number for the correct answer goes here.
|
||||
````
|
||||
|
||||
> [!NOTE]
|
||||
@@ -192,7 +204,7 @@ ObjectId("5a474d78df58bafeb3535d34")
|
||||
|
||||
The result is a new id, for example, `5a474d78df58bafeb3535d34` above.
|
||||
|
||||
Sobald du deine ID hast, fügst du sie in die Markdown-Datei als `id`-Feld am Anfang ein, z. B.
|
||||
Once you have your id, put it into the markdown file as the `id` field at the top, e.g.
|
||||
|
||||
```yml
|
||||
---
|
||||
@@ -202,13 +214,13 @@ title: Aufgabentitel
|
||||
|
||||
## Aufgaben benennen
|
||||
|
||||
Dinge zu benennen ist schwer. Wir haben es einfacher gemacht, indem wir ein paar Einschränkungen festgelegt haben.
|
||||
Naming things is hard. We've made it easier by imposing some constraints.
|
||||
|
||||
Alle Aufgabentitel sollten eindeutig sein und diesem Muster folgen:
|
||||
All challenge titles should be explicit and should follow this pattern:
|
||||
|
||||
\[Verb\]\[Objektsatz\]
|
||||
\[verb\]\[object clause\]
|
||||
|
||||
Hier sind einige Beispielnamen für Aufgaben:
|
||||
Here are some example challenge names:
|
||||
|
||||
- Verwende die Uhrzeiger-Notation, um das Padding eines Elements festzulegen
|
||||
- Arrays mit .reduce komprimieren
|
||||
@@ -216,48 +228,48 @@ Hier sind einige Beispielnamen für Aufgaben:
|
||||
|
||||
## Aufgabenbeschreibungen/ Instruktionen
|
||||
|
||||
Die Sätze sollten klar und präzise sein und möglichst wenig Fachjargon enthalten. Wenn Fachjargon verwendet wird, sollte er sofort in einfachem Englisch erklärt werden.
|
||||
Sentences should be clear and concise with minimal jargon. If used, jargon should be immediately defined in plain English.
|
||||
|
||||
Halte die Absätze kurz (etwa 1-4 Sätze). Es ist wahrscheinlicher, dass die Leute mehrere kurze Absätze lesen als eine Wand aus Text.
|
||||
Keep paragraphs short (around 1-4 sentences). People are more likely to read several short paragraphs than a wall of text.
|
||||
|
||||
Der Aufforderungstext sollte in der zweiten Person ("du") verfasst sein, um ihm einen unterhaltenden Ton zu verleihen. Auf diese Weise scheinen der Text und die Instruktionen direkt zu dem/der Teilnehmer/in zu sprechen, der/die die Aufgabe bearbeitet. Versuche, die Verwendung der ersten Person zu vermeiden ("ich", "wir", "lass uns" und "uns").
|
||||
Challenge text should use the second person ("you") to help to give it a conversational tone. This way the text and instructions seem to speak directly to the camper working through the challenge. Try to avoid using the first person ("I", "we", "let's", and "us").
|
||||
|
||||
Verwende keine ausgehenden Links. Sie unterbrechen den Fluss. Die Teilnehmer/innen sollten bei diesen Aufgaben nie etwas googeln müssen. Wenn du Ressourcen hast, von denen du denkst, dass sie für die Teilnehmer/innen nützlich sind, füge sie zu dem Artikel im Leitfaden für Aufgaben hinzu.
|
||||
Don't use outbound links. These interrupt the flow. Campers should never have to google anything during these challenges. If there are resources you think campers would benefit from, add them to the challenge's Guide-related article.
|
||||
|
||||
Du kannst bei Bedarf Grafiken hinzufügen.
|
||||
You can add diagrams if necessary.
|
||||
|
||||
Verwende keine Emojis oder Emoticons in Aufgaben. freeCodeCamp hat eine globale Community und die kulturelle Bedeutung eines Emojis oder Emoticons kann auf der ganzen Welt unterschiedlich sein. Außerdem können Emojis auf verschiedenen Systemen unterschiedlich dargestellt werden.
|
||||
Don't use emojis or emoticons in challenges. freeCodeCamp has a global community, and the cultural meaning of an emoji or emoticon may be different around the world. Also, emojis can render differently on different systems.
|
||||
|
||||
Eigennamen sollten, wenn möglich, in korrekter Großschreibung verwendet werden. Im Folgenden findest du eine Liste der Wörter, wie sie in den Aufgaben vorkommen sollten.
|
||||
Proper nouns should use correct capitalization when possible. Below is a list of words as they should appear in the challenges.
|
||||
|
||||
- JavaScript (Großbuchstaben bei "J" und "S" und keine Abkürzungen)
|
||||
- Node.js
|
||||
- Obwohl sie manchmal ungenau sind, sollten die nicht mit Bindestrichen versehenen Formen von "Back-End" und "Front-End" verwendet werden, da sie weiter verbreitet sind.
|
||||
|
||||
### Die 2-Minuten-Regel
|
||||
### The 2-minute rule
|
||||
|
||||
Jede Aufgabe sollte von einem englischen Muttersprachler, der die vorangegangenen Aufgaben gelöst hat, innerhalb von 120 Sekunden gelöst werden können. Dazu gehört auch die Zeit, die du brauchst, um die Instruktionen zu lesen, den vorgegebenen Code zu verstehen, deinen Code zu schreiben und alle Tests zu bestehen.
|
||||
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.
|
||||
|
||||
Wenn du länger als zwei Minuten brauchst, um die Aufgabe zu lösen, hast du zwei Möglichkeiten:
|
||||
If it takes longer than two minutes to complete the challenge, you have two options:
|
||||
|
||||
- vereinfache die Aufgabe, oder
|
||||
- Teile die Aufgabe in zwei Aufgaben auf.
|
||||
|
||||
The 2-minute rule forces you, the challenge designer, to make your directions concise, your seed code clear, and your tests straightforward.
|
||||
|
||||
Wir verfolgen, wie lange die Teilnehmer brauchen, um die Aufgaben zu lösen, und nutzen diese Informationen, um Aufgaben zu identifizieren, die vereinfacht oder aufgeteilt werden müssen.
|
||||
We track how long it takes for campers to solve challenges and use this information to identify challenges that need to be simplified or split.
|
||||
|
||||
### Modularität
|
||||
### Modularity
|
||||
|
||||
Jede Aufgabe sollte genau ein Konzept lehren, und dieses Konzept sollte aus dem Namen der Aufgabe ersichtlich sein.
|
||||
Each challenge should teach exactly one concept, and that concept should be apparent from the challenge's name.
|
||||
|
||||
Wir können bereits behandelte Konzepte durch Wiederholungen und Variationen festigen - zum Beispiel h1-Elemente in einer Aufgabe und h3-Elemente ein paar Aufgaben später.
|
||||
We can reinforce previously covered concepts through repetition and variations - for example, introducing h1 elements in one challenge, then h3 elements a few challenges later.
|
||||
|
||||
Unser Ziel ist es, tausende von 2-minütigen Aufgaben zu haben. Diese können ineinander übergehen und bereits gelernte Konzepte wiederholen.
|
||||
Our goal is to have thousands of 2-minute challenges. These can flow together and reiterate previously-covered concepts.
|
||||
|
||||
### Aufgabentext formatieren
|
||||
### Formatting challenge text
|
||||
|
||||
Hier findest du spezielle Formatierungsrichtlinien für Aufgabentexte und einige Beispiele:
|
||||
Here are specific formatting guidelines for challenge text and examples:
|
||||
|
||||
- Sprachliche Schlüsselwörter stehen in `` \` `` Backticks. Zum Beispiel HTML-Tag-Namen oder CSS-Eigenschaftsnamen.
|
||||
- Verweise auf Codeteile (d. h. Funktions-, Methoden- oder Variablennamen) sollten in `` \` ``-Backticks eingeschlossen werden. Siehe untenstehendes Beispiel:
|
||||
@@ -270,9 +282,9 @@ Verwende `parseInt`, um die Variable `realNumber` in eine Integerzahl umzuwandel
|
||||
- Mehrzeiligen Codeblöcken **muss eine Leerzeile vorangestellt werden**. Die nächste Zeile muss mit drei Backticks beginnen, unmittelbar gefolgt von einer der [unterstützten Sprachen](https://prismjs.com/#supported-languages). To complete the code block, you must start a new line that only has three backticks and **another empty line**. Siehe untenstehendes Beispiel:
|
||||
- Whitespace ist in Markdown wichtig, deshalb empfehlen wir, ihn in deinem Editor sichtbar zu machen.
|
||||
|
||||
**Hinweis:** Wenn du einen Beispielcode in YAML verwendest, benutze `yaml` anstelle von `yml` für die Sprache rechts von den Backticks.
|
||||
**Note:** If you are going to use an example code in YAML, use `yaml` instead of `yml` for the language to the right of the backticks.
|
||||
|
||||
Im Folgenden findest du ein Codebeispiel:
|
||||
The following is an example of code:
|
||||
|
||||
````md
|
||||
```{Sprache}
|
||||
@@ -316,13 +328,13 @@ Example of a valid single-line JavaScript comment:
|
||||
// Only change code below this line
|
||||
````
|
||||
|
||||
Beispiel für einen gültigen CSS-Kommentar:
|
||||
Example of a valid CSS comment:
|
||||
|
||||
```css
|
||||
/* Only change code above this line */
|
||||
```
|
||||
|
||||
Wenn eine Aufgabe nur eine einzige Stelle hat, an der Codeänderungen erforderlich sind, verwende bitte die Kommentare im folgenden Beispiel, um dem Teilnehmer mitzuteilen, wo die Änderungen vorgenommen werden sollen.
|
||||
If a challenge only has a single place where code changes are needed, please use the comments in the following example to instruct the user where changes should be made.
|
||||
|
||||
```js
|
||||
var a = 3;
|
||||
@@ -335,7 +347,7 @@ b = 9 + b;
|
||||
c = c + 7;
|
||||
```
|
||||
|
||||
Wenn eine Aufgabe mehrere Stellen hat, an denen der Benutzer den Code ändern soll (z. B. die React-Aufgaben)
|
||||
If a challenge has multiple places where the user is expected to change code (i.e. the React challenges)
|
||||
|
||||
```jsx
|
||||
class MyComponent extends React.Component {
|
||||
@@ -368,9 +380,9 @@ class MyComponent extends React.Component {
|
||||
|
||||
### Translation of Seed Code Comments
|
||||
|
||||
Für jede Sprache gibt es ein eigenes Kommentarwörterbuch. The [English version of the comment dictionary](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/dictionaries/english/comments.json) 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.json`. Jedes Wörterbuch besteht aus einem Array von Objekten mit einer eindeutigen `id`-Eigenschaft und einer `text`-Eigenschaft. Nur der `text` sollte geändert werden, damit er die Übersetzung des entsprechenden englischen Kommentars enthält.
|
||||
There are separate comment dictionaries for each language. The [English version of the comment dictionary](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/dictionaries/english/comments.json) 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.json`. 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.
|
||||
|
||||
Einige Kommentare können ein Wort/einen Satz enthalten, das/der nicht übersetzt werden sollte. Zum Beispiel sollten Variablennamen oder Bibliotheksnamen wie "React" nicht übersetzt werden. Schau dir den Kommentar unten als Beispiel an. Das Wort `myGlobal` sollte nicht übersetzt werden.
|
||||
Some comments may contain a word/phrase that should not be translated. For example, variable names or proper library names like "React" should not be translated. See the comment below as an example. The word `myGlobal` should not be translated.
|
||||
|
||||
```text
|
||||
Deklariere die Variable myGlobal unterhalb dieser Zeile
|
||||
@@ -382,11 +394,11 @@ Deklariere die Variable myGlobal unterhalb dieser Zeile
|
||||
|
||||
## Hinweise und Lösungen
|
||||
|
||||
Jede Aufgabe hat einen `Erhalte einen Tipp` Button, so dass ein Teilnehmer alle Tipps/Lösungen, die für die Aufgabe erstellt wurden, abrufen kann. Tipps und Lösungen für den Studienplan findest du in [unserem Forum](https://forum.freecodecamp.org/c/guide) unter der Kategorie `Guide`.
|
||||
Each challenge has a `Get a Hint` button, so a user can access any hints/solutions which have been created for the challenge. Curriculum hints/solutions topics are located on [our forum](https://forum.freecodecamp.org/c/guide) under the `Guide` category.
|
||||
|
||||
Wenn du ein Problem in einem bestehenden Thema für Tipps/Lösungen findest, kannst du in der [Kategorie contributors](https://forum.freecodecamp.org/c/contributors) im Forum Vorschläge machen. Moderatoren und Nutzer mit Vertrauensstufe 3 prüfen die Kommentare und entscheiden, ob die Änderungen in das entsprechende Hinweis-/Lösungsthema aufgenommen werden oder nicht.
|
||||
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.
|
||||
|
||||
### Neue Aufgabenhinweise/Lösungsthemen hinzufügen
|
||||
### Adding new Challenge hints/solutions Topics
|
||||
|
||||
Take the following steps when adding a new challenge hints/solutions-related topic.
|
||||
|
||||
@@ -397,7 +409,7 @@ Take the following steps when adding a new challenge hints/solutions-related top
|
||||
|
||||
### 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. Dies beinhaltet den gesamten ursprünglichen Startcode sowie alle Änderungen, die nötig sind, um alle Aufgabentests zu bestehen. Die folgende Vorlage sollte verwendet werden, wenn du neue Hinweise/Lösungen für Themen erstellst:
|
||||
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:
|
||||
|
||||
````md
|
||||
# Aufgabentitel hier eintragen
|
||||
|
||||
@@ -4,7 +4,7 @@ Ignorare questi passaggi può sporcare la tua copia, rendendo difficoltosi i pro
|
||||
|
||||
## Contribuire al codebase
|
||||
|
||||
Ora puoi apportare modifiche ai file e fare dei commit con i tuoi cambiamenti al fork, che puoi preparare leggendo [come impostare freecodecamp](how-to-setup-freecodecamp-locally.md).
|
||||
You can now make changes to files and commit your changes to your fork, which you can prepare by reading [how to set up freeCodeCamp locally](how-to-setup-freecodecamp-locally.md).
|
||||
|
||||
Segui questi passaggi:
|
||||
|
||||
|
||||
@@ -246,10 +246,11 @@ Next, let's seed the database. In this step, we run the below command that fills
|
||||
pnpm run seed
|
||||
```
|
||||
|
||||
By default, you will be signed in as a new user without any completed certifications. Run the following command if you need to develop with completed certifications:
|
||||
By default, you will be signed in as a new user without any completed certifications. Run the following commands if you need to develop with completed certifications:
|
||||
|
||||
```console
|
||||
pnpm run seed:certified-user
|
||||
pnpm run seed:exams
|
||||
```
|
||||
|
||||
> [!WARNING] Running `pnpm run seed:certified-user` will log you out. You will have to clear your browser cookies and sign in again.
|
||||
@@ -283,5 +284,6 @@ A quick reference to the commands that you will need when working locally.
|
||||
| `pnpm install` | Installs / re-installs all dependencies and bootstraps the different services. |
|
||||
| `pnpm run seed` | Creates authorized test users and inserts them into MongoDB. |
|
||||
| `pnpm run seed:certified-user` | Creates authorized test users with certifications fully completed, and inserts them into MongoDB. |
|
||||
| `pnpm run seed:exams` | Creates exams and inserts them into MongoDB. |
|
||||
| `pnpm run develop` | Starts the freeCodeCamp API Server and Client Applications. |
|
||||
| `pnpm run clean` | Uninstalls all dependencies and cleans up caches. |
|
||||
|
||||
@@ -136,29 +136,41 @@ Le soluzioni sono usate dai test CI per assicurarsi che i cambiamenti alla sezio
|
||||
// terza soluzione ecc. - La tua soluzione deve essere in HTML.
|
||||
```
|
||||
|
||||
# --assignments--
|
||||
|
||||
This will show a checkbox that campers have to check before completing a challenge
|
||||
|
||||
---
|
||||
|
||||
This will show another checkbox that campers have to check before completing a challenge
|
||||
|
||||
# --question--
|
||||
|
||||
Questi campi sono usati attualmente per le domande a scelta multipla nelle sfide di Python.
|
||||
These fields are currently used for the multiple-choice Python challenges.
|
||||
|
||||
## --text--
|
||||
|
||||
Il testo della domanda va qui.
|
||||
The question text goes here.
|
||||
|
||||
## --answers--
|
||||
|
||||
Risposta 1
|
||||
Answer 1
|
||||
|
||||
### --feedback--
|
||||
|
||||
This will be shown as feedback when campers guess this answer
|
||||
|
||||
---
|
||||
|
||||
Risposta 2
|
||||
Answer 2
|
||||
|
||||
---
|
||||
|
||||
Altre risposte
|
||||
More answers
|
||||
|
||||
## --video-solution--
|
||||
|
||||
Il numero della risposta corretta va qui.
|
||||
The number for the correct answer goes here.
|
||||
````
|
||||
|
||||
> [!NOTE]
|
||||
@@ -192,7 +204,7 @@ ObjectId("5a474d78df58bafeb3535d34")
|
||||
|
||||
The result is a new id, for example, `5a474d78df58bafeb3535d34` above.
|
||||
|
||||
Una volta che hai il tuo id, mettilo nel file markdown nel campo `id` in cima, per esempio
|
||||
Once you have your id, put it into the markdown file as the `id` field at the top, e.g.
|
||||
|
||||
```yml
|
||||
---
|
||||
@@ -202,13 +214,13 @@ title: Challenge Title
|
||||
|
||||
## Dare un nome alle sfide
|
||||
|
||||
Dare un nome alle cose è difficile. Lo abbiamo reso più semplice dando dei limiti.
|
||||
Naming things is hard. We've made it easier by imposing some constraints.
|
||||
|
||||
Tutti i titoli delle sfide devono essere espliciti e seguire questo schema:
|
||||
All challenge titles should be explicit and should follow this pattern:
|
||||
|
||||
\[verb\]\[clausola oggetto\]
|
||||
\[verb\]\[object clause\]
|
||||
|
||||
Ecco alcuni esempi di nomi di sfide:
|
||||
Here are some example challenge names:
|
||||
|
||||
- Usare la notazione in senso orario per specificare il padding di un elemento
|
||||
- Condensare array usando .reduce
|
||||
@@ -216,48 +228,48 @@ Ecco alcuni esempi di nomi di sfide:
|
||||
|
||||
## Istruzioni e descrizione di una sfida
|
||||
|
||||
Le frasi dovrebbero essere chiare e concise con minimo utilizzo di linguaggio tecnico. Se il linguaggio tecnico è usato, deve essere subito seguito da una definizione in linguaggio comune.
|
||||
Sentences should be clear and concise with minimal jargon. If used, jargon should be immediately defined in plain English.
|
||||
|
||||
I paragrafi devono essere corti (1-4 frasi circa). È più probabile che vengano lette alcune frasi corte invece di un muro di testo.
|
||||
Keep paragraphs short (around 1-4 sentences). People are more likely to read several short paragraphs than a wall of text.
|
||||
|
||||
Il testo della sfida dovrebbe usare la seconda persona ("tu") per aiutare ad avere un tono colloquiale. In questo modo il testo e le istruzioni sembrano parlare direttamente al camper che lavora sulle sfide. Cerca di evitare la prima persona ("io", "noi", "facciamo").
|
||||
Challenge text should use the second person ("you") to help to give it a conversational tone. This way the text and instructions seem to speak directly to the camper working through the challenge. Try to avoid using the first person ("I", "we", "let's", and "us").
|
||||
|
||||
Non usare link a siti esterni. Questi interrompono il flusso. I camper non dovrebbero mai cercare qualcosa su Google durante queste sfide. Se ci sono risorse di cui pensi che il camper possa beneficiare, aggiungile all'articolo della sfida nella guida.
|
||||
Don't use outbound links. These interrupt the flow. Campers should never have to google anything during these challenges. If there are resources you think campers would benefit from, add them to the challenge's Guide-related article.
|
||||
|
||||
Puoi aggiugere diagrammi se necessario.
|
||||
You can add diagrams if necessary.
|
||||
|
||||
Non usare emoji o emoticon nelle sfide. freeCodeCamp ha una comunità globale, e il significato culturare di una emoji o emoticon può essere differente nelle varie parti del mondo. In più, le emoji possono avere un aspetto diverso su diversi sistemi.
|
||||
Don't use emojis or emoticons in challenges. freeCodeCamp has a global community, and the cultural meaning of an emoji or emoticon may be different around the world. Also, emojis can render differently on different systems.
|
||||
|
||||
I nomi propri dovrebbero usare le maiuscole correttamente quando possibile. Qui sotto trovi una lista di parole come dovrebbero apparire nelle sfide.
|
||||
Proper nouns should use correct capitalization when possible. Below is a list of words as they should appear in the challenges.
|
||||
|
||||
- JavaScript (lettere maiuscole in "J" e "S" e senza abbreviazioni)
|
||||
- Node.js
|
||||
- Anche se a volte inaccurate, le forme senza trattino di "back end" e "front end" dovrebbero essere usate, poiché sono le forme più comuni.
|
||||
|
||||
### La regola dei due minuti
|
||||
### The 2-minute rule
|
||||
|
||||
Ogni sfida dovrebbe essere risolvibile entro 120 secondi da un nativo inglese che ha completato tutte le sfide precedenti. Questo include l'ammontare di tempo necessario a leggere le istruzioni, comprendere il codice di partenza, scrivere il loro codice e avere tutti i test superati.
|
||||
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.
|
||||
|
||||
Se servono più di due minuti a completare la sfida hai due possibilità:
|
||||
If it takes longer than two minutes to complete the challenge, you have two options:
|
||||
|
||||
- Semplificare la sfida, o
|
||||
- Dividere la sfida in due sfide.
|
||||
|
||||
The 2-minute rule forces you, the challenge designer, to make your directions concise, your seed code clear, and your tests straightforward.
|
||||
|
||||
Teniamo traccia di quanto tempo serve agli utenti per risolvere le sfide e usiamo questa informazione per identificare sfide che devono essere semplificate o divise.
|
||||
We track how long it takes for campers to solve challenges and use this information to identify challenges that need to be simplified or split.
|
||||
|
||||
### Modularità
|
||||
### Modularity
|
||||
|
||||
Ogni sfida dovrebbe insegnare esattamente un concetto, e quel concetto dovrebbe apparire nel titolo della sfida.
|
||||
Each challenge should teach exactly one concept, and that concept should be apparent from the challenge's name.
|
||||
|
||||
Possiamo rinforzare concetti introdotti in precedenza tramite ripetizione e variazioni, per esempio introducendo gli elementi h1 in una sfida e gli elementi h3 alcune sfide più tardi.
|
||||
We can reinforce previously covered concepts through repetition and variations - for example, introducing h1 elements in one challenge, then h3 elements a few challenges later.
|
||||
|
||||
Il nostro obbiettivo è di avere migliaia di sfide da due minuti. Queste possono scorrere insieme e rinforzare concetti già introdotti in precedenza.
|
||||
Our goal is to have thousands of 2-minute challenges. These can flow together and reiterate previously-covered concepts.
|
||||
|
||||
### Formattare il testo delle sfide
|
||||
### Formatting challenge text
|
||||
|
||||
Ecco le linee guidee di formattazione specifiche per il testo delle sfide e degli esempi:
|
||||
Here are specific formatting guidelines for challenge text and examples:
|
||||
|
||||
- Le parole chiave del linguaggio vanno in `` \` `` backtick. Per esempio i nomi dei tag HTML o i nomi delle proprietà CSS.
|
||||
- Riferimenti a parti di codice (come nomi di funzioni, metodi o variabili) dovrebbero essere in `` \` `` backtick. Vedi gli esempi seguenti:
|
||||
@@ -270,9 +282,9 @@ Usa `parseInt` per convertire la variabile `realNumber` a un numero intero.
|
||||
- I blocchi di codice multi-riga **devono essere preceduti da una riga vuota**. La riga successiva deve iniziare con tre backticks seguiti immediatamente da uno dei [linguaggi supportati](https://prismjs.com/#supported-languages). To complete the code block, you must start a new line that only has three backticks and **another empty line**. Vedi l'esempio seguente:
|
||||
- Gli spazi bianchi hanno significato in Markdown, raccomandiamo di renderli visibili nel tuo editor.
|
||||
|
||||
**Nota:** Se devi usare un esempio di codice in YAML, usa `yaml` invece di `yml` per il linguaggio a fianco dei tre backtick.
|
||||
**Note:** If you are going to use an example code in YAML, use `yaml` instead of `yml` for the language to the right of the backticks.
|
||||
|
||||
Il seguente è un esempio di codice:
|
||||
The following is an example of code:
|
||||
|
||||
````md
|
||||
```{language}
|
||||
@@ -316,13 +328,13 @@ Example of a valid single-line JavaScript comment:
|
||||
// Only change code below this line
|
||||
````
|
||||
|
||||
Esempio di un commento CSS valido:
|
||||
Example of a valid CSS comment:
|
||||
|
||||
```css
|
||||
/* Only change code above this line */
|
||||
```
|
||||
|
||||
Se la sfida ha un unico punto dove il codice ha bisogno di cambiamenti, per favore usa i commenti nel seguente esempio per istruire l'utente su dove dovrebbe fare i cambiamenti.
|
||||
If a challenge only has a single place where code changes are needed, please use the comments in the following example to instruct the user where changes should be made.
|
||||
|
||||
```js
|
||||
var a = 3;
|
||||
@@ -335,7 +347,7 @@ b = 9 + b;
|
||||
c = c + 7;
|
||||
```
|
||||
|
||||
Se la sfida ha diversi punti dove l'utente deve fare cambiamenti al codice (come in una sfida React)
|
||||
If a challenge has multiple places where the user is expected to change code (i.e. the React challenges)
|
||||
|
||||
```jsx
|
||||
class MyComponent extends React.Component {
|
||||
@@ -368,9 +380,9 @@ class MyComponent extends React.Component {
|
||||
|
||||
### Translation of Seed Code Comments
|
||||
|
||||
Ci sono directory separate per ogni lingua. La [versione inglese della directory dei commenti](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/dictionaries/english/comments.json) è la base per le traduzioni trovate nelle corrispondenti versioni non-inglesi del file. La versione non-inglese della directory dei commenti cinese si trova in `/curriculum/dictionaries/chinese/comments.json`. Ogni directory consiste di un array di oggetti con una proprietà `id` unica e una proprietà `text` che contiene il testo del commento. Solo `text` dovrebbe essere modificato per includere la traduzione del corrispondente commento inglese.
|
||||
There are separate comment dictionaries for each language. The [English version of the comment dictionary](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/dictionaries/english/comments.json) 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.json`. 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.
|
||||
|
||||
Alcuni commenti potrebbero contenere delle parole o frasi che non devono essere tradotte. Per esempio, nomi di variabili o nomi propri di librerie come "React" non dovrebbero essere tradotti. Vedi il commento seguente come esempio. La parola `myGlobal` non deve essere tradotta.
|
||||
Some comments may contain a word/phrase that should not be translated. For example, variable names or proper library names like "React" should not be translated. See the comment below as an example. The word `myGlobal` should not be translated.
|
||||
|
||||
```text
|
||||
Declare the myGlobal variable below this line
|
||||
@@ -382,11 +394,11 @@ Declare the myGlobal variable below this line
|
||||
|
||||
## Suggerimenti e soluzioni
|
||||
|
||||
Ogni sfida ha un pulsante `Get a Hint` (Ottieni un suggerimento), cosicché un utente possa avere accesso a suggerimenti e soluzioni che sono stati creati per la sfida. I suggerimenti e le soluzioni del curriculum si trovano nei topic [del nostro forum](https://forum.freecodecamp.org/c/guide) nella categoria `Guide`.
|
||||
Each challenge has a `Get a Hint` button, so a user can access any hints/solutions which have been created for the challenge. Curriculum hints/solutions topics are located on [our forum](https://forum.freecodecamp.org/c/guide) under the `Guide` category.
|
||||
|
||||
Se trovi un problema con i suggerimenti e le soluzioni delle sfide puoi inviare i tuoi suggerimenti aprendo un topic nella [categoria contributors](https://forum.freecodecamp.org/c/contributors) sul forum. Moderatori e utenti con un livello di fiducia 3 rivedranno i tuoi commenti e decideranno se includere o meno i cambiamenti nel topic corrispondente.
|
||||
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.
|
||||
|
||||
### Aggiungere nuovi topic per i suggerimenti e le soluzioni delle sfide
|
||||
### Adding new Challenge hints/solutions Topics
|
||||
|
||||
Take the following steps when adding a new challenge hints/solutions-related topic.
|
||||
|
||||
@@ -397,7 +409,7 @@ Take the following steps when adding a new challenge hints/solutions-related top
|
||||
|
||||
### 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. Questo include sia il codice seed originale sia i cambiamenti necessari per superare i test. Dovresti usare il seguente template per creare nuovi topic per suggerimenti e soluzioni:
|
||||
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:
|
||||
|
||||
````md
|
||||
# [Qui il nome della sfida]
|
||||
|
||||
@@ -4,7 +4,7 @@ Ignoring these steps may soil your copy which makes the contributing, maintainin
|
||||
|
||||
## Contributing to the Codebase
|
||||
|
||||
You can now make changes to files and commit your changes to your fork, which you can prepare by reading [how to set up freecodecamp](how-to-setup-freecodecamp-locally.md).
|
||||
You can now make changes to files and commit your changes to your fork, which you can prepare by reading [how to set up freeCodeCamp locally](how-to-setup-freecodecamp-locally.md).
|
||||
|
||||
Follow these steps:
|
||||
|
||||
|
||||
@@ -246,10 +246,11 @@ Next, let's seed the database. In this step, we run the below command that fills
|
||||
pnpm run seed
|
||||
```
|
||||
|
||||
By default, you will be signed in as a new user without any completed certifications. Run the following command if you need to develop with completed certifications:
|
||||
By default, you will be signed in as a new user without any completed certifications. Run the following commands if you need to develop with completed certifications:
|
||||
|
||||
```console
|
||||
pnpm run seed:certified-user
|
||||
pnpm run seed:exams
|
||||
```
|
||||
|
||||
> [!WARNING] Running `pnpm run seed:certified-user` will log you out. You will have to clear your browser cookies and sign in again.
|
||||
@@ -283,5 +284,6 @@ A quick reference to the commands that you will need when working locally.
|
||||
| `pnpm install` | Installs / re-installs all dependencies and bootstraps the different services. |
|
||||
| `pnpm run seed` | Creates authorized test users and inserts them into MongoDB. |
|
||||
| `pnpm run seed:certified-user` | Creates authorized test users with certifications fully completed, and inserts them into MongoDB. |
|
||||
| `pnpm run seed:exams` | Creates exams and inserts them into MongoDB. |
|
||||
| `pnpm run develop` | Starts the freeCodeCamp API Server and Client Applications. |
|
||||
| `pnpm run clean` | Uninstalls all dependencies and cleans up caches. |
|
||||
|
||||
@@ -136,29 +136,41 @@ console.log('freeCodeCamp is awesome!');
|
||||
// 3番目のソリューション等 - ソリューションは HTML でなければなりません。
|
||||
```
|
||||
|
||||
# --assignments--
|
||||
|
||||
This will show a checkbox that campers have to check before completing a challenge
|
||||
|
||||
---
|
||||
|
||||
This will show another checkbox that campers have to check before completing a challenge
|
||||
|
||||
# --question--
|
||||
|
||||
現在、このフィールドは多肢選択式 Python チャレンジ用に使用されています。
|
||||
These fields are currently used for the multiple-choice Python challenges.
|
||||
|
||||
## --text--
|
||||
|
||||
質問のテキストをここに記述します。
|
||||
The question text goes here.
|
||||
|
||||
## --answers--
|
||||
|
||||
回答 1
|
||||
Answer 1
|
||||
|
||||
### --feedback--
|
||||
|
||||
This will be shown as feedback when campers guess this answer
|
||||
|
||||
---
|
||||
|
||||
回答 2
|
||||
Answer 2
|
||||
|
||||
---
|
||||
|
||||
他の回答
|
||||
More answers
|
||||
|
||||
## --video-solution--
|
||||
|
||||
正解の番号をここに記述します。
|
||||
The number for the correct answer goes here.
|
||||
````
|
||||
|
||||
> [!NOTE]
|
||||
@@ -192,7 +204,7 @@ ObjectId("5a474d78df58bafeb3535d34")
|
||||
|
||||
The result is a new id, for example, `5a474d78df58bafeb3535d34` above.
|
||||
|
||||
id を取得したら、上部の `id` フィールドとしてマークダウンファイルに入れてください。例えば、次のようになります。
|
||||
Once you have your id, put it into the markdown file as the `id` field at the top, e.g.
|
||||
|
||||
```yml
|
||||
---
|
||||
@@ -202,13 +214,13 @@ title: Challenge Title
|
||||
|
||||
## チャレンジ名の決定
|
||||
|
||||
チャレンジ名を決めるのは難しいです。 しかし、いくつかの制約を課すことで簡単になります。
|
||||
Naming things is hard. We've made it easier by imposing some constraints.
|
||||
|
||||
すべてのチャレンジタイトルは明示的でなければなりません。そして、以下のパターンに従う必要があります。
|
||||
All challenge titles should be explicit and should follow this pattern:
|
||||
|
||||
\[動詞\]\[目的語 (節)\]
|
||||
\[verb\]\[object clause\]
|
||||
|
||||
チャレンジ名の例を以下に示します。
|
||||
Here are some example challenge names:
|
||||
|
||||
- Use Clockwise Notation to Specify the Padding of an Element
|
||||
- Condense arrays with .reduce
|
||||
@@ -216,29 +228,29 @@ title: Challenge Title
|
||||
|
||||
## チャレンジの説明 / 指示
|
||||
|
||||
文章は最小限の専門用語で明確かつ簡潔にする必要があります。 専門用語を使用する場合、平易な英語で定義する必要があります。
|
||||
Sentences should be clear and concise with minimal jargon. If used, jargon should be immediately defined in plain English.
|
||||
|
||||
段落は短くしてください (1-4 文程度)。 多くの人にとって、長文よりもいくつかの短い段落のほうが読みやすいです。
|
||||
Keep paragraphs short (around 1-4 sentences). People are more likely to read several short paragraphs than a wall of text.
|
||||
|
||||
チャレンジテキストでは、会話調にするために二人称 ("you") を使用する必要があります。 これにより、チャレンジで作業しているキャンパーは、テキストと指示を通して直接話しかけられているように感じます。 一人称 ("I", "we", "let's", and "us") をできるだけ使用しないようにしてください。
|
||||
Challenge text should use the second person ("you") to help to give it a conversational tone. This way the text and instructions seem to speak directly to the camper working through the challenge. Try to avoid using the first person ("I", "we", "let's", and "us").
|
||||
|
||||
外部のサイトへのリンクは使用しないでください。 フローの妨げとなります。 チャレンジの間、キャンパーが Google で検索を行う必要がないようにしてください。 キャンパーが恩恵を受けると思われるリソースがある場合は、それらをチャレンジガイド関連記事に追加します。
|
||||
Don't use outbound links. These interrupt the flow. Campers should never have to google anything during these challenges. If there are resources you think campers would benefit from, add them to the challenge's Guide-related article.
|
||||
|
||||
必要に応じてダイアグラムを追加できます。
|
||||
You can add diagrams if necessary.
|
||||
|
||||
チャレンジに絵文字や顔文字を使用しないでください。 freeCodeCamp は、グローバルコミュニティを持っており、絵文字や顔文字の文化的意味は世界中で異なる場合があります。 また、絵文字は異なるシステムでは異なるレンダリングをします。
|
||||
Don't use emojis or emoticons in challenges. freeCodeCamp has a global community, and the cultural meaning of an emoji or emoticon may be different around the world. Also, emojis can render differently on different systems.
|
||||
|
||||
固有名詞は、極力正しい大文字表記を使用することが適切です。 以下は、チャレンジで表示される単語のリストです。
|
||||
Proper nouns should use correct capitalization when possible. Below is a list of words as they should appear in the challenges.
|
||||
|
||||
- JavaScript (「J」と「S」が大文字、省略形なし)
|
||||
- Node.js
|
||||
- 不正確な場合もありますが、より広く使われているため、ハイフンなしの 'back end' と 'front end' を使用します。
|
||||
|
||||
### 2 分ルール
|
||||
### The 2-minute rule
|
||||
|
||||
各チャレンジは、そこまでのチャレンジを完了した英語のネイティブスピーカーによって 120 秒以内に解決されるべきです。 これには、命令 / 指示を読み、シードされたコードを理解し、コードを書き、すべてのテストに合格するのにかかる時間が含まれます。
|
||||
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.
|
||||
|
||||
チャレンジを完了するのに 2 分以上かかる場合は、2 つの選択肢があります。
|
||||
If it takes longer than two minutes to complete the challenge, you have two options:
|
||||
|
||||
- チャレンジを簡素化する
|
||||
- チャレンジを 2 つのチャレンジに分ける
|
||||
@@ -247,17 +259,17 @@ The 2-minute rule forces you, the challenge designer, to make your directions co
|
||||
|
||||
We track how long it takes for campers to solve challenges and use this information to identify challenges that need to be simplified or split.
|
||||
|
||||
### モジュール化
|
||||
### Modularity
|
||||
|
||||
チャレンジごとに、1 つのコンセプトを教えるべきであり、そのコンセプトはチャレンジ名から明らかであるべきです。
|
||||
Each challenge should teach exactly one concept, and that concept should be apparent from the challenge's name.
|
||||
|
||||
繰り返しやバリエーションにより、以前学んだコンセプトを強化することができます。例えば、1 つのチャレンジに h1 要素を導入し、いくつかのチャレンジの後に h3 要素を導入します。
|
||||
We can reinforce previously covered concepts through repetition and variations - for example, introducing h1 elements in one challenge, then h3 elements a few challenges later.
|
||||
|
||||
私たちの目標は、数千個の 2 分間チャレンジを行うことです。 これらは同じフローであり、以前に網羅されたコンセプトを繰り返すことができます。
|
||||
Our goal is to have thousands of 2-minute challenges. These can flow together and reiterate previously-covered concepts.
|
||||
|
||||
### チャレンジテキストのフォーマット
|
||||
### Formatting challenge text
|
||||
|
||||
チャレンジテキストと例の具体的なフォーマットガイドラインは次のとおりです。
|
||||
Here are specific formatting guidelines for challenge text and examples:
|
||||
|
||||
- 言語キーワードは `` \` `` のバックティックに入ります。 例えば、HTML タグ名や CSS プロパティ名です。
|
||||
- コード部品 (すなわち、関数、メソッド、変数名) への参照は、`` \` `` バックティックで囲みます。 下記の例を参照してください。
|
||||
@@ -270,9 +282,9 @@ We track how long it takes for campers to solve challenges and use this informat
|
||||
- 複数行コードブロック **の前に空行** が必要です。 次の行は、3つのバックティックに続いて [対応言語](https://prismjs.com/#supported-languages) の1つで始まります。 To complete the code block, you must start a new line that only has three backticks and **another empty line**. 下記の例を参照してください。
|
||||
- 空白はマークダウンでも重要ですので、エディターで表示させることをお勧めします。
|
||||
|
||||
**注:** YMAL のコード例を使用する場合、バックティックの右側に記載する言語は、 `yml` ではなく `yaml` を使用してください。
|
||||
**Note:** If you are going to use an example code in YAML, use `yaml` instead of `yml` for the language to the right of the backticks.
|
||||
|
||||
以下はコードの例です。
|
||||
The following is an example of code:
|
||||
|
||||
````md
|
||||
```{language}
|
||||
@@ -316,13 +328,13 @@ Example of a valid single-line JavaScript comment:
|
||||
// Only change code below this line
|
||||
````
|
||||
|
||||
有効な CSS コメントの例は次のとおりです。
|
||||
Example of a valid CSS comment:
|
||||
|
||||
```css
|
||||
/* Only change code above this line */
|
||||
```
|
||||
|
||||
チャレンジに、コード変更が必要な場所が 1 つしかない場合、以下の例のコメントを使用してユーザーに変更を行うべき場所を指示してください。
|
||||
If a challenge only has a single place where code changes are needed, please use the comments in the following example to instruct the user where changes should be made.
|
||||
|
||||
```js
|
||||
var a = 3;
|
||||
@@ -335,7 +347,7 @@ b = 9 + b;
|
||||
c = c + 7;
|
||||
```
|
||||
|
||||
チャレンジに、ユーザがコード変更を行うべき場所が複数存在する場合 (例: React のチャレンジ) は、次のようになります。
|
||||
If a challenge has multiple places where the user is expected to change code (i.e. the React challenges)
|
||||
|
||||
```jsx
|
||||
class MyComponent extends React.Component {
|
||||
@@ -368,9 +380,9 @@ class MyComponent extends React.Component {
|
||||
|
||||
### Translation of Seed Code Comments
|
||||
|
||||
各言語には、個別のコメント辞書があります。 The [English version of the comment dictionary](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/dictionaries/english/comments.json) 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.json`. それぞれの辞書は一意の `id` プロパティと `text` プロパティを持つオブジェクトの配列で構成されています。 `text` のみ、対応する英語のコメントの翻訳を含むように変更する必要があります。
|
||||
There are separate comment dictionaries for each language. The [English version of the comment dictionary](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/dictionaries/english/comments.json) 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.json`. 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.
|
||||
|
||||
一部のコメントには、翻訳してはいけない単語 / フレーズが含まれています。 例えば、変数名や「React」のような固有ライブラリ名は翻訳しません。 例として以下のコメントをご覧ください。 `myGlobal` という単語は翻訳しません。
|
||||
Some comments may contain a word/phrase that should not be translated. For example, variable names or proper library names like "React" should not be translated. See the comment below as an example. The word `myGlobal` should not be translated.
|
||||
|
||||
```text
|
||||
この行の下に myGlobal 変数を宣言してください。
|
||||
@@ -382,11 +394,11 @@ class MyComponent extends React.Component {
|
||||
|
||||
## ヒントとソリューション
|
||||
|
||||
各チャレンジには `Get a Hing` ボタンがあり、ユーザーはチャレンジ用に作成されたヒント / ソリューションにアクセスできます。 カリキュラムヒント / ソリューショントピックは、`Guide` カテゴリの下の [フォーラム](https://forum.freecodecamp.org/c/guide) にあります。
|
||||
Each challenge has a `Get a Hint` button, so a user can access any hints/solutions which have been created for the challenge. Curriculum hints/solutions topics are located on [our forum](https://forum.freecodecamp.org/c/guide) under the `Guide` category.
|
||||
|
||||
既存のチャレンジのヒント / ソリューショントピックに関わる問題がある場合は、フォーラムの [contributors カテゴリ](https://forum.freecodecamp.org/c/contributors) で提案を行うことができます。 信頼レベル 3 のモデレーターとユーザーは、コメントをレビューし、対応するヒント / ソリューションのトピックに変更を含めるかどうかを決定します。
|
||||
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.
|
||||
|
||||
### 新しいチャレンジのヒント / ソリューションの追加
|
||||
### Adding new Challenge hints/solutions Topics
|
||||
|
||||
Take the following steps when adding a new challenge hints/solutions-related topic.
|
||||
|
||||
@@ -397,7 +409,7 @@ Take the following steps when adding a new challenge hints/solutions-related top
|
||||
|
||||
### 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. これには、すべての元のシードコードと、すべてのチャレンジテストに合格するために必要な変更が含まれています。 次のテンプレートは、新しいヒント / ソリューションのトピックを作成する際に使用する必要があります。
|
||||
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:
|
||||
|
||||
````md
|
||||
# ここにチャレンジ名を記述します。
|
||||
|
||||
@@ -4,7 +4,7 @@ Ignorar essas etapas pode causar problemas à sua cópia, o que dificulta os pro
|
||||
|
||||
## Contribuindo para a base de código
|
||||
|
||||
Agora, você pode fazer alterações nos arquivos e fazer o commit das alterações no seu fork, que você pode preparar lendo [Como configurar o freeCodeCamp](how-to-setup-freecodecamp-locally.md).
|
||||
Agora, você pode fazer alterações nos arquivos e fazer o commit das alterações no seu fork, que você pode preparar lendo [Como configurar o freeCodeCamp localmente](how-to-setup-freecodecamp-locally.md).
|
||||
|
||||
Siga estes passos:
|
||||
|
||||
|
||||
@@ -246,10 +246,11 @@ Em seguida, vamos criar o banco de dados. Nesta etapa, executamos o comando abai
|
||||
pnpm run seed
|
||||
```
|
||||
|
||||
Por padrão, você será conectado como um novo usuário sem nenhuma certificação concluída. Execute o seguinte comando se precisar desenvolver com certificados concluídos:
|
||||
Por padrão, você será conectado como um novo usuário sem nenhuma certificação concluída. Execute os seguintes comandos se precisar desenvolver com certificados concluídos:
|
||||
|
||||
```console
|
||||
pnpm run seed:certified-user
|
||||
pnpm run seed:exams
|
||||
```
|
||||
|
||||
> [!WARNING] Executar `pnpm run seed:certified-user` desconectará você. Você precisará limpar os cookies do seu navegador e fazer login novamente.
|
||||
@@ -283,5 +284,6 @@ Uma rápida referência aos comandos que você precisará ao trabalhar localment
|
||||
| `pnpm install` | Instala/reinstala todas as dependências e inicializa os diferentes serviços. |
|
||||
| `pnpm run seed` | Cria usuários de testes autorizados e os insere no MongoDB. |
|
||||
| `pnpm run seed:certified-user` | Cria usuários de testes autorizados com certificações totalmente completas e os insere no MongoDB. |
|
||||
| `pnpm run seed:exams` | Cria exames e os insere no MongoDB. |
|
||||
| `pnpm run develop` | Inicia o servidor de API freeCodeCamp e aplicativos Cliente. |
|
||||
| `pnpm run clean` | Desinstala todas as dependências e limpa os caches. |
|
||||
|
||||
@@ -136,18 +136,30 @@ Soluções são usadas para os testes CI a fim de garantir que mudanças nas dic
|
||||
// terceira solução etc. - Suas soluções devem estar em HTML.
|
||||
```
|
||||
|
||||
# --assignments--
|
||||
|
||||
Isto mostrará uma caixa de seleção que os campers precisam verificar antes de completar um desafio
|
||||
|
||||
---
|
||||
|
||||
Isto mostrará outra caixa de seleção que os campers precisam verificar antes de completar um desafio
|
||||
|
||||
# --question--
|
||||
|
||||
Esses espaços são utilizados geralmente para questões de múltipla escolha dos desafios de Python.
|
||||
|
||||
## --text--
|
||||
|
||||
O texto da questão vêm aqui.
|
||||
O texto da questão vem aqui.
|
||||
|
||||
## --answers--
|
||||
|
||||
Resposta 1
|
||||
|
||||
### --feedback--
|
||||
|
||||
Isto será exibido como feedback quando os campers adivinharem essa resposta
|
||||
|
||||
---
|
||||
|
||||
Resposta 2
|
||||
@@ -222,7 +234,7 @@ Mantenha os parágrafos curtos (em torno de 1-4 frases). É mais provável que a
|
||||
|
||||
O desafio de texto deve usar a segunda pessoa ("você") para ajudar a dar um tom coloquial. Dessa forma, o texto e as instruções parecem falar diretamente ao usuário freeCodeCamp que está resolvendo o desafio. Tente evitar usar a primeira pessoa ("eu", "nós", "vamos").
|
||||
|
||||
Não use links externos. Eles interrompem o fluxo. Os usuários do freeCodeCamp nunca devem precisar pesquisar nada no Google durante esses desafios. Se há recursos que você acha que os usuários irão se beneficiar, adicione-os no artigo relacionado ao guia do desafio.
|
||||
Não use links externos. Eles interrompem o fluxo. Os usuários do freeCodeCamp nunca devem precisar pesquisar nada no Google durante esses desafios. Se há recursos que você acha que os usuários aproveitarão, adicione-os no artigo relacionado ao guia do desafio.
|
||||
|
||||
Você pode adicionar diagramas se necessário.
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@
|
||||
|
||||
## Внесок до кодової бази
|
||||
|
||||
Тепер ви можете робити зміни у файлах та затверджувати їх у розгалуженнях, прочитавши [як налаштувати freeCodeCamp](how-to-setup-freecodecamp-locally.md).
|
||||
Тепер ви можете робити зміни у файлах та затверджувати їх у розгалуженнях, прочитавши [як налаштувати freeCodeCamp локально](how-to-setup-freecodecamp-locally.md).
|
||||
|
||||
Дотримуйтеся цих вказівок:
|
||||
|
||||
|
||||
@@ -246,10 +246,11 @@ mongod
|
||||
pnpm run seed
|
||||
```
|
||||
|
||||
Ви увійдете як новий користувач без будь-яких завершених сертифікацій за замовчуванням. Запустіть цю команду, якщо потрібні наявні виконані сертифікації:
|
||||
Ви увійдете як новий користувач без будь-яких завершених сертифікацій за замовчуванням. Запустіть ці команди, якщо потрібні наявні виконані сертифікації:
|
||||
|
||||
```console
|
||||
pnpm run seed:certified-user
|
||||
pnpm run seed:exams
|
||||
```
|
||||
|
||||
> [!WARNING] Якщо запустити `pnpm run seed:certified-user`, ви вийдете з облікового запису. Вам доведеться очистити cookies свого браузера та увійти знову.
|
||||
@@ -283,5 +284,6 @@ pnpm run develop
|
||||
| `pnpm install` | Встановлює/перевстановлює всі залежності та запускає різні служби. |
|
||||
| `pnpm run seed` | Створює авторизованих тестових користувачів і розміщує їх у MongoDB. |
|
||||
| `pnpm run seed:certified-user` | Створює автоматизованих тестових користувачів, які завершили сертифікації, і розміщує їх у MongoDB. |
|
||||
| `pnpm run seed:exams` | Створює екзамени та вставляє їх в MongoDB. |
|
||||
| `pnpm run develop` | Запускає сервер API та клієнтські програми freeCodeCamp. |
|
||||
| `pnpm run clean` | Видаляє всі залежності й очищає кеш. |
|
||||
|
||||
@@ -136,18 +136,30 @@ console.log('freeCodeCamp is awesome!');
|
||||
// третій розв’язок і т. д. - ваш розв’язок має бути на HTML.
|
||||
```
|
||||
|
||||
# --assignments--
|
||||
|
||||
Це покаже прапорець, де кемпери мають поставити галочку перед тим, як завершити завдання
|
||||
|
||||
---
|
||||
|
||||
Це покаже інший прапорець, де кемпери мають поставити галочку перед тим, як завершити завдання
|
||||
|
||||
# --question--
|
||||
|
||||
Наразі ці поля використовуються для завдань з Python з декількома варіантами відповіді.
|
||||
|
||||
## --text--
|
||||
|
||||
Текст запитання знаходиться тут.
|
||||
Запитання повинне бути тут.
|
||||
|
||||
## --answers--
|
||||
|
||||
Відповідь 1
|
||||
|
||||
### --feedback--
|
||||
|
||||
Тут буде зворотний зв’язок після того, як кемпери вгадають відповідь
|
||||
|
||||
---
|
||||
|
||||
Відповідь 2
|
||||
|
||||
Reference in New Issue
Block a user