Closed Bug 984381 Opened 11 years ago Closed 11 years ago

Make wording of sign-up button task specific

Categories

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

Tracking

(Not tracked)

RESOLVED FIXED
2014Q2

People

(Reporter: atopal, Assigned: rehandalal+mozilla)

References

Details

(Whiteboard: u=contributor c=wiki p=1 s=2014.7)

In bug 984377 we are moving the sign-in button to the task specific subpages. The button to sign-up should be customized to those tasks. The button on the L10n page could read something like: "Help Firefox users in your language - sign up"
1pt for copy and possibly CSS changes.
Whiteboard: u=contributor c=wiki p= s=2014.6 → u=contributor c=wiki p=1 s=2014.6
I'm just making sure I have the subpages right before working on this: L10N Knowledge Base Support Forum Army of Awesome Am I missing anything?
(In reply to Joni Savage from comment #2) > I'm just making sure I have the subpages right before working on this: > > L10N > Knowledge Base > Support Forum > Army of Awesome > > Am I missing anything? That should be it! For reference, see the bottom of https://support.mozilla.org/en-US/get-involved and all the subpages.
Thanks, Ricky! May I have visuals or a little more clarity on what a subpage might look like? Is there a character limit for each button? Also, if the subpage gives enough context for the user, perhaps a simple "Sign Up to Contribute" button would suffice so the messaging isn't redundant. Assuming that the character limit doesn't matter and the sign up button needs to have all the info, here's what I'd put: L10N page - "Sign Up - Translate Help Articles to Your Language" AoA - "Sign Up - Help Users on Twitter" KB - "Sign Up - Improve our Help Articles" Support Forums - "Sign Up - Help Users in the Forums"
(In reply to Joni Savage from comment #4) > May I have visuals or a little more clarity on what a subpage might look > like? The subpages are: https://support.mozilla.org/en-US/get-involved/army-of-awesome https://support.mozilla.org/en-US/get-involved/questions https://support.mozilla.org/en-US/get-involved/kb https://support.mozilla.org/en-US/get-involved/l10n > Assuming that the character limit doesn't matter and the sign up button > needs to have all the info, here's what I'd put: > L10N page - "Sign Up - Translate Help Articles to Your Language" > AoA - "Sign Up - Help Users on Twitter" > KB - "Sign Up - Improve our Help Articles" > Support Forums - "Sign Up - Help Users in the Forums" These seem long to go inside the button. But they could replace the "Sign up as a volunteer" text on the left. Thoughts?
Ricky, yes, that was the idea. Joni, thanks for the copy. The idea is that not everybody will read the whole page before clicking on sign-up. So, the copy right next to it should reduce false positives - people who sign up as contributors, but are not interested in contributing. Madalina, are you okay with these?
Flags: needinfo?(mana)
Joni has provided the text. Un-assigning. Thanks!!
Assignee: jsavage → nobody
Due to Marketplace-related busyness, I haven’t had the time to work on any contributor onboarding flow bug all week. Rest assured that they’ll come early next week. Sorry.
Sounds good to me!
Flags: needinfo?(mana)
Because the button on the right already contains the word “Sign Up”, we don’t need to repeat it again in the heading on the left-side. Otherwise, the wording could be exactly the same as what Joni had suggested: * Translate help articles to your language [Sign me up] * Help users on Twitter [Sign me up] * Improve our help articles [Sign me up] * Help users in the forums [Sign me up] In parallel to this, we will also track the page that each contributor is signing up from. By knowing the source of the registration, we can tailor the onboarding experience uniquely.
This missed the sprint. Moving to next.
Whiteboard: u=contributor c=wiki p=1 s=2014.6 → u=contributor c=wiki p=1 s=2014.7
Q1 is over. Bring it on, Q2!
Target Milestone: 2014Q1 → 2014Q2
Assignee: nobody → rdalal
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.