Architecture

This site is a collection of static files generated with Hugo. Its architecture is deliberately narrow so that the published result remains easy to inspect.

Request path

A browser requests a URL and receives a prebuilt HTML document. That document may request one local stylesheet and, when the article needs them, local images or audio.

There is no browser-side application. The site does not use JavaScript, WebAssembly, a database, an API, authentication, forms, comments, analytics, cookies, advertisements, web fonts, iframes, service workers, Workers, or Pages Functions.

Normal links may lead to other websites. No third-party site is contacted until a reader chooses to follow one of those links.

Content and media

Posts are written in Markdown and stored as Hugo page bundles. Images and audio belonging to a post are kept beside its Markdown source rather than fetched from an external media service.

Informative images receive useful alternative text. Spoken audio requires a transcript. Non-speech audio receives a text equivalent describing what it contains. Media is included only when its purpose can be stated plainly.

Privacy and browser policy

The site does not add analytics or construct visitor profiles. As with any hosted website, delivery infrastructure may process request metadata needed to serve and protect traffic. The site itself does not add a separate tracking layer.

Browser policy begins from default-src 'none'. Styles, images, and media are limited to the same origin, while scripts are disabled. Responses also request no referrer information, MIME sniffing protection, a restrictive permissions policy, and an initial short HSTS lifetime.

These controls reduce unnecessary capability. They are guardrails, not a claim that software or hosting can be made risk-free.

Build and publication

Every build removes the previous public/ directory before generating a new one. A local audit then checks the generated artifact for prohibited executable content, unsafe markup, unexpected file types, accidental source files, secrets, and external subresource requests.

Only public/ is a publication artifact. Source files, build scripts, and local tooling are not part of the deployed site.

Why document this

Architecture affects readers even when it is invisible. It influences loading behavior, privacy, accessibility, maintenance, and the number of ways a page can fail. Publishing these boundaries makes those choices open to inspection.