All the tools have course calendars which are a PAIN to write.
One file per week as an authoring tool seems hard.
the programming is easiest if every date is defined explicitly, but in classes with consistent schedules, that is hard.
I, personally, prefer 1 file with all assignment dates
each assignment needs:
release date
due date
content / spec link
submission link
probably number of points
This info is ideally not duplicated manually.
How can we support the table-style calendar (CS10, 161, 188, others)?
Long Shot: Google Sheets / CSV sync?
Does it make sense to have the tool build a calendar file from a Google sheet?
If a sheet URL is shared via link, it's trivial to get/import a CSV. This means at build time (if desired) or locally (if the output is committed to the repo) we can generate a calendar from a format easier to write/update.
All the tools have course calendars which are a PAIN to write.
One file per week as an authoring tool seems hard.
Long Shot: Google Sheets / CSV sync?
Does it make sense to have the tool build a calendar file from a Google sheet? If a sheet URL is shared via link, it's trivial to get/import a CSV. This means at build time (if desired) or locally (if the output is committed to the repo) we can generate a calendar from a format easier to write/update.