Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix UX nitpicks on Collections page #97

Merged
merged 10 commits into from
Feb 27, 2020

Conversation

newswangerd
Copy link
Member

Screen Shot 2020-02-05 at 16 44 52-fullpage
Screen Shot 2020-02-05 at 16 44 39-fullpage
Screen Shot 2020-02-05 at 16 44 34-fullpage

@romanblanco
Copy link
Contributor

@newswangerd to be consistent with b68a370, could we adjust the empty state for search on Partners and Namespaces page as well?

The changes in b68a370 look good!

Screenshot_2020-02-07 Ansible Automation Hub(1)

Screenshot_2020-02-07 Ansible Automation Hub

@romanblanco
Copy link
Contributor

Maybe to consider: at the empty state, we could give the user a hint on what would be the next action (see ManageIQ/manageiq-ui-classic#5434 (comment)).

@sbuenafe-rh could know, if that is something we want to do.

@sbuenafe-rh
Copy link

@newswangerd Collections pages look good. I would want to make sure that there's 24px between the card/list view buttons and the compact pagination component.

Also, for the filter input field, are we filtering by the name of the collection? If so, I would change the placeholder text to be "Filter by collection".

@sbuenafe-rh
Copy link

@romanblanco the Partners page, no results found/matched, the message should be the same as the no collections found. See mock for reference: https://marvelapp.com/project/4271938/screen/65612952

@sbuenafe-rh
Copy link

@romanblanco also, for the My namespaces empty page (Day 1 user), the toolbar should be removed and the action button to create a namespace should be in the empty state message. See mock for reference: https://marvelapp.com/project/4271938/screen/65785967

@sbuenafe-rh
Copy link

For a PF Empty state component reference, the pages that we've talked about to should be using the Empty State - Large. See PF documentation: https://www.patternfly.org/v4/documentation/core/components/emptystate#large

@newswangerd
Copy link
Member Author

@sbuenafe-rh

Also, for the filter input field, are we filtering by the name of the collection? If so, I would change the placeholder text to be "Filter by collection".

I checked. It performs a search, not a filter.

@sbuenafe-rh
Copy link

sbuenafe-rh commented Feb 7, 2020

@newswangerd

Also, for the filter input field, are we filtering by the name of the collection? If so, I would change the placeholder text to be "Filter by collection".

I checked. It performs a search, not a filter.

Ok knowing this, the no matches found message will probably need to be tweaked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants