Hi, as my team moves along in Fibery, we continue to find References probably the most unique and useful feature. It is amazingly easy to simply type “ctrl” + K, then start typing out the name of any existing entity, or similarly create inline a new entity, while writing in Fibery. The fact that these mentioned entities then pick up the whole context of what’s written in their references area is huge.
A big way this can provide flexibility and save time when navigating in Fibery is if you want to essentially comment on more than one entity at once. You can simply mention the entity while composing your comment. This makes it seamless to update two or more entities at once.
Using the mentions around Fibery extensively, our team now has many DB’s that we have significant entities that both contain a lot of comments, and references. Things such as:
- DB’s of long-term projects
- Company objectives
- Internal systems we track in Fibery
and so on.
With this flexibility to use references, what happens is in order to see the most recent activity in an entity, the reader of the entity on our team must be sure to both read through comments and references. Sometimes however the most recent discussion may be in a reference, not the actual comments area. So we have found that it would be great if you had the flexibility to merge both comments and references, and have the freedom to sort them per your preference. Sometimes we might have the most recent comment in an actual Project entity that is a month old, but the project was references in two meetings the last few days. However, the natural tendency is to read the comments, so the reader might think there was no update to the project without being able to see the references that are more recent ahead of the older comment.
This is also closely related to Index comments in search as we continue to build very relevant content around Fibery in both comments and References.
Thanks for considering this!