This can be used in other places, but ensures caches are invalidated
whenever something about a page changes.
- Add a util to get wagtail-specific fragment cache keys
- Don't pollute context when injecting site variable
- Add documentation on wagtail fragment caching
- Define an intelligent cache key for pages
- Allow the components of the cache key to be easily modified
- Note that some manual changes may not create a new cache key
Co-authored-by: Andy Babic <andyjbabic@gmail.com>
Closes #5074
- Link getting started section to elasticsearch backend, not performance page as this is more relevant.
- Mention frontend caching on performance page
- Mention prefetching image renditions on performance page
Most of these are no longer applicable due to the introduction of Wagtail guide, where possible the new guide links are used now
- Re-add missing docs image for extending Draftail
- There is no Guide page (yet) for Inserting videos or images so those links have been removed
- Fix some additional reference issues where the page name and reference were causing issues
* Clean up the performance page structure
Many of the sections mentioned here will improve performance for much more than just the editor experience.
* Link to Django's performance page
- Allow users to override the default attributes given to an image
- Update tests to account for new tags
- Add documentation for custom image attributes
- Recommend that loading=lazy & decoding=async be considered for performance in front-end sites
