devvmh / hackthesymphony Goto Github PK

Add something like this:

meta name="MobileOptimized" content="width"
meta name="HandheldFriendly" content="true"
meta name="viewport" content="width=device-width"
meta http-equiv="cleartype" content="on"

Research what it all means

Consider adding a way of tracking whether the user:

• Liked or disliked their recommendations
• Clicked on the ticket/website link
• Purchased a ticket
• Liked the show

Make a database entry table for inputting concert answer scores--this has to be really easy for KW Symphony to keep up/manage.

Make sure the back button works all the time.

Write CSS that displays comments and pro-tips in an engaging/impactful/pretty way.

Consider offering a way for the user to give the feedback that the recommendations they received weren't good for them. Also, this would be good for us/KW Symphony to know so that bad recommendations would be flagged and fixed.

Minimum fix: offering something light at the bottom of the recommendations page like "Do none of these look great to you? Click here to go back and the quiz again--and this time, be honest!"

Make sure there are points assigned to all answers/shows.

Add features:

• Preview this music (YouTube or other link or embedded?)
• Ability to see more information without leaving the web app
• Link to that show page on KW Symphony website
• Better description in general (may be restricted on this)

Also decide which features make the most sense/impact for the user.

• Add/refine questions/answers
• Test this a lot

Question 5 (about Beethoven/dogs) has a second answer that's too long for the red box it's supposed to fit in. This is a CSS issue.

=D

Write instructions for setting up/editing:

• new shows (including useful descriptions)
• concert answer scores
• questions and answers (including question logic)

Things like:

• Vertically centre the button text
• Follow any brand guidelines we're given by KW Symphony

We need different fields for comments and pro-tips so they can be displayed differently and more impact fully through CSS. It's likely to be more sustainable for the symphony to just treat these as different things rather than assign classes to them.

the /scores table requires a login but redirects incorrectly. I think we should just redirect to /admin/login wherever possible

Input shows including descriptions into database. Make sure we have all the shows for the 2015/16 season in the brochure. [This is just the content, not the answer/score system.]