POSITIONING

• [ ] State target roles clearly on the homepage (e.g., "JavaScript + Cloud/DevOps," "Frontend Platform," "Full-stack Node/Next")
• [ ] One-paragraph positioning statement about systems you build and operate (not tool lists)
• [ ] Prominent links to résumé, email, LinkedIn, Dice, GitHub

SITE BASICS

• [ ] Custom domain with HTTPS and working contact (form or mailto) plus spam protection
• [ ] Clear navigation: About, Projects, Case Studies, Blog/Notes, Contact, Press/Talks
• [ ] Mobile-responsive layout, dark mode, basic accessibility (keyboard nav, contrast, focus)

PROJECT LISTING (INDEX PAGE)

• [ ] Each project card shows: title, 1-sentence outcome, tech scope tags (JS/TS, cloud, testing, CI/CD, observability)
• [ ] Links to live demo and repo are obvious
• [ ] Badge strip: tests passing, last deploy date, uptime snapshot (image or text), CWV snapshot

PROJECT CASE STUDY (DETAIL PAGE) — PER PROJECT

• [ ] Problem statement and business context (who, pain, constraints)
• [ ] Success criteria and measurable outcome
• [ ] "How it's built" summary: architecture diagram + stack list
• [ ] Key tradeoffs (serverless vs containers, SQL vs NoSQL, caching choices)
• [ ] SDLC evidence: testing, CI/CD, observability, security choices
• [ ] What I'd do in v2 and known limitations
• [ ] Links: live demo, repo root, ADRs, runbook, status page (if public)