Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically update links and embeds for room timetables #57

Open
313ctric opened this issue Oct 11, 2024 · 2 comments
Open

Automatically update links and embeds for room timetables #57

313ctric opened this issue Oct 11, 2024 · 2 comments

Comments

@313ctric
Copy link
Contributor

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.

@adamskrz adamskrz changed the title Update links and embeds for room timetables Automatically update links and embeds for room timetables Nov 1, 2024
@adamskrz
Copy link
Member

adamskrz commented Nov 1, 2024

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...

@313ctric
Copy link
Contributor Author

313ctric commented Nov 1, 2024

I think both is probably the best option.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants