Note of Archival: After three gruesome years, they finally changed the reservation system to a usable one. This website is not needed any longer.
Motivation: the KIT website is bad
When opening the index page, the different areas are displayed. Those are based on src/areas.config.js
Every AreaCard
fetches some data from the KIT Server.
This creates a lot of requests (which I hope is fine)
/api/fetch?area=<code>
fetches the booking data for a givenarea
(KIT Neubau 1.OG has code20
)/api/book?area=<area>&room=<seat-id>&period=<slot-id>
basically redirects to KIT website/api/dummy_fetch?area=0
use this when testing (a lot quicker AND you don't spam the KIT servers)
Note: the /api/fetch
endpoint uses the /api/dummy_fetch
handler when NODE_ENV === 'development'
- Fix inconsistent (and sometimes straight up wrong) server time in
/src/utils.js
- Implement all areas (build some ui for ungrouped areas)
- Do SEO and better enforce SSR and SSG with next
- Cache the fetch requests by default for ~60 seconds
- Explain to SCC why their servers get so many requests