866533 - Improve copy of registration page

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: Sign-in, enhancement)

Description

[Janet Swisher]

What feature should be changed? Please provide the URL of the feature if possible.
==================================================================================
On the account registration page (https://developer.mozilla.org/en-US/users/browserid_register), the title is simply   <title>Mozilla Developer Network</title>, and the first heading is <h1>Persona is here!</h1>

These should be updated to reflect the purpose of the page. The language of the page also needs updating.

What problems would this solve?
===============================

The switch to Persona is old news, and is not really what this page is about. 

Who would use this?
===================
Primarily brand new MDN contributors, as part of their first exposure to contributing to the site. The percentage of people with pre-Persona accounts is probably quite small at this point. 

What would users see?
=====================
Something like <title>Create a profile | MDN<title> and <h1>Create an account on MDN</h1>

You can get rid of the info about Persona, since the user has already been through the Persona login process at this point.

In addition, I suggest changing "We couldn't find an MDN profile for your Persona." to "Please create an MDN profile for your Persona." Also add "<em>Do not</em> use your email address as your user name, because it is displayed publicly on the site."

What would users do? What would happen as a result?
===================================================
Users would be less likely to be deterred from completing the registration process by a confusing and outdated page. 

Is there anything else we should know?
======================================
There is a typo in the "Forgot your email?" section: "usname" for "user name". Is there even a path to get to this page anymore if you forgot the email address you used?

Comment 1

[Eric Shepherd [:sheppy]]

Agreed; we switched to Persona a very long time ago and it's time to stop acting as if it's new. :)

Comment 2

[Eric Shepherd [:sheppy]]

I don't think this is an issue anymore. Can anyone confirm?

Comment 3

[Janet Swisher]

Attachment: MDN new account screen

Comment 4

[Janet Swisher]

Still the same. I was waiting to see if the Github integration changes this.

Comment 5

[John Karahalis [:openjck]]

Hi Janet!

As it happens, I went ahead and updated this page about two weeks ago. Did not know about this bug at the time. Would you mind taking a look at the new version of the page and letting us know what you think? Feel free to also suggest any copy changes you think would be beneficial.

Comment 6

[Janet Swisher]

Attachment: Revised new account screen

Comment 7

[Janet Swisher]

I added a screenshot of the new version, in case anybody else wants to see it without creating a new account. 

Suggested page copy:

=Finish setting up your MDN account=

Thanks for signing in to MDN with [Persona]. You have one more step to join MDN and set up your account: '''choose a user name.'''

You can access everything on the MDN website even without an account. However, by joining MDN, you'll be able to edit docs, submit demos, and have your own profile page.

To set up your account, please '''choose a user name''' for MDN. Your user name will be displayed on MDN to identify any contributions (edits, demos, etc.) that you make.

If you're '''having trouble''' signing in or creating an account, '''[let us know].'''

User Name
[       ]
Please enter the name you'd like to display to other users to identify your contributions.
Validation text: User name may contain only letters, numbers, and these characters: '''. - _'''

'''Firefox Apps & Hacks Newsletter'''

Subscribe for periodic news about Firefox OS, Firefox Marketplace and the Open Web apps ecosystem. 

[] Send me the newsletter 

[Create my account]

Comment 8

[Janet Swisher]

This text is a little bit redundant, but sometimes people need to read something more than once in order to understand it. So I think it's just enough redundancy.

Comment 9

[John Karahalis [:openjck]]

Thanks Janet! We always appreciate your attention to copy. This will be in very soon.

Comment 10

[John Karahalis [:openjck]]

Just wanted to share an update.

Our registration logic is being updated to support GitHub. If the required fields and other interface elements do not need to change, we will be able to use the copy that was written here without modification. If the required fields and/or user interface does need to change, we might need to revisit the copy. We are still working this out, but should know soon.

Comment 11

[Janet Swisher]

The one thing that would need to change is:

Thanks for signing in to MDN with [Persona|Github].

Comment 12

[John Karahalis [:openjck]]

Quick follow-up to comment 10.

The registration page user interface is being redesigned after all. Janet, I can let you know when the design is complete so that you have the opportunity to make any updates to the copy.

Comment 13

[Jannis Leidel [:jezdez]]

This may have some overlap with bug #1047448 which tracks copy updates to the "signin" page which is shown whenever a user hits a page that requires authentication while not being signed in.

Comment 14

[John Karahalis [:openjck]]

Scratch comment 12. The signup page input fields have not changed.

Comment 15

[John Karahalis [:openjck]]

Attachment: 1408136122487-developer-local.allizom.org.png

Hi Janet,

The registration page did not change much after adding GitHub authentication. We can use the copy you wrote in comment 7 in most situations.

However, in some cases (probably around 5%) the user will be asked to specify their main email address. Should we use different copy in this circumstance?

A screenshot of this second, more rare interface is attached. (You'll notice that, for the time being, the copy from comment 7 is used.)

Comment 16

[[github robot]]

Commit pushed to github-connect-request at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/afdc4a57abe29c7b0ac1357f49003a902d1c6342
Bug 866533: Make interim registration copy updates

Comment 17

[Janet Swisher]

Email address
[      ]
What email address should we use for MDN-related messages and notifications?


Note that bug 1051000 is debating terminology related to accounts, so whatever's decided there should apply here, too. (Such as changing "MDN account" to "MDN profile")

Comment 18

[John Karahalis [:openjck]]

Wonderful! Thank you, Janet.

I was also wondering what you thought about the "one step" phrase in cases where the user needs to provide both a username and an email address. Should we leave that as-is?

Comment 19

[Janet Swisher]

Oops, missed that. I think slightly different copy is needed for that case.

Use this text in all cases:
You have one more step to join MDN: set up your profile.

Use different text if email is needed:
To set up your profile, please choose a user name [and email address] for MDN.

Change to what I wrote above:
Email address
[      ]
What email address should we use to send you MDN-related messages and notifications? This address will <em>not</em> be displayed on MDN and will be used according to our <a href="link">privacy policy</a>.

Comment 21

[John Karahalis [:openjck]]

Holly suggests the title "Create your profile to continue" in bug 1054560. I'm happy to go with either. We might want to keep the terms consistent, however. (We use the term "account" elsewhere on the page.)

Comment 22

[Stephanie Hobson [:shobson]]

As per Bug #1051000 it is an "MDN Profile" ;)

So "Create your profile to continue".

Comment 23

[Janet Swisher]

What shobson said. Use "profile" in place of "account" wherever it refers to the MDN account.

Comment 24

[John Karahalis [:openjck]]

See also bug 1054559

Comment 25

[[github robot]]

Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/1d2505c571278ab89414cc3e110fef031d0704b4
Fix bug 866533, 1054559: Update registration page

Update the registration page copy (bug 866533). In updating the copy, we
ensure that the copy is visible even when a user signs in with GitHub
(bug 1054559).

https://github.com/mozilla/kuma/commit/5b6221e193fd815fd07153276320c24f6d749c7d
bug 866533 - tests for sign-in and sign-up pages

https://github.com/mozilla/kuma/commit/b37482cf01a31e8c5de13b2fb190babf9f93f231
bug 866533 - remove unused attribute values from signup form

https://github.com/mozilla/kuma/commit/9aa0997274661aa8523330a8a4a0938d21d60944
Merge pull request #2698 from groovecoder/registration-copy-866533

Fix bug 866533, 1054559: Update registration page