Decisions Log
Key choices made on this project and why. Keeping this current means agents and humans can pick up where things left off without relitigating past decisions.
| Date | Decision | Rationale | Alternatives Considered |
|---|---|---|---|
| 2026-04-26 | Implement SEO metadata and crawl discoverability baseline: canonical/OG/Twitter tags on layouts + homepage, JSON-LD for Website/Person/Article/CreativeWork, plus robots.txt and sitemap.xml |
Improves search understanding, social preview quality, and crawler pathing across all public pages without changing visual UX. | Relying on minimal title/description tags only |
| 2026-04-26 | Implement full code/semantic remediation pass: converted homepage project cards to native links, added semantic landmarks/headings, replaced redirect-only projects/index.html with a crawlable index, added static project summaries/metadata in front matter, and improved modal keyboard focus handling |
Resolves the runbook’s code/semantics findings while preserving current visual direction and JS-enhanced case-study detail flows. | Deferring semantics fixes until after copy/fact-check work |
| 2026-04-26 | Execute full-content website review runbook pass (all fixed 6 persona + 4 discipline agents) and publish synthesized report at work/website-review/runs/2026-04-26-full-content-review-report.md |
Moves review from homepage-only to full-site content coverage with deduped, prioritized actions aligned to current style guides. | Deferring to ad-hoc/manual review of only changed files |
| 2026-04-26 | Split style guidance into context/code-style-guide.md and context/tone-voice-style-guide.md, with context/style-guide.md as an index file |
Clarifies implementation vs writing expectations and improves agent reliability when proposing edits. | Keeping one combined style guide only |
| 2026-04-26 | Rewrite operational docs: replaced next-steps.md, expanded README.md, updated multi-agent review runbook to default all pages, and added context/style-guide.md referenced by review agents |
Prevents stale-path failures in agent workflows and creates one current writing standard for consistent, credible updates. | Keeping homepage-only review scope; embedding style notes only in README |
| 2026-04-26 | Refresh documentation for publish clarity: expanded README.md, copy-edited blog posts, and renamed the AI post file to match front matter date (2026-03-14-...) |
Keeps published docs grammatically clean and aligns filename/date conventions to avoid confusion in future publishing workflows. | Changing front matter date to match filename; leaving docs as-is |
| 2026-04-21 | Apply finalized homepage copy to root index.html (hero, descriptors, About, Work intro + list blurbs, Now, Contact, meta description) per hurn-co-copy-revisions.md |
Single pass to align the shipped page with approved voice and project summaries before deploy/fact-check. | Rewriting overlay case bodies in the same pass (deferred until blurbs are validated in browser) |
| 2026-04-22 | Rebuild index-puzzle.html around a piece-plus-copy project list with full-screen case study overlays |
This kept the clearer, more editorial project-list format Jenny preferred while preserving the stronger case-study header and top-line summary structure from the earlier concept. | Shelf-only layouts; inline scrolling case studies |
| 2026-04-22 | Revise index-puzzle.html toward a luxury-editorial direction: larger multi-row shelves, no sideways scroll, and full-page case studies below the grid |
Improved readability and made the concept feel more premium while preserving the puzzle metaphor in a clearer, more intentional way. | Small horizontally scrolling boxes; side drawer case studies |
| 2026-04-22 | Build index-puzzle.html as a self-contained alternate portfolio concept using a “puzzle shelf” case-study metaphor |
Preserves the memorable concept while keeping the implementation portable, polished, and easier to review independently from the main homepage. | Folding the concept directly into index.html; keeping the earlier broken multi-file prototype |
| 2026-04-15 | Start the personal website in other-projects/ |
The work is active, but it does not clearly belong to Ascend marketing, sales, or operations yet. | Creating it under marketing/; leaving it unstructured |
| 2026-04-15 | Homepage: Opening, About, Selected work, Writing, Now (reading / thinking / building), Contact | Matches agreed IA; POV woven into About. | Separate manifesto section; stats-led hero |
| 2026-04-15 | Selected work: outcome-first project cards; subtle M&S / People / Ops tags | Shows range without resume framing. | Role timeline; skills matrix |
| 2026-04-15 | Aesthetic: startup-coded dark UI (Syne + Inter + JetBrains Mono; grid; orbs; cyan/teal accents) | Reads as product/operator identity; avoids “Google Doc” flat editorial. | Prior serif-only editorial pass |
| 2026-04-15 | Deploy: GitHub Pages + custom domain when ready | Per stack preference. | Netlify, etc. |
| 2026-04-15 | Writing: one essay stub + two placeholders until LinkedIn sources provided | Unblocks layout; real posts replace stubs. | “Coming soon” only |
| 2026-04-15 | Typography: Work Sans (display) + Source Sans 3 (body) + JetBrains Mono (chrome); no font picker | Cleaner production surface; Jenny preference. | Syne + Inter; multi-font picker |
| 2026-04-15 | Selected work: title → impact (metrics/callouts with .card-stat) → description; long-form copy on homepage |
Credibility and specificity; stat-led proof intentional. | Short blurbs only; no stats |
| 2026-04-15 | Public identity on prototype: hurn.co, hello@hurn.co | Domain-aligned contact and footer. | hello@jennyhurn.com placeholder |
| 2026-04-15 | Phase 1 prototype treated as done; next gate is Phase 2 (approval + fact-check) then Phase 3 (deploy) | Matches evolved index.html and next-steps.md. |
Redo Phase 1 build |
| 2026-04-15 | GitHub Pages repo: jennyhurn/website | Single canonical remote for deploy; project-site URL jennyhurn.github.io/website/. |
USERNAME.github.io user site |
How to Use
Add a row each time a meaningful choice is made — format, audience, approach, what to cut, what to prioritize. Brief is fine. The goal is continuity, not documentation for its own sake.