Install

Add the module to your site’s hugo.toml:

[module]
  [[module.imports]]
    path = "github.com/saltstack/pydata-hugo-theme"

Then fetch it and its build-time npm dependencies (FontAwesome’s JS+SVG icon kit, Bootstrap’s JS bundle, mounted via [[module.mounts]]):

hugo mod get github.com/saltstack/pydata-hugo-theme
npm install

That’s it — hugo server/hugo build will now resolve the theme.

Offline / reproducible builds

By default Hugo resolves the module (and its npm mounts) fresh at build time, which needs Go and network access. If you’d rather commit a fully offline, reproducible copy — no Go toolchain, no npm, no live fetch during CI — run:

hugo mod vendor

This copies the resolved module into your site’s _vendor/ directory, which you check into your own repo; Hugo then always builds from that local copy. One gotcha: hugo mod vendor only copies Hugo-relevant files (layouts/, static/, hugo.toml, etc.) — it skips this module’s own LICENSE/README.md, so re-copy those manually into _vendor/.../pydata-hugo-theme/ after every re-vendor if you want the attribution notice to travel with the vendored copy.

Another gotcha, specific to vendoring a version for the first time (a cold cache — including any CI runner, which is always cold): the plain npm install above is enough for a live (non-vendored) build, since Hugo resolves the node_modules-sourced mounts against your site’s own node_modules in that case. But hugo mod vendor resolves those same mounts against Hugo’s own on-disk copy of the module itself — a separate directory from both your site’s node_modules and from Go’s own module cache (go list -m’s answer is a different, unrelated copy). If that module copy has never had its npm deps installed, hugo mod vendor fails outright looking for node_modules/@fortawesome/.... To fix it, install them directly into Hugo’s resolved copy before vendoring:

# Find the version Hugo actually resolved:
hugo mod graph --ignoreVendorPaths "**"
# Then, using that version:
cd "${HUGO_CACHEDIR:-$HOME/.cache/hugo_cache}/modules/filecache/modules/pkg/mod/github.com/saltstack/pydata-hugo-theme@<version>"
npm ci
cd - && hugo mod vendor

A real, in-production example of this pattern — including a small wrapper script that automates the bump/vendor/re-copy sequence — lives in salt-project-website’s scripts/update-vendored-theme.sh . It’s specific to that repo’s layout, so it isn’t shipped as part of this module, but it’s a good reference to adapt.