adding some lines

projects/homelab/diagrams.md

@@ -13,6 +13,20 @@ tags: ['homelab', 'infrastructure', 'network']
 
 ---
 
+## 2026 Home lab
+
+{{< rawhtml >}}
+<iframe
+  src="http://homelable/view?key=live"
+  width="100%"
+  height="600px"
+  style="border:none; border-radius: 8px; box-shadow: 0 4px 6px rgba(0,0,0,0.1);"
+  allowfullscreen>
+</iframe>
+{{< /rawhtml >}}
+
+---
+
 ## 2024 Home Lab
 
 ![sc_apartment_network_diagram_2024.png](/projects/homelab/sc_apartment_network_diagram_2024.png)

projects/nginx-proxy-manager/index.md

@@ -32,6 +32,8 @@ configurations.
 {{% include "/srv/configs/docker_compose/nginx-proxy-manager/docker-compose.yaml" %}}
 ```
 
+---
+
 ## Automation (Docker Labels)
 
 To avoid manually configuring Proxy Hosts in the UI (and to keep configuration tightly coupled with the services themselves), I use the `npm-sync` sidecar container. 
@@ -56,6 +58,8 @@ services:
 > [!important] Direct Edits
 > Avoid making direct edits to NPM `.conf` files on the host, as it will desync the database and the Web UI. Always use the Web UI or API-driven automation like `npm-sync`.
 
+---
+
 ## Nginx routing
 
 Nginx gives you that great routing to your internal networked servers. Also
@@ -72,6 +76,8 @@ all traffic to nginx. Then based on some rules I have set up I can point that
 traffic to my internal server. For this I will need a domain name server (DNS)
 to point to my external IP.
 
+---
+
 ## DNS
 
 A domain name server (DNS) allows me to make a name that can be easily looked up
@@ -172,3 +178,5 @@ Use https here only if you have ssl setup on your origin server and your server
 is set up to accept https, otherwise you make get bad gateway 502 errors.
 
 ![nginx_ssl_internal_scheme_example.png](nginx_ssl_internal_scheme_example.png#center)
+
+---