The resume is still the canonical artifact on this site, but it is no longer the only one.
The new writing archive exists for a practical reason: some work is best understood as a two-page operating brief, and some work is better explained in longer form. The resume captures scope, scale, and outcomes. The blog is where the reasoning behind those outcomes can accumulate without turning the homepage into a wall of text.
What belongs here
The archive is designed for a narrow set of topics:
- developer velocity as a product and platform problem
- release excellence and reliability guardrails
- AI workflow acceleration inside engineering systems
- the mechanics of turning developer research into roadmap decisions
Why Eleventy
Eleventy keeps the site implementation close to the properties that matter here:
- content can stay in Markdown
- the output stays static and deployment-friendly
- the design system can remain plain HTML and CSS
- the homepage and blog can share one layout and metadata system
That combination matters because this site is meant to be durable. It should be easy to update, fast to ship, and legible to both humans and machines.
What changes next
From here, new posts only need front matter and Markdown. The archive, tag pages, Atom feed, sitemap, and homepage latest-post rail all update from that content.
That keeps the maintenance burden low and makes the writing surface a real extension of the resume rather than a disconnected side project.