Blog ADRs — Overview
Architecture Decision Records for the public-facing blog at blog.comptech-lab.com — captures the load-bearing decisions made while building the Astro + ReactFlow + multi-collection site.
This sub-section captures Architecture Decision Records (ADRs) for the public blog at blog.comptech-lab.com. The blog is intentionally a separate concern from the comptech platform documented in the rest of /docs/, but the ADR discipline applies the same way: each load-bearing decision gets a short, dated record explaining the context, the decision, and the consequences — including the alternatives considered and rejected.
The blog ADRs are numbered independently (0001 onward) from the platform ADRs, and they live in a sub-folder to keep audiences separate. If you’re here for OpenShift platform decisions, see the parent 06-architecture-decisions/ section.
What’s in here
| ADR | Title | Status |
|---|---|---|
| 0001 | Multi-collection content model | Accepted |
| 0002 | ReactFlow over Mermaid for all diagrams | Accepted |
| 0003 | Category-based sidebar with frontmatter metadata | Accepted |
| 0004 | Learning section as parallel collection to docs | Accepted |
| 0005 | SEO baseline (sitemap, RSS, OG, JSON-LD) | Accepted |
| 0006 | Brac POC as a top-level content collection | Superseded by 0007 |
| 0007 | /docs/ as a master section with per-module sub-trees | Accepted |
Format
Each ADR follows the standard template:
- Status — Proposed / Accepted / Superseded, with date and (if superseded) a pointer to the replacement.
- Context — what triggered the decision; what alternatives were on the table.
- Decision — the actual choice made.
- Consequences — what changed in the codebase, in the operating model, in future-flexibility.
- Related — cross-links to other ADRs, blog posts, or code locations.
ADRs are not implementation guides. They’re the explanation for why the code is the way it is, written close enough in time to the decision that the rationale isn’t lost.