133
edits
Mozillians/Phonebook: Difference between revisions
→Registration: Added registration flow and help required
(→Features: Added new Registration section) |
(→Registration: Added registration flow and help required) |
||
| Line 6: | Line 6: | ||
== Features == | == Features == | ||
=== Registration === | === Registration === | ||
This registration section is specifically geared to help new contributors get started and up to speed as quickly as possible. | |||
The page that addresses existing contributors have not been designed or decided yet, but it’s a subset of the new contributors flow. It can be an extra explanatory text on the text box, rather than an entirely new page. | |||
==== Help Required ==== | |||
* Most of these pages will require a copywriter/copy editor’s help, not only for interface texts and paragraphs, but also email copy. | |||
* Visual design help would be nice to make high res prototypes that are ready for developers to implement | |||
* Help from analytics would be needed, in order to determine most used group/tag | |||
==== UX Flow ==== | |||
# A new contributor starts on the home page. It will explain what, why, and how new contributors should join Mozillians. What’s the benefit? Who are the Mozillians? What will joining involve, and what will happen? | |||
# The user clicks on “Join”. The registration page appears with a text box asking the user for his email address. Below it, a FAQ answer the user’s concerns. What is BrowserID? What email address should I use? Remember that a lot of people uses their spam email addresses for services like this, so we have to address this first rather than deal with angry users later. | |||
# After entering and submitting the emaill address, the user is led to BrowserID registration. We’re not in control of this process, but hopefully we’ve clarified what it will entail. | |||
# After the registration process finishes, the user is redirected to Mozillians. A page appears with a note thanking the user for registering, and that a general community steward will contact him soon. The user can also select from a list of groups that he can get started with. | |||
** This list will be culled from the most used group/tag from Mozillians, as well as the list of departments inside Mozilla. From this, we’ll get names like “Platform”, “SUMO”, “Identity”, WebDev”, “UX”, “Community Tools”, “Marketing”, etc. | |||
** From this list, we’ll need to identify which departments gets the most use, which one tends to require more contributor helps, etc. | |||
** Finally, we’ll write a human-readable list of top 15–20 groups. A new contributor might not understand “Platform”, “WebDev” or “SUMO”, but he can understand if he wants to help with “Firefox for Desktop and Laptop”, “Websites” or “Mozilla Product Support” | |||
# When the user clicks the checkbox beside the list, the text box below will populate itself with the existing groups/tags that is used in Mozillians. For example, when a user click on “I would like to help with… Websites”, the text box will populate with the tag “WebDev”. And so on. | |||
# After the user clicks to confirm his group selection, a new page appears with information about the groups that the users have selection. This information includes: | |||
** User selections (“Websites”, “Support”, “Translation”) | |||
** Group names (“WebDev”, “SUMO”, “l10n”) | |||
** Group website or wiki | |||
** List of projects (which can be a subset of the website or wiki) | |||
** Code repository (if available) | |||
** IRC Channel | |||
** The steward that will contact the user, along with his IRC name. For example: Aakash Desai [:aakashd] | |||
Below these info boxes are a few things the user can do with this information. For example, he is encouraged to go the the group’s website, check out its projects, and join in the conversation on IRC. | |||
=== Profile === | === Profile === | ||
==== Tagging ==== | ==== Tagging ==== | ||
=== Search === | === Search === | ||
=== Invite === | === Invite === | ||