Resource rack

Sections: purpose, who it is for, three must-have tasks, what is out of scope, who decides. Keep it to one page; if it grows, split the project.

List domain registrar, hosting, email, app store developer accounts and analytics (if any). For each: who owns it, who has access, where recovery codes live.

Can a new visitor tell what this is in five seconds? Is the main action obvious? Can it be done on a phone? Are errors explained? Can it be done by keyboard?

Body text should be comfortably readable at default zoom; check text against its background with a contrast tool and test at 200% zoom.

Disable the button while sending, keep the draft on failure, show success only after the server confirms, and never claim an email was delivered.

Check at roughly 390, 768 and 1440 pixels wide, plus one very narrow width. Look for sideways scrolling and overlapping elements.

Prepare description text, screenshots for required sizes, a privacy statement, support contact and notes for the reviewer explaining any login.

Confirm backups, check DNS and certificates, test forms on the live domain, keep a rollback note open, and tell support who to contact.

Say what you were trying to do, what happened instead, when it started, on which device and browser, and what you have already tried.

Use a password manager, switch on two-step sign-in where offered, and remove access for people who no longer need it.