things like:
• we can't have any dynamic pages, everything has to be static HTML
• we don't control the actual page; our job is to create a fragment of HTML that the CMS stitches into the body, then associate that fragment with some publish metadata...
• ...but during development, we need a simulacra of the NYT article template
• we have to be able to create AMP versions of almost every page
• our old app was already fairly Svelte-centric, and we wanted to reuse as much as possible
• we wanted to use client-side navigation to avoid page reloads (while capturing custom navigation analytics) e.g. because it makes no sense to make people load MapboxGL repeatedly
It's possible that we could have coaxed one of the existing static site generators into fulfilling all these requirements, but it seemed like we'd be in uncharted territory without the benefit of having the SSG maintainer on staff!