Update:RequirementsV32: Difference between revisions
Line 84: | Line 84: | ||
</table> | </table> | ||
* I'm hoping that we can leave our "Other" but include it for now. | * I'm hoping that we can leave our "Other" but include it for now for migration purposes. It's the default category for add-ons whose categories have been eliminated. | ||
</td> | </td> | ||
</tr> | </tr> | ||
Line 130: | Line 130: | ||
** We'd like to introduce the new multi-tier PFS system and integrate into AMO in a nicer way | ** We'd like to introduce the new multi-tier PFS system and integrate into AMO in a nicer way | ||
** Desire to keep the categories list simple | ** Desire to keep the categories list simple | ||
* | * The default new location for add-ons not specifically remaped will be "Other". This will be the holding bin. Then, there will be some "manual reclassification" that will need to happen to move the various items there into new categories. | ||
</td> | </td> |
Revision as of 23:45, 5 October 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
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 | |||||||||||||||||||||||||||||||||||||||||
|
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. Implement Image Viewer (IMG-1) bug 396743
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 | |||
|
||||
APP-2 | P1 | Remove the existing "Application Selector" from the current AMO site and demote it to a small link at the bottom of the page. Include application names as a special search result. | ||
APP-3 | P1 | Preserve (as much as possible) the old URL scheme for accessing addons content since people link directly to AMO detail pages |