10000 create markdown · ShMcK/coderoad-python-test@72803c0 · GitHub
[go: up one dir, main page]

Skip to content

Commit 72803c0

Browse files
committed
create markdown
0 parents  commit 72803c0

File tree

2 files changed

+37
-0
lines changed

2 files changed

+37
-0
lines changed

.gitignore

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
node_modules
2+ 10000
package-lock.json
3+
.DS_Store

TUTORIAL.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
# Insert Tutorial's Title here
2+
3+
Short description to be shown as a tutorial's subtitle
4+
5+
## L1 Put Level's title here
6+
7+
> Level's summary: a short description of the level's content in one line.
8+
9+
The level is identified and distributed following the regex:
10+
11+
```js
12+
/^(##\s(?<levelId>L\d+)\s(?<levelTitle>.*)\n*(>\s*(?<levelSummary>.*))?\n+(?<levelContent>[^]*))/;
13+
```
14+
15+
The Level can be split into steps or have no steps. Levels without steps are meant to be used as only informative content, for example: use a Level without steps at the end of the tutorial to congratulate the student and provide some additional related resources.
16+
17+
Tutorial's content. It can span through multiple paragraphs and use headers `####` and `#####`.
18+
19+
Steps are identified and their content described using the following regex:
20+
21+
```js
22+
/^(###\s(?<stepId>(?<levelId>L\d+)S\d+)\s(?<stepTitle>.*)\n+(?<stepContent>[^]*))/;
23+
```
24+
25+
The numbers identifying the levels and steps are irrelevant but keep in mind that they will be executed in order. A level with id `10` will be executed before another one with id `20` and so on. These `ids` should have a match in the configuration file (`coderoad.yaml`).
26+
27+
### L1S1 A step title (not being shown on the extension at this moment)
28+
29+
Short description of the step's purpose. Should be short and fit in one line
30+
31+
**Important**
32+
33+
1. Both level and step ids must have an entry with the same id on the configuration file;
34+
2. Step Ids are based on its level id. Any step from level `L234` must start with `L234S`, followed by the sequential digits.

0 commit comments

Comments
 (0)
0