Move nodes/services into reference section, fix broken links

mfisher87 · Dec 25, 2023 · c6fb846 · c6fb846
1 parent eabf95c
commit c6fb846
Show file tree

Hide file tree

Showing 11 changed files with 18 additions and 20 deletions.
diff --git a/_quarto.yml b/_quarto.yml
@@ -32,12 +32,8 @@ website:
       - text: "💡 Ideas"
         href: "ideas/index.md"
       - text: "---"
-      - text: "Nodes"
-        href: "nodes/index.md"
-        contents: "nodes/*.md"
-      - text: "Services"
-        href: "services/index.md"
-        contents: "services/*.md"
+      - text: "Reference"
+        contents: "reference/*/index.md"
       - text: "How to"
         href: "how-to/index.md"
         contents: "how-to/*.md"

diff --git a/changes/2023-11-disk-failure-incident-response/index.md b/changes/2023-11-disk-failure-incident-response/index.md
@@ -23,7 +23,8 @@ need to be recreated from scratch to replace all the services that were running
 ### Labels!
 
 Finding the physical failed drive was far more of a challenge than I wanted it to be. I
-printed labels for each drive bay on the [storage node](/nodes/storage.md) including:
+printed labels for each drive bay on the [storage node](/reference/nodes/storage.md)
+including:
 
 * Internal SATA port the bay is connected to
 * The drive model currently in the bay

diff --git a/incidents/2023-10-28-disk-failure/index.md b/incidents/2023-10-28-disk-failure/index.md
@@ -1,8 +1,9 @@
 ---
 title: "2023-10-28: Disk failure"
 description: |
-  A 1TB HDD in the [storage node](/nodes/storage.md) failed. This drive was used for VM
-  backups, and (mistakenly) for a services VM disk. This resulted in minor data loss.
+  A 1TB HDD in the [storage node](/reference/nodes/storage.md) failed. This drive was
+  used for VM backups, and (mistakenly) for a services VM disk. This resulted in minor
+  data loss.
 ---
 
 This disk was unfortunately unprotected, because I figured it was just VM backups and if
@@ -15,5 +16,5 @@ relatively unimportant secrets.
 
 ## Infrastructure changes
 
-See the related [change document](/changes/2023-11-incident-response/index.md) for more
-details about changes as a result of this incident.
+See the related [change document](/changes/2023-11-disk-failure-incident-response/index.md)
+for more details about changes as a result of this incident.
diff --git a/index.md b/index.md
@@ -6,9 +6,9 @@ title: "My infrastructure"
 
 I have two physical nodes:
 
-1. [Storage](nodes/storage.md): An older build from new parts in a Supermicro chassis with 12
+1. [Storage](/reference/nodes/storage.md): An older build from new parts in a Supermicro chassis with 12
    hotswap drive bays.
-2. [Compute](nodes/compute.md): A newer build from used eBay parts in a Supermicro
+2. [Compute](/reference/nodes/compute.md): A newer build from used eBay parts in a Supermicro
    chassis with lots of airflow.
 
 

diff --git a/nodes/compute.md → reference/nodes/compute.md b/nodes/compute.md → reference/nodes/compute.md
diff --git a/nodes/index.md → reference/nodes/index.md b/nodes/index.md → reference/nodes/index.md
@@ -1,5 +1,5 @@
 ---
 title: "Nodes"
 listing:
-  type: table
+  type: "grid"
 ---
diff --git a/nodes/storage.md → reference/nodes/storage.md b/nodes/storage.md → reference/nodes/storage.md
diff --git a/services/end-user.md → reference/services/end-user.md b/services/end-user.md → reference/services/end-user.md
diff --git a/reference/services/index.md b/reference/services/index.md
@@ -0,0 +1,5 @@
+---
+title: "Services"
+listing:
+  type: "grid" 
+---
diff --git a/services/infrastructure.md → reference/services/infrastructure.md b/services/infrastructure.md → reference/services/infrastructure.md
@@ -3,6 +3,6 @@ title: "Infrastructure services"
 ---
 
 Services which provide resources needed to run [end-user
-services](/services/end-user.md).
+services](/reference/services/end-user.md).
 
 E.g. _Proxmox VE_, _Kubernetes_, _Docker_, _Traefik_, _MinIO_, etc.
diff --git a/services/index.md b/services/index.md