The user's published site should be re-rendered as soon as the user makes a change. Caching the entire site for an extended period of time or updating only the edited page will show stale content and might leak information (for example, a just hidden page will still appear on the public site). A solution is to use a versioned cache key for the entire site, which regenerates on every edit and is cached for 10s. Another option is to purge the cache for the entire site. Because Fernsage uses Supabase, any edits go through Supabase to the database without needing to go through a server or edge function. If we want to purge the cache, we would need to trigger an external call to Cloudflare whenever the database changes. This might sometimes fail, perhaps due to rate limiting, and we would need additional infrastructure to monitor and retry. Using a versioned cache key that is stored in the database and bumps on every edit is more compatible with Supabase because edits are already doing to the database, and requires less infrastructure.