Hi Paul,
I think what you are describing sounds more similar to field grouping than tagging. These are open ideas about it:
Declutter the entity display by grouping fields in collapsible field groups.
Currently the fields, especially many to many relation fields which cannot be hidden, are taking up a lot of space and is a big UX tension.
In general, I see that users (including myself) work mostly with title and richt text content of entities.
Although Fibery apears more structure oriented, day to day work with Fibery requires a lot of clicks and the fields are a big distraction. Drupal solved this also with the f…
When working with larger databases, tables can quickly grow to many dozens of fields, which makes navigation across columns harder.
Currently it is possible to hide columns individually, but in practice many fields belong to logical groups (for example planning fields, metrics, metadata, etc.).
Suggestion:
Allow creating column groups inside table views.
For example:
Planning
• Start Date
• End Date
• Owner
Metrics
• Budget
• Revenue
• Conversion Rate
Metadata
• Created By
• Creat…
Having a lot of fields visible and then managing work around them can feel overwhelming. To ease this it would be very handy to organize sets of fields into named areas/sections. Certainly, I’d like to be able to name and re-arrange those sections as well.
In general, I think Labels/Tags are solvable today with Single or Multi selects. Or to-one or to-many relationships. But I might be mistaken, as I don’t know the date of Fibery well enough when this post was created to know what was changed since.