Colophon — How TechFuel HQ Is Built

What this page is

A public record of how this site gets built — the publishing stack, the sourcing approach, and the editorial rules every article has to clear before it ships. The short version is on the About page. This is the long version with names, versions, and rules written out.

Publishing stack

TechFuel HQ is a static site built with Hugo extended (v0.145.0) and deployed to GitHub Pages from the main branch via GitHub Actions.

• Hosting: GitHub Pages
• Build: Hugo extended (v0.145.0), --gc --minify on every deploy
• Source control: GitHub. Changes land on main — some through a pull request, most pushed directly — and every push runs an automated ship gate (build, link check, and SEO//disclosure checks) that has to pass before the site deploys
• CDN / DNS: Cloudflare in front of GitHub Pages (migrated 2026-06-20)
• Analytics: Google Analytics 4 (GA4)
• Search: Google Search Console for indexing state
• Domain: techfuelhq.com, registered to the site author

Layouts and styles are written from scratch. No third-party theme.

How hardware figures are sourced

The site includes both first-party benchmarks and reviews based on external testing. The Ollama–LM Studio comparison includes August 26, 2026 RTX 5080 captures; the Home Assistant voice benchmark includes August 25–26 captures, a versioned command corpus and raw responses. External hardware figures are sourced from named publications and primary documentation, including:

• Power and homelab hardware: ServeTheHome reviews and power testing, plus manufacturer spec sheets
• Linux and storage benchmarks: Phoronix and the OpenZFS documentation
• General hardware and GPUs: Tom’s Hardware and the AnandTech archive
• First-party specs and standards: manufacturer product pages, Intel ATX design guides, JEDEC, PCI-SIG, and IEEE documents

The editorial policy calls for each figure to name its source and for vendor specifications to be distinguished from independent measurements.

AI in the workflow

AI tools are part of the research and drafting workflow. The editorial policy requires benchmark, price and specification claims to be supported by cited sources or labeled first-party data. The site’s human byline identifies who is accountable for recommendations and corrections.

Editorial standards

Every article on this site has to clear all of these before it ships:

1. No sponsored articles, no vendor samples, no paid placement. A recommendation is never shaped by anything other than the merits of the product.
2. Methodology and sources. Benchmark-based articles should name the test setup, source publications and primary documentation that support their figures.
3. Separate source checks from page updates. An explicit source-check date is labeled “Last verified” or “Sources checked.” Otherwise, date labels identify a page update or its publication. Individual source and price records can carry their own dates.
4. Cited benchmarks or no benchmarks. Vendor spec-sheet numbers are labeled separately from independent third-party measurements. Made-up benchmarks are worse than no benchmarks; any figure that cannot be attributed to a named source is removed rather than estimated.
5. No paid placement, ever. No product appears because a vendor paid, gifted, or sponsored it; placement is editorial only.
6. Cite primary sources inline. Vendor docs, official changelogs, and reputable trade press get linked. Reddit and forum threads get linked when they are the primary signal but get labeled as community-reported, not as vendor-confirmed.
7. No fabricated first-party claims. Present-tense first-person measurement claims (“I measured…”, “on my own bench…”) are used only when backed by a real, current artifact. Where no such artifact exists, figures are sourced to named third parties and the prose says so. Past-tense references to gear genuinely owned in 2024–2025 are allowed and labeled as past.

Where the policy pages live

This page is the toolchain-and-history record. The rules themselves each live in exactly one place, so they cannot drift apart:

• Source standards — what counts as a citable source and when forum posts qualify: methodology.
• Money — which links earn a commission and why that never changes a pick: the disclosure page, summarized in methodology. No paid placement, ever.
• Corrections — how errors get fixed and logged: methodology.

Contact

Spot something wrong, want to challenge a recommendation, or have a question about how a specific article was produced? Email contact@techfuelhq.com.

Last updated: 2026-09-08.