Skip to content

Backlog

Track documentation cleanup, missing diagrams, and future portfolio rewrite candidates here.

Content

Nothing below can be written without real input — these are deliberately left as honest placeholders rather than invented.

  • About — professional profile / bio (homepage, near the bottom).
  • Projects — the three named case studies (Project Forge, Efficient Supports / CareOps, EKS Incident Response) need their actual write-ups: problem, architecture, security, outcomes.
  • Architecture (top-level) — planned additions: Azure Landing Zones, Hybrid Identity & Federation, Kubernetes GitOps, Zero Trust network design.
  • Cloud — zero documents; 9 planned categories mirroring Infrastructure's shape.
  • SOPs, Runbooks, Labs — all zero documents; see Placement Rules for which new work goes where.
  • Certifications — nothing listed until there's something verified to list.

Presentation

  • Footer is currently just a GitHub icon and copyright line (Material's native extra.social). A fuller footer in the Customer.io/Steep style — a couple of real nav columns plus LinkedIn — needs a real LinkedIn (or other contact) URL, which isn't guessed at here.
  • 36 Infrastructure documents use unlabeled fenced code blocks (no syntax highlighting). Fixing this means reading every block to tell commands from config from output — a real pass, not a mechanical one.
  • assets/okubuilt-mark.svg is a static mark, not theme-aware. Its palette was tuned for dark-mode legibility, which weakens its contrast against a white background specifically. A fully adaptive version would need two SVGs or inline page-aware styling.
  • 10 top-level nav tabs (11 with Home) is a lot for mostly-empty sections. Worth pruning or merging once real content shows which ones actually get used.