I am in the process of setting up Fibery for my company and really, really like the concept of the structure that I can enforce with views & smart folders - which I missed in Clickup.
After reading through some discussions I setup a Document database instead of using Docs natively.
All the arguments that apply for Docs-as-Entities apply for Comments as well.
I would like to setup comments as an entity implementation (maybe through Highlights - or as direct relationships?)
My pain comes now from the fact that I need to tell the team to not use Docs.
Which is going to be exacerbated with Comments. This slowly feels like I’m trying to hack around native UX.
Is there a way to disable Docs if I decide I want to use entities-as-docs? What about comments?
Do I allow Docs if I want them in the sidebar, or do I only allow them through Smart Folders?
The problem becomes that the UX very quickly starts becoming messy. The sidebar doesn’t allow me to show specific single entities, only views - but docs are an exception.
The comments have nice UX around them, and if I force people to go the entity-way, it feels quite cumbersome.
Relevant threads:
In short, I do not recommend using non-native comments, it will be a mess. UI will be quite bad, unintuitive, etc. And you will not gain much having comment as a database. BTW, what exactly you need?
As for Docs, we did a mistake initially and created Docs via Views. That is why you see them in left menu, etc.
In future we are going to migrate Docs to a database of some generic kind, I hope it will happen next year. We do recommend creating Document database and use it and indeed you will have to tell people to not use Docs as Views. Right now it is not possible to disable it, but I think we may add such an option in near future.
3 Likes
Some usecases I listed here: Add COMMENTS and REFERENCES to Feed - #21 by PsyRoelofs
But essentially a lot of it is to do that using notifications as the main discovery point into comments lead to a lot of issues for us as we scaled-up in Clickup.
We needed to setup various views to make sure that comments were not missed.
It’s all good when you can stay completely on top of your notifications, but as things happen more async, you start getting into an issue where you need to keep certain notifications semi-permanent for the fear of them falling out of scope and being lost forever.
I think it’s why Clickup has all sorts of filters specific to comments & assignments, and options to visualize the comments in views.
All of that UX is missing in Fibery, but would be available with Comments-as-Entities.