I think this is a great example @Chr1sG of the larger concepts around overall structure of the data in Fibery - and any Work Management app for that matter.
As I move along with Fibery, which I think is the best solution to interacting work entities than anything else out there, I think about my experience up till now - way too much time spent in other apps, for better or worse, but I got well-acquainted with quite a few. The experience with Fibery has had me thinking for a while about the best solution to “grouping” data vs. “relating.” As I have been thinking this through, we got a great article by @antoniokov explaining this very concept elegantly:
Anton is talking about the approach of all the apps out there, and I think with this point Chris you are hitting on the issue of the “groups” of entities and their value in the overall scheme of things.
Right now we have a huge step in the right directly because in Fibery we can already relate to Views, Docs, basically everything except Apps and Types if I’m not mistaken.
****As a side, I’d love to see a small widget on Views/Whiteboards/Docs listing references, perhaps an upcoming feature?
I agree it would be very useful to be able to reference those “entities” - which I think they are in a sense - across Fibery. I’ve found this need as well. And thank you for the reference to my question about location of an Entity within its Type or App for reference. This is right along the need for some kind of “home base” dashboard, etc. that you describe. Being able to mention these “areas” for lack of a better term for now I think is key. And if we gave them some metadata, they could start to resemble “folders” or “groups” at a higher level of hierarchy, and I think that would be very useful, too.
As a closing point, I noticed that Coda, among all other apps out there, let’s you reference just about anything - sections, Table Views, etc. Granted, there is no bi-directional or anything else useful around that feature, but it is an example of this. Unlike Notion, where everything is a page, Coda is letting you reference every “thing” inside Coda, and there are many different entities - Pages, sections, rows, Tables, Table views, etc.
Hope that made sense and Cheers!