Create a responsive calendar page that has a material design look.

[BenJetson]

A few links for personal reference:

• http://fullcalendar.io/docs/
• https://github.com/fullcalendar/fullcalendar/blob/master/src/gcal/gcal.js
• https://github.com/jackyliang/Material-Design-For-Full-Calendar

[BenJetson]

As much as I don't like it, the club Google Calendar is being ditched. Just to get a simple JSON feed of calendar events from Google Calendar, we'd have to set up API hooks and keys. While that is simple enough, these will break every time the website maintainer for the club graduates from the school since the district erases your Google Apps account and associated content after graduation.

Instead of creating something that will cyclically break, I'm implementing our own JSON calendar database in the repository. This will never break as the repository will stay up indefinitely and the ownership can be transferred easily. To keep the database relatively small, I'm creating one JSON file per calendar year (2016.json includes 2016 events, etc.). Then, a master JSON file in the _data directory will tell FullCalendar which years to import. Documentation for event creation is available in the FullCalendar docs.

On a completely unrelated note: this also brought to mind the need for the site wiki documentation so that whoever I pass the torch to when I graduate can sift through my codebase with some guidance. :stuck_out_tongue_closed_eyes:

[brenapp]

Can't you just use a personal account, which will not be erased when you graduate?

[BenJetson]

Yes, I'd thought of that.

However, I'm strongly leaning this way -- one less thing I have to transfer out later. I've already got so much other stuff to pass on (not just for robotics, either) when I graduate that I really don't want to add more to it. It also keeps the data for the site just within this repo itself. :P

Plus, I've kinda already got an outline going for the database on my local clone... :D

[brenapp]

I don't care, do what you want