1.1.0 – Cache Feature

Cache pages between sessions and revalidate with modification timestamps

Even without caching enabled, the frontend will cache pages between indiviual routes/views. Once you reload the tab however, every page data has to be fetched from the api once again.

If you wish to create apersistent store which caches pages between browser sessions, set in your .env:

• KIRBY_CACHE to true
• VITE_PERSIST_API_STORE to true

By that, the pages state will be saved to IndexedDB each time a page has been fetched.

While calling up the website for the first time, the home page will be always be fetched. It holds site data with an index of modification timestamps for each page id. This is relevant, because before returning a cached page, the timestamp will be compared with the latest modification timestamp from the site modification index. If it differs, the cached page will be removed and freshly fetched.

Initial Release

This project is a migration the a11y-kirby-vue-starterkit to use Vite instead of the Vue CLI. And of course Vue 3 itself.

The Vite config is much smaller than the former Webpack config. It works pretty well. Setup scripts like the PHP server start via Node for development have been optimized as well.