Support/Goals/2011Q3/Identity Documentation: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
== Summary == | |||
The goal for this quarter is to support the Identity team to have the support materials (i.e. KB articles), customization of SUMO site, in product help content, etc. ready for the public launch of Browser ID in Q4. | |||
BrowserID is the first product launched as part of the Identity initiative. | |||
The SUMO team with the Product team have decided that the support content for users using the feature will be included in our support.m.o site. After reviewing the use-cases we haven't identify any special need that required additonal developments of customization of our SUMO platform. | |||
Together with the Product team we have decide to use SUMO as canonical resource for support content. This means that we will map support from BrowserID product and website to SUMO. This needs to happen as part of the rebranding that will happen in Q4. | |||
== Team == | == Team == | ||
Line 44: | Line 18: | ||
== Goals == | == Goals == | ||
* To support the Identity team in the launch of BrowserID. | |||
* To draft, write and review SUMO articles to cover the "expected" most popular uses cases of Browser ID. | * To draft, write and review SUMO articles to cover the "expected" most popular uses cases of Browser ID. | ||
* Set up an easy access to the content (i.e. link) so the beta users can find the information after the launch. | * Set up an easy access to the content (i.e. link) so the beta users can find the information after the launch. | ||
== What needs to be done? == | |||
Launch: | |||
*Content creation | |||
**What's BrowserID? | |||
*How does BrowserID work? | |||
*Point BrowserID site to SUMO | |||
*Tag Forum questions accordingly | |||
Second Phase: | |||
*Identity Support Home Page | |||
*Refinement of forum tagging (i.e. Sign in to browser, etc) | |||
*Integrate SUMO content in BrowserID site through API: BrowserID will be the initial customer of the upcoming SUMO API (https://wiki.mozilla.org/Support/Kitsune/SUMO_API) | |||
== What's missing for BrowserID launch? == | |||
Activities to be performed after the BrowserID rebranding in Q4 | |||
*Include BrowserID in the AAQ flow | |||
*Refine drafts into an article. | |||
== Dependencies - Blockers == | |||
In order to finish the SUMO documentation/articles the BrowserID team needs to close the UX/UI of the Add-On and the branding. We will continue to work closely with them to be up to date. | |||
== Project Plan == | == Project Plan == | ||
# Initial topic selection by Product and SuMo | # Initial topic selection by Product and SuMo | ||
# Draft of the articles | |||
# Draft of the articles | # Decide with Product how drive user with issues to support. | ||
# Implement support path. (i.e. Do we want to link to these articles from www.browswerid.org?) | |||
# Decide with Product | |||
# Implement support path. (i.e. Do we want to link to these articles from www.browswerid.org? | |||
== Non-Goals == | == Non-Goals == |
Revision as of 12:40, 21 September 2011
Summary
The goal for this quarter is to support the Identity team to have the support materials (i.e. KB articles), customization of SUMO site, in product help content, etc. ready for the public launch of Browser ID in Q4.
BrowserID is the first product launched as part of the Identity initiative.
The SUMO team with the Product team have decided that the support content for users using the feature will be included in our support.m.o site. After reviewing the use-cases we haven't identify any special need that required additonal developments of customization of our SUMO platform.
Together with the Product team we have decide to use SUMO as canonical resource for support content. This means that we will map support from BrowserID product and website to SUMO. This needs to happen as part of the rebranding that will happen in Q4.
Team
Who's working on this?
- Goal Manager: Ibai Garcia
- Lead Developer: Ben Adida
- Product Manager: Dan Mills
Team list should make it clear who to ask about what, and who to ping when they're needed.
Goals
- To support the Identity team in the launch of BrowserID.
- To draft, write and review SUMO articles to cover the "expected" most popular uses cases of Browser ID.
- Set up an easy access to the content (i.e. link) so the beta users can find the information after the launch.
What needs to be done?
Launch:
- Content creation
- What's BrowserID?
- How does BrowserID work?
- Point BrowserID site to SUMO
- Tag Forum questions accordingly
Second Phase:
- Identity Support Home Page
- Refinement of forum tagging (i.e. Sign in to browser, etc)
- Integrate SUMO content in BrowserID site through API: BrowserID will be the initial customer of the upcoming SUMO API (https://wiki.mozilla.org/Support/Kitsune/SUMO_API)
What's missing for BrowserID launch?
Activities to be performed after the BrowserID rebranding in Q4
- Include BrowserID in the AAQ flow
- Refine drafts into an article.
Dependencies - Blockers
In order to finish the SUMO documentation/articles the BrowserID team needs to close the UX/UI of the Add-On and the branding. We will continue to work closely with them to be up to date.
Project Plan
- Initial topic selection by Product and SuMo
- Draft of the articles
- Decide with Product how drive user with issues to support.
- Implement support path. (i.e. Do we want to link to these articles from www.browswerid.org?)
Non-Goals
- The goal for this quarter doesn't involve the full localization of the content.
- This project doesn't aim to cover every possible issue but to have an initial collection of articles before the official launch.
Additional Documentation
- Identity Roadmap
Legend (remove if you like)
Healthy: feature is progressing as expected. | |
Blocked: feature is currently blocked. | |
At Risk: feature is at risk of missing its targeted release. | |
ETA | Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date. |