How I build this site
This site has no deploy button. Every change to the main branch goes through the same automated pipeline: build, measure, test, and only then release. If a check fails, nothing is deployed and visitors keep the last version that passed. There’s no step for me to forget.
What has to pass
It has to build. The pages are generated ahead of time, and if one fails, the run stops there.
The tests have to pass. The API behind the contact form and the demos has unit tests that run against in-memory stand-ins for the cloud services, so they need no credentials and give the same result every time.
It has to be fast. Every page has a size budget, and Lighthouse, Google’s page-quality tool, loads the built pages on a simulated phone: the home page has to show its main content in under 1.5 seconds. Checked on every push, performance can’t drift without my build kicking it back to me.
Every screen size
A second test suite loads every page at 35 screen sizes, from the 280-pixel cover screen of a folding phone to a 5,120-pixel ultrawide monitor, in portrait and landscape, in both Chrome and Firefox. Some runs behave like touch screens; others set the browser’s default text to 150%, as a lot of people with low vision do. It also resizes the window through about two hundred in-between sizes, because that’s usually where layouts break.
At every size it checks the same rules: nothing scrolls sideways, nothing pinned to the screen covers more than half of it, every button and link is big enough to tap, and no script throws an error. An accessibility audit runs in both the light and dark themes. That’s a little over two thousand checks, and I run them before any change to the layout goes up.
Static where possible
Most of the site is the same for every visitor, so it’s built once and served as plain files from cloud storage behind a CDN, which answers most requests from a data center near the visitor. There’s no server to crash and nothing to scale up for a busy day.
A server only where it’s needed
The contact form and the demos do need a server, so they get one small API on Cloud Run. It scales to zero when nobody is using it, and I pay for the seconds it runs. One service is less to secure and less to pay for.
Tyler SandersEngineer, Computer Scientist, Tech Enthusiast