6 Ship with confidence
Shipping a documentation site moves through four stages: previewing locally, pinning or updating the theme module, running a clean production build, and deploying to your hosting provider. Checking each stage in order makes build or deployment problems easy to isolate.
Check each stage in order
| Stage | What it verifies | What still needs checking |
|---|---|---|
| Local preview | Pages, navigation, and edits render cleanly in hugo server |
Production base URL, draft exclusion, and clean module state |
| Theme module pin | hugo mod graph resolves the target public tag in go.mod and go.sum |
Whether site content and overrides build cleanly against that tag |
| Production build | Content, configuration, and go.mod build cleanly in --environment production |
Hosting workflow, CDN caching, and live public routes |
| Live deployment | CI workflow succeeds and key public URLs load as expected | Desktop and mobile layout across representative pages |
Validate the smallest useful surface
From your Starter repository, run a clean production build before pushing to your deployment workflow:
Confirm that hugo mod graph resolves the expected release in go.mod, then
follow the Starter deployment steps.
An ordinary Starter site needs no npm build script or sibling theme checkout.
If you are developing changes to the OINK theme itself, follow the
theme-development workflow.
Review the rendered result
Automated checks catch broken links, duplicate IDs, invalid shortcodes, and accessibility regressions, while visual review checks layout and readability. Inspect representative English and Chinese pages at desktop and mobile widths, including Hero cropping, wide tables, navigation, theme controls, code blocks, and the whole-book print view.
Keep a release checklist
When opening a pull request or upgrading the theme, record the Hugo version,
the theme version in go.mod, the build output, and the routes you reviewed
against Table 6-1. Keeping a concise
checklist in your pull request makes reviews and rollbacks straightforward.
The full operational references are Preview the site, Deploy the site, and Troubleshoot a build.