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 WEBSITE LAB / TOPIC
DNSLink
Connect names to approved releases.
DNSLink is useful when a memorable name should signal a content path. It belongs alongside, not in place of, your plan for ordinary HTTPS delivery and retained content.
Review the domain guide for naming and delivery boundaries, then the Hugo guide for canonical metadata and generated links. Keep the preferred public domain consistent while testing the actual gateway context. Record the previous value before a release change and keep its content available during the transition. A readable name is most useful when it points to an already tested artifact.
Start with IPFS Hosting or IPFS Hugo Website, then continue with the field guides below.
DNSLink and IPFS gateways: connect a domain without breaking releases
Understand what DNSLink changes, what HTTPS delivery still needs, and how to test a custom domain before switching its published release.