Site Infrastructure#

This portfolio is a static Hugo site. Content lives in Git, and Cloudflare Pages builds and publishes it directly from the repo on every push.

source -> cloudflare pages build (hugo) -> static output -> cloudflare cdn

The Webpage#

The site uses Hugo with the Terminal theme as a Hugo Module. The homepage is Markdown rendered through a small custom layout for the infrastructure card, with a CSS override for layout and readability.

  • Source: content/_index.md
  • Theme: github.com/panr/hugo-theme-terminal/v4
  • Config: hugo.toml
  • Generated output: public/ during CI only

Hosting Platform#

Cloudflare Pages serves the static output over Cloudflare’s CDN. The production site has no application server, database, or committed build directory.

Current runtime footprint:

  • static HTML, CSS, and generated assets
  • Cloudflare Pages hosting + CDN
  • Cloudflare git integration for builds and deploys
  • no backend service in this repository

Build Pipeline#

Cloudflare Pages builds on pushes to master (and generates preview deploys for other branches/PRs). The build runs hugo --gc --minify with the Hugo Extended binary.

push to master -> cloudflare pages build (hugo --gc --minify) -> deploy

Deployment Pipeline#

Cloudflare deploys the build output straight to its edge network — no separate artifact/deploy step.

hugo build output -> cloudflare pages -> cdn

Site URL:

https://portfolio.alaric-tech.workers.dev/

Operations#

Rollback is handled through Git, or by re-promoting a previous deployment in the Cloudflare Pages dashboard. Reverting and merging a rollback commit triggers a fresh build of the previous site state.

Reasonable next checks:

  • scheduled link check
  • Lighthouse or accessibility check in CI
  • custom domain and DNS notes
  • lightweight uptime monitoring