These calendars are based on our official WAFL fixtures, but are provided openly and collaboratively by members of our community, for ease of use (in your own calendar app). All files/code for the calendars and this website can be viewed and contributed to here on Github.
The website and calendars from this repository are automatically deployed at fixtures.blackducks.au using Cloudflare Pages for the easy access of our SDFC community and members. The SDFC logo is visible on this GitHub page and website (directly from the club official website) solely to accurately represent the club and provide basic numbers on how many people use these community built calendars to the club.
Important
Want to contribute? Fork the repo, make your edits (after reading below) and lodge a pull request. After successfully contributing a few pull requests, @duyfken will add you as a collaborator to more easily add your future contributions.
Keep in mind, the calendars provided here are in the iCalendar format (*.ics files). As a result, for these calendars to work correctly when people subscribe to them, any updates must adhere to the specification standards of the iCalendar format (namely RFC 5545 and its updates). Regardless of whether you use an iCalendar editor or manually create/edit events on the calendar, they must adhere to these standards. The following are some guidelines that will help us to make sure the calendars adhere to the required specification standards and will keep working correctly for all subscribers.
League Fixtures = sdfc-league.ics
Reserves Fixtures = sdfc-reserves.ics
Colts Fixtures = sdfc-colts.ics
WAFLW Fixtures = sdfc-waflw.ics
Rogers Cup Fixtures = sdfc-rogers-cup.ics
BEGIN:VEVENT
DTEND;TZID=Australia/West:20250405T173000
DTSTAMP:20241222T031124Z
DTSTART;TZID=Australia/West:20250405T143000
LOCATION:Steel Blue Oval, Bassendean
SEQUENCE:0
SUMMARY:Swan Districts vs West Perth - WAFL Round 1
TRANSP:OPAQUE
UID:2c714e63-05c3-45bd-b21d-73d020b10115
END:VEVENT
All events must have these properties/lines as a minimum, though others may be added if needed (such as DESCRIPTION:First line/nSecond line, to add a detailed, multi-line description, such as broadcast information or results, where the /n denotes a line break)
The specifications for each property will be mentioned here, as it's the raw files that are visible in this repo, and what will be contributed using Git. If you use a iCalendar editor to create or edit events, it is the contributors responsibility to confirm their contributions conform to the required specifications, as not all Calendar apps create events that conform to the iCalendar specifications all the time (we're looking at you Google and Microsoft 😉) Properties can be mentioned in any order, the order does not matter (other than 1. exception), simply that they exist to provide the necessary information.
- Like all things in life, an event must have a
BEGIN:VEVENTand anEND:VEVENT. They must be at the start and end, for obvious reasons. - An event must have both a start and end timezone/time, with the timezone in the tz database identifier format (
Australia/Westfor our UTC+08:00 WA timezone) and the time in the ISO 8601 format for that timezone (local).
DTSTART;TZID=Australia/West:20250405T143000
DTEND;TZID=Australia/West:20250405T173000
- A timestamp for when the event was created must be mentioned in ISO 8601 format at Zulu/UTC (+0) time.
DTSTAMP:20241222T031124Z - A location must be mentioned for the event. For our fixtures, please mention the official name of the oval and the suburb it is in.
LOCATION:Steel Blue Oval, Bassendean - When creating an event,
SEQUENCE:0must be included. This number is progressed +1 when editing an event, to ensure the apps of those subscribed to the calendar know that there has been an update to an event. In this example, if you don't progress it toSEQUENCE:1when editing the event, apps that don't correctly conform to the iCalendar specifications may not provide your edit to people subscribed to the calendar. TRANSP:OPAQUEdesignates that the event takes up the subscribers time, allowing the event to be detected by free-busy time searches.- The event must have a Universally Unique IDentifier. You can use any UUID generator (if you are creating the event manually, outside a calendar editor) but it must be unique, as if there are any events with the same UID, it will cause conflicts that mean one or all of the events with the same UID will not be updated.
UID:2c714e63-05c3-45bd-b21d-73d020b10115 - Finally, your event must have a title. In our case, please specify the parameters in this order:
Home Team vs Away Team - Competition Round ##so we have all event titles in the same format. Such as from our example:SUMMARY:Swan Districts vs West Perth - WAFL Round 1