fix broken links

docs/developer-guide/projects/osbuild-composer/index.md

@@ -25,5 +25,5 @@ Activate this API by invoking `systemctl start osbuild-composer.socket`. Systemd
 
 This is the `/api/image-builder-composer/v2/` API endpoint. There are currently two clients, which are integrating with `osbuild-composer` using this API:
 
-* [image-builder](https://github.com/osbuild/image-builder), described in more detail in the [Image Builder service architecture](../../../image-builder-service/architecture.md) document.
+* [image-builder](https://github.com/osbuild/image-builder), described in more detail in the [Image Builder service architecture](../../../service/architecture.md) document.
 * [koji-osbuild](https://github.com/osbuild/koji-osbuild) plugin, which integrates `osbuild-composer` with the [Koji](https://koji.build/) build system.

docs/on-premises/blueprint-reference.md

@@ -139,7 +139,7 @@ containers = [
 ]
 ```
 
-To access protected container resources a `containers-auth.json(5)` file can be used, see [Container registry credentials](../user-guide/container-auth.md).
+To access protected container resources a `containers-auth.json(5)` file can be used, see [Container registry credentials](container-auth.md).
 
 
 ## Customizations
@@ -459,7 +459,7 @@ Third-party repositories are supported by the blueprint customizations. A reposi
 An optional `filename` argument can be set, otherwise the repository will be saved using the the repository ID, i.e. `/etc/yum.repos.d/<repo-id>.repo`.
 
 Please note custom repositories **cannot be used at build time to install third-party packages**. These customizations are used to save and enable third-party repositories on the image. For more information, or if you
-wish to install a package from a third-party repository, please continue reading [here](../user-guide/repository-customizations.md).
+wish to install a package from a third-party repository, please continue reading [here](repository-customizations.md).
 
 The following example can be used to create a third-party repository:
 

docs/on-premises/oscap-remediation.md

@@ -17,7 +17,7 @@ To solve this issue, an [osbuild stage] runs the `OpenSCAP` tool on the filesyst
 the standard evaluation for the given profile and applies the remediations to the image. This process enables the user to build a more completely
 hardened image compared to running the remediation on a live system.
 
-[osbuild stage]: 'https://github.com/osbuild/osbuild/blob/main/stages/org.osbuild.oscap.remediation'
+[osbuild stage]: https://github.com/osbuild/osbuild/blob/main/stages/org.osbuild.oscap.remediation
 
 ## Openscap Example
 ```

docs/on-premises/repository-customizations.md

@@ -21,7 +21,7 @@ to use custom repositories for installing third-party packages, continue reading
 ## 2. Save repository configurations
 In the second scenario, to make third-party repository configurations persistent and make the repositories available to users on the system, one would use the blueprint `custom repository`
 configurations to enable this. The repository will be configured and saved to `/etc/yum.repos.d` as a `.repo` file. GPG keys are not imported at build time, but are imported when first 
-installing a third-party package from the desired repository. You can find the blueprint reference for custom repositories [here](../blueprint-reference/blueprint-reference.md).
+installing a third-party package from the desired repository. You can find the blueprint reference for custom repositories [here](blueprint-reference.md).
 
 ## 3. Install a third-party package and save configurations
 In this case it is necessary to use a combination of payload repositories and custom repositories in order to achieve the desired outcome. This will ensure that the package is installed during 

docs/service/architecture.md

@@ -39,7 +39,7 @@ If you want to contribute to our frontend or backend, here are guides on how to
 * 🟢 Deployment metadata is open. [[1]](https://github.com/osbuild/osbuild-composer/blob/main/templates/composer.yml) [[2]](https://github.com/osbuild/image-builder/blob/main/templates/image-builder.yml)
 #### 🟢 Contribution workflow
 * 🟢 External contributors can follow the same workflow as team members.
-* 🟢 [The workflow is publicly documented.](../developer-guide/general/workflow.html)
+* 🟢 [The workflow is publicly documented.](../developer-guide/general/workflow.md)
 * 🟢 Regular contributors can trigger CI.
 * 🟢 External contributions are eagerly reviewed.
 #### 🟠 Issue tracking and planning

docusaurus.config.ts

@@ -91,15 +91,6 @@ const config: Config = {
     footer: {
       style: 'dark',
       links: [
-        {
-          title: 'Docs',
-          items: [
-            {
-              label: 'Tutorial',
-              to: '/docs/intro',
-            },
-          ],
-        },
         {
           title: 'Community',
           items: [