You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The /events page has a beautiful map with a ton of thumbnails and direct links, that is small to represent. It sucks that each client has to go through the rigmarole, and the added round-trips getting the gallery.
If the jekyll build can access the network, render the page in puppeteer or something (or fetch the apis, ...) and cache the html, then that can be written to disk and simply served. The js can replace the cached list when it completes getting newer photos.
The text was updated successfully, but these errors were encountered:
The /events page has a beautiful map with a ton of thumbnails and direct links, that is small to represent. It sucks that each client has to go through the rigmarole, and the added round-trips getting the gallery.
If the jekyll build can access the network, render the page in puppeteer or something (or fetch the apis, ...) and cache the html, then that can be written to disk and simply served. The js can replace the cached list when it completes getting newer photos.
The text was updated successfully, but these errors were encountered: