From 7f35c09b3b7b11d27a4516da5c1a4d888a9997ec Mon Sep 17 00:00:00 2001
From: Stefan Koelle <stefan.koelle@gmail.com>
Date: Fri, 11 Sep 2026 22:20:45 +0200
Subject: [PATCH] Fix broken internal links missing section path prefixes

---
 infra/dev-environment/index.njk    | 2 +-
 infra/openwrt/index.njk            | 2 +-
 infra/proxmox/index.njk            | 4 ++--
 smarthome/tasmota-energy/index.njk | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/infra/dev-environment/index.njk b/infra/dev-environment/index.njk
index 6fbe5bf..d6885e0 100644
--- a/infra/dev-environment/index.njk
+++ b/infra/dev-environment/index.njk
@@ -9,7 +9,7 @@ layout: base.njk
 <h1>Xubuntu Dev VM</h1>
 <div class="detail-content">
 
-<p>This is a Xubuntu virtual machine on <a href="/proxmox/">Proxmox pve2</a> in the study that serves as my main development environment, replacing the need for a dedicated physical workstation. It's designed to be lightweight, remotely accessible from anywhere, and, most importantly, completely disposable, which is what makes it a safe place to let AI coding agents operate with far more autonomy than I'd otherwise allow.</p>
+<p>This is a Xubuntu virtual machine on <a href="/infra/proxmox/">Proxmox pve2</a> in the study that serves as my main development environment, replacing the need for a dedicated physical workstation. It's designed to be lightweight, remotely accessible from anywhere, and, most importantly, completely disposable, which is what makes it a safe place to let AI coding agents operate with far more autonomy than I'd otherwise allow.</p>
 
 <h2>Why a disposable VM is the biggest advantage</h2>
 <ul>
diff --git a/infra/openwrt/index.njk b/infra/openwrt/index.njk
index 78af30f..a9ec683 100644
--- a/infra/openwrt/index.njk
+++ b/infra/openwrt/index.njk
@@ -37,6 +37,6 @@ layout: base.njk
 </ul>
 
 <h2>Monitoring</h2>
-<p>The OpenWrt router is integrated into the <a href="/monitoring/">Prometheus monitoring stack</a> via SNMP exporter, providing visibility into WAN uptime, throughput, and connection quality across both paths.</p>
+<p>The OpenWrt router is integrated into the <a href="/infra/monitoring/">Prometheus monitoring stack</a> via SNMP exporter, providing visibility into WAN uptime, throughput, and connection quality across both paths.</p>
 
 </div>
diff --git a/infra/proxmox/index.njk b/infra/proxmox/index.njk
index 68282f2..87e97e3 100644
--- a/infra/proxmox/index.njk
+++ b/infra/proxmox/index.njk
@@ -9,12 +9,12 @@ layout: base.njk
 <h1>Proxmox Virtualization</h1>
 <div class="detail-content">
 
-<p>Proxmox VE (Virtual Environment) is a free, open-source virtualization platform that combines KVM-based full virtual machines with lightweight LXC containers in a single web-managed system. It's built on top of Debian, includes ZFS storage management, backup/restore, clustering and monitoring out of the box, and is the foundation my entire homelab runs on, both the <a href="/docker/">Docker</a> hosts and the standalone <a href="/lxc/">LXC services</a> live as guests on top of it.</p>
+<p>Proxmox VE (Virtual Environment) is a free, open-source virtualization platform that combines KVM-based full virtual machines with lightweight LXC containers in a single web-managed system. It's built on top of Debian, includes ZFS storage management, backup/restore, clustering and monitoring out of the box, and is the foundation my entire homelab runs on, both the <a href="/infra/docker/">Docker</a> hosts and the standalone <a href="/infra/lxc/">LXC services</a> live as guests on top of it.</p>
 
 <h2>Hardware</h2>
 <ul>
 <li><strong>PVE (main server)</strong>, a Beelink Mini-PC, running as the primary Proxmox host. It has a 500GB SSD for VM and container storage, and connects to the network via the server-room Zyxel switch.</li>
-<li><strong>pve2 (test server)</strong>, a second Proxmox host, physically located in the study and connected via the OpenWRT-side Zyxel switch. It's dedicated purely to testing and development, running the third <a href="/docker/">Docker host VM (docker-host-pve2)</a> plus experimental setups without risking the production environment.</li>
+<li><strong>pve2 (test server)</strong>, a second Proxmox host, physically located in the study and connected via the OpenWRT-side Zyxel switch. It's dedicated purely to testing and development, running the third <a href="/infra/docker/">Docker host VM (docker-host-pve2)</a> plus experimental setups without risking the production environment.</li>
 <li><strong>Backups</strong>, nightly VM backups from PVE run at 00:30 to an NFS share on the Synology (<code>nas:/volume1/backup</code>), with retention of the last 3 daily, 3 monthly and 1 yearly backup.</li>
 </ul>
 
diff --git a/smarthome/tasmota-energy/index.njk b/smarthome/tasmota-energy/index.njk
index f7c9a56..bf33e53 100644
--- a/smarthome/tasmota-energy/index.njk
+++ b/smarthome/tasmota-energy/index.njk
@@ -56,7 +56,7 @@ via Flux to display real-time and historical usage charts.</p>
 </ul>
 
 <h2>Air quality and climate data</h2>
-<p>The same InfluxDB instance also stores temperature and humidity readings from HomematicIP room sensors and ESP32 DHT22 devices. These feed the <a href="/air-quality/">air quality dashboard</a>, which visualizes 24-hour climate history across 10 rooms. The energy and climate data share the MQTT-to-InfluxDB pipeline but live in separate measurement categories, keeping power monitoring and environmental sensing cleanly separated.</p>
+<p>The same InfluxDB instance also stores temperature and humidity readings from HomematicIP room sensors and ESP32 DHT22 devices. These feed the <a href="/smarthome/air-quality/">air quality dashboard</a>, which visualizes 24-hour climate history across 10 rooms. The energy and climate data share the MQTT-to-InfluxDB pipeline but live in separate measurement categories, keeping power monitoring and environmental sensing cleanly separated.</p>
 
 <h2>Why Tasmota over alternatives</h2>
 <p>Tasmota was chosen over alternatives like ESPHome or Tuya firmware for