Public Website QA Checklist
A public page is not ready because it builds. It is ready when a human eye cannot immediately spot spacing, cropping, copy, or mobile mistakes.
When this matters
This page is for operators who want Rocky to produce usable work without turning the system into a mystery box. Use it when you need a practical path, a clear verification step, and a boundary between suggestion and action.
The operating pattern
- Capture desktop and mobile. Use representative viewport screenshots, not only DOM checks.
- Inspect hierarchy. Headlines, cards, buttons, and captions should feel intentional.
- Check text wrapping. Avoid orphan words, clipped headings, smashed uppercase, and awkward line breaks.
- Open the live URL. Local success is not deployment proof.
- Check console and links. Broken scripts or dead buttons make a polished page feel fake.
Pre-flight checklist
- Desktop screenshot reviewed
- Mobile screenshot reviewed
- No horizontal overflow
- No clipped/cut-off images
- Critical links return 200
- Console is clean
Common failure modes
- Build-only confidence: A successful deploy can still look bad.
- Mobile afterthoughts: Mobile is often where spacing and nav problems appear.
- Fake links: Visible buttons should either work or be removed.
Verification
A page is not done because it was drafted. Verify the source, run the workflow, inspect the output, and record what changed. If a step touches money, customers, accounts, permissions, or private data, keep it behind an explicit human approval gate.