chore(docs): Streamline for integration into docs.opendesk.eu

docs/enhanced-configuration/groupware-migration.md

@@ -1,10 +1,11 @@
-r<!--
+<!--
 SPDX-FileCopyrightText: 2024 Zentrum für Digitale Souveränität der Öffentlichen Verwaltung (ZenDiS) GmbH
 SPDX-License-Identifier: Apache-2.0
 -->
 
 <h1>Migration from M365 with audriga migration service and master authentication</h1>
 
+<!-- TOC -->
 * [Context](#context)
 * [Prerequisites](#prerequisites)
   * [Prepare M365 tenant for access](#prepare-m365-tenant-for-access)
@@ -17,8 +18,7 @@ SPDX-License-Identifier: Apache-2.0
     * [Add multiple user accounts via CSV file](#add-multiple-user-accounts-via-csv-file)
   * [Start the migration](#start-the-migration)
   * [Monitor migration status](#monitor-migration-status)
-
-# Context
+<!-- TOC -->
 
 Most organizations already have email accounts on various platforms that need to be migrated to openDesk. This document describes the migration from M365 accounts to openDesk using the [audriga Migration Service](https://www.audriga.com) in combination with the master authentication option in openDesk. Other source platforms are also supported, and their migrations work in a similar manner.
 

docs/enhanced-configuration/idp-federation.md

@@ -5,6 +5,7 @@ SPDX-License-Identifier: Apache-2.0
 
 <h1>Federation with external identity provider (IdP)</h1>
 
+<!-- TOC -->
 * [Context](#context)
 * [Prerequisites](#prerequisites)
   * [User accounts](#user-accounts)
@@ -17,8 +18,7 @@ SPDX-License-Identifier: Apache-2.0
     * [Separate realm](#separate-realm)
     * [OIDC Client](#oidc-client)
   * [openDesk IdP](#opendesk-idp)
-
-# Context
+<!-- TOC -->
 
 Most organizations already have an Identity and Access Management (IAM) system with an identity provider (IdP) for single sign-on to internal or external web applications.
 

docs/enhanced-configuration/matrix-federation.md

@@ -12,8 +12,6 @@ SPDX-License-Identifier: Apache-2.0
   * [Separate Matrix domain](#separate-matrix-domain)
 <!-- TOC -->
 
-# Context
-
 The Element chat application and its server component Synapse are based on the Matrix protocol,
 that supports federation with other Matrix servers to communicate with the users with accounts on these servers.
 

docs/enhanced-configuration/self-signed-certificates.md

@@ -12,8 +12,6 @@ SPDX-License-Identifier: Apache-2.0
   * [Option 2: Use cert-manager.io](#option-2-use-cert-managerio)
 <!-- TOC -->
 
-# Use case
-
 Deploying openDesk into an environment with custom public key infrastructure (PKI) that is usually not part of
 public certificate authority chains or deploying openDesk into a local cluster without ACME challenge.
 

docs/enhanced-configuration/separate-mail-matrix-domain.md

@@ -5,6 +5,7 @@ SPDX-License-Identifier: Apache-2.0
 
 <h1>Separate domains for mail and or Matrix </h1>
 
+<!-- TOC -->
 * [Context](#context)
 * [Example configuration](#example-configuration)
   * [Mail domain](#mail-domain)
@@ -13,8 +14,7 @@ SPDX-License-Identifier: Apache-2.0
     * [Webserver](#webserver)
       * [Content Security Policy](#content-security-policy)
       * [.well-known](#well-known)
-
-# Context
+<!-- TOC -->
 
 As communication over mail and chat can go beyond the borders of your openDesk installation, you may want to use different domains for the mail and/or Matrix.