Reshaping CompFlu sub-category for the post-Manuel age...

User guidelines, orga stuff (it's possibly fine to go on polluting the root namespace with this)
- ~~rooms/buildings~~ → Admin
- ~~group seminar~~ → seminars
- website
work
- blue-pill (general concepts, up to (power-)end-user troubleshooting)
  - cluster usage (slurm)
    - Modules (more or less clever)
    - ~~Scope definition for queues~~ → cluster-usage
    - ~~–exclusive policy (vs. RAM limits)~~
    - salloc -p haswell -w sun-14
  - working places, workstations/laptops/remote
  - Jupyter hub (see python)
  - software, sun-specific workflows
    - git
    - LB3D
    - PV for OPV
  - hallway screen
  - compute projects
  - data storage, quota, backups
  - password change (Qlustar: AD = via ITS-Selfservice/Ctrl-Alt-Del; local user = ql-change-passwd)
- red-pill (nasty admin-only stuff)
  - mailing list alarm levels
  - Rittal
  - server-layout
  - User creation policies (contract, types of external users)
  - NFS how-to (QluMan set-up + manually editing /etc/fstab, action after reboot)
  - ~~EasyBuild Howto~~ → superseded by spack
  - History of SSL certificates
archive (seminars-2019, DevelCafe etc.), guidelines when to archive stuff

CompFlu content

Split soft LB3D documentation into generic (to put into the source repo) and HI-ERN-specific parts (to put here)

it-guy Makes sense to have, but only if properly maintained (by whom?). Is the place of some technical information that is nowhere else on the wiki (that should not be the case)