Skip to content

Placement Rules

Main Rule

Did this happen in the real homelab?
  yes -> infrastructure/
  no  -> cloud/

Section Rule

Once a document is sorted into infrastructure/ or cloud/ by the Main Rule above, decide its top-level home by document type:

Is this a specific incident with a start and an end?
  spans one category    -> that category's own folder (e.g. networking/)
  spans multiple         -> troubleshooting-incidents/

Is this routine, repeatable work done *before* anything breaks
(provisioning, rotation, onboarding)?
  yes -> top-level sops/

Is this a reactive playbook for a *class* of future incident, not one
specific past event (deployment, disaster recovery, incident response,
identity operations)?
  yes -> top-level runbooks/

Is this a sandbox or one-off experiment, not a persistent system?
  yes -> top-level labs/

Is this cross-cutting system design reasoning spanning more than one
project or domain?
  yes -> top-level architecture/

Is this a polished, public write-up of a completed project?
  yes -> top-level portfolio/ (displayed in the nav as "Projects")

Date Rule

Remove dates from:

  • filenames
  • visible headings
  • indexes
  • generated metadata
  • runbook body content

Use logical event order instead of date order.

Ordering Rule

Order documents by logical event flow inside each category.

design/planning -> baseline setup -> configuration -> incident -> recovery -> hardening -> follow-up