01 · Start with the task
Before choosing a stack, identify what a visitor, operator, or maintainer must be able to accomplish. A clear primary task gives navigation, content, and interaction something to organize around.
02 · Keep facts authoritative
Product status, business context, and public destinations should come from a maintained source. A site can have its own voice without making up its own availability promise.
03 · Design for the difficult state
Small screens, long content, no JavaScript, reduced motion, failed media, and handoff are normal states. They belong in the first design pass.
04 · Deliver a route someone can repeat
Source revision, build command, hosting target, custom domain, verification result, and rollback reference form a practical release record. That record makes a future repair safer.