981702 - Improve language & capitalization in Add an Event form

Status: RESOLVED FIXED

(Webmaker Graveyard :: Events, defect)

Description

[Cassie McDaniel [:cassiemc]]

Am looking at: https://events.webmaker.org/#/add

* Have noticed some inconsistencies in capitalization for the field labels. Let's do it so that the first word is capitalized and subsequent words are not – so "Event link" instead of "Event Link" and "How long?" instead of "How Long?" etc.

* Instead of "basics" let's call it: "Tell us about your event" (a little friendlier)

* Don't think we need the "about you" header. The only thing there currently is the admin email, so this feels like overkill.

* The field hint under "Event location" is currently "Enter a location" which is redundant. Let's help them here, esp. since venue and address are currently in one field. Instead let's make the hint, "Enter a venue and/or address"

* "administrator" feels a bit stiff. Suggest calling it "Event organizer" instead

* Text below the email field is currently "You must log in with this email to edit this event." Sounds a bit severe, so I suggest changing it to "You'll need to log in with this email to make changes to this event."

* Instead of having "Log in with a different email" as a button next to the email field (it is currently styled so it looks like an input field), let's append it to the text underneath the email field. So that text should read "You'll need to log in with this email to make changes to this event. [link: Log in with a different email]

If anyone has better ideas for any of these changes, I'm open!

cc'ing Erikad for copy insights, if we can improve these suggestions at all. :)

Comment 1

[Gavin Suntop [:gvn]]

Attachment: redpens

320: https://redpen.io/m5k9z2
960: https://redpen.io/z7ktj2

Comment 2

[Cassie McDaniel [:cassiemc]]

Left some comments on redpen re. spacing and the 'log in' button.

Everything else looks good.

Comment 3

[Erika Drushka]

I made some copy suggestions on https://redpen.io/m5k9z2

Comment 4

[Gavin Suntop [:gvn]]

Attachment: https://github.com/mozilla/webmaker-events-2/pull/33

Comment 5

[Gavin Suntop [:gvn]]

Kate, attachments are borked, so can you just give me a manual R?

https://github.com/mozilla/webmaker-events-2/pull/33

Comment 6

[Gavin Suntop [:gvn]]

Ok, looks like the R? finally posted.

Comment 7

[inactivate account for kate]

Comment on attachment 8389310 [details] [review]
https://github.com/mozilla/webmaker-events-2/pull/33

Code looks good, there is still too much space between the subheadings and form elements though

I would suggest about this much:

https://www.dropbox.com/s/jph584l4ophk5jo/Screenshot%202014-03-11%2015.45.20.png

Comment 8

[inactivate account for kate]

Comment on attachment 8389310 [details] [review]
https://github.com/mozilla/webmaker-events-2/pull/33

Oops sorry I was looking at the wrong patch

Removing the subheadings makes this way less readable, why are we doing this?

Comment 9

[Cassie McDaniel [:cassiemc]]

(In reply to Kate Hudson (:k88hudson) from comment #8)
> Removing the subheadings makes this way less readable, why are we doing this?

Erikad brought it up in her copy review and I agreed that they were a bit superfluous. If you feel strongly they should be there though, I'm okay to leave them in.

Comment 10

[inactivate account for kate]

Also, I noticed the misalignment in the first section makes the fields harder to scan now

https://www.dropbox.com/s/ridobsky5ua0rcz/Screenshot%202014-03-11%2015.49.25.png

Perhaps we could put the 'how many attendees' first and the help text after the link input?

Comment 11

[inactivate account for kate]

I could find some form usability studies to back this up, splitting up long forms into sections is a helps users feel less overwhelmed and more likely to fill it out

Comment 12

[Cassie McDaniel [:cassiemc]]

No need to find usability studies :) It's true – but this isn't a very long form. Still, I'm okay to put them back in.

Agreed with the other solution of putting attendees dropdown on the top.