This is loosely inspired by the dendritic pattern. I think a flat hierarchy makes configs hard to read, which is why I decided to introduce a hierarchy for the different types of modules.

For now the hierarchy looks as follows:

1. abstract - Foundational configuration, mostly of the flake itself
2. base - Base NixOS modules that will apply to all systems
3. case - Use case (desktop, development, server)
4. device-type - Device type (laptop, workstation, server)
5. extensions - Modules that might be shared between individual machines, but don't apply to a whole class/type (postgres, nginx, traefik)