restructure to use page bundles

also fix post thumbnail embeds

Author: udf

.gitignore

@@ -1,4 +1,5 @@
 node_modules
 *.lock
 resources/_gen
-public
+public
+draft.md

static/taiga-this-is-dumb-thumb.jpg renamed to content/blog/custom-partial-nix-store-path/cover.jpg

@@ -4,7 +4,7 @@ title: "Brute forcing NixOS store paths for no particular reason"
 description: "This is the second dumbest thing I've ever done."
 date: 2022-02-07
 tags: ["nixos", "memes"]
-thumbnail: /taiga-this-is-dumb-thumb.jpg
+thumbnail: cover.jpg
 ---
 
 ## The Nix store

content/blog/custom-partial-nix-store-path.md renamed to content/blog/custom-partial-nix-store-path/index.md

@@ -4,7 +4,7 @@ title: "Generating a custom Syncthing device ID"
 description: "Et tu, Brute-force?"
 date: 2024-05-22
 tags: ["syncthing", "openssl"]
-thumbnail: /syncthing-device-id.jpg
+thumbnail: cover.jpg
 ---
 
 ## What's a Syncthing?
@@ -38,7 +38,7 @@ It is in the format `xxxxxxx-xxxxxxA-xxxxxxx-xxxxxxB-xxxxxxx-xxxxxxC-xxxxxxx-xxx
 where `A`, `B`, `C`, and `D` are check digits using [a slightly altered version of the Luhn mod N algorithm](https://forum.syncthing.net/t/v0-9-0-new-node-id-format/478/5), and the `x`s are characters from the hash represented in base32.
 
 Each group of the ID is 7 characters long, and the first group is displayed in the GUI in the identification section:
-{{< figure src="/syncthing-device-gui.png" title="A device in Syncthing's GUI" >}}
+{{< figure src="device-gui.png" title="A device in Syncthing's GUI" >}}
 
 
 ## A dumb idea
@@ -279,4 +279,4 @@ $ openssl x509 -inform DER -in 2327237.der -out cert.pem
 ```
 
 And after replacing the `cert.pem` and `key.pem` files and restarting Syncthing (as well as re-accepting every share on every device):
-{{< figure src="/syncthing-device-alice.jpg" title="The custom device ID now matches the device name, how chic!" >}}
+{{< figure src="device-alice.jpg" title="The custom device ID now matches the device name, how chic!" >}}

static/syncthing-device-id.jpg renamed to content/blog/custom-syncthing-id/cover.jpg

@@ -4,7 +4,7 @@ title: "exFAT data recovery"
 date: 2023-04-15
 description: "Recovering data from a damaged exFAT filesystem"
 tags: ["misc", "data recovery"]
-thumbnail: /vitarec.jpg
+thumbnail: cover.jpg
 ---
 
 ## A simple mistake
@@ -51,11 +51,11 @@ The size of the blocks is at the beginning of the drive, along with other import
 
 I found a metadata block in [ImHex](https://github.com/WerWolv/ImHex/), after it ends there are a bunch of zeros, and the next block looks like the start of a PNG file:
 
-{{< figure src="/vitarec-metadata.png" title="A metadata block" >}}
+{{< figure src="metadata.png" title="A metadata block" >}}
 
-{{< figure src="/vitarec-end-of-metadata.png" title="The end of the metadata block's data" >}}
+{{< figure src="end-of-metadata.png" title="The end of the metadata block's data" >}}
 
-{{< figure src="/vitarec-a-wild-png.png" title="The start of the next block" >}}
+{{< figure src="a-wild-png.png" title="The start of the next block" >}}
 
 This lets me calculate the block size of the filesystem:  
 `0x16ECE78000` - `0x16ECE70000` = `0x8000` (32 KiB)
@@ -216,7 +216,7 @@ offset which will let me know the address of any block number.
 
 I ran the game and made a new save (after watching all the unskippable cutscenes again) to get a look at the the file structure:
 
-{{< figure src="/vitarec-ffx-saves.png" title="FFX saves (directories are blue, files are green)" >}}
+{{< figure src="ffx-saves.png" title="FFX saves (directories are blue, files are green)" >}}
 
 Surprisingly, the filename `data0000.bin` is only shared with Gravity Rush (another [PhyreEngine](https://en.wikipedia.org/wiki/PhyreEngine) game). So I repeated the same file name search as before:
 
@@ -297,7 +297,7 @@ I guess that the file was fragmented when part of it was changed. So I combined
 
 I then threw the recovered files onto my Vita and:
 
-{{< figure src="/vitarec-ffx.png" title="It works!" >}}
+{{< figure src="ffx.png" title="It works!" >}}
 
 (I got insanely lucky)
 
@@ -576,7 +576,7 @@ with open('unknown.txt', 'w') as f:
 {{< /details >}}
 
 I plotted the blocks to see what the candidates look like:
-{{< figure src="/vitarec-plot-unknown.png" title="Each pixel is a block, green ones are not in my backups" >}}
+{{< figure src="plot-unknown.png" title="Each pixel is a block, green ones are not in my backups" >}}
 
 Out of the 7806338 blocks:
 - 4866578 are unique **(62.34%)**
@@ -724,4 +724,4 @@ I don't know what the name of each file should be, so I will just have to guess:
 5463477.32k -> SAVE255.DAT
 ```
 
-{{< figure src="/vitarec-cold-steel.png" title="Success? The fragmented thumbnail doesn't seem to decrypt correctly, but the save does." >}}
+{{< figure src="cold-steel.png" title="Success? The fragmented thumbnail doesn't seem to decrypt correctly, but the save does." >}}

static/syncthing-device-alice.jpg renamed to content/blog/custom-syncthing-id/device-alice.jpg

@@ -4,7 +4,7 @@ title: "Making user IDs deterministic on NixOS"
 description: "Now with $100% more containers!"
 date: 2021-07-18
 tags: ["nixos", "containerisation"]
-thumbnail: /kuroneko-deterministic.png
+thumbnail: cover.png
 ---
 
 ## Why?

static/syncthing-device-gui.png renamed to content/blog/custom-syncthing-id/device-gui.png

@@ -4,7 +4,7 @@ title: "NixOS - Automatically restarting a systemd unit when a local config file
 description: "A simple fix for a simple problem."
 date: 2022-03-15
 tags: ["nixos", "guide"]
-thumbnail: /nixos-auto-restart-service.jpg
+thumbnail: cover.jpg
 ---
 
 ## The Setup

content/blog/custom-syncthing-id.md renamed to content/blog/custom-syncthing-id/index.md

@@ -4,7 +4,7 @@ title: "How to run a local script as a systemd service on NixOS"
 description: "No packaging necessary."
 date: 2022-02-07
 tags: ["nixos", "guide"]
-thumbnail: /nixos-local-script-service.jpg
+thumbnail: cover.jpg
 ---
 
 If your script is small and using shell, then your service definition could look like this:

static/vitarec-a-wild-png.png renamed to content/blog/exfat-data-recovery/a-wild-png.png

@@ -4,7 +4,7 @@ title: "Setting up NixOS on a dedicated server"
 description: "No human interaction needed."
 date: 2021-02-09
 tags: ["nixos", "devops"]
-thumbnail: /feed-me-a-server.jpg
+thumbnail: cover.jpg
 ---
 
 ## Preamble
@@ -71,6 +71,6 @@ So what can we do? [Build our own ISO](https://nixos.wiki/wiki/Creating_a_NixOS_
 And that's about it, so I crossed my fingers and rebooted the system.
 
 ...and it worked!  
-{{< figure src="/nixos-iso-hanzo-boot.jpg" title="You have no idea how happy I am" >}}
+{{< figure src="nixos-iso-hanzo-boot.jpg" title="You have no idea how happy I am" >}}
 
 That's about the end of everything that [the excellent NixOS wiki](https://nixos.wiki/wiki/NixOS_Installation_Guide) can't explain.

static/vitarec-cold-steel.png renamed to content/blog/exfat-data-recovery/cold-steel.png

@@ -4,7 +4,7 @@ title: "In-place rebuilding of a docker compose project with systemd"
 description: "Did you just restart prod again?"
 date: 2024-05-15
 tags: ["containerisation", "docker", "systemd"]
-thumbnail: /docker-systemd.jpg
+thumbnail: cover.jpg
 ---
 
 ## The usual approach