Why it matters
A sprawling site fails when every experiment shares one fragile runtime. The counter-move is to ship static pages by default, keep interaction local to the route, and let Worker endpoints handle data, queues, and recovery instead of page composition.
The growth case for boring delivery
A giant utility and article network gets its distribution from indexable pages, fast first paint, and predictable deploys. That favors pre-rendered shells over an app-wide client runtime.
When each route brings only the JavaScript it needs, failures stay local. That matters more than elegance once the property starts adding dozens of independent calculators, generators, and long-tail explainers.
- Static pages stay cheap to deliver and easy to cache.
- Worker APIs keep dynamic concerns off the page shell.
- Route-level scripts sharply reduce cross-page interference.
How this turns into an expansion engine
The winning pattern is not a single masterpiece homepage. It is a production line that can stamp out new surfaces without increasing blast radius. Shared contracts, content schemas, and deploy gates do most of that work.
Once the shell is stable, Codex can safely add new tools or articles because every change is forced through the same route matrix, rights checks, and health snapshots.