984385 - Streamline sign-up page for new contributors

Status: RESOLVED FIXED

(support.mozilla.org :: Knowledge Base Software, task, P2)

Description

[Kadir Topal [:atopal]]

The sign-up page for contributors should be similar to the general sign-in page.

In particular: 
* Reduce visibility of sign-in like in the AAQ flow
* Add path to AAQ

Comment 1

[Ricky Rosario [:rrosario, :r1cky]]

1pt for HTML + CSS changes

Comment 2

[Ricky Rosario [:rrosario, :r1cky]]

Pull request:
https://github.com/mozilla/kitsune/pull/1883

Landed on master:
https://github.com/mozilla/kitsune/commit/b4b79b8aa89d0dc3c50cc6dee8a9ceb8cd758cd5

This is on stage now. Holding off to deploy to prod until Monday.

Comment 3

[Bram Pitoyo [:bram]]

Attachment: sumo - contributor registration page - 01

Just a food for thought (feel free to discard this suggestion if our time is limited). Is it worth it to make the contributor registration page similar to the sign in page, with 6-grid wide form div, and “Ask a question” link to the right of the form? Or is this design distracting?

I particularly like the link the says “You don’t need an account to [ask a question], because the call to action there is very clear.

So my suggestion is to maybe use the layout similar to the one attached here, but modify the AAQ block wording so it says something that incorporates the call to action above.

It could be something like:

“Our support forums are a great place to get help. Asking a question is easy, and most questions are answered within [x] hours.

[Ask a question]”

What do you think? Is saying the number of hours something realistic that we can do, given how awesome our forum contributors are at answering questions in a timely manner?

And What do you think about changing more AAQ call to actions to mention the number of hours? (I’m aware that this discussion is beyond the scope of this bug).

Comment 4

[Ricky Rosario [:rrosario, :r1cky]]

Deployed to prod now.

Comment 5

[Ricky Rosario [:rrosario, :r1cky]]

Comment 3 came after this had landed already. Do we want to do any of that in a followup bug?