@@ -20,6 +20,7 @@ parts:
     chapters:
     - file: "part3/documentation"
     - file: "api"
+    - file: "part3/publishing_book"
 
   - caption: Demos
     chapters:
 
@@ -26,6 +26,8 @@ exclude = docs,venv
 max-line-length = 100
 ```
 
+To ignore `flake8` formatting on certain lines, or ignore certain rules, see: [Ignoring Errors with Flake8](https://flake8.pycqa.org/en/3.1.1/user/ignoring-errors.html).
+
 ## Code consistency
 Flake8 only checks the consistency of your code to a certain extent.
 Modern Python allows for [type hints](https://peps.python.org/pep-0484/) which means that you can specify the input and output type for functions.
@@ -55,4 +57,6 @@ files = [
     "tests" # Does not show errors when importing untyped libraries
 ]
 ```
-where `ignore_missing_imports` is set to `True` to supress all errors coming from third-party libraries that are untyped.
+where `ignore_missing_imports` is set to `True` to supress all errors coming from third-party libraries that are untyped.
+
+To let `mypy` ignore single lines or whole files, see: [Locally silencing the checker](https://mypy.readthedocs.io/en/stable/common_issues.html#spurious-errors-and-locally-silencing-the-checker).
@@ -10,11 +10,13 @@ More information about workflows can be found in the [Github Documentation](http
 
 ## Actions
 [Github Actions](https://github.com/features/actions) is a prebuilt set of instructions to make it easier to interact with Github.
-The actions officially maintained by Github can be found at: phttps://github.com/actions](https://github.com/actions)
+The actions officially maintained by Github can be found at: [GitHub/actions](https://github.com/actions)
 
 ## Uploading artifacts
 As covered in the [Coverage report](../part1/coverage)-section, we use the [Upload artifact action](https://github.com/actions/upload-artifact#readme)
 
+(publishing-to-pages)=
+
 ## Publishing to Pages
 There are several ways to publish a set of html files to Github Pages.
 One can either:
 
@@ -0,0 +1,22 @@
+# Publishing a Jupyter-book as a webpage
+
+To make it simple to integrate the Jupyter-book with Github, we using Github Pages, as described in 
+[Publishing to Github Pages](publishing-to-pages).
+
+## Official Github Actions
+Follow the steps in [Publishing with a Github Custom Actions workflow](https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#publishing-with-a-custom-github-actions-workflow)
+
+Follow the steps in [Creating a custom Github Actions](https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#creating-a-custom-github-actions-workflow-to-publish-your-site),
+
+For step 3, we would call `make doc` to generate the documentation at `docs/_build/html`, which in turn is the folder we upload as a Github page.
+
+A Github action showing some of the steps can be found at [Actions/deploy-pages](https://github.com/actions/deploy-pages#usage).
+
+
+## Using a Github branch for publishing
+If one is using the `legacy` workflow from [peaceiris/actions-gh-pages](https://github.com/peaceiris/actions-gh-pages#github-pages-action) one would publish the html files to a branch, usually `gh-pages`.
+
+1. On Github navigate to your repository
+2. Under your repository name, choose `Settings`
+3. Press `Pages`.
+4. Under `Build and deployment` choose `Source: Deploy from a branch` and set the `branch` to `gh-pages`.