Deployment and previews on OINK

Deployment with Amazon S3 and CloudFront

Mon, 01 Jan 0001 00:00:00 +0000

There are several options for publishing your web site using Amazon Web Services. This section describes the most basic option, deploying your site using an S3 bucket and activating the CloudFront CDN (content delivery network) to speed up the delivery of your deployed contents.

After your registration at AWS, create your S3 bucket, connect it with your domain, and add it to the CloudFront CDN. This blog post has all the details and provides easy to follow step-by-step instructions for the whole procedure.

Deployment on GitHub Pages

Mon, 01 Jan 0001 00:00:00 +0000

If your source is hosted on GitHub, GitHub Pages can build and publish the site with a single Actions workflow. The consuming site needs Hugo Extended but does not need Node.js, npm, PostCSS, or a generated deployment branch.

Project sites use a URL such as https://<OWNER>.github.io/<REPOSITORY>/; user and organization sites use https://<OWNER>.github.io/. Custom domains are also supported.

Prepare the repository

Push the complete site source to GitHub and confirm that this command succeeds from the repository root:

Serving your site locally

Mon, 01 Jan 0001 00:00:00 +0000

Depending on your deployment choice you may want to serve your site locally during development to preview content changes. To serve your site locally:

Ensure you have an up to date local copy of your site files cloned from your repo.
Ensure Hugo Extended and any source-fetch tools required by your chosen installation method are installed, as described in Prerequisites and installation. Node.js and PostCSS are not site-build prerequisites.
Run the hugo server command in your site root. By default your site will be available at http://localhost:1313.

Deployment on Netlify

Mon, 01 Jan 0001 00:00:00 +0000

Netlify can build a site from GitHub, GitLab, or Bitbucket and publish a preview for each pull request. An OINK consumer build runs Hugo Extended directly; it does not install Node.js packages or invoke PostCSS.

Configure the site

Push the complete source to your Git provider, import the repository in Netlify, and use these build settings:

Setting	Value
Build command	`hugo --gc --minify`
Publish directory	`public`
`HUGO_VERSION`	`0.164.0` or another theme-validated version

If Netlify detects package manifests that exist only for theme-maintainer tooling, disable automatic dependency installation for the site. They are not part of the consumer build contract.

Page chrome

Mon, 01 Jan 0001 00:00:00 +0000

The theme renders the complete navbar, sidebar, table of contents, search entry, and footer in each applicable page. This is the canonical production structure for normal builds, previews, offline archives, search crawlers, and clients without JavaScript.

The experimental upstream td.chrome = shared donor/restoration mode is not part of this theme. The params.td.chrome setting has no effect and should be removed from migrated site configuration. Keeping one server-rendered structure avoids a second visual implementation and keeps navigation, language selection, accessibility semantics, and offline behavior deterministic.