Confirmed users
1,424
edits
Support/Kitsune/Thunderbird-integration: Difference between revisions
Support/Kitsune/Thunderbird-integration (view source)
Revision as of 09:12, 19 April 2012
, 19 April 2012→Feature overview
| Line 17: | Line 17: | ||
The UX research work did already lay down the foundation for the parts that are browsable in the KB. Once the product based navigation lands we would be able to support more products in our KB. | The UX research work did already lay down the foundation for the parts that are browsable in the KB. Once the product based navigation lands we would be able to support more products in our KB. | ||
An area that needs to accommodate more products still is the search results page. Faceted search would allow users to drill down on a certain product while still allowing us to use one unified source for results. | An area that needs to accommodate more products still is the search results page. Faceted search would allow users to drill down on a certain product while still allowing us to use one unified source for results. | ||
The non-user facing part of | The non-user facing part of supporting more than one product is mainly focused on the various dashboards that tell our contributors what they should be doing next and that tell us how we are doing in general. | ||
In addition the user to user support | In addition the user to user support would need to be extended to hold more than one product without being confusing to users or contributors (including the way people ask questions) | ||
While the above covers the improvements on the SUMO side we'd also need to lay down the rules for migrating articles and media (and possibly user accounts) to SUMO. From our last experience of migration we know that this is a particularly messy subject that needs careful planning. | |||
===Users & use cases=== | ===Users & use cases=== | ||