Static publishing.

Keep source, artifacts, and public URLs connected. Static publishing separates authoring and building from the files visitors receive. That makes the public artifact a useful review boundary, but it still needs a repeatable workflow. This collection covers generated output, clean paths, preview environments, link checks, sitemap and feed consistency, and identifiable releases. Start with the Hugo publishing guide to understand the source-to-public handoff, then use the Git and GitLab guide to connect that artifact to an approval and destination. Always verify deep links and assets at the deployed location rather than relying on a successful local build.