HugoBlox Kit comparison

What it is

HugoBlox Kit provides Hugo-based site building blocks. This evaluation will use its official Hugo starter rather than a hand-written imitation, retaining the starter content and layouts for a meaningful comparison.

Why test it against Quartz

Quartz is the Markdown operational-wiki baseline. HugoBlox is being evaluated for broader block-composed sites, portfolios, publishing layouts, Hugo static output, and Pagefind search. A successful build alone will not establish that its authoring workflow is preferable. Quartz upstream supplies the wiki baseline.

flowchart LR
  A[Verified upstream sources] --> B[Application preparation pending]
  B --> C[Build and interaction proof pending]
  D[Quartz operational wiki] --> E[Setup and release evidence]

Verified versions and source

Verified on 2026-09-27: stable HugoBlox module modules/blox/v0.12.0, commit bf6e0287286303dfaf83e60a64930136b3eba6a6; official starter commit 66efb1916bd62287ea2fef3caacb1245b2f34da2. The starter pins Hugo Extended 0.162.0; the separately verified latest stable Hugo is 0.166.0. Compatibility with 0.166.0 is not yet built or proven.

HugoBlox Kit · official starter · stable module release · Hugo

Version lookups establish source provenance, not installed or deployed versions. The project versions.json records exact source pins, lookup dates, and unknown values separately.

Read by task

• setup — source-derived preparation, output paths, and acceptance checks.
• Restricted operations — the intended authenticated full-build operations route.
• Application destination — intended destination, not a current availability claim.

Current status

Application pending. This is the initial wiki-first preparation. No application build, deployment, search interaction, shared chat integration, browser screenshot, or authentication proof is claimed here. Wiki configuration and source content have been prepared; publication and live route verification remain the release owner’s responsibility.

The intended access split is an authenticated application, a public wiki root, and an authenticated full wiki under /private/. This describes the deployment contract, not observed ingress behavior. The public build excludes the source private directory; frontmatter alone is not an access control.