Pack 162 Modernization
A Cloudflare-first modernization plan for a Cub Scouts site, using an edge proxy and progressive migration instead of a risky full rewrite.
Modernize a legacy site safely by changing the surface before changing the foundation.
Description
Instead of rebuilding everything at once, this architecture uses a Worker as a smart edge layer so the experience can improve immediately while the existing site keeps doing its job.
Challenge
The legacy site already serves real families and workflows, so the migration has to reduce risk, preserve key routes, and leave room for a better long-term UI.
Approach
The plan starts with an edge proxy and HTML rewriting for fast wins, then moves key routes into a modern Pages app as confidence grows.
Next step
Stand up a dedicated project surface when the first public-facing modern route is ready to ship.
- Status
prototype - Visibility
public - Suggested surface
Apex detail page - Technologies
Workers, Pages, HTMLRewriter, KV, R2
What is already true.
- Architecture and phased rollout are documented and implementation-ready.
- Critical legacy paths are treated as passthrough routes to avoid breaking essential flows.
- The migration path explicitly accounts for privacy, youth-safety, and operational risk.