Seasons Spice

**What does your Instant Answer do?**
 The Instant Answers gives time and date of solstices and equinoxes.

**What problem does your Instant Answer solve (Why is it better than organic links)?**
Answers to questions this instant answer provides are usually definitive and relatively simple to answer. It saves the user from having to hunt through the organic list of links to find their answer.

**What is the data source for your Instant Answer? (Provide a link if possible)**
http://www.timeanddate.com/calendar/seasons.html

**Why did you choose this data source?**
Timeanddate.com provides a nice API and DDG already has other Instant Answers that use the API.

**Are there any other alternative (better) data sources?**
underground.com, weather.com, almanac.com (and others) all provide this data, but I have not found anyone who exposes this data through an API.

**What are some example queries that trigger this Instant Answer?**
first day of spring
summer solstice
start of fall in 2015

**Which communities will this Instant Answer be especially useful for? (gamers, book lovers, etc)**
trivia, photographers, weather observers, religious

**Is this Instant Answer connected to a DuckDuckHack [Instant Answer idea](https://duck.co/ideas)?**
https://duck.co/ideas/idea/4682/when-does-season-start

**Which existing Instant Answers will this one supersede/overlap with?**
None that I'm aware of

**Are you having any problems? Do you need our help with anything?**
No

**What are the terms of use for the API? Will DuckDuckGo need specific authorization (e.g. an API key)? Are there any costs associated with API usage?**
There is a cost for the API usage, but DDG is already partnering with the data provider.

**Where did you hear about DuckDuckHack? (For first time contributors)**
DDG's blog and website.

**What does the Instant Answer look like? (Provide a screenshot for new or updated Instant Answers)**
![screenshot](https://cloud.githubusercontent.com/assets/2772/5352752/ba379a88-7f21-11e4-9444-c7e24819bc17.png)


## Checklist
Please place an 'X' where appropriate.

```
[X] Added metadata and attribution information
[X] Wrote test file and added to t/ directory
[X] Verified that instant answer adheres to design guidelines (https://duck.co/duckduckhack/design_styleguide)
[X] Verified that instant answer adheres to code styleguide (https://duck.co/duckduckhack/code_styleguide)
[X] Tested cross-browser compatibility

    Please let us know which browsers/devices you've tested on:
    - Windows 8
        [] Google Chrome
        [] Firefox
        [] Opera
        [X] IE 10

    - Windows 7
        [] Google Chrome
        [] Firefox
        [] Opera
        [] IE 8
        [] IE 9
        [X] IE 10

    - Windows XP
        [X] IE 7
        [X] IE 8

    - Mac OSX
        [X] Google Chrome
        [] Firefox
        [] Opera
        [X] Safari

    - iOS (iPhone)
        [X] Safari Mobile
        [] Google Chrome
        [] Opera

    - iOS (iPad)
        [X] Safari Mobile
        [] Google Chrome
        [] Opera

    - Android
        [] Firefox
        [] Native Browser
        [] Google Chrome
        [] Opera
```
Wow, I had no idea we were doing that. Regardless, I would prefer we play it safe and use jQuery. That approach aligns better with our [Code Styleguide](https://duck.co/duckduckhack/code_styleguide#javascript) and I feel that it also helps to spread good practices in general. I'd rather not mix in potentially unsafe/unsupported JS because it might influence other devs to do the same.

Does that sound reasonable?