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

Rethink CP nav customisation to improve UX and reduce confusion. #1170

Open
robdekort opened this issue May 29, 2024 · 4 comments
Open

Rethink CP nav customisation to improve UX and reduce confusion. #1170

robdekort opened this issue May 29, 2024 · 4 comments

Comments

@robdekort
Copy link

robdekort commented May 29, 2024

When you group items using the CP nav feature you can't set icons, which is an open issue (#9667). However something else that's a bit confusing is that collections and taxonomies you move out of a certain main nav item remain in the overview table.

In this case I made a group that contains two taxonomies and one collection:
Screenshot 2024-05-29 at 11 11 40

But in the collection and taxonomy overview tables you still see them listed, when they're removed from the sidebar:
Screenshot 2024-05-29 at 11 12 33
Screenshot 2024-05-29 at 11 12 39

This is a bit inconsistent and possibly confusing. It might be better for them to be removed from the overview table as well.

@duncanmcclean
Copy link
Member

I think I see where you're coming from but moving collections in the nav is just a visual thing. I would personally still expect the collections index page to list all the collections, nevermind if they've been moved/hidden via the CP nav customizer.

@robdekort
Copy link
Author

robdekort commented May 29, 2024

It's def. up for debate. But when it does "just" this, the feature doesn't make much sense to me as it mostly adds confusion imho. Even when you regard it as just a visual thing, why would the content on the left differ from the content on the right?

@robdekort
Copy link
Author

robdekort commented May 29, 2024

Then again, when you would change this, how would you enter collection configuration? That probably isn't possible with the current solution. Perhaps I would expect a main level group always to generate an overview table. So if you would click on Pricing here:
Screenshot 2024-05-29 at 11 11 40

You would see an overview table containing Tiers, Features and Groups to further decrease inconsistency. Anyways, I guess this should go to the ideas repo. :-)

@duncanmcclean
Copy link
Member

Yeah, let's move this into the ideas repository.

It's not really a bug but more a UX thing that might be slightly confusing for some.

@duncanmcclean duncanmcclean transferred this issue from statamic/cms May 29, 2024
@robdekort robdekort changed the title CP nav customisation inconsistency Rethink CP nav customisation to improve UX and reduce confusion. May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants