Hey great point, and I couldn’t help but think of this whole convo:
Where I am suggesting that you can get by in Fibery with your Docs need by just using Entities instead and bypass docs entirely. Wasn’t sure if that came across clearly in that whole discussion, but in reading this, I just had to follow-on re: that point since this is my desire in the end - have Docs function as entities. My team essentially has created a Type called “Doc,” and this allows us to get the benefit of seeing things like references, comments doc-wide, etc. that you can’t do in Docs as they are limited here.
Also, one thing interesting that I wanted to also put into this discussion is right now if you install the Docs extension, you can link to any doc from any entity. Would you say that this, along with the ability to link to Whiteboards in the same way via extension, is basically as close as we have to Polymorphic? By that I mean you can it’s an area where you can link, not reference, to anything? I can see a bunch of uses for this arbitrary-type extension, one I’d really love to see is Dependencies as you’d have some real power in Fibery if you could make any entity dependent on any other. This is a real limitation of the “traditional” work management stuff out there like Asana, Wrike, ClickUp (which you seem well familiar with), and you can’t do stuff like make Projects dependent on each other, or on a task, etc. This is requested of these tools heavily if you look at their communities, but none has it.
Bottom line is I agree 100% you should be able to have what you are using as a “Doc” in Fibery have full Entity capabilities!