chore(i18n,docs): update translations (#42606)
This commit is contained in:
@ -32,10 +32,10 @@ Before you work on the curriculum, you would need to set up some tooling to help
|
|||||||
### How to work on practice projects
|
### 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)
|
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
|
## Challenge Template
|
||||||
|
|
||||||
````md
|
````md
|
||||||
|
|
||||||
---
|
---
|
||||||
id: Unique identifier (alphanumerical, MongoDB_id)
|
id: Unique identifier (alphanumerical, MongoDB_id)
|
||||||
title: 'Challenge Title'
|
title: 'Challenge Title'
|
||||||
@ -49,9 +49,7 @@ forumTopicId: 12345
|
|||||||
Challenge description text, in markdown
|
Challenge description text, in markdown
|
||||||
|
|
||||||
```html
|
```html
|
||||||
<div>
|
<div>example code</div>
|
||||||
example code
|
|
||||||
</div>
|
|
||||||
````
|
````
|
||||||
|
|
||||||
# --instructions--
|
# --instructions--
|
||||||
@ -92,9 +90,7 @@ Boilerplate code to render to the editor. This section should only contain code
|
|||||||
|
|
||||||
```html
|
```html
|
||||||
<body>
|
<body>
|
||||||
<p class="main-text">
|
<p class="main-text">Hello world!</p>
|
||||||
Hello world!
|
|
||||||
</p>
|
|
||||||
</body>
|
</body>
|
||||||
```
|
```
|
||||||
|
|
||||||
@ -156,8 +152,6 @@ More answers
|
|||||||
## --video-solution--
|
## --video-solution--
|
||||||
|
|
||||||
The number for the correct answer goes here.
|
The number for the correct answer goes here.
|
||||||
|
|
||||||
|
|
||||||
````
|
````
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
@ -231,7 +225,7 @@ Proper nouns should use correct capitalization when possible. Below is a list of
|
|||||||
|
|
||||||
- JavaScript (capital letters in "J" and "S" and no abbreviations)
|
- JavaScript (capital letters in "J" and "S" and no abbreviations)
|
||||||
- Node.js
|
- Node.js
|
||||||
- Front-end development (adjective form with a dash) is when you're working on the front end (noun form with no dash). The same goes with "back end", "full stack", and many other compound terms.
|
- Although sometimes inaccurate, non-hyphenated forms of 'back end' and 'front end' should be used, as they are more widely used.
|
||||||
|
|
||||||
### The 2-minute rule
|
### The 2-minute rule
|
||||||
|
|
||||||
@ -260,9 +254,11 @@ Here are specific formatting guidelines for challenge text and examples:
|
|||||||
|
|
||||||
- Language keywords go in `` \` `` backticks. For example, HTML tag names or CSS property names.
|
- Language keywords go in `` \` `` backticks. For example, HTML tag names or CSS property names.
|
||||||
- References to code parts (i.e. function, method, or variable names) should be wrapped in `` \` `` backticks. See example below:
|
- References to code parts (i.e. function, method, or variable names) should be wrapped in `` \` `` backticks. See example below:
|
||||||
|
|
||||||
```md
|
```md
|
||||||
Use `parseInt` to convert the variable `realNumber` into an integer.
|
Use `parseInt` to convert the variable `realNumber` into an integer.
|
||||||
```
|
```
|
||||||
|
|
||||||
- References to file names and path directories (e.g. `package.json`, `src/components`) should be wrapped in `` \` `` backticks.
|
- References to file names and path directories (e.g. `package.json`, `src/components`) should be wrapped in `` \` `` backticks.
|
||||||
- Multi-line code blocks **must be preceded by an empty line**. The next line must start with three backticks followed immediately by one of the [supported languages](https://prismjs.com/#supported-languages). To complete the code block, you must start a new line which only has three backticks and **another empty line**. See example below:
|
- Multi-line code blocks **must be preceded by an empty line**. The next line must start with three backticks followed immediately by one of the [supported languages](https://prismjs.com/#supported-languages). To complete the code block, you must start a new line which only has three backticks and **another empty line**. See example below:
|
||||||
- Whitespace matters in Markdown, so we recommend that you make it visible in your editor.
|
- Whitespace matters in Markdown, so we recommend that you make it visible in your editor.
|
||||||
@ -270,6 +266,7 @@ Use `parseInt` to convert the variable `realNumber` into an integer.
|
|||||||
**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.
|
**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:
|
The following is an example of code:
|
||||||
|
|
||||||
````md
|
````md
|
||||||
```{language}
|
```{language}
|
||||||
|
|
||||||
@ -338,7 +335,7 @@ class MyComponent extends React.Component {
|
|||||||
constructor(props) {
|
constructor(props) {
|
||||||
super(props);
|
super(props);
|
||||||
this.state = {
|
this.state = {
|
||||||
text: "Hello"
|
text: 'Hello'
|
||||||
};
|
};
|
||||||
// Change code below this line
|
// Change code below this line
|
||||||
|
|
||||||
@ -346,20 +343,20 @@ class MyComponent extends React.Component {
|
|||||||
}
|
}
|
||||||
handleClick() {
|
handleClick() {
|
||||||
this.setState({
|
this.setState({
|
||||||
text: "You clicked!"
|
text: 'You clicked!'
|
||||||
});
|
});
|
||||||
}
|
}
|
||||||
render() {
|
render() {
|
||||||
return (
|
return (
|
||||||
<div>
|
<div>
|
||||||
{ /* Change code below this line */ }
|
{/* Change code below this line */}
|
||||||
<button>Click Me</button>
|
<button>Click Me</button>
|
||||||
{ /* Change code above this line */ }
|
{/* Change code above this line */}
|
||||||
<h1>{this.state.text}</h1>
|
<h1>{this.state.text}</h1>
|
||||||
</div>
|
</div>
|
||||||
);
|
);
|
||||||
}
|
}
|
||||||
};
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
### Translation of seed code comments
|
### Translation of seed code comments
|
||||||
@ -371,6 +368,7 @@ Some comments may contain a word/phrase that should not be translated. For examp
|
|||||||
```text
|
```text
|
||||||
Declare the myGlobal variable below this line
|
Declare the myGlobal variable below this line
|
||||||
```
|
```
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
>
|
>
|
||||||
> We are working on an integration to make it possible to work on i18n for the comment dictionary.
|
> We are working on an integration to make it possible to work on i18n for the comment dictionary.
|
||||||
|
@ -32,10 +32,10 @@ Antes de trabajar en el plan de estudios, necesitarás configurar algunas herram
|
|||||||
### How to work on practice projects
|
### 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)
|
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
|
## Plantilla de desafío
|
||||||
|
|
||||||
````md
|
````md
|
||||||
|
|
||||||
---
|
---
|
||||||
id: Unique identifier (alphanumerical, MongoDB_id)
|
id: Unique identifier (alphanumerical, MongoDB_id)
|
||||||
title: 'Challenge Title'
|
title: 'Challenge Title'
|
||||||
@ -49,9 +49,7 @@ forumTopicId: 12345
|
|||||||
Challenge description text, in markdown
|
Challenge description text, in markdown
|
||||||
|
|
||||||
```html
|
```html
|
||||||
<div>
|
<div>example code</div>
|
||||||
example code
|
|
||||||
</div>
|
|
||||||
````
|
````
|
||||||
|
|
||||||
# --instructions--
|
# --instructions--
|
||||||
@ -92,9 +90,7 @@ Boilerplate code to render to the editor. This section should only contain code
|
|||||||
|
|
||||||
```html
|
```html
|
||||||
<body>
|
<body>
|
||||||
<p class="main-text">
|
<p class="main-text">Hello world!</p>
|
||||||
Hello world!
|
|
||||||
</p>
|
|
||||||
</body>
|
</body>
|
||||||
```
|
```
|
||||||
|
|
||||||
@ -156,8 +152,6 @@ More answers
|
|||||||
## --video-solution--
|
## --video-solution--
|
||||||
|
|
||||||
The number for the correct answer goes here.
|
The number for the correct answer goes here.
|
||||||
|
|
||||||
|
|
||||||
````
|
````
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
@ -231,7 +225,7 @@ Proper nouns should use correct capitalization when possible. Below is a list of
|
|||||||
|
|
||||||
- JavaScript (mayúsculas en "J" y "S" y sin abreviaturas)
|
- JavaScript (mayúsculas en "J" y "S" y sin abreviaturas)
|
||||||
- Node.js
|
- 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.
|
- Although sometimes inaccurate, non-hyphenated forms of 'back end' and 'front end' should be used, as they are more widely used.
|
||||||
|
|
||||||
### The 2-minute rule
|
### The 2-minute rule
|
||||||
|
|
||||||
@ -260,9 +254,11 @@ Here are specific formatting guidelines for challenge text and examples:
|
|||||||
|
|
||||||
- Language keywords go in `` \` `` backticks. For example, HTML tag names or CSS property names.
|
- Language keywords go in `` \` `` backticks. For example, HTML tag names or CSS property names.
|
||||||
- References to code parts (i.e. function, method, or variable names) should be wrapped in `` \` `` backticks. See example below:
|
- References to code parts (i.e. function, method, or variable names) should be wrapped in `` \` `` backticks. See example below:
|
||||||
|
|
||||||
```md
|
```md
|
||||||
Use `parseInt` to convert the variable `realNumber` into an integer.
|
Use `parseInt` to convert the variable `realNumber` into an integer.
|
||||||
```
|
```
|
||||||
|
|
||||||
- References to file names and path directories (e.g. `package.json`, `src/components`) should be wrapped in `` \` `` backticks.
|
- References to file names and path directories (e.g. `package.json`, `src/components`) should be wrapped in `` \` `` backticks.
|
||||||
- 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 which only has three backticks and **another empty line**. Ver el ejemplo a continuación:
|
- 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 which only has three backticks and **another empty line**. Ver el ejemplo a continuación:
|
||||||
- Whitespace matters in Markdown, so we recommend that you make it visible in your editor.
|
- Whitespace matters in Markdown, so we recommend that you make it visible in your editor.
|
||||||
@ -270,6 +266,7 @@ Use `parseInt` to convert the variable `realNumber` into an integer.
|
|||||||
**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.
|
**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:
|
The following is an example of code:
|
||||||
|
|
||||||
````md
|
````md
|
||||||
```{language}
|
```{language}
|
||||||
|
|
||||||
@ -338,7 +335,7 @@ class MyComponent extends React.Component {
|
|||||||
constructor(props) {
|
constructor(props) {
|
||||||
super(props);
|
super(props);
|
||||||
this.state = {
|
this.state = {
|
||||||
text: "Hello"
|
text: 'Hello'
|
||||||
};
|
};
|
||||||
// Change code below this line
|
// Change code below this line
|
||||||
|
|
||||||
@ -346,20 +343,20 @@ class MyComponent extends React.Component {
|
|||||||
}
|
}
|
||||||
handleClick() {
|
handleClick() {
|
||||||
this.setState({
|
this.setState({
|
||||||
text: "You clicked!"
|
text: 'You clicked!'
|
||||||
});
|
});
|
||||||
}
|
}
|
||||||
render() {
|
render() {
|
||||||
return (
|
return (
|
||||||
<div>
|
<div>
|
||||||
{ /* Change code below this line */ }
|
{/* Change code below this line */}
|
||||||
<button>Click Me</button>
|
<button>Click Me</button>
|
||||||
{ /* Change code above this line */ }
|
{/* Change code above this line */}
|
||||||
<h1>{this.state.text}</h1>
|
<h1>{this.state.text}</h1>
|
||||||
</div>
|
</div>
|
||||||
);
|
);
|
||||||
}
|
}
|
||||||
};
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
### Translation of seed code comments
|
### Translation of seed code comments
|
||||||
@ -371,6 +368,7 @@ Some comments may contain a word/phrase that should not be translated. For examp
|
|||||||
```text
|
```text
|
||||||
Declare the myGlobal variable below this line
|
Declare the myGlobal variable below this line
|
||||||
```
|
```
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
>
|
>
|
||||||
> Estamos trabajando en una integración que permita trabajar en i18n para el diccionario de comentarios.
|
> Estamos trabajando en una integración que permita trabajar en i18n para el diccionario de comentarios.
|
||||||
|
@ -32,10 +32,10 @@ Before you work on the curriculum, you would need to set up some tooling to help
|
|||||||
### How to work on practice projects
|
### 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)
|
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
|
## Challenge Template
|
||||||
|
|
||||||
````md
|
````md
|
||||||
|
|
||||||
---
|
---
|
||||||
id: Unique identifier (alphanumerical, MongoDB_id)
|
id: Unique identifier (alphanumerical, MongoDB_id)
|
||||||
title: 'Challenge Title'
|
title: 'Challenge Title'
|
||||||
@ -49,9 +49,7 @@ forumTopicId: 12345
|
|||||||
Challenge description text, in markdown
|
Challenge description text, in markdown
|
||||||
|
|
||||||
```html
|
```html
|
||||||
<div>
|
<div>example code</div>
|
||||||
example code
|
|
||||||
</div>
|
|
||||||
````
|
````
|
||||||
|
|
||||||
# --instructions--
|
# --instructions--
|
||||||
@ -92,9 +90,7 @@ Boilerplate code to render to the editor. This section should only contain code
|
|||||||
|
|
||||||
```html
|
```html
|
||||||
<body>
|
<body>
|
||||||
<p class="main-text">
|
<p class="main-text">Hello world!</p>
|
||||||
Hello world!
|
|
||||||
</p>
|
|
||||||
</body>
|
</body>
|
||||||
```
|
```
|
||||||
|
|
||||||
@ -156,8 +152,6 @@ More answers
|
|||||||
## --video-solution--
|
## --video-solution--
|
||||||
|
|
||||||
The number for the correct answer goes here.
|
The number for the correct answer goes here.
|
||||||
|
|
||||||
|
|
||||||
````
|
````
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
@ -231,7 +225,7 @@ Proper nouns should use correct capitalization when possible. Below is a list of
|
|||||||
|
|
||||||
- JavaScript (capital letters in "J" and "S" and no abbreviations)
|
- JavaScript (capital letters in "J" and "S" and no abbreviations)
|
||||||
- Node.js
|
- Node.js
|
||||||
- Front-end development (adjective form with a dash) is when you're working on the front end (noun form with no dash). The same goes with "back end", "full stack", and many other compound terms.
|
- Although sometimes inaccurate, non-hyphenated forms of 'back end' and 'front end' should be used, as they are more widely used.
|
||||||
|
|
||||||
### The 2-minute rule
|
### The 2-minute rule
|
||||||
|
|
||||||
@ -260,9 +254,11 @@ Here are specific formatting guidelines for challenge text and examples:
|
|||||||
|
|
||||||
- Language keywords go in `` \` `` backticks. For example, HTML tag names or CSS property names.
|
- Language keywords go in `` \` `` backticks. For example, HTML tag names or CSS property names.
|
||||||
- References to code parts (i.e. function, method, or variable names) should be wrapped in `` \` `` backticks. See example below:
|
- References to code parts (i.e. function, method, or variable names) should be wrapped in `` \` `` backticks. See example below:
|
||||||
|
|
||||||
```md
|
```md
|
||||||
Use `parseInt` to convert the variable `realNumber` into an integer.
|
Use `parseInt` to convert the variable `realNumber` into an integer.
|
||||||
```
|
```
|
||||||
|
|
||||||
- References to file names and path directories (e.g. `package.json`, `src/components`) should be wrapped in `` \` `` backticks.
|
- References to file names and path directories (e.g. `package.json`, `src/components`) should be wrapped in `` \` `` backticks.
|
||||||
- Multi-line code blocks **must be preceded by an empty line**. The next line must start with three backticks followed immediately by one of the [supported languages](https://prismjs.com/#supported-languages). To complete the code block, you must start a new line which only has three backticks and **another empty line**. See example below:
|
- Multi-line code blocks **must be preceded by an empty line**. The next line must start with three backticks followed immediately by one of the [supported languages](https://prismjs.com/#supported-languages). To complete the code block, you must start a new line which only has three backticks and **another empty line**. See example below:
|
||||||
- Whitespace matters in Markdown, so we recommend that you make it visible in your editor.
|
- Whitespace matters in Markdown, so we recommend that you make it visible in your editor.
|
||||||
@ -270,6 +266,7 @@ Use `parseInt` to convert the variable `realNumber` into an integer.
|
|||||||
**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.
|
**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:
|
The following is an example of code:
|
||||||
|
|
||||||
````md
|
````md
|
||||||
```{language}
|
```{language}
|
||||||
|
|
||||||
@ -338,7 +335,7 @@ class MyComponent extends React.Component {
|
|||||||
constructor(props) {
|
constructor(props) {
|
||||||
super(props);
|
super(props);
|
||||||
this.state = {
|
this.state = {
|
||||||
text: "Hello"
|
text: 'Hello'
|
||||||
};
|
};
|
||||||
// Change code below this line
|
// Change code below this line
|
||||||
|
|
||||||
@ -346,20 +343,20 @@ class MyComponent extends React.Component {
|
|||||||
}
|
}
|
||||||
handleClick() {
|
handleClick() {
|
||||||
this.setState({
|
this.setState({
|
||||||
text: "You clicked!"
|
text: 'You clicked!'
|
||||||
});
|
});
|
||||||
}
|
}
|
||||||
render() {
|
render() {
|
||||||
return (
|
return (
|
||||||
<div>
|
<div>
|
||||||
{ /* Change code below this line */ }
|
{/* Change code below this line */}
|
||||||
<button>Click Me</button>
|
<button>Click Me</button>
|
||||||
{ /* Change code above this line */ }
|
{/* Change code above this line */}
|
||||||
<h1>{this.state.text}</h1>
|
<h1>{this.state.text}</h1>
|
||||||
</div>
|
</div>
|
||||||
);
|
);
|
||||||
}
|
}
|
||||||
};
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
### Translation of seed code comments
|
### Translation of seed code comments
|
||||||
@ -371,6 +368,7 @@ Some comments may contain a word/phrase that should not be translated. For examp
|
|||||||
```text
|
```text
|
||||||
Declare the myGlobal variable below this line
|
Declare the myGlobal variable below this line
|
||||||
```
|
```
|
||||||
|
|
||||||
> [!NOTE]
|
> [!NOTE]
|
||||||
>
|
>
|
||||||
> We are working on an integration to make it possible to work on i18n for the comment dictionary.
|
> We are working on an integration to make it possible to work on i18n for the comment dictionary.
|
||||||
|
Reference in New Issue
Block a user