Category: Tutorial

Diagnosis starts from a clean production build: BASH hugo --gc --minify --logLevel info A consumer build command should never invoke npm, PostCSS, or Autoprefixer, and should never download the theme’s browser assets. Seeing those in the log means an …

Containers are not required — OINK only asks for Hugo Extended. They suit a team that wants a pinned toolchain, or that would rather not install Hugo on every workstation. Build the image Dockerfile DOCKERFILE FROM debian:bookworm-slim ARG …

pgsty/oink.pgsty.com is OINK’s bilingual example and regression site. It is deliberately more complete than a minimal consuming site — treat it as a reference, then delete what your product does not need. This path suits you if you want a working …

Hugo reads site-level settings from hugo.yaml, hugo.toml, or hugo.json. The OINK project site uses YAML because multilingual menus and theme options are easier to read and review in that form. This page covers the configuration a site needs to run. …

This page builds a minimal bilingual site from scratch. For a reference that is already fully configured, see the project site instead. Create the skeleton BASH hugo new site --format yaml my-docs cd my-docs hugo mod init github.com/example/my-docs …

OINK is published as the Hugo Module github.com/pgsty/oink. Modules are the recommended method for every site — it is the only one where Hugo resolves the version, verifies checksums, and leaves an audit record in go.sum. The other three methods …

The only required tool on the consumer side is Hugo Extended. Whether you also need Git and Go depends on how you obtain the theme. Install Hugo Extended Install 0.160.1 or newer. The project site currently validates against 0.164.0. Follow Hugo’s …

OINK is a Hugo theme that ships its browser runtimes with the theme. A consuming site needs only Hugo Extended: no Node.js, no PostCSS, no CDN, and no remote theme asset download during the build. What this chapter covers Read these seven pages in …