Local fallback pages for edge services
A fallback page should be ordinary, fast, and independent of the public entry point.
A local fallback page is most useful when it has no external dependencies. It should render even when upstream services or package registries are unavailable.
The page does not need to be impressive. It needs to be coherent, have a few expected files, and answer basic requests without errors.
A small sitemap, favicon, and privacy note are enough to make the site feel maintained.
Filed under: fallbacks