Agenda component

[n-d-r-d-g]

I started working on the Agenda component. However, before developing anything concrete, I wanted to run a few things by you @MrSunshyne.

1. Is there a preferred layout for the agenda, e.g. time or room on the y-axis (will there be different rooms)?
2. Which information needs to be displayed on each session's card, e.g. speakers, speaker avatar, room, time?
3. Will there be a redirection to a session detail page when the user clicks on its session card (in the agenda)?
4. Ideas on which features the agenda needs to have, e.g. search functionality, select session?
5. Are the sessions data that's currently displayed on the website dummy data?
6. I was thinking about the session selection feature being used by the organizing team to make logistics-related decisions, e.g. room size to assign to which speaker, amount of goodies, food & drinks, in adverts to provide a better value proposition to sponsors. We would then need to store the selected sessions when the user is signed in. That means we would need to have a sign in feature as well (we'd need one anyway to RSVP right?). Let me know what you think.

[MrSunshyne]

Hi @n-d-r-d-g

1. Two rooms/tracks
2. Card Info
   • Session Title
   • Time
   • Speakers
     -- Avatar
     -- Name
     -- Link to profile
     -- Bookmark session?
3. Yes, click card(or session title) to view full session detail
4. Feature
   • Time awareness (current session, a line to show the time: aboveline is past sessions)
   • Bookmarks (local storage only) (maybe we could do auth)
   • Like a session (nice to have)
5. Yes, these are all dummy data taken from the tailwindui conference template
6. We could wire this up to the same auth mechanism we have now, and introduce extra fields for the user preference. RSVP is indeed needed. It could be interesting to see which sessions people want to attend indeed, but realistically i dnt think people will use it. I'd classify this as 'nice to have'

[n-d-r-d-g]

Alright, thanks for the answers!


4. The like feature sounds interesting. We can discuss further about it (e.g. the design, where to place it, etc...) once the agenda component is built. I don't think it will be too hard to implement.


6. Yeah fair point.

I'll keep this issue open so it get closed when the PR is merged.