I spend A LOT OF TIME recreating the the same structure for collection views.
Note that an organization needs a STANDARD way to display ALL VIEWS, to prevent confusion. This is for example.
Fields:
| Database label | Database ID | Created By Icon | Name | Content Status | Importancer | Creation Date |
Filters:
| High Importance (Team) | Recent (Team) | High Importance (Me) | Recent (Me) |
For consistency, this needs to be reflected as much as possible in all content views (even if possible across lists and tables)
Who will need View Templates
- Space designer: Views setup happens more in the setting up phase of a workspace and after an initial period, it should occur less often.
- Anyone who maintains a team environment, e.g. coordinator, manager, tech lead, administrator, private environment user - they will create and adjust views regularly.
Why this matters: Standards
Fibery is undeniably complex at first sight, and even when using space templates, an organinzation will need to adjust the views to reflect the needs of the teams or departments, and to create organizational consistency of how data is displayed.
Closing the gap between space templates and need for either cross-space or smaller standards.
This is what I see is a blind spot in Fibery currently - which I think makes people drop out as customers.
First impression - Wow space templates make it so easy to set up a deparment workflow.
Reality kicks in - Wow I changed the space to our needs but it becomes pretty messy very fast. How to make it look easy again for users? No idea.
Solution: think how the most confusing part of Fibery - views and relations - become simpler by implementing views templates.