Here is the JSON data for your reference:
, 'start': new Date ('2011-01-01'),
This represents an example JSON snippet:
,"start":"2011-06-10",
The date formatting can be quite tricky and prone to bugs, but the latest version promises improvements in this area.
This quote is directly sourced from the official Documentation:
start Date. Required.
Specifies the starting date and time of an event.
When defining Event Objects for events or event sources, you have the option to input a date string in IETF format (e.g., "Wed, 18 Oct 2009 13:00:00 EST"), ISO8601 format (e.g., "2009-11-05T13:15:30Z"), or a UNIX timestamp.
Take note of the 'T' in the time representation, as not all serializers include it - so exercise caution with that. Also, the presence of 'Z' denotes no-time-zoning, which may pose challenges for users in different regions - another potential bug to watch out for.
Additionally, below is a more intricate JSON excerpt from my platform:
[{"title":"Tee Times","start":"2011-06-30T00:00:00","end":"2011-06-30T00:00:00","allDay":true,"color":"rgb(21,144,51)","groupsize":"","className":"data-brs clickable","cache":null,"EventName":null,"description":null,"EventCompTypeMSP":null,"url":null,"ID":null,"ID2":null,"CompName":null,"CompCourseName":null,"CompNumberDivs":null,"CompQualifierYN":null,"CompNumber":null},{"title":"Test","start":"2011
...and so forth spanning several pages until conclusion.
ompetitions.aspx?compID=1088909","ID":40,"ID2":1088909,"CompName":"March Medal","CompCourseName":"Red Tee's","CompNumberDivs":1,"CompQualifierYN":"Y","CompNumber":40}]