admin2/template
1
0
Fork 0
mirror of https://github.com/TeachBooks/template.git synced 2026-11-12 22:25:52 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update 009.md

Browse source
This commit is contained in:
Tom van Woudenberg 2025-04-22 08:44:09 +02:00 • committed by GitHub
parent f497a26939
commit 313d19b25d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

14
book/syntax_exercises/009.md
View file

@ -79,7 +79,7 @@ The displacement can be found using the equation $s = v \cdot t$.
12. It is also possible to use custom colours! Look [here](https://teachbooks.io/manual/external/Sphinx-Named-Colors/README.html#) for documentation about the TeachBook extension which allows custom colours.
12. Colours are added to equations using `\namedcolour{...}`, replacing `namedcolour` with the colour of choice. Test this out with the examples in the table below:
13. Colours are added to equations using `\namedcolour{...}`, replacing `namedcolour` with the colour of choice. Test this out with the examples in the table below:
::::{list-table}
:widths: auto
@ -95,25 +95,25 @@ The displacement can be found using the equation $s = v \cdot t$.
::::
13. For colours with hyphens we use need to use the class-based command `\class{named-colour}{...}. Try this using the format shown below:
14. For colours with hyphens we use need to use the class-based command `\class{named-colour}{...}. Try this using the format shown below:
```md
$$ \class{hyphen-color}{\sum}_{n=1}^\infty $$
```
14. Test your understanding by creating a block equation where each term is a different colour!
15. Test your understanding by creating a block equation where each term is a different colour!
```{tip}
This is especially helpful for highlighting changes between equations or focusing attention on specific terms!
```
15. When you are ready, commit your changes to the repository by clicking on the green `Commit changes` button.
16. When you are ready, commit your changes to the repository by clicking on the green `Commit changes` button.
16. Add a commit message.
17. Add a commit message.
17. To see your changes, go to {octicon}`play` `Actions` - The most recent workflow run `overview.md / the commit message of the commit you just made` - Wait for it to finish - In the summary, click on the link of your book shown in the table `Branches deployed` and under `Primary book at root` (getting bored of waiting? There'll be exercising on doing this locally which prevents you from waiting).
18. To see your changes, go to {octicon}`play` `Actions` - The most recent workflow run `overview.md / the commit message of the commit you just made` - Wait for it to finish - In the summary, click on the link of your book shown in the table `Branches deployed` and under `Primary book at root` (getting bored of waiting? There'll be exercising on doing this locally which prevents you from waiting).
18. Do you see your change? If you don't see it click `CTRL`+`F5`/`Control`+`F5`to refresh the page.
19. Do you see your change? If you don't see it click `CTRL`+`F5`/`Control`+`F5`to refresh the page.
```{admonition} Check your understanding