← WorkEngineering practice

This website

TUF Web's own website, a static site run like production software, with its infrastructure, its release checks and the figures on this page all in code.

Role
Design, build and operation
Hosting
S3 + CloudFront
Template
~11 KB of a 51,200-byte limit
Hosting cost
~$0–1 a month (estimate)
Asset cache
1 year, immutable
The TUF Web home page in the light theme on a desktop. A large black TUF wordmark crossed by an orange stripe over a faint engineering grid, with angle annotations and the line “Cloud-native software, and the infrastructure that runs it.”
The home page leads with the mark, drawn like an engineering drawing.

This is TUF Web’s own website, designed, built and operated by TUF Web. It says what TUF Web does, shows selected real projects, and makes contact easy. It replaces an older site whose whole page was one raster logo.

It’s also a deliberate piece of evidence. A brochure site has the same failure modes as a bigger system: environments that drift apart, a deploy that only works from one laptop, a security header nobody remembers adding, an accessibility regression that ships unnoticed. So this one is built and run to the same standard as anything else.

What’s in place

  • Static by default. Pages are plain HTML built ahead of time, and complete without JavaScript. The only scripts are the theme switch, a copy button and the home page’s slide-in. Nothing needed a server, an API or a database, so there isn’t one.
  • A strict content security policy with no exemptions. Scripts, styles and fonts load only from this site. Nothing is inlined, and the build fails if anything inline reaches the output, so the policy never needs an exception.
  • Everything is code. The bucket, CDN, certificate, DNS records and security headers are one AWS CDK app, tested before it deploys. One command runs every check, deploys the infrastructure, uploads the content and clears the CDN, and a smoke test checks the result from outside.
  • Caching that can’t serve stale pages. Hashed assets are cached for a year and old ones are kept. HTML is revalidated on every request, and each deploy clears the CDN. A rollback is a redeploy of the last good version.
  • The brand is a dependency. Marks, colours and motion are synced from a separate brand repository, and a check fails the release if the site’s copy drifts from it.
  • Figures are measured, not typed. A script runs Lighthouse, measures first-visit transfer, runs accessibility checks on every page in both themes and counts the tests, then writes the results into this page at build time.

Problems worth solving

Deploying CDK without bootstrapping the account. The site’s AWS account is set up without the usual CDK bootstrap, and CDK’s obvious options still depend on it. One points CloudFormation at the bootstrap’s roles, and the first deploy failed on that before creating anything. The fix was CDK’s legacy synthesizer, which deploys with plain credentials and sends the template inline. That keeps the stack to native resources, under CloudFormation’s inline size limit, with tests asserting it creates nothing outside its own names. It’s a deliberate experiment that’s still being evaluated, not a recommendation.

Keeping private material out of a public build. The repository holds things that must never be published: draft project pages, other projects’ internal addresses, cloud endpoints. Drafts are left out of every deployable build. A guard scans the whole output for forbidden names, internal hostnames, cloud endpoints, credential-like strings and markup that would break the security policy, and checks every page has one heading, a title, a description and a canonical URL. Any hit fails the build, so publishing something private takes a failing check, not just a missed review.

Measured, not claimed

Lighthouse scores are for the home page in its mobile profile. Weights are the bytes the home page transfers on a first visit, fonts included. A script measures all of it and writes the results into this page at build time.

Lighthouse perf.
100
Accessibility
100
Best practices
100
SEO
66 (noindex by design)
Home page weight
187.4 KB
JavaScript
6.2 KB
Requests
14
Axe violations
0
Tests
14 unit · 44 browser
Measured
2026-10-30 @ 9f2cd60
Measured on
Deployed dev site (noindex)

Stack

  • Astro
  • TypeScript
  • AWS CDK
  • Amazon S3
  • Amazon CloudFront
  • Playwright
  • axe-core
  • Lighthouse