A build checklist that fits on one page
Five checks for a small publishing project, from clean installation to a recoverable release.
Demo article · written for this development preview, not author-approved.
A release checklist is useful when it records what you can actually verify. For a small publication, five focused questions cover more ground than a long list of vague assurances.
Can another machine build it?
Pin the runtime range and commit the package lockfile. Test a clean installation rather than relying on whatever happens to be in a local dependency folder.
npm ci
npm run check
npm test
npm run build
Does the output contain only public material?
Look at generated files, not only rendered pages. An unlinked draft image in a public folder is still public. A hidden article in a search index is still published.
Can a reader use it without a mouse?
Start at the address bar and press Tab. The focus indicator should remain visible, navigation should have meaningful labels, and code examples should be readable on a narrow screen.
Do the links describe the right deployment?
Check canonical links, feed URLs, sitemap entries, and image URLs. A successful build can still contain links to the wrong hostname.
Can you recover?
Record how to restore a previous deployment and how to revert a content commit. Keep those as separate operations: rolling back a deployment does not automatically correct the source that the next build will use.
This is demonstration guidance, not a claim that a live deployment has already passed these checks.