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
Currently the timetable links and embeds are for the 23/24 site, so they are all blank or out of date.
(eg the Avon and Milburn pages)
We could easily go though and change all the links to 24/25, but this would then require yearly updates. Ideally it would switch over automatically each year, but I don't know if that is even possible.
The text was updated successfully, but these errors were encountered:
This is pretty easy to fix annually with a find and replace, but doing it automatically could be nice. Probably the most comprehensive source for on working with timetables and room info is the room search command in the UWCS Apollo discord bot (https://github.com/UWCS/apollo/blob/master/cogs/commands/roomsearch.py).
Adding some of this would allow for generating links for next week etc. too, but doing it on build raises some more general architectural issues given this is a statically generated site (do we cron job a fresh build each week?). You could probably also implement it client side, but that feels wrong too...
All the real people using the site will have JS enabled so will get the up to date info from there.
And then we also keep the static url so that loads are faster if it's the correct URL, and to support non-js visitors (bots and crawlers).
I figure that the site will probably be generated at least once a term (eg. Adding info about past shows) so the static data will never be too far out of date.
Currently the timetable links and embeds are for the 23/24 site, so they are all blank or out of date.
(eg the Avon and Milburn pages)
We could easily go though and change all the links to 24/25, but this would then require yearly updates. Ideally it would switch over automatically each year, but I don't know if that is even possible.
The text was updated successfully, but these errors were encountered: