Fix broken links and update docusaurus config

Author: fzdarsky

docs/developer/index.md

@@ -157,5 +157,3 @@ make deploy-e2e-extras
 ```
 
 The Prometheus web UI is then accessible on `http://localhost:9090`
-
-For detailed information about the metrics system architecture, see [Metrics Architecture](architecture/metrics.md).

docs/developer/service-quadlets.md

@@ -265,7 +265,7 @@ The RPM upgrade process includes:
 > Database migration dry-run can be enabled/disabled by editing `/etc/flightctl/flightctl-services-install.conf` and setting `FLIGHTCTL_MIGRATION_DRY_RUN=1`. This is recommended to catch potential migration issues before they affect production.
 
 > [!NOTE] 
-> Downgrades are not supported. Be sure to back up your system before upgrading. If an upgrade fails, follow the [Flight Control Restore Operations](restore.md#flight-control-restore-operations).
+> Downgrades are not supported. Be sure to back up your system before upgrading. If an upgrade fails, follow the [Flight Control Restore Operations](../user/restore.md).
 
 ### Running the Services Container
 

docs/user/building-images.md

@@ -20,9 +20,9 @@ At a high level, the image building process for bootc works as follows:
 4. Build, publish, and sign an **OS disk image** using `bootc-image-builder` (bib) and `skopeo`.
 
 <picture>
-  <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/flightctl/flightctl/main/docs/images/image-building.svg">
-  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/flightctl/flightctl/main/docs/images/image-building-dark.svg">
-  <img alt="Diagram of image building process" src="https://raw.githubusercontent.com/flightctl/flightctl/main/docs/images/image-building.svg">
+  <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/flightctl/flightctl/main/docs/images/image-building.svg"/>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/flightctl/flightctl/main/docs/images/image-building-dark.svg"/>
+  <img alt="Diagram of image building process" src="https://raw.githubusercontent.com/flightctl/flightctl/main/docs/images/image-building.svg"/>
 </picture>
 
 The OS disk image is used to image (or "flash") a device when it is provisioned. For subsequent device updates, only the OS image (bootc) is required. This is because bootc is a *file system* image, that is it contains just the files in the file system including their attributes, but the disk layout (partitions, volumes) and file systems need to have been created first. The OS disk image includes everything, the disk layout, bootloader, file systems, and the files in the OS image (bootc). It can therefore be written verbatim to the device's drive.

docs/user/getting-started.md

@@ -174,7 +174,7 @@ FC_API_URL=<API_URL>
 
 ```
 
-For managing ongoing Flight Control deployments including upgrades, rollbacks, and monitoring, refer to the [Helm Chart Documentation](../../deploy/helm/flightctl/README.md#upgrade-chart).
+For managing ongoing Flight Control deployments including upgrades and monitoring, refer to the [Helm Chart Documentation](https://github.com/flightctl/flightctl/blob/main/deploy/helm/flightctl/README.md).
 
 ## Installing the Flight Control CLI
 

docs/user/index.md

@@ -18,7 +18,7 @@ Welcome to the Flight Control user documentation.
   * [Considerations for Specific Target Platforms](building-images.md#considerations-for-specific-target-platforms)
     * [Red Hat OpenShift Virtualization](building-images.md#red-hat-openshift-virtualization)
     * [VMware vSphere](building-images.md#vmware-vsphere)
-  * [Best Practices](building-images.md#best-practices)
+  * [Best Practices](building-images.md#best-practices-when-building-images)
 * **[Provisioning Devices](provisioning-devices.md)** - How to provision a device with an OS image.
   * [Testing an OS image on a developer machine](provisioning-devices.md#testing-an-os-image-on-a-developer-machine)
   * [Provisioning Physical Devices](provisioning-devices.md#provisioning-physical-devices)
@@ -42,7 +42,6 @@ Welcome to the Flight Control user documentation.
   * [Selecting Devices into a Fleet](managing-fleets.md#selecting-devices-into-a-fleet)
   * [Defining Device Templates](managing-fleets.md#defining-device-templates)
   * [Defining Rollout Policies](managing-fleets.md#defining-rollout-policies)
-  * [Managing Fleets Using GitOps](managing-fleets.md#managing-fleets-using-gitops)
 * **Solving Specific Use Cases** - How to solve specific use cases in Flight Control.
   * [Auto-Registering Devices with MicroShift into ACM](registering-microshift-devices-acm.md)
   * [Adding Device Observability](device-observability.md)

docs/user/managing-devices.md

@@ -40,7 +40,7 @@ NAME                                                  APPROVAL  APPROVER  APPROV
 
 Once approved, the device will get issued its initial management certificate and get registered to the device inventory and is now ready to be managed.
 
-## Viewing and Customizing the Device System Information
+## Viewing the Device Inventory and Device Details
 
 Flight Control automatically gathers system information from each device to help identify its hardware, OS, and environment. This data is shown in the `status.systemInfo` field. Fields can optionally be promoted to labels during the enrollment process, this must be done manually or through external automation. Promoting fields to labels enables powerful grouping and querying capabilities, such as filtering devices by region or OS version. You can also define your own fields in `status.systemInfo.customInfo`, allowing the agent to collect user-defined metadata through custom commands.
 
@@ -947,7 +947,7 @@ Each schedule supports:
 | `timeZone`             | (Optional) The time zone used to evaluate the schedule. Defaults to the device’s local system time zone. Must be a valid [IANA time zone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). |
 | `startGraceDuration`   | (Optional) A duration string that extends the allowed start time window after a schedule trigger. Follows the [Go duration format](https://pkg.go.dev/time#ParseDuration), such as `"1h"` or `"45m"`. |
 
-The Flight Control agent evaluates these schedules during its control loop to determine whether each policy is currently allowed to proceed. While the device waits for the update window the device status will read `OutOfDate`. For more details please see [Device API Statuses](device-api-statuses.md#device-api-statuses).
+The Flight Control agent evaluates these schedules during its control loop to determine whether each policy is currently allowed to proceed. While the device waits for the update window the device status will read `OutOfDate`. For more details please see [Device API Statuses](device-api-statuses.md).
 
 >[!TIP]
 > Use [crontab guru](https://crontab.guru/) to create and test cron expressions interactively.

docs/user/tpm-authentication.md

@@ -67,7 +67,7 @@ The Flight Control API server needs TPM manufacturer CA certificates to validate
 
 ### TPM Manufacturer CA Certificates
 
-Several [well-known](https://trustedcomputinggroup.org/membership/certification/tpm-certified-products/) discrete [TPM manufacturer certificates](../../tpm-manufacturer-certs) have been downloaded for use. They are provided in PEM format to be directly compatible with Flight Control services, and contain metadata indicating their download URL and when they were downloaded.
+Several [well-known](https://trustedcomputinggroup.org/membership/certification/tpm-certified-products/) discrete [TPM manufacturer certificates](https://github.com/flightctl/flightctl/tree/main/tpm-manufacturer-certs) have been downloaded for use. They are provided in PEM format to be directly compatible with Flight Control services, and contain metadata indicating their download URL and when they were downloaded.
 
 - **Infineon**
   - [TPM Product Page](https://www.infineon.com/products/security-smart-card-solutions/optiga-embedded-security-solutions/optiga-tpm). Each product's documents were inspected and individual intermediate certificates were pulled. Root certificates were obtained via following the AIA chain in the intermediate certs.

docusaurus.config.js

@@ -26,7 +26,6 @@ const config = {
   projectName: "flightctl.github.io", // Usually your repo name.
 
   onBrokenLinks: "throw",
-  onBrokenMarkdownLinks: "warn",
 
   // Even if you don't use internationalization, you can use this field to set
   // useful metadata like html lang. For example, if your site is Chinese, you
@@ -36,6 +35,13 @@ const config = {
     locales: ["en"],
   },
 
+  markdown: {
+    hooks: {
+      onBrokenMarkdownLinks: 'warn',
+      onBrokenMarkdownImages: 'throw',
+    }
+  },
+
   presets: [
     [
       "classic",