Merge branch 'main' into manual_description

README.md

@@ -32,7 +32,7 @@ Demonstration for a public repository, video available [here](https://youtu.be/n
 :name: create_new_repository
 ```
 
-3. You can choose for `Private` only if you've GitHub Pro, GitHub Team, GitHub Enterprise Cloud, or GitHub Enterprise Server. Otherwise, you won't be able to publish your TeachBook online.
+3. You can choose for `Private` only if you've GitHub Pro, GitHub Team, GitHub Enterprise Cloud, or GitHub Enterprise Server. Otherwise, you won't be able to publish your TeachBook online. Furthermore, it prevents people from contributing to your book, making your book essentially 'closed' instead of 'open.
 
 4. (Only required for private repositories:) Create a Personal Access Token (classic) with at least the scopes `repo`, `read:org` and `gist` as described in the [github documentation](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens), and add this token with the name `GH_PAT` as a `Repository secret` or `Organization secret` (<svg aria-label="Edit repository metadata" role="img" height="16" viewBox="0 0 16 16" version="1.1" width="16" data-view-component="true" class="octicon octicon-gear float-right">    <path d="M8 0a8.2 8.2 0 0 1 .701.031C9.444.095 9.99.645 10.16 1.29l.288 1.107c.018.066.079.158.212.224.231.114.454.243.668.386.123.082.233.09.299.071l1.103-.303c.644-.176 1.392.021 1.82.63.27.385.506.792.704 1.218.315.675.111 1.422-.364 1.891l-.814.806c-.049.048-.098.147-.088.294.016.257.016.515 0 .772-.01.147.038.246.088.294l.814.806c.475.469.679 1.216.364 1.891a7.977 7.977 0 0 1-.704 1.217c-.428.61-1.176.807-1.82.63l-1.102-.302c-.067-.019-.177-.011-.3.071a5.909 5.909 0 0 1-.668.386c-.133.066-.194.158-.211.224l-.29 1.106c-.168.646-.715 1.196-1.458 1.26a8.006 8.006 0 0 1-1.402 0c-.743-.064-1.289-.614-1.458-1.26l-.289-1.106c-.018-.066-.079-.158-.212-.224a5.738 5.738 0 0 1-.668-.386c-.123-.082-.233-.09-.299-.071l-1.103.303c-.644.176-1.392-.021-1.82-.63a8.12 8.12 0 0 1-.704-1.218c-.315-.675-.111-1.422.363-1.891l.815-.806c.05-.048.098-.147.088-.294a6.214 6.214 0 0 1 0-.772c.01-.147-.038-.246-.088-.294l-.815-.806C.635 6.045.431 5.298.746 4.623a7.92 7.92 0 0 1 .704-1.217c.428-.61 1.176-.807 1.82-.63l1.102.302c.067.019.177.011.3-.071.214-.143.437-.272.668-.386.133-.066.194-.158.211-.224l.29-1.106C6.009.645 6.556.095 7.299.03 7.53.01 7.764 0 8 0Zm-.571 1.525c-.036.003-.108.036-.137.146l-.289 1.105c-.147.561-.549.967-.998 1.189-.173.086-.34.183-.5.29-.417.278-.97.423-1.529.27l-1.103-.303c-.109-.03-.175.016-.195.045-.22.312-.412.644-.573.99-.014.031-.021.11.059.19l.815.806c.411.406.562.957.53 1.456a4.709 4.709 0 0 0 0 .582c.032.499-.119 1.05-.53 1.456l-.815.806c-.081.08-.073.159-.059.19.162.346.353.677.573.989.02.03.085.076.195.046l1.102-.303c.56-.153 1.113-.008 1.53.27.161.107.328.204.501.29.447.222.85.629.997 1.189l.289 1.105c.029.109.101.143.137.146a6.6 6.6 0 0 0 1.142 0c.036-.003.108-.036.137-.146l.289-1.105c.147-.561.549-.967.998-1.189.173-.086.34-.183.5-.29.417-.278.97-.423 1.529-.27l1.103.303c.109.029.175-.016.195-.045.22-.313.411-.644.573-.99.014-.031.021-.11-.059-.19l-.815-.806c-.411-.406-.562-.957-.53-1.456a4.709 4.709 0 0 0 0-.582c-.032-.499.119-1.05.53-1.456l.815-.806c.081-.08.073-.159.059-.19a6.464 6.464 0 0 0-.573-.989c-.02-.03-.085-.076-.195-.046l-1.102.303c-.56.153-1.113.008-1.53-.27a4.44 4.44 0 0 0-.501-.29c-.447-.222-.85-.629-.997-1.189l-.289-1.105c-.029-.11-.101-.143-.137-.146a6.6 6.6 0 0 0-1.142 0ZM11 8a3 3 0 1 1-6 0 3 3 0 0 1 6 0ZM9.5 8a1.5 1.5 0 1 0-3.001.001A1.5 1.5 0 0 0 9.5 8Z"></path> </svg>`Settings` > <svg aria-hidden="true" height="16" viewBox="0 0 16 16" version="1.1" width="16" data-view-component="true" class="octicon octicon-key-asterisk">    <path d="M0 2.75A2.75 2.75 0 0 1 2.75 0h10.5A2.75 2.75 0 0 1 16 2.75v10.5A2.75 2.75 0 0 1 13.25 16H2.75A2.75 2.75 0 0 1 0 13.25ZM2.75 1.5c-.69 0-1.25.56-1.25 1.25v10.5c0 .69.56 1.25 1.25 1.25h10.5c.69 0 1.25-.56 1.25-1.25V2.75c0-.69-.56-1.25-1.25-1.25Z"></path><path d="M8 4a.75.75 0 0 1 .75.75V6.7l1.69-.975a.75.75 0 0 1 .75 1.3L9.5 8l1.69.976a.75.75 0 0 1-.75 1.298L8.75 9.3v1.951a.75.75 0 0 1-1.5 0V9.299l-1.69.976a.75.75 0 0 1-.75-1.3L6.5 8l-1.69-.975a.75.75 0 0 1 .75-1.3l1.69.976V4.75A.75.75 0 0 1 8 4Z"></path></svg>`Secrets and variables` > `Actions` > `Repository secrets` or `Organization secrets`).
 

book/_config.yml

@@ -1,4 +1,3 @@
-title: Template
 author: TeachBooks Team, built with <a href="https://teachbooks.io">TeachBooks</a> and <a href="https://jupyterbook.org/">Jupyter Book</a>, <a href="https://creativecommons.org/licenses/by/4.0/" target="_blank" rel="license noopener noreferrer"">CC BY 4.0<img style="height:22px!important;margin-left:3px;vertical-align:text-bottom;" src="https://mirrors.creativecommons.org/presskit/icons/cc.svg" alt=""><img style="height:22px!important;margin-left:3px;vertical-align:text-bottom;" src="https://mirrors.creativecommons.org/presskit/icons/by.svg" alt=""></a> #add your own name here
 
 execute:

book/_toc.yml

@@ -7,6 +7,14 @@ parts:
     - file: some_content/overview.md
       sections:
       - file: some_content/text_and_code.ipynb
+    - file: exercises/exercises
+      sections:
+      - file: exercises/001.md
+      - file: exercises/002.md
+      - file: exercises/003.md
+      - file: exercises/004.md
+      - file: exercises/005.md
+      - file: exercises/006.md
     - file: references.md
     - file: changelog.md
     - file: credits.md

book/exercises/001.md

@@ -0,0 +1,26 @@
+# Exercise 1: First file edit
+
+Let's start with the most basic edit: add some text to a file and see that the website is updated.
+
+> Can you add some content to the intro page?
+
+1. Go to the the file `book/intro.md` on your GitHub repository (`https://github.com/<your_username>/<your_repo_name>`) - {octicon}`code;1em` `Code` - `Book` - `intro.md` - {octicon}`pencil;1em` `Edit this file`
+2. Add some text. Feeling brave? Have a look at the [MyST cheat sheet](https://jupyterbook.org/en/stable/reference/cheatsheet.html). Don't worry if that feels daunting, there will be exercises on this!
+3. Click `Commit changes`
+4. Add a message and description of your change. With this `commit` you save your changes to the git-timeline. Any commit can always be reverted. Therefore, it's useful to shortly explain what is included in your commit. Later on, you'll make commits which may contain changes to many different files. In that case, a descriptive commit message and description is even more useful!
+5. Select `Commit directly to the main branch` (this adds your change your change to the default version instead of making a new one)
+6. Click `Commit changes`.
+7. Go to {octicon}`play;1em` `Actions` - The most recent workflow run `Update intro.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`
+8. Do you see your change? If you don't see it click `CTRL`+`F5`/`Control`+`F5`to refresh the page (your browser keeps a cached version of website you recently visit, but we actually want the most up-to-date version!).
+
+```{admonition} Check your understanding
+:class: note
+
+Before moving on to the next exercise, make sure you understand the following:
+- Where are the contents of the book stored?
+- How can you edit a single file via the GitHub browser interface?
+- What is a commit and what role does it play in the editing process?
+- Given a specific GitHub repository, can you determine the URL of the book website?
+- How can you view the changes you made to the book?
+- What is the purpose of a commit message and description?
+```

book/exercises/002.md

@@ -0,0 +1,54 @@
+# Exercise 2: Add a new file to the table of contents
+
+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!
+
+> Can you add the file named `file_to_be_added_to_toc.md` to the book website?
+
+1. Go to the (`https://github.com/<your_username>/<your_repo_name>`) - {octicon}`code;1em` `Code` - `Book` directory of your GitHub repository and find the location of `file_to_be_added_to_toc.md`
+2. Go to the the file `book/_toc.yml` on your GitHub repository (`https://github.com/<your_username>/<your_repo_name>`) - {octicon}`code;1em` `Code` - `Book` - `_toc.yml` - {octicon}`pencil;1em` `Edit this file`
+3. Add `file_to_be_added_to_toc.md` as a second item in the `Some content` chapter
+
+````{admonition} Need some help?
+:class: tip, dropdown
+Your `_toc.yml` should look like
+```yaml
+format: jb-book
+root: intro.md
+
+parts:
+  - caption: Contents
+    chapters:
+    - file: some_content/overview.md
+      sections:
+      - file: some_content/text_and_code.ipynb
+      - file: file_to_be_added_to_toc.md
+    - file: exercises/exercises
+      sections:
+      - file: exercises/001.md
+      - file: exercises/002.md
+      - file: exercises/003.md
+      - file: exercises/004.md
+      - file: exercises/005.md
+      - file: exercises/006.md
+    - file: references.md
+    - file: changelog.md
+    - file: credits.md
+```
+````
+4. Click `Commit changes`
+5. Add a message and description of your change
+6. Select `Commit directly to the main branch` (this adds your change your change to the default version instead of making a new one)
+7. Click `Commit changes`
+8. Go to {octicon}`play;1em` `Actions` - The most recent workflow run `Update _toc.yml / 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)
+9. Do you see your change? If you don't see it click `CTRL`+`F5`/`Control`+`F5`to refresh the page.
+
+```{admonition} Check your understanding
+:class: note
+
+Before moving on to the next exercise, make sure you understand the following:
+- Are all files in the repository added to the website?
+- What is the purpose of the `_toc.yml` file?
+- What happens if a file is not listed in the `_toc.yml`?
+- How can you verify that your changes to `_toc.yml` were successful?
+- Does the structure of the `_toc.yml` file need to match the directory structure of the repository?
+```

book/exercises/003.md

@@ -0,0 +1,46 @@
+# Exercise 3: Change book configuration
+
+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. 
+
+> 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?
+
+1. Go to the the file `book/_config.yml` on your GitHub repository (`https://github.com/<your_username>/<your_repo_name>`) - {octicon}`code;1em` `Code` - `Book` - `_config.yml` - {octicon}`pencil;1em` `Edit this file`
+2. In the `Edit` field, change the author which will be shown in the footer of the book website.
+````{admonition} Need some help?
+:class: tip, dropdown
+The first line of your `_config.yml` should look like
+```yaml
+author: <your_name>, built with <a href="https://teachbooks.io">TeachBooks</a> and <a href="https://jupyterbook.org/">Jupyter Book</a>, <a href="https://creativecommons.org/licenses/by/4.0/" target="_blank" rel="license noopener noreferrer"">CC BY 4.0<img style="height:22px!important;margin-left:3px;vertical-align:text-bottom;" src="https://mirrors.creativecommons.org/presskit/icons/cc.svg" alt=""><img style="height:22px!important;margin-left:3px;vertical-align:text-bottom;" src="https://mirrors.creativecommons.org/presskit/icons/by.svg" alt=""></a>
+```
+````
+3. In the `Edit` field, change the title of your homepage which will under the logo and above the table of contents
+````{admonition} Need some help?
+:class: tip, dropdown
+The 21st line of your `_config.yml` should look like
+```yaml
+        text: <your_title>
+```
+````
+4. In the `Edit` field, change the repository url which will be used to allow other people to open your repository, suggest edits and open issues as shown in top right corner of the built book under {octicon}`mark-github;1em`.
+````{admonition} Need some help?
+:class: tip, dropdown
+The 24th line of your `_config.yml` should look like
+```yaml
+      repository_url: "https://github.com/<your_username>/<your_repository>"
+```
+````
+5. Click `Commit changes`
+6. Add a message and description of your change
+7. Select `Commit directly to the main branch` (this adds your change your change to the default version instead of making a new one)
+8. Click `Commit changes`
+9. Go to {octicon}`play;1em` `Actions` - The most recent workflow run `Update _config.yml / 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`
+10. Do you see your change? If you don't see it click `CTRL`+`F5`/`Control`+`F5`to refresh the page.
+
+```{admonition} Check your understanding
+:class: note
+
+Before moving on to the next exercise, make sure you understand the following:
+- What is this special `_config.yml` file?
+- Changes in `_config.yml` can have effect on multiple pages in the book
+- The `_config.yml` is generally not used for adding content
+```

book/exercises/004.md

@@ -0,0 +1,26 @@
+# Exercise 4: _Your_ Version of the Book
+
+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).
+
+> Can you make a new branch of your book with an additional file `file_on_new_version.md` and view it online?
+
+1. Add a new Issue to let people know you're working on something by going to your repository (`https://github.com/<your_username>/<your_repo_name>`) - {octicon}`issue-opened;1em` `Issues` - `New issue` (note that is not required for making your own version, but it's good practice so that people know where you're working on)
+2. Add a title and description, eg. `Added some content`
+3. On `Assignees`, click `Assign yourself` to make clear that you feel responsible for this issue.
+4. Click `Submit new issue`
+5. In the new window, under `Development`, click `Create a branch` (note that you could also make branches in other ways, but in this way it's directly linked to the issue). A 'branch' is a separate version of the book which keeps the link with the original book.
+6. Use the default options and click `Create branch`
+7. Ignore the `checkout in your local repository`- popup for now (later on you'll know what this is and how to use it)
+8. Go to `Code` - {octicon}`git-branch;1em` `main` and click on `1-<your_issue_title>` to open your branch.
+9. Add a book page as explained in [](./002.md) and make sure you commit to the  `1-<your_issue_title>`-branch.
+10. Go to {octicon}`play;1em` `Actions` - The most recent workflow run `Update _toc.yml / the commit message of the commit you just made` - Wait for it to finish - In the summary, you should now see multiple Branches. Click on the link of your new branch ``1-<your_issue_title>`
+11. Do you see your change? If you don't see it click `CTRL`+`F5`/`Control`+`F5`to refresh the page.
+
+```{admonition} Check your understanding
+:class: note
+
+Before moving on to the next exercise, make sure you understand the following:
+- What is the purpose of creating a new branch in your repository?
+- Why is it good practice to create an issue before starting work on a new feature or change?
+- How can you view the changes made in your new branch online?
+```

book/exercises/005.md

@@ -0,0 +1,28 @@
+# Exercise 5: Merge your version in the original book
+
+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!
+
+> Can you merge your branch into `main` with a pull request?
+
+1. Go to your repository homepage (`https://github.com/<your_username>/<your_repo_name>`). Probably, it will have big yellow announcement saying {octicon}`git-branch;1em` `1-<your_issue_title> had recent pushes <some> minutes ago - Compare & Pull request`. We'll ignore that for now and do it manually.
+2. Go to the pull request page on your repository homepage (`https://github.com/<your_username>/<your_repo_name>`) - {octicon}`git-pull-request;1em` and click `New pull request`
+3. On {octicon}`git-compare;1em` make sure you point from your branch `1-<your_issue_title>` into `main`. So, `main` on the left, {octicon}`arrow-left;1em`, and `1-<your_issue_title>` on the right. Main is the default name for the branch which has the most recent/stable version. The page should now show all the changes you made on the `1-<your_issue_title>`-branch. If there would be changes on the `main` branch in the meantime, they should show up here too.
+4. Click `Create pull request` to start the process of moving your changes into the `main` branch. If there were changes on both branches which are conflicting, it will tell you there's a merge conflict. If you followed the steps until now, that shouldn't be the case. Solving those merge conflicts is topic for another exercise.
+5. Add a title and description described the changes you made. This is done to give other people a summary of what has been changed.
+6. Assign yourself to make clear that you feel responsible.
+7. Click `Create pull request`. On the next page you'll see that GitHub gives an announcement {octicon}`bookmark;1em` `<your_username> linked an issue now that may be closed by this pull request`. That sounds useful!
+8. As you're the only one in this repo there's nobody to review your work. So let's continue and merge your changes into `main` by clicking `Merge pull request` and `Confirm merge` (eventually specifying the suggested commit message and description)
+9. As this issue is now closed, you can safely remove the branch `1-<your_issue_title>` as you don't need it anymore. You can do so by clicking `Delete branch`.
+10. Go to {octicon}`play;1em` `Actions` - The most recent workflow run `Merge pull request #2 from <your_username>/1-<your_issue_title> / the commit message of the commit you just made` - Wait for it to finish - In the summary, click the link of the main branch or the primary book at root.
+11. Do you see your change from your branch 1-<your_issue_title>? If you don't see it click `CTRL`+`F5`/`Control`+`F5`to refresh the page. Check that the url indeed shows that you're on main.
+
+```{admonition} Check your understanding
+:class: note
+
+Before moving on to the next exercise, make sure you understand the following:
+- What is the purpose of creating a pull request?
+- How do you manually create a pull request on GitHub?
+- Why is it important to add a title and description to your pull request?
+- What is the final step after merging your pull request?
+- How can you verify that your changes have been successfully merged into the main branch?
+```

book/exercises/006.md

@@ -0,0 +1,51 @@
+# Exercise 6: Contribute to the book of somebody else
+
+```{tip}
+For this exercise you will need a partner, as well as your own book. In the first part, each of you will make a change in the book of the other, then request the other to review and merge the change. In the second part, you will go back to your book and accept the change made by your partner.
+```
+
+So far you did everything on your own, within a single repository. However, book-editing would be really boring if it would always be like that. Let's team up with someone to see the potential of collaborative book editing using Git! In this exercise you will take the book of someone else and create your own version of that one. However, unlike a previous exercise, we cannot simply make a branch, because you don't have _access_ to their repository. However, you can make a copy of the repository on your own account and make some changes there. Then, you can send that back to your friend's repository and see if they would like to incorporate your changes. The repository you create (your own version) is called a **fork**.
+
+```{note}
+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.
+```
+
+> Can you fork a book repository of someone else, make changes and contribute back?
+
+```{tip}
+This part describes how you can make a change in the book of someone else.
+```
+
+1. Go to the repository to which you want to contribute (`https://github.com/<your_friends_username>/<your_friends_repo_name>`), then add an issue to let people know you're working on something - {octicon}`issue-opened;1em` `Issues` - `New issue`. You did this in [](./004.md).
+2. Go back to the home page of repository to which you want to contribute (`https://github.com/<your_friends_username>/<your_friends_repo_name>`) and click {octicon}`repo-forked;1em``Fork` at the top right corner to create a copy of the repository under your GitHub account.
+3. Choose yourself as an owner and click `Create fork`. In the new screen you should see the same repo but on your own account. Furthermore, it mentions `forked from <your_friends_username>/<your_friends_repo_name>`
+4. Make some changes on the main branch of your forked repo. *Make sure you make changes to something in the book subdirectory!_
+5. Check the changes in the online book.
+6. Go to the pull request page on your forked repository homepage (`https://github.com/<your_username>/<your_friends_repo_name>/pulls`) - {octicon}`git-pull-request;1em` and click `New pull request`.
+7. On {octicon}`git-compare;1em` make sure you point from your repositories branch `head repository: <your_username>/<your_friends_repo_name>:compare: main` into the original repository `base repository: <your_friends_username>/<your_friends_repo_name> base:main`. This should be the case by default.
+8. In the description, add some explanation which for your friend to understand what your changes includes. Furthermore, it's useful to add `Closes #<number_of_issue_created_in_step_1>` so that the pull request is linked to the issue.
+9. Click `Create pull request`. On the next page you'll see that the pull request is created in your friends repository.
+10. Your friend will get a notification, but it wouldn't hurt to ask the person to review your pull request. Your friend might have some feedback or will just accept it right away!
+
+```{tip}
+This part describes how you can accept the changes in your book made by someone else.
+```
+
+1. First, how can you tell someone has made a pull request from a fork into your repository? One way is to check your GitHub notifications, which you can find most easily by clicking on the inbox icon in the top right corner of [github.com](https://github.com). You can also find this by going to your repository and clicking on {octicon}`git-pull-request;1em` `Pull requests`.
+2. Once on the pull request page, you should see that something is listed there. Click on it and read what it says. Just as in a previous exericse, you should see some notes from the Pull Request creator, as well as a summary of the commits, and a tab to view "Files changed." Can you identify how you can tell whether or not this is from a forked repository?
+3. At the top of the page, next to the status icon (which should say "Open" in green), look for the summary. It should say "`<your friend>` wants to merge x commit(s) into `<your_username>`:`main` from `<your_friends_username>`:`main`. Where in each case `main` is the branch, and the usernames before the `:` symbol indicate the owner of the repository; because the merge is coming from your friend's repository, it is obvious that it is a fork.
+4. Review the change from your friend. Note that if this were a "real" project, you may want to use some of the useful GitHub collaboration features, for example: adding comments in the conversation tab, commenting on specific lines of code, requesting changes, or making additional commits to the pull request yourself. However, for this exercise, you can simply click `Merge pull request` if you are happy with the changes.
+5. Once the merge is complete, check that the book is updated via the Actions tab, and visit the page to check that the changes are there.
+
+Now that the changes have been successfully incorporated, you should have seen that both Pull Requests (one in your book repo, the other in your forked repo) have been completed. Unless you want to continue collaborating in the future, you can delete your forked repository. 
+
+```{admonition} Check your understanding
+:class: note
+
+Before moving on, make sure you understand the following:
+- What is a fork and how does it differ from a branch?
+- Why is it important to create an issue before starting to work on a contribution?
+- How do you create a pull request from a forked repository to the original repository?
+- What should you include in the description of a pull request?
+- How can you ensure that your friend is aware of your pull request?
+```

book/exercises/exercises.md

@@ -0,0 +1,3 @@
+# Exercises
+
+Want to get started making books? Follow these exercises!

book/file_to_be_added_to_toc.md

@@ -0,0 +1,2 @@
+# Title of the file to be added to the toc
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Aenean id diam non mauris auctor sollicitudin. Ut quis nunc lobortis, iaculis massa id, eleifend justo. Nulla ac auctor sapien. Etiam sit amet est a ex vestibulum porta. Nulla non lacus a purus luctus blandit sit amet non nibh. Curabitur vitae cursus dolor. Ut eu nisi nec enim ullamcorper fermentum.

book/intro.md

@@ -1,6 +1,6 @@
 (intro)=
 # Welcome to the Template Book
 
-_Write book intro here. This is the first page the student will see when opening the url._
+_This is the first page the student will see when opening the url._
 
-This book can be used as a template for other books. It includes a starter package of the software developed by the TeachBooks initiative.
+This book can be used as a template for other books. It includes a starter package of the software developed by the TeachBooks initiative and some exercises to get you going!

book/some_content/overview.md

@@ -1,3 +1,3 @@
-# Overview
+# Some content
 
 Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.