54
Add a "folder-like" group function to organize content types
P
Plot Chit
I believe it would greatly improve the user experience if we can add a "folder-like" grouping function to content types (single type and collection type), so that if you have a lot of content types (for example if you have like 50 webpages, you will have like 50 single types), it really makes a lot more sense to have groups. For now users can only mitigate this by using some naming conventions, but I doubt if this is an elegant solution.
Activity Feed
Sort by
Małgo Plichta
Important as h*ll ^^ I can't believe MAY is the first time it has been mentioned, we've been in a great need for such a functionality from the day we started using Strapi.
Yves Benini
100% necessary for UX - We need to be able to create the same structure as for the settings menu
Gregor Sondermeier
I remember in the v3 project I inherited it was hacked with a very ugly admin panel customization. Luckily such ugly hacks are not possible anymore in v4, but grouping content types would be very helpful for us as our Strapi instance drives multiple websites and grouping the content types per website would be great.
I
Ivan Grasso
I agree. This is very much needed!
S
S
This is really needed. It's a real dealbreaker for my clients, for updating to v4.
I have 40+ content types, it would become a mess if migrated to v4.
g
gu-stav
Johanna K, Aida B-F, Plot Chit Do you think grouping content-types would be sufficient for your cases or would you also need custom sort orders?
Would it be possible for you to share specific use-cases with us? I'd be mostly interested in:
- How many content-types do you have?
- How would you group your content-types?
Johanna K
gu-stav:
I have about 50 content-types single and collection types combined and growing monthly. For my use case, I am mostly interested in grouping collection types.
For example:
Blog Articles,
Blog Categories
Press Articles
Press Categories
I would group these under Blog and Press.
Landing Pages Marketing
Landing Pages Customer Service
Landing Pages CRM
I would group all under Landing Pages.
This is probably where it gets the most messy for me:
I have collection types which just acts as a source of truth for content that is frequently updated such as disclaimers, social reviews or app downloads. I later use these collection types for components in dynamic zone so my editors just need to update the app download count in the collection type instead of each and every landing page that is using that component. I would group these by Components.
Aida B-F
gu-stav: I have about 15 collection types in production already and will double that number before end of year. I also have about 10 single types.
My main problem is that the editors working in our Strapi installation are distributed in a large organisation and with very varying degrees of knowledge and experience. It would make it easier and would give a much better user experience if we could group collection types (maybe even single types) based on perhaps department or location. No custom order would be necessary for me.
Aida B-F
Yes, this is very much needed!
I am a developer working in a fairly new project with only a handful of collection and single types and already it is getting a bit messy. Especially for our actual editors.
Johanna K
Yes this is super important!