👋
← Hyzer

U.S. Department of Veterans Affairs · Accelerated Publishing

Cut VA.gov's publishing gate from two hours to twenty minutes

Every content update to VA.gov rebuilt the whole site. Publishing a clinic closure took 45 minutes on a good day, over two hours on a bad one. I led the team of six that replaced the build with a Next.js system that publishes pages on demand. I designed the migration that let both systems run side by side while 55,000 pieces of content moved across. Nine months, and under twenty minutes by the end.

Production readiness 2023–2024 via Agile Six

Publish gate
2 hrs → 20 min
Content items
55,000+
Built in
9 months
Engineers led
6

The problem

VA.gov's front end ran on a fork of Metalsmith, a markdown static site generator, bent over years into the build tool for a headless Drupal site. That site held more than 55,000 pieces of content. Every publish rebuilt all of it, so build time gated every change. It cost the most on the updates that mattered most in the moment: a facility closure, a weather warning, one clinic's hours. All of it queued behind a full rebuild.

What I did

We built a Next.js system that publishes pages on demand. Getting there was the hard part. VA.gov is built by many product teams on separate contracts, and most were not migrating inside our window. So the PM and I designed a co-existence path: both systems running at once, pages moving across in batches, content routed to the right S3 bucket behind VA's firewall, fallbacks on every path. Every page that moved was one the old system no longer had to build, so publish times dropped through the whole migration.

I also built CMS preview: ephemeral preview servers on every PR environment, plus staging and production. Editors could finally see their content laid out the way it would publish. Before that they proofread it field by field.

The result

Under twenty minutes by the end of the contract, down from a 45-minute floor and a two-hour ceiling. About eighteen months later every page had migrated and VA retired the legacy build.

Full on-demand publishing is still sitting there unflipped. We proposed a single nightly snapshot, which met the legal retention requirement. VA wanted a full-site snapshot per build instead. They can flip it whenever they want.

Let's build.

Tell me where you're stuck and I'll tell you what it'll take.

Book a call