Is your feature request related to a problem? Please describe.
Defining the schedule in JSON or Firestore is complex and error prone. It creates a lot of blank schedules and stale schedules when an error causes the schedule to not get generated.
Describe the solution you'd like
A UI for building out the schedule. It should allow organizers to specify blocks with start and end times that reference a room and session.
A possible solution would be a Google Sheet. It would be relatively easy to fetch and consume via the Sheets API.
Describe alternatives you've considered
- Maybe a Notion table. Notion free tier is more limited than Sheets.
- A Markdown table would keep it in the repo as a version controlled file.
Is your feature request related to a problem? Please describe.
Defining the schedule in JSON or Firestore is complex and error prone. It creates a lot of blank schedules and stale schedules when an error causes the schedule to not get generated.
Describe the solution you'd like
A UI for building out the schedule. It should allow organizers to specify blocks with start and end times that reference a room and session.
A possible solution would be a Google Sheet. It would be relatively easy to fetch and consume via the Sheets API.
Describe alternatives you've considered