Yes great point here Chris (sorry just catching up to some older posts I wanted to weigh in on…).
I think you and @rothnic , if I’m not mistaken, have been advocating for more unification of functionality around all of the “items” we have in Fibery. If so, this is a big ask of mine. I think all off this list:
- Views
- Apps
- Types
- Whiteboards
- Comments (this is one seldom discussed, but of increased relevance to my team)
Had essentially most of the functionality in Entities. So you could:
- reference one with another (via comments if they won’t all have Rich Text available)
- Assign any of them.
- Have use of a Date Extension where it would make sense
As for Docs, I have come to think that Docs could really just be another Type. I can’t see any particular benefit using an actual Doc over an individual Entity, other than aesthetically losing the border around the Rich Text box. But the existence of Docs as yet another item in Fibery - which is currently unevolved since you can’t reference them, comment in them, etc. - complicates my use. My sentiment here is partially influenced by Notion and how Docs and Entities are basically interchangeable, which I think works great in Notion. You simply choose do you have a “page” - a “doc” in Fibery - by simply clicking “return” when you create one, or if you have an Fibery equivalent “entity” - if you decide to add a new Page to an existing db. Notion falls down badly in the areas of Views, relations, Hierarchy view, etc. but in the case of Doc. vs. Entity I think it shows how interchangeable those can be, and Fibery is perfectly equipped to handle this because you can create such a powerful doc with an Entity. Try doing that in Wrike or ClickUp!
And I want to add that I really hope Comments become first-class citizens and get into this discussion, too. I have had several instances when I wanted to quote a comment around Fibery as liberally as I can now quote/reference an Entity. There are unanswered Comments that need to be referenced in various types of Entities to make sure they are documented - this is just one use case.
Clubhouse.io does a great job here - each Comment has its own ID, and this is a real help in referencing them across that app.
Thanks guys!