Simplify the packages list by consolidating versions of the package into the detail page
Background
This issue relates to the UX scorecard recommendations issue
Problem
It's difficult to search for a specific package when there are many entries on the package table to parse. Displaying a line in the table for each version of the package adds unnecessary noise to this screen:
Proposal - see designs attached to issue
Logic
- The most recent package version (by date) will be shown on the package list page
- if a package has more than 1 version, the number of versions are listed on the package list page
Image | Explanation |
---|---|
If a package has multiple versions, show that after the most recent version on the package registry list page. | |
If a package has only 1 version, show only the version number. |
Notable changes from current implementation
Current implementation | Proposal | Reason |
---|---|---|
Show only the author on the Right. Note that there is also a change to link the project. This can happen outside of this issue and is related to #349010 (closed) |
||
The most important information on the Other versions tab is the version |
Future iterations
- we improve it by showing latest release based on
latest
tag (a convention we decide to adopt). If there are no packages with thelatest
tag we fallback to time-based (iteration 1) - Then again we could improve this even further letting users decide what tags to look for when showing the latest package version and again, if no package version is found we fallback to time-based (iteration 1). By default we would use our convention, the
latest
tag
Edited by Katie Macoy