General idea being to run two calendars simultaneously.
One dev calendar and one user calendar.
The dev calendar being the one we update and creates the weekly schedule and all the bot related things.
The user calendar which is the one users subscribe too but is parsed and updated by the dev calendar.
The fundamentals of which are that when the dev calendar is updated we sanitize the markdown so the users don't see all the funky brackets. Would require synchronization between dev calendar and user calendar.
Example
[**RLCS 21/22: OCE Regional 1 - Day 2**](https://liquipedia.net/rocketleague/Rocket_League_Championship_Series/2021-22/Winter/Oceania/1)
becomes
RLCS 21/22: OCE Regional 1 - Day 2
With all other relevant properties such as timings and location (twitch.tv) in the same place and/or description.
Requirements
Create new calendar (dev) so current users don't have to migrate to a new calendar.
Give mods access to dev calendar to update from now on.
They can continue to update it as usual
Repoint all bot code to use the dev calendar
dev calendar sanitizes markdown and updates events in user calendar.
Never update the user calendar directly, but only through the dev calendar. (Would cause them to be out of sync)
General idea being to run two calendars simultaneously. One
dev
calendar and oneuser
calendar. Thedev
calendar being the one we update and creates the weekly schedule and all the bot related things. Theuser
calendar which is the one users subscribe too but is parsed and updated by thedev
calendar. The fundamentals of which are that when thedev
calendar is updated we sanitize the markdown so the users don't see all the funky brackets. Would require synchronization betweendev
calendar anduser calendar
.Example
becomes
With all other relevant properties such as timings and location (twitch.tv) in the same place and/or description.
Requirements
dev
) so current users don't have to migrate to a new calendar.dev
calendar to update from now on.dev
calendardev
calendar sanitizes markdown and updates events inuser
calendar.user
calendar directly, but only through thedev
calendar. (Would cause them to be out of sync)