20 Chapter Page Template
Introduction goes here.
20.1 Section
First section. One sentence per line. Emphasis should be with italics via underscores
New paragraph through a line break above.
Lists can be rendered with hyphens as bullets, and 4 spaces for sub-bullets:
- Bullet 1
- Bullet 2
- Sub-bullet 1
- Sub-bullet 2
- Bullet 3
Bold can be used to indicate first words of a list as above, or as a word that could be included in a glossary.
20.1.1 Sub section
Here is an example of a code block. The line before must end in a full stop.
echo "Hello world!"
The code block above has bash
as the code identifier. Inline text should only be used for single commands, file extensions, or paths, i.e., not whole commands.
For code blocks that execute - by default only R - should be set to eval=FALSE
. Pre-made output should be copy pasted and placed in a collapsible block. For example the following.
print('SPAAM Rules!')
1] "SPAAM Rules!" [
Can be written as.
```{.r eval=FALSE}
print('SPAAM Rules!')
```
```{.r eval=FALSE}
[1] "SPAAM Rules!"
```
Other code blocks will not execute by default, and can be simply set without setting no execution.
```bash
echo "SPAAM Rules!"
```
20.2 Second section
Here is an example of a figure. It must have a caption, and a label for referencing in text.
The label must be prefixed with fig-<chaptername>-<figureidentifier>
and should be in lowercase.
20.3 Third section
Tables should also have a caption and a label for referencing in text.
Default | Left | Right | Center |
---|---|---|---|
12 | 12 | 12 | 12 |
123 | 123 | 123 | 123 |
1 | 1 | 1 | 1 |
20.3.1 Third sub section
This is a call out block with a warning style.
Note that we reserve some callout formatting styles for specific objects!
For example the end of every section should have a task or question with a hidden answer.
Your question(s) goes here.
The answer(s) goes here, in a by-default ‘hidden’ block the reader can open to view.
20.4 Summary
Please refer to Chapter Writing Guidelines for the full list of guidelines.
Citations come from the associated .bib
file, and are referenced in the text like this (Fellows Yates and Warinner 2024). References are automatically rendered for you at the end of the chapter.