Skip to content

Latest commit

 

History

History
34 lines (27 loc) · 2.09 KB

REVIEW-CHECKLIST.md

File metadata and controls

34 lines (27 loc) · 2.09 KB

Redesign acceptance review

Completed. Evidence and validation scope are recorded in REVIEW-RESULTS.md; screenshots and machine-readable reports are in artifacts/review/.

Intent and content

  • Personal introduction, startup and interests; no hiring or consulting funnel.
  • CarrotOnTheHorse has a useful explanation, accurate role and working public link.
  • Side projects are described honestly as projects or experiments without invented outcomes.
  • Full-time employer stays unnamed. No private knowledge-base details, source paths, business numbers or third-party names appear in generated HTML/assets.
  • Mail, GitHub and LinkedIn destinations match the existing public site.
  • User-provided brief remains unchanged.

Rendering and interaction

  • Desktop, tablet and narrow-phone screenshots inspected.
  • No horizontal overflow, cropped headings, unreadable muted text or broken images.
  • Keyboard skip link, visible focus, navigation and contact controls work.
  • Canvas visible, responsive, pausable and static with reduced motion; hidden/offscreen work stops.
  • Essential content and navigation work with JavaScript disabled.
  • Legacy hash routes, compatibility pages and custom 404 work.
  • All internal links resolve; external destination URLs are correct.

Delivery

  • Type checking and production build pass with the documented Node version.
  • Production preview has no unexpected console/network errors.
  • Accessibility scan inspected and actual visible controls reviewed.
  • Local performance measured; findings recorded with scope and limits.
  • Title, canonical, description, social image, favicon, robots and sitemap verified in build output.
  • Only public assets are shipped; no source brief, review notes or private source material in dist.
  • Build instructions and static deployment notes are accurate; no force-push deployment helper remains.
  • Opus implementation is evidenced by a completed model run; final browser review performed by Codex.
  • Local preview and final screenshots available for user review; nothing deployed.