Christoffer
(Christoffer Furnes)
1
This has been bugging me for years: why can’t there be conditional visibility for CMS collection fields? Right now, we have to permanently show custom fields for every possible option in a CMS collection, even if they’re not always used.
For example, if a collection template page needs a dynamic info box, the CMS collection has to display all the fields for this info box all the time.
If I can add conditional visibility to a toggle switch to show the info box on the template page, why not also let the toggle hide or show the corresponding CMS fields for this info box? Show the fields when you need them!
1 Like
alexdixon
(Alex Dixon)
2
Agreed, this would be a solid upgrade to collection item screens (Conditional Field Groups).
Additionally, just being able to visually group fields would also be handy, rather than relying solely on naming conventions: CMS Settings: Group fields Into sections and add | Webflow Wishlist
If a section was switched off but contained required fields, it could also ignore them.
To be honest, the CMS collection screens are long overdue a UX and functional upgrade.
2 Likes
Totally,having conditional logic inside the CMS editor would save a ton of clutter. Right now the only workaround is grouping fields carefully with naming or tabs, but native conditional field groups would streamline content entry big time.
1 Like
Christoffer
(Christoffer Furnes)
4
I just continue to dump more “this has been bugging me for years” stuff:
The ‘Compress assets’ feature is great, but in collections it’s only possible to compress all assets in all collections at once. If we could compress assets at the collection list and collection field level too, it would be much more useful!
alexdixon
(Alex Dixon)
5
