Hugo should validate output formats

Yeah, that one.

Build and deployment workflows vary greatly, from automated CI/CD pipelines to manual processes involving local builds and uploads. Users also employ diverse operating systems like macOS, Windows, and various Linux distributions.

Given these variations, there’s no single “recommended” setup. For instance, if you’re building and deploying with GitHub Pages, here’s an example workflow for a monolingual site:

https://github.com/jmooring/hosting-github-pages/blob/main/.github/workflows/hugo.yaml

Note that the “validate” job in this example is generic, applicable to any website, similar to how CSS, HTML, and JavaScript are universally applicable.

While we won’t officially document this, feel free to share your insights in a blog post or a forum topic.


EDIT 2026-01-11T11:37:18-08:00

I’ve revereted the GitHub Pages workflow file in the test repo above to match our current deployment docs, removing the validation job. You can see the workflow file that includes the validation job here:

https://github.com/jmooring/hosting-github-pages/blob/f17950ccf3bd024932e89ed578a04736eecbfc16/.github/workflows/hugo.yaml

2 Likes