# Static-site release checklist

This is a compact checklist for publishing a generated static site. Adapt paths and commands to the project that owns the artifact.

## Build

- [ ] Confirm the generator version and source commit.
- [ ] Build into a clean output directory.
- [ ] Confirm index.html, 404.html, robots.txt, and sitemap.xml exist.

~~~sh
hugo version
hugo --gc --minify --destination public
test -s public/index.html
test -s public/404.html
test -s public/robots.txt
test -s public/sitemap.xml
~~~

## Inspect

- [ ] Search generated files for local paths, development hosts, and unresolved placeholders.
- [ ] Check that every downloadable file is present and has the expected content type.
- [ ] Check that no credential, cookie, private key, or access token is in the artifact.

~~~sh
rg -n 'localhost|127\.0\.0\.1|TODO|example\.com|/Users/' public
find public -type f -print | sort
~~~

## Exercise routes

- [ ] Request the home page, notes index, resources index, and a missing path.
- [ ] Confirm the missing path returns HTTP 404.
- [ ] Check security headers on both successful and error responses.
- [ ] Check one narrow mobile viewport before publishing.

## Record

- [ ] Save the source commit, generator version, build time, and resource checksums.
- [ ] Keep the previous known-good artifact until the new artifact passes its checks.