Closed conorsch closed 7 years ago
Updates to page content made through the Wagtail CMS automatically trigger frontend cache invalidation, thanks to the default behavior of the frontend cache invalidator.
Frontend cache invalidation for updates to content that is not managed by Wagtail requires custom code, and should be handled on a case-by-case basis.
When content updates happen, the caching should be reset, so changes go live quickly.