HugoBlox Kit setup

Application pending. Commands below are grounded in inspected upstream sources, not deployment evidence. Return to index.

flowchart LR
  A[Pinned source] --> B[Install and adapt]
  B --> C[Static output]
  C --> D[Browser and access proof]

Verified upstream inputs

Use the official starter pinned at 66efb1916bd62287ea2fef3caacb1245b2f34da2. Its go.mod requires github.com/HugoBlox/kit/modules/blox v0.12.0; that release resolves to commit bf6e0287286303dfaf83e60a64930136b3eba6a6. The npm hugoblox CLI 0.12.8 is a separate version namespace.

The starter’s hugoblox.yaml selects Hugo Extended 0.162.0. Its workflow uses Node 22, Tailwind CLI, Hugo, and Pagefind; package.json pins pnpm@10.14.0. Preserve its blocks, sample content, and layouts rather than substituting a custom generic landing page.

Prepare and build

These commands describe the upcoming application phase and have not run. From the project apps directory, with an unused hkit destination:

git clone https://github.com/HugoBlox/hugo-starter.git hkit
cd hkit
git checkout --detach 66efb1916bd62287ea2fef3caacb1245b2f34da2
nice -n 10 npx --yes pnpm@10.14.0 install --frozen-lockfile

Use a project-local Hugo Extended executable. Latest stable Hugo 0.166.0 was independently verified, but compatibility with this starter is pending. Do not call it the starter-tested version: that is 0.162.0. Both artifact digests are recorded in versions.json. Verify the downloaded Linux x64 Extended archive against its recorded SHA-256 before extraction.

For the planned latest-stable executable at tools/hugo-0.166.0/hugo, run from apps/hkit:

PATH="$PWD/node_modules/.bin:$PATH" HUGO_ENVIRONMENT=production nice -n 10 ../../tools/hugo-0.166.0/hugo --minify --baseURL https://hkit.loca.zone/
nice -n 10 npx --yes pnpm@10.14.0 exec pagefind --site public

Expected static output: apps/hkit/public. Invoke Pagefind directly: the upstream package script suppresses its failures with 2>/dev/null || true, so that script’s green exit is not search proof. Any version compatibility failure must be recorded rather than silently changing pins.

Acceptance still required

Confirm real upstream starter content and layouts render, generated links use the intended host, and Pagefind indexing succeeds without suppressed errors. Exercise search and result navigation against the static output. Inspect 390 and 1280 pixel layouts, keyboard navigation, and console errors. Verify anonymous access to every application asset remains gated. The proposed shared chat element and real cited OMP response require independent proof after application preparation.