🔥 Clean up README even further

README.md

···
 <h1 align="center">Puzzlevision<br></h1>
 <div align="center">Non-stop entertainment! The wackiest NixOS configuration to-date.</div>
 <br>
-<div align="center">
-    <img src=".tangled/assets/powered-by-nixos.gif" width="88px" height="31px">
-    <img src=".tangled/assets/i-love-reproducing-nix-btw.gif" width="88px" height="31px">
-    <img src=".tangled/assets/anything-but-windows.gif" width="88px" height="31px">
-</div>
-<br>
 
-## 💡 Welcome to the 3rd iteration of this flake (new version again, yay :3)
-Any and all changes on this branch are officially part of the 3rd iteration of these NixOS dotfiles.
-
-NOTHING here is stable or in any way ready for production use, please keep that in mind, if you ever find yourself looking through the structure/code.
+> [!CAUTION]
+> Any and all changes on this branch are officially part of the 3rd iteration of these NixOS dotfiles.
+> NOTHING here is stable or in any way ready for production use, please keep that in mind, if you ever find yourself looking through the structure/code.
 
 ## 🚀 Deployment
 To deploy a system run the following command in your terminal of choice.
···
 sudo nixos-rebuild build-vm --flake .#hostname --accept-flake-config
 ```
 
-## 🔑 Secrets Management
-Secrets are managed by the [sops-nix](https://github.com/Mic92/sops-nix) nixos/home-manager modules respectively.
-
-- General secrets are stored within the `secrets` directory.
-- System specific secrets are stored within their respective `systems/<system_type>/<system_name>/secrets` directory.
-- User secrets are stored within their respective `homes/<system_type>/<user_name>/secrets` directory.
-
-The following command may be used to convert the SSH host key of a new machine to an age key:
-
-```sh
-nix-shell -p ssh-to-age --run 'ssh-keyscan example.com | ssh-to-age'
-```
-
-Additionally, the following command may be used to create a new sops secret file:
-
-```sh
-nix-shell -p sops --run "sops secrets/example.yaml"
-```
-
-You may also encrypt arbitrary binary formats, like .cfg, using the following command:
-
-> [!IMPORTANT]
-> The original file location also HAS to match one of the sops creation rules, not just the output.
-> Yes, I know this is stupid, and yes, I've wasted way too much time dealing with this :3
-
-```sh
-nix-shell -p sops --run "sops -e original_file.cfg > secrets/encrypted_file.cfg"
-```
-
-Finally, when adding new systems, make sure to update any required secret files with the following command:
-
-```sh
-nix-shell -p sops --run "sops updatekeys secrets/example.yaml"
-```
-
 ## 👷 CI/CD coverage
 There will be CI/CD coverage based on the Spindle-Pipeline-System™, when I find the time.
 
 ## 🏗️ Structure
-This flake follows an opinionated directory structure, described below.
-
-```
-flake.nix  --> The flake.
-/systems   --> NixOS configurations for various types of systems, using easy-hosts.
-/modules   --> Modules that are mapped to their corresponding easy-hosts class (and home modules).
-  /nixos   --> (example) Modules specific to the nixos class configured in easy-hosts.
-/homes     --> Directory for home-manager configurations, not specific to the system type.
-/lib       --> A place for custom lib attributes exposed on the flake namespace (lib.puzzlevision.mkOpt).
-(more...)  --> Additional directories have been considered (e.g. shells), but as of right now, they serve no use to me.
-```
+The folder structure of this flake will be documented here, once finalised.
 
 ## 🎨 Credits
 Parts of this flake were inspired by the likes of: