Decision Log

Decision log

Record consequential choices with their date, status, rationale, alternatives, and evidence. Statuses: Proposed, Accepted, Superseded. Preserve replaced decisions and link to their successors.

D001 — Use the wiki as the ongoing project record

• Date: September 30, 2026
• Status: Accepted
• Decision: Use this wiki for requirements, decisions, configuration context, the roadmap, and development history. Use issues for actionable tasks and the source repository for executable configuration.
• Rationale: Give future contributors and AI sessions a shared record and preserve material for public writing about the project.
• Source: John's request to use the wiki for development tracking and AI session continuity.

D002 — Resolve staging before v2 implementation

• Date: September 30, 2026
• Status: Accepted
• Decision: Establish and validate an isolated staging workflow before implementing v2. Design exploration may continue.
• Rationale: Review the redesign while the current site remains live.
• Open alternatives: Shared staging versus per-PR previews; provider, URL, and promotion approach were initially undecided; see D004 for the selected approach.
• Source: #25.
• Scope note: Staging and wiki setup are separate, related efforts.

D003 — Initial homepage direction

• Date: September 30, 2026
• Status: Accepted
• Decision: Follow the homepage structure, scrolling behavior, mobile adaptation, and exact copy recorded in V2 requirements.
• Rationale: A spacious personal introduction and clear paths into John's work and writing support the Clear, Clean, Clever principles.
• Alternatives: Earlier compact concepts were rejected as too busy. Journal-style imagery is a possible later exploration.
• Open choices: Platform/theme, typography, palette, imagery, Work label, grid organization, and content selection.
• Evidence: Existing V2 requirements, wiki commit 2ca2f68.

D004 — GitHub-only shared staging

• Date: September 30, 2026
• Status: Accepted approach; implementation validation pending
• Decision: Keep source in johnapaz.github.io on v2; use public johnapaz-staging for a separate Pages deployment at staging.johnapaz.com. Start with shared staging.
• Rationale and alternatives: John requested everything stay in GitHub; Netlify was considered and declined. A separate Pages repository isolates the full redesign. Per-PR previews may be added later.
• Implementation: Destination Actions reads public v2 and publishes with its temporary built-in token. No persistent deploy key or secret. Manual refresh plus 30-minute schedule; v2 pushes validate the build.
• Promotion: John reviews the exact source commit, then approves a PR into the current production branch. Rollback uses a revert and rebuild.
• Evidence: John explicitly authorized setup and public repository creation; #25, Development workflow. DNS, HTTPS, live review and rollback validation remain pending.

New decision template

• ID and title:
• Date:
• Status:
• Decision:
• Rationale and alternatives:
• Consequences / affected requirements:
• Evidence: Issue, commit, prototype, or user approval.
• Supersedes / superseded by: If applicable.

D005 — Use the résumé as an explorable, shareable work story

• Date: October 1, 2026
• Status: Accepted and integrated into v2
• Decision: Enrich the existing résumé rows with grounded impact statements, industry/team context, interactive work/tool badges and expandable details. Keep chronology as the default and offer work-type and industry grouping, with URL-persistent filters and Copy view link.
• Rationale: Help hiring readers recognize relevant problem-solving experience quickly and send a focused, persistent view to colleagues or managers.
• Alternatives: A logo wall alone would identify brands without explaining the work. Replacing the accepted desktop layout with a new card grid would discard spacing John explicitly wanted to retain.
• Consequences: Preserve the canyon design language and existing desktop spacing. Use a stacked mobile timeline. Six recent roles remain the default; three earlier examples surface on demand or through filters. Keep claims grounded in the résumé and saved LinkedIn export. Physical Fold6 validation remains part of release review.
• Evidence: John's prototype request and approval; PR #40, v2 merge 7b04338ababbfae33ed22cf80f223b7f4fa0811f; requirements and validation.

John’s subsequent Education refinement is implemented at 4bd9d60ebe07493902e3ac1b5e01faca1f9bfbc3: dedicated section, official UCF mark, complete degree/track, Class of 2008, and desktop/mobile layout.