Package Registry: Adjust the max width for non-fluid screens to be 990
Problem to solve
The package registry list view shows users a list of all the packages contained inside of a registry through a list view.
Currently, the UI width has a max of 1248px. Given the content in the page, a 1248px width is too wide and can hinder users to draw connections on a single line item on either side of the line.
Current width |
---|
Intended users
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
User experience goal
Help users consume the data on the Package Registry list view by shortening the width of the page for users who have not opted for the "fluid layout" mode. This should help users connect data we display on the left and right side of a line item.
Proposal
Set the width of the Package Registry UI to be 990px by default (unless a user has selected the fluid-layout mode).
Package List at 990px wide |
---|
Further details
The reason the width of the Package Registry UI may be a result of the two-column layout in the Package Detail View
Package Detail View |
---|
If this is the case, we should not adjust the width of the Package Registry List view until the Package Detail View can also come down to the 990px goal width.
We currently have a design issue dedicated to putting the package details into a single column: #225337 (closed).
this issue may be blocked until we complete the single column layout change because having the UI width change between the list and detail view could be jarring for users.
@nmezzopera could you confirm this?
Permissions and Security
n/a
Documentation
Its possible screenshots of the UI will need to be updated in the documentation, but that may not be necessary for "just" changing the width.
Availability & Testing
n/a
What does success look like, and how can we measure that?
The package registry list and detail views both render at 990px wide for users who have not selected the "fluid UI" preference.
What is the type of buyer?
n/a
Is this a cross-stage feature?
n/a