Add toc to docs

docs/content/doc/setup/backups.md

@@ -13,6 +13,8 @@ menu:
 Vikunja does not store any data outside of the database.
 So, all you need to backup are the contents of that database and maybe the config file.
 
+{{< table_of_contents >}}
+
 ## MySQL
 
 To create a backup from mysql use the `mysqldump` command:

docs/content/doc/setup/docker-start-to-finish.md

@@ -17,6 +17,8 @@ We'll use [docker compose](https://docs.docker.com/compose/) to make handling th
 
 > If you have any issues setting up vikunja, please don't hesitate to reach out to us via [matrix](https://riot.im/app/#/room/!dCRiCiLaCCFVNlDnYs:matrix.org?via=matrix.org), the [community forum](https://community.vikunja.io/) or even [email](mailto:hello@vikunja.io).
 
+{{< table_of_contents >}}
+
 ## Preparations (optional)
 
 Create a directory for the project where all data and the compose file will live in.

docs/content/doc/setup/full-docker-example.md

@@ -21,7 +21,9 @@ For all available configuration options, see [configuration]({{< ref "config.md"
 All examples on this page already reflect this and do not require additional work.
 </div>
 
-### Redis
+{{< table_of_contents >}}
+
+## Redis
 
 To use redis, you'll need to add this to the config examples below:
 

docs/content/doc/setup/install-backend.md

@@ -15,6 +15,8 @@ menu:
 <a href="{{< ref "utf-8.md">}}">make sure your db is utf-8 compatible</a>.
 </div>
 
+{{< table_of_contents >}}
+
 ## Install from binary
 
 Download a copy of Vikunja from the [download page](https://vikunja.io/en/download/) for your architecture.

docs/content/doc/setup/install-frontend.md

@@ -17,6 +17,8 @@ Unzip them and store them somewhere your server can access them.
 
 You also need to configure a rewrite condition to internally redirect all requests to `index.html` which handles all urls. 
 
+{{< table_of_contents >}}
+
 ## API URL configuration
 
 By default, the frontend assumes it can reach the api at `/api/v1` relative to the frontend url.

docs/content/doc/setup/reverse-proxies.md

@@ -13,6 +13,8 @@ menu:
 These examples assume you have an instance of the backend running on your server listening on port `3456`.
 If you've changed this setting, you need to update the server configurations accordingly.
 
+{{< table_of_contents >}}
+
 ## NGINX
 
 Below are two example configurations which you can put in your `nginx.conf`:

docs/content/doc/setup/utf-8.md

@@ -17,6 +17,8 @@ Vikunja itself will work just fine until you want to use non-latin characters in
 On this page, you will find information about how to fully ensure non-latin characters like aüäß or emojis work 
 with your installation.
 
+{{< table_of_contents >}}
+
 ## Postgresql & SQLite
 
 Postgresql and SQLite should handle utf-8 just fine - If you discover any issues nonetheless, please 
@@ -49,11 +51,11 @@ The charset `latin1` means the db is encoded in the `latin1` encoding which does
 
 (The following guide is based on [this thread from stackoverflow](https://dba.stackexchange.com/a/104866))
 
-#### 0. Backup your database
+### 0. Backup your database
 
 Before attempting any conversion, please [back up your database]({{< ref "backups.md">}}).
 
-#### 1. Create a pre-conversion script
+### 1. Create a pre-conversion script
 
 Copy the following sql statements in a file called `preAlterTables.sql` and replace all occurences of `vikunja` with 
 the name of your database:
@@ -70,7 +72,7 @@ SELECT concat("ALTER TABLE `",table_schema,"`.`",table_name, "` CHANGE `",column
 FROM `COLUMNS` where table_schema like 'vikunja' and data_type in ('text','tinytext','mediumtext','longtext');
 {{< /highlight >}}
 
-#### 2. Run the pre-conversion script
+### 2. Run the pre-conversion script
 
 Running this will create the actual migration script for your particular database structure and save it in a file called `alterTables.sql`:
 
@@ -78,7 +80,7 @@ Running this will create the actual migration script for your particular databas
 mysql -uroot < preAlterTables.sql | egrep '^ALTER' > alterTables.sql
 {{< /highlight >}}
 
-#### 3. Convert the database
+### 3. Convert the database
 
 At this point converting is just a matter of executing the previously generated sql script:
 
@@ -86,7 +88,7 @@ At this point converting is just a matter of executing the previously generated
 mysql -uroot < alterTables.sql
 {{< /highlight >}}
 
-#### 4. Verify it was successfully converted
+### 4. Verify it was successfully converted
 
 If everything worked as intended, your db collation should now look like this: