domus-docs: Docs-as-Code System
Problem
Technical documentation sprawls across wikis, READMEs, and random markdown files:
-
Scattered knowledge - Multiple repos, no central index
-
Inconsistent formatting - Each repo has its own style
-
Manual deployment - FTP uploads, rsync scripts
-
No version control - Can’t track changes or rollback
Result: Documentation rot. Information exists but nobody can find it.
Solution
domus-docs aggregates 19 component repositories into a unified documentation site using Antora:
Component Repositories
| Repository | Content | Status |
|---|---|---|
domus-infra-ops |
PKI, backup, disaster recovery, runbooks |
Active |
domus-ise-linux |
802.1X EAP-TLS, NetworkManager, wpa_supplicant |
Active |
domus-linux-ops |
Shell mastery, AWK, Grep, Sed, command reference |
Active |
domus-secrets-ops |
Vault, Gopass, certificate management |
Active |
domus-netapi-docs |
netapi CLI reference and patterns |
Active |
domus-siem-ops |
QRadar AQL, Sentinel KQL, Wazuh |
Active |
domus-identity-ops |
Keycloak, FreeIPA, AD integration |
Active |
domus-captures |
Work logs, meeting notes, decisions |
Active |
Links
-
Site: docs.domusdigitalis.dev
-
Aggregator: github.com/EvanusModestus/domus-docs
-
UI Bundle: github.com/EvanusModestus/domus-antora-ui