Currently a lot of messages in en.json have hardcoded dates (opening & closing of application) and URLs (for 2014's website etc.). This should be made more flexible and easy to change.
Description
Description
Event Timeline
Comment Actions
It might be worth while to pass the opening and closing dates from the database config into the messages that use them, but would classify it as low priority. I think the other dates and urls are fine to deal with annually when the committee comes up with their new survey and content.