MozFest 2015 site: Build site

[edrushka]

This ticket is for Scott's build

Additional tickets:
Meta-ticket in plan
UI tickets
QA ticket

[edrushka]

Here are the SVG assets from Adil: https://www.dropbox.com/sh/woqt8g4oaq72ad0/AAAEYtaZbh2ocSTunjEtpTZua?dl=0

[ScottDowne]

It's getting close. https://mozfest-2015-staging.herokuapp.com/

I'm adding in a list of things I still need to do, mostly for my own organization. Seems like a lot, but most of it is p2/not a blocker.

P1 and a blocker to shipping.

• Proposal form needs error handling and validation.
• Proposal form needs success happenings.
• Insert Mark Surman signature and photo.
• here's the signature: http://cl.ly/bGBT
• here's the photo: https://www.dropbox.com/sh/njzalxillwaus0q/AAAsg_dukij8UuWQpCtBSTRTa?dl=0
• Plug in real sched paid account and remove my free test account.
• Sarah made you an admin on her account. Pls confirm
• Live site and better staging site with Travis integration. -jbuck

P2 but cannot ship it as is, so a blocker. So either needs to be finished or links need to be hidden.

• Home page play button needs to open a video.
• here's the link: https://www.youtube.com/watch?v=dYoiHhsdHCk
• Volunteer page. P2
• BSD page is here: https://sendto.mozilla.org/page/s/mozfest-2015-volunteer
  -We can either link directly to it (MVP), or create a nicer user experience by applying Adil's Submit a Proposal UI (nice-to-have).
• About page. P2
• Contact us page email links. P2.
• use this email for all festival contacts: festival@mozilla.org

P2 and not a blocker.

• Tickets page could have fancier use of ti.to with custom buttons.
• Fringe events page.
• Where to stay bit at end of what to expect page.
• Hover states. -ricardo
• Mobile support. Needs to be done before event.

[ScottDowne]

Something that occurred to me, we need some sort of success message when a proposal is successfully submitted. Maybe a button for "submit another proposal"? Do we encourage people submit multiple proposals?

Also need an error message when a required field is missing. There would be an error message for each field. Examples: "session name is a required field" or "you must agree to our privacy policy"

These would appear under each field in red.

[edrushka]

@Saallen are we encouraging multiple proposal submissions? What should the success message say?

@ScottDowne let me know if you need a hand with copy for the 'required field is missing' messages. What you've given as examples is fine, but happy to help if you need it.

[ScottDowne]

@edrushka Yeah, I can use those errors.

I do need copy for two other errors that are a bit more involved. For duplicate session name submissions, example "A session with that name already exists, please change the name and try again"

The other error is a little weirder. It's a generic catch all error. It's really just a fallback, but shouldn't be hitting it. The copy should give them something to do, maybe an email for help? Maybe "Error submitting session proposal, please try again later or email help@mozilla.org" Something like that.

[edrushka]

@ScottDowne for duplicate sessions, what you have suggested is great.

For the catch-all error, how about "Uh oh! There's an unknown error with your session proposal. Please try again later, or email [address] for help." @Saallen what address would you like them to email?

[ScottDowne]

For now, this is what I have as a placeholder session proposal success page: https://mozfest-2015-staging.herokuapp.com/session-add-success

If we want to add a button to propose another, that's easy. Until then though, I felt it was better to leave it out.

[Saallen]

Yes, people can submitt another or many sessions for consideration so giving them a clear pathway to submit again would be appreciated.
There is one address for all festival enquiries which is festival@mozilla.org so all contact paths lead to this address. Eventurally we will need another pathway for press but I will field all enquires until closer to the festiavl.

Before I add the text to be seen post submission- did we confirm whether we could see submitted proposals anywhere? I am guessing that by using the sched.com app this will not be possible??

[ScottDowne]

@Saallen perfect, that answers my questions.

For the sched question. We're hiding the proposed submissions from anyone cept admins to the sched account. I have this working on the staging site.

[cassiemc]

@ScottDowne Here is the final photo of Mark as well as his signature: https://www.dropbox.com/sh/njzalxillwaus0q/AAAsg_dukij8UuWQpCtBSTRTa?dl=0

[Saallen]

Hey, I spoke with Adam on Friday and it has been advised that we do not use BSD for any MozFest 2015 apart from Updates sign up. So we might have to hide the volunteers link on the footer until I build the sign up form on TI.TO- I need to work on this with Spike, our volunteer coodinator and we have a meeting this week. I might have the volunteer form on a separate ti.to account so Spike can have autonomy.I will work as fast as I can here.

[ScottDowne]

Because a lot of p1s are done, I'm cleaning up the above list:

P1 and a blocker to shipping.

• Update schedule for weekend in what to expect page
• Live site and better staging site with Travis integration. -jbuck Mozfest 2015 site needs to live somewhere #39
• Volunteer page no longer links to BSD, needs to be something else. Volunteer page link to ti.to and not BSD #69
• About page. About page is not loading #45
• Session field limits. Test that session proposals properly handle description limits #59
• Proposal tags. Call for Proposals #48
• Speech bubble copy changes Update Mark's speech bubble with latest version #63

P2 and not a blocker.

• Tickets page could have fancier use of ti.to with custom buttons.
• Hover state update when session is poposed. add hover states to site #40

P2 and needs to be done closer to the event.

• Fringe events page.
• Where to stay bit at end of what to expect page.
• Mobile support improved, not great.

[ScottDowne]

@Saallen I filed the volunteer issue as a new issue and assigned you for now: #69

[Saallen]

Thanks @ScottDowne will work on that asap- Wanted to return to the view submitted proposals question from above- So submitted sessions can only be seen by those with admin rights. Those who submit a proposal cannot see their sessions?