Package Detail UI - Update the package detail main body to include a history, install commands, and additional metadata.
Problem to solve
The GitLab Package Registry helps users by storing and sharing a variety of different package formats. Currently, the package detail UI is cluttered. This leaves the feature set feeling disconnected from the rest of the GitLab product UI and can be difficult to discern.
Current UI |
---|
Intended users
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
- Sam (Security Analyst)
- Rachel (Release Manager)
- Alex (Security Operations Engineer)
- Simone (Software Engineer in Test)
User experience goal
Users can easily view and understand the details related to a specific version of a package.
Proposal
Update the main section of the package detail UI. The changes include:
- Include a new "History" feed that shares the time-based metadata related to a package.
- Next show the Install commands and registry setup instructions
- Add an "Additional Metadata" to capture any non-time related metadata. This additional metadata section offers the flexibility of including a variety of details specific to different package formats.
Updated UI |
---|
Further details
The history section specifically includes the following data points:
- Package creation
- Package update (if applicable)
- Commit and Branch time and related data
- Pipeline time and data
- Published to the registry data
The additional metadata section will require each new type of data points to be looked at to form the correct "sentence" since this is no longer a key|value pair.
Permissions and Security
n/a
Documentation
Updates to the screenshots inside the documentation may be required.
We may also need to update or clarify the documentation when speaking specifically to what different data points are.
Availability & Testing
What does success look like, and how can we measure that?
Users are able to quickly understand the history and data related to an individual package.
What is the type of buyer?
n/a
Is this a cross-stage feature?
No