Package Registry: Design an updated package detail view to follow Pajamas guidelines and utilize a single column layout
Problem to solve
Users visit the Package Registry UI in order to find a specific package and view the details of that package. The user interface related to the details of the package registry can be difficult to digest and contains duplicative information which increases the mental load required to understand the package itself.
Current Detail UI |
---|
![]() |
Intended users
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
- Rachel (Release Manager)
User experience goal
Improve the readability of the Package Detail view and ensure that the page conforms to the Pajamas Guidelines
Proposal
Design in progress.
Current iteration |
---|
![]() |
Further details
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
Edited by Iain Camacho