From 262c07df11fdce2741a19bb8ced97d351422fac2 Mon Sep 17 00:00:00 2001 From: Tom van Woudenberg Date: Sun, 26 Jan 2025 20:17:52 +0100 Subject: [PATCH] Fix topics --- book/exercises/001.md | 2 +- book/exercises/002.md | 2 +- book/exercises/003.md | 2 +- book/exercises/004.md | 2 +- book/exercises/005.md | 2 +- book/exercises/006.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/book/exercises/001.md b/book/exercises/001.md index 0c481a2..0865c21 100644 --- a/book/exercises/001.md +++ b/book/exercises/001.md @@ -2,7 +2,7 @@ Let's start with the most basic edit: add some text to a file and see that the website is updated. -::::::{topic} +::::::{topic} Exercise objective Can you add some content to the intro page? :::::: diff --git a/book/exercises/002.md b/book/exercises/002.md index 170ad3c..df5eee8 100644 --- a/book/exercises/002.md +++ b/book/exercises/002.md @@ -2,7 +2,7 @@ Let's continue by adding one additional step. Let's add a file to the table of contents! the `_toc.yml` contains a list of all the files to be shown in your book-website. Let's add a file which is not in the table of contents yet! -::::::{topic} +::::::{topic} Exercise objective Can you add the file named `file_to_be_added_to_toc.md` to the book website? :::::: diff --git a/book/exercises/003.md b/book/exercises/003.md index e0cd370..a53e9a4 100644 --- a/book/exercises/003.md +++ b/book/exercises/003.md @@ -2,7 +2,7 @@ As we've added some content by now, let's make this book a bit more personal! We'll make some changes to the `_config.yml` file which changes the configuration of the book website. -::::::{topic} +::::::{topic} Exercise objective Can you edit the repository url defined in the `_config.yml`, change the title shown below the logo and change the author as shown in the footer? :::::: diff --git a/book/exercises/004.md b/book/exercises/004.md index 15d1227..8f2c172 100644 --- a/book/exercises/004.md +++ b/book/exercises/004.md @@ -2,7 +2,7 @@ By now, we've covered the essentials: content files, `_toc.yml` and `_config.yml`. But what if you want to make some changes but don't want to share them directly with the general public of your book website? Or what if you have some work-in-progress that you want to share with colleagues? You need a version of your book! Let's try and do that! Later on, you'll probably want to merge your newest version back into the original book. That's what we'll do in [](./005.md). -::::::{topic} +::::::{topic} Exercise objective Can you make a new branch of your book with an additional file `file_on_new_version.md` and view it online? :::::: diff --git a/book/exercises/005.md b/book/exercises/005.md index 0cdbf48..db67832 100644 --- a/book/exercises/005.md +++ b/book/exercises/005.md @@ -2,7 +2,7 @@ In [](./004.md) you created your own version of a book. But it would be a pity if you never contribute back to the original book right? Probably your additions are very useful there too! You'll merge you version of the book which is stored on a branch into the original book which is on main. If there've been some changes on that main branch in the meantime, git will take care of that! -::::::{topic} +::::::{topic} Exercise objective Can you merge your branch into `main` with a pull request? :::::: diff --git a/book/exercises/006.md b/book/exercises/006.md index f56a6ab..9287d06 100644 --- a/book/exercises/006.md +++ b/book/exercises/006.md @@ -10,7 +10,7 @@ So far you did everything on your own, within a single repository. However, book The fork-pull request workflow is very common in open-source projects. It allows people to work independently without asking for access or worrying about affecting the original source code, as well as give the original author of the code a clear way to review the changes and decide if they want to include them in the original repository. ``` -::::::{topic} +::::::{topic} Exercise objective Can you fork a book repository of someone else, make changes and contribute back? ::::::