bruinthetachi.com
A replacement for my fraternity chapter's WordPress site: a static build the next webmaster can edit without knowing what a build is. It runs, and the domain has not been cut over to it yet.
The decision
The old site is linked from alumni emails going back years, so breaking those links is the real cost of a migration, and the redirect map is the part of this I care most about getting right. It is not done: see the limit below for what still 404s and by how much. The member family tree is laid out at build time and shipped as plain SVG, so no visitor downloads a graph library to look at a static picture.
What it does not do
The redirect map is incomplete and I would rather say by how much. The old sitemap index names 6 sub-sitemaps and 292 URLs; 60 resolve on the replacement. The 232 that do not include 8 of the 13 top-level pages, among them /about/, /brotherhood/, /social/. Measured by ops/measure-migration.mjs rather than counted by hand, because counting it by hand produced a wrong answer twice. The live chapter domain still serves the old WordPress site, and the cutover is mine to schedule. One chapter, not a product, and not something anyone else should adopt without reading the photo policy first.