Update:RequirementsV32: Difference between revisions
| Line 181: | Line 181: | ||
</table> | </table> | ||
Revision as of 17:48, 19 September 2007
The goal of AMO Version 3.2 is to radically simplify the add-ons experience for end users thru better navigation, recategorization and site design.
AMO site redesign mockups are available here and here.
| ID | Priority | Requirement | Assignee | Bug/Design links |
|---|---|---|---|---|
| DES-1 | P1 | Implement Add-Ons details page | bug 396736 | |
|
||||
| DES-2 | P1 | Implement categories page | bug 396737 | |
| DES-3 | P1 | Implement front page | bug 396738 | |
| DES-4 | P1 | Implement search results page (SRP) | bug 396739 | |
Category Revision
The goal of the category revision is to help eliminate the confusion associated with the various "Add-On" types. These types may remain but will not be a primary distinguisher of an add-on. The type may continue to be indicated (e.g. on SRPs) but the functionality offering should be the bigger emphasis.
| ID | Priority | Requirement | Assignee | Bug/Design links |
|---|---|---|---|---|
| CAT-1 | P1 | Implement new categories list | bug 396741 | |
|
||||
| CAT-2 | P1 | Reclassify all existing add-ons into new categories | bug 396742 | |
|
Here is the general mapping: There will be some "manual work" that will need to happen to classify items in the "Miscellaneous" and "Site-Specific" categories. |
||||
Search Changes
| ID | Priority | Requirement | Assignee | Bug/Design links |
|---|---|---|---|---|
| SRCH-1 | P1 | Visually indicate experimental add-ons in Search Results | ||
| SRCH-2 | P1 | Include title, category and description as valid search terms. SRP can include individual addons (all types) as well as category names or content from the addon description (not just the addon summary). | ||
| SRCH-3 | P1 | Manually review top 50 searches and see if expected results are shown, otherwise, tweak to include more targeted results. |
Image viewer
Replace the existing thumbnail viewer with a lightbox style viewer.
Experimental Login Flow Page
If an add-on is experimental, we want people to know about it but also to be wary of doing such installations. A new flow of installing a sandbox'ed extension will be defined.
Application segregation
| ID | Priority | Requirement | Assignee | Bug/Design links |
|---|---|---|---|---|
| APP-1 | P1 | Create staging and production instances of AMO v3.1 for Thunderbird, SeaMonkey and Sunbird | ||
|
||||
| APP-2 | P1 | Remove the "Application Selector" from the current AMO site such that addons.mozilla.org is Firefox only. (We may keep this in the interim). | ||
| APP-3 | P1 | Preserve (as much as possible) the old URL scheme for accessing addons content since people link directly to AMO detail pages | ||