You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2. An array of json objects with files, content, or images to be rendered within the katacoda step.
354
+
1. The title of the step.
355
+
2. An array of json objects with files, content, or images to be rendered within the Katacoda step. The use for this function is to display an image and some descriptive text. No Katacoda syntax is allowed in the files or the content!
356
356
3. (Optional) Path to the current directory where the user is located (relative to the workspace directory). Only needed if the directory is changed within this step.
357
357
#### example
358
-
nextKatacodaStep("Step title", [{ "file": "files/description.md" }, { "content": "This is just plain content." }, { "image": "files/image.png" }])
358
+
display("Step title", [{ "file": "files/description.asciidoc" }, { "content": "This is just plain content." }, { "image": "files/image.png" }])
359
359
360
360
#### Details
361
361
Available attributes in the json objects:
362
362
363
-
file: Path to a file whose content is to be displayed in the katacoda step (e.g. .md or .txt file).
364
-
content: Plain text to be displayed in the katacoda step.
365
-
image: Path to an image to be displayed in the katacoda step.
363
+
1. file: Path to a file whose content is to be displayed in the Katacoda step (e.g. .asciidoc or .txt file). The file should be following the formating of asciidoc files.
364
+
2. content: Plain text to be displayed in the Katacoda step. This Text should be following the formating of asciidoc files.
365
+
3. image: Path to an image to be displayed in the Katacoda step.
366
+
367
+
#### Formatting rules for content and .asciidoc or .txt files.
368
+
* You can add headers to structure your text. The generated headers are shown in the examples below. The headers should fit into the overall structure of the generated wiki so level 1 header are not allowed, but the other header can be used at your judgement.
369
+
* A list always needs an empty newline between the last row and the list.
370
+
* Use asciidoc style of links
371
+
372
+
#### examples
373
+
```
374
+
Existing header structure
375
+
= Level 1: tutorial title
376
+
== Level 2: subtitle
377
+
=== Level 3: prerequisites and learning goals
378
+
== Level 2: steptitle
379
+
=== Level 3: titles from functions
380
+
==== Level 4: subtitles from functions
381
+
== Level 2: conclusion
382
+
383
+
List:
384
+
This an unordered List (The empty line is necessary)
385
+
386
+
* First Item
387
+
* Second Item
388
+
389
+
Link:
390
+
The tutorials repository can be found https://github.com/devonfw-tutorials/tutorials/issues[here].
0 commit comments