Its tries to connect to the network first to fetch the latest spec and then renders it. If the network fails it falls back to the data stored in the service worker.
This makes sense for the lnug homepage as it changes frequently, but does not make sense for the code of conduct.
it should be possible to specify for each page what caching strategy they should use. Some example include:
only update with new service worker (with-service-worker)
show old data - update in the background. (show-old-load-new)
always try to fetch the latest data. (latest)
note: this will apply to the data requests initially.
Current each page has the same caching strategy.
Its tries to connect to the network first to fetch the latest spec and then renders it. If the network fails it falls back to the data stored in the service worker.
This makes sense for the lnug homepage as it changes frequently, but does not make sense for the code of conduct.
it should be possible to specify for each page what caching strategy they should use. Some example include:
only update with new service worker (with-service-worker)
show old data - update in the background. (show-old-load-new)
always try to fetch the latest data. (latest)
note: this will apply to the data requests initially.