Publish a Hugo website on IPFS: URLs, assets, and repeatable builds
Turn a Hugo project into a portable static release, inspect its generated routes, and keep canonical metadata separate from delivery paths.
IPFS Hugo Website / STATIC GENERATION
Write in Hugo. Publish a tested release.
Keep the authoring workflow you know. Make the generated directory—not the preview server—the artifact you review and publish.
Inspect the publish directory
A Hugo source project is not the same as its public output. Build into a clean destination and verify that only intended pages and assets remain. Renamed content can leave stale files behind when an old output directory is reused carelessly. Record the generator version, theme revision, and production command so another maintainer can understand the release.
Review URL behavior in the theme
Set the canonical site address deliberately and inspect how the theme constructs links. A single relative-URL setting does not guarantee that hardcoded images, scripts, shortcodes, and pagination become portable. Test a nested page through the intended gateway context. Keep the branded canonical identity separate from temporary delivery URLs used during a deployment test.
Treat archives and feeds as first-class pages
Check category pages, tag archives, pagination, RSS, and the sitemap alongside the homepage. Their metadata and publication dates should describe the actual content consistently. Exclude drafts and future content according to the editorial policy. Avoid marking every article as newly modified merely because the generator rebuilt the site after an unrelated change.
Keep builds and releases traceable
Pin dependencies and record the relationship between a source revision and the root CID of its generated directory. Investigate unexpected output differences rather than assuming every new build should be identical or every difference is harmless. Retain the approved release before changing the public name. Keep the previous release available through a deliberate rollback period.
Technical reference: Hugo configuration reference. Review the relevant configuration before applying it to a production environment.
COMMON QUESTIONS
IPFS Hugo Website: the details
Must the public server run Hugo?
No. A generated static output directory can be served without running Hugo for each request. Hugo remains part of your authoring and build workflow.
Should I always enable relative URLs?
Do not treat a global setting as a universal fix. Review the official setting behavior and inspect the output of your particular theme in the delivery contexts you support.
FIELD GUIDES
Go deeper in the Website Lab
An IPFS website CMS workflow: edit privately, publish static releases
Design a content workflow that separates authoring, previews, approvals, static output, and IPFS publication without exposing the CMS to every visitor.