You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I am not wrong, using if_before: end_week N is easy to run a course by adding further modifiers without manual adjust the date/time rule in ISO-formatted dates/time format. So, if the offset (starting date/time) of the course is set, then other time is determined. However, I can't find in documentations about the setting the offset variable in course.yaml.
The text was updated successfully, but these errors were encountered:
They're stored in the database (rather than the YML course material), and so they can change from one edition of the course to the next while leaving the course material the same.
If you want what you suggest (which is to have everything offset from the start date of the course), you would create one event, say start_of_course, and then express all dates as, say start_of_course + 3 weeks or start_of_course + 3 weeks + 1 day @14:50. But you're also free to have as many events as you like, and fix those to more natural anchor points (that may shift from one run of the class to the next), such as lecture_on_foo. To give you an idea, I mainly use events for homework_due and lecture 12 as anchor points.
If I am not wrong, using
if_before: end_week N
is easy to run a course byadding further modifiers
without manual adjust the date/time rule inISO-formatted dates/time
format. So, if the offset (starting date/time) of the course is set, then other time is determined. However, I can't find in documentations about the setting the offset variable incourse.yaml
.The text was updated successfully, but these errors were encountered: