Architecture
Architecture
domus-captures is the captures Antora component — one spoke in a 15-spoke documentation ecosystem aggregated by the domus-docs hub and deployed to Cloudflare Pages.
Every push to this repository triggers an automatic rebuild.
The architecture prioritizes single-source-of-truth partials, machine-parseable metadata, and a governance hierarchy that scales without restructuring.
Component Identity
| Field | Value |
|---|---|
Name |
|
Title |
Work Chronicles |
start_page |
|
Nav Order |
2 |
Category |
Core |
Deploy URL |
Spoke-Hub Model
Fifteen spoke repositories publish independently.
The domus-docs hub aggregates them via antora-playbook.yml.
Cloudflare Pages auto-builds on any spoke push — the hub is only re-pushed when the playbook or UI bundle changes.
domus-captures ──┐ domus-infra-ops ─┤ domus-ise-linux ─┤ domus-netapi-docs┤ domus-secrets-ops┤ ┌──────────────────┐ domus-antora-ui ─┼── domus-docs ──▶│ Cloudflare Pages │ domus-homelab ───┤ (hub) │ docs.domus...dev │ domus-pki ───────┤ └──────────────────┘ domus-firewall ──┤ domus-dns ───────┤ domus-dhcp ──────┤ domus-monitoring─┤ domus-backup ────┤ domus-vault ─────┤ domus-identity ──┘
Directory Skeleton
Twenty top-level page directories organize content by function:
| Directory | Purpose |
|---|---|
|
Chronological captures — worklogs, meeting notes, daily documents |
|
Vendor TAC cases with timelines and resolution |
|
Unplanned outages and security events |
|
Planned change requests with implementation phases |
|
Root cause analyses linked back to incidents |
|
Deployment records with validation checklists |
|
CLI reference library — the Arsenal |
|
Certification tracks, languages, literature, RHCSA |
|
Red Hat Certified System Administrator study |
|
Technical and classical reading notes |
|
Reusable patterns with Aristotelian taxonomy |
|
Project documentation following STD-001 |
|
Personal infrastructure and tooling projects |
|
Workplace projects and deployments |
|
Progress tracking dashboards |
|
STD-001 through STD-020 governance documents |
|
Claude Code collaboration session logs |
|
Training session records and exercises |
|
Document templates for each file prefix |
|
Work in progress not yet categorized |
Partials Architecture
Partials hold the content; pages are thin shells with a single include:: directive.
Fifteen subdirectories contain the bulk of authored material:
| Directory | Files | Purpose |
|---|---|---|
|
20 |
One partial per STD document |
|
602 |
All project content — phases, features, appendices, metadata |
|
189 |
Work, personal, and education tracking tables |
|
86 |
Reference material and quick-lookup content |
|
8 |
Navigation partials included by |
|
21 |
Section templates for daily worklogs |
|
15 |
Monthly summaries and periodic reports |
|
15 |
CLI codex content partials |
|
12 |
Operational runbook content |
|
10 |
Task list partials |
|
10 |
Mathematics study content |
|
8 |
Discovery and exploration notes |
|
4 |
Education track content |
|
2 |
Strategic objective definitions |
|
1 |
All shared attributes — included globally |
Examples Library
The examples/ directory holds 389 files of executable code, diagrams, and drill content.
Code blocks in partials reference these via include::example$category/name.ext[] to maintain a single source of truth.
| Category | Files | Content |
|---|---|---|
|
— |
API interaction scripts and payloads |
|
— |
CLI reference code snippets |
|
— |
Command examples for codex entries |
|
— |
D2 and ASCII diagram source files |
|
— |
Terminal session recordings and output |
|
— |
Mathematical notation and computation examples |
|
— |
Music theory notation files |
|
— |
Functional programming monad examples |
|
— |
Nav structure examples |
|
— |
Regular expression practice exercises |
|
— |
jq filter and transformation drills |
|
— |
Python practice exercises |
|
— |
Lua scripting drills |
|
— |
ETL pipeline practice |
|
— |
Lab environment scripts and configs |
|
28 |
AI context files for Claude Code agents |
|
— |
Generated output samples |