Build test

the fundamentals Accurate as of 11 August 2026

Not a real question. This page exists to test the layout.

This page proves the chain works end to end: markdown in the repo, Hugo on Cloudflare’s build image, a real URL you can open on a phone. It is not part of the series, it carries noindex, and it should be deleted the day the first real article goes live.

Everything below is an element the article layout has to get right. If one of them looks wrong here, it would have looked wrong in an article.

A code fence

Plain monospace, no syntax colouring — that is a decision in hugo.toml, not an oversight.

select date_trunc('day', event_ts) as day,
       count(*)                    as events
from   telemetry.events
where  event_ts >= current_date - interval '7 days'
group  by 1
order  by 1;

A table

Element	Comes from	Fails how
Footnote	`[^id]` written in prose	silently, if it is written inside a code fence
Depth	the `depth:` key	prints the raw key instead of the phrase
Freshness	the `accurate_as_of:` key	goes stale without ever saying so
Provenance	the `provenance:` key	the line above the article body goes missing

A footnote

Compacting an Iceberg table rewrites data files. It does not rewrite the manifests that point at them.¹

A list, and inline code

relURL for assets, so the site survives being served from a subpath
.Permalink for the canonical tag, so a mirror points home instead of competing
draft: driven by pipeline status, so nothing unapproved can ship by accident

A quote

The check that has never failed is not a check.

A deliberately unremarkable footnote. The point is that it renders at all, that it is numbered, and that the arrow at the end of it takes you back to where you were reading. ↩︎

← everything else