Events-adding ease Pt 2 (after initial site work in #973 done)

[amandavisconti]

Follow up on #973 for further needed work:

Jeremy:

• Check if new setup closes Events that start on one day and end on another aren't displayed on /events list after start date #1136 (close that ticket, if so)
• @jeremyboggs?: See if there's a way on /events to show today's+upcoming events at top of page, followed by a section of "recent events" containing past events from this term only (might need two API pulls?)
• @jeremyboggs?: Style /events-archive so that description text from Fall 2024 events onward is included, but doesn't clog page (e.g. is there an accessible way to hide it behind uncollapse arrows, so it's on the page and doesn't need new markdown file per past event, but only visible if you click to see it?)

Amanda

• @amandavisconti has scheduled themselves to do a manual copy of LibCal events to /_past-events at the end of spring, summer, and fall terms each year. Only copy: Event title, Speaker/instructor, Event date, Event Time (LM requested!), Event description/body text. (I.e. no location, reg info, images).
• re:doubled categories, once libcal live on site: I can’t see where to set whether something is calendar-specific vs. system wide. When you create an event, it lets you choose either. So I guess instead of editing further events, I can set up a test event just on system-wide-SLab-category and one on just-calendar-specific-Slab-category, and if both are pulled into our feed it doesn’t matter. UPDATE: unneeded as code pulls both into SLab site.
• @amandavisconti look into automating past-term => SLab events archive more (eg CSV export=> display from CSV in folder's data?). See Ammon's setup here
• @amandavisconti Work w/Laura on Some 2023-2024 events are on LibCal but not SLab site; move into SLab site archive #1104 (making sure all old events, e.g. 2023-2024 especially but maybe Jan 2018-July 2024 even?) are in events archive, then close that ticket
• Test locally if moving all /_past-events items into folders per year breaks anything on /events-archive page
• Update documentation on SLub /events/archiving-events page once this work completed

[jeremyboggs]

Style /events-archive so that description text from Fall 2024 events onward is included, but doesn't clog page (e.g. is there an accessible way to hide it behind uncollapse arrows, so it's on the page and doesn't need new markdown file per past event, but only visible if you click to see it?)

The events archive has a links that go to the past event's page, which includes the description. I'd suggest just keeping that instead of trying to display the text for each event on this page, even in a hidden/collapsible way?

[amandavisconti]

Style /events-archive so that description text from Fall 2024 events onward is included, but doesn't clog page (e.g. is there an accessible way to hide it behind uncollapse arrows, so it's on the page and doesn't need new markdown file per past event, but only visible if you click to see it?)

The events archive has a links that go to the past event's page, which includes the description. I'd suggest just keeping that instead of trying to display the text for each event on this page, even in a hidden/collapsible way?

Let me check with Laura—I think we might be interested in having that descriptive text on our site somewhere, but there are only ways to do that (e.g. biannual post collecting events from past term). We also wanted a Slab-held record in case someone deletes the LibCal past events (e.g. a non-SLab person tidying things), though just exporting and holding that as a CSV in our GDrive covers for that concern.