Decision Records
Decisions about the homelab’s architecture, tooling, and conventions, recorded as architectural decision records (ADRs).
Why I did the thing, for future me. Subject to change when I inevitably regret it.
Will I use this for ALL my decisions? Hell nah.
Copy the template to start a new ADR. Add it to the table below and keep its status in the table up to date.
Check whether your new ADR supersedes an older one. If it does, update the older ADR’s status to
Superseded by.Decisions
| ADR | Decision | Status |
|---|---|---|
| 0001 | Use Diátaxis for the documentation framework | Accepted |
| 0002 | Use the Google developer documentation style guide, enforced with Vale | Accepted |
| 0003 | Use Hugo with Hextra for documentation | Accepted |
| 0004 | Follow each product’s own conventions | Accepted |
| 0005 | Prefer reproducible, automation-first homelab management | Accepted |
| 0006 | Use Task as the command wrapper | Accepted |
| 0007 | Use Talos Linux to run Kubernetes | Accepted |
| 0008 | Use Proxmox VE as the hypervisor | Accepted |
| 0009 | Use OpenTofu instead of Terraform | Accepted |
| 0010 | Use GitHub Pages to serve documentation | Accepted |
| 0011 | Use pre-commit for local and CI checks | Accepted |
| 0012 | Use mise to manage development tools | Accepted |
| 0013 | Use Renovate for dependency updates | Accepted |