Conference Schedule

What you'll need

1. A list of accepted talks (preferably a spreadsheet)
2. A daily schedule for the conference

Creating the schedule

You need to convert the schedule provided by the LPC into a yaml structure. First, take a look at the /_data/conf/examples/schedule.yml file. The file contains an array of "event objects". Each event object has the following attributes:

Attribute	Type	Purpose
timeImg	string	This is the clockface image that will be displayed in the timeline. There is a readme in /assets/img/clockface with more details. Essentially, you need a corresponding clockface PNG that matches the start time of this schedule object
time	string	The start to end time of the event. 24hour format, hh:mm-hh:mm with leading zeroes
title	string	The title of the event. Note that : should be written as :
day1	bool	Does this event occur on day 1?
day2	bool	Does this event occur on day 2?
day3	bool	Does this event occur on day 3?
groupId	int	See below for additional information about groups

We used to have UTC times stored in start & end but I don't think those are used anywhere. Events are sorted lexically by their time property.

Day: day1, day2, day3

If an event occurs at the same time on multiple days, you may mark it with multiple day* attributes. Note that for schedule purposes we don't count the preconference day.

Groups

Groups allow you to chunk multiple talks together in a large block. It requires that your event have a groupId attribute AND your post have a groupId attribute in its frontmatter.

Posts

Posts will need to have four schedule-related properties added to their frontmatter:

Attribute	Type	Purpose
day1/2/3	int	which day the talk is on (talks will only have one of these three properties)
groupId	int	must match an event in schedule.yml, this lets us display the talks on the daily schedules
spot	int	for sorting the talks within each group, e.g. spot=1 goes first
startTime	datetime	used to display date/time information on the talk page, format is like 2020-12-25T09:30