Repository navigation
Event invites #39
Description
Activity
One angle is splitting up the Markdown rendering from
[...slug]/page.tsxinto different layouts for events, community, docs, etc.Pro: accomplishes the different layouts which we want at least for events vs. other pages, in a more idiomatic way than a bunch of conditionals within
[...slug]/page.tsxCon: larger effort; will take time to implement effectively the same layout for community & docs
Route
Option 1 example:
/events/2025-02-21/staging/invite
Option 2 example:/invite/2025-02-21/stagingRelevant considerations:
- If we go with Option 1, what does going to the base route do? Presumably render whatever Markdown is in there, or to 404/redirect if none (as is current behavior)
- How about past events and/or events with no invite? We shouldn't assume all events will have one
Re: RSVPs... I think I may have to cave on a database/CMS over Markdown for storing events... how else will we track them?
Decision re: RSVPs:
For big events like cascade and DEPLOY, they have their own registration systems, but for compsigh nights: ideally we could gauge e.g. how much food to get, and it'd be nice to have
[an accurate number of who is going to each compsigh night], but I don't think we'd get that on any RSVP system 😂After thinking about it and yapping with @drshooby, I think the engineering effort around RSVPs is not worth it, at least for now when I can help by doing design & branding, especially for DEPLOY. We run RSVP stuff maybe three times a semester, so I think Partiful or whatever we like for the first compsigh night, and the usual registration systems on the other platforms is fine.
Can for sure still implement event "invites" as a whole. It'd be nice if each event had its own link (which is not the case currently) that people can share with friends, add to calendar, and view the recap when it's written.
- added a parent issue
on Aug 9, 2025
Event invites
Part of web platform Summer 2025 redesign
Adding a dedicated layout for each event page:
Collect RSVPs (going/maybe/can't go)Toggling whether RSVPs are required or not/eventscards. All with an invite are now clickable (+ some affordance they have an invite) and inline show quick actionsConsiderations
[...slug]/page.tsxshould be kept super minimal. Likely only rendering acover_imageat the top if not null.linkin frontmatter).RSVPs: related to User accounts #5? Where do they go?Todos
/eventscards) on each event page/events