# Nov 9, 2023 / 🎤 Thread View (experimental), Grid View improvements **URL:** \ **Category:** Changelog\ **Created:** [November 9, 2023, 2:03pm UTC](https://community.fibery.io/t/nov-9-2023-thread-view-experimental-grid-view-improvements/5392 "2023-11-09T14:03:07Z")\ **Posts on this page:** 1\ **Showing post:** 48
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [May 21, 2025, 12:55pm UTC](https://community.fibery.io/t/nov-9-2023-thread-view-experimental-grid-view-improvements/5392/48 "2025-05-21T12:55:50Z")
> [@Yuri\_BC](#): > > **Introduce a new Discussion View** , enabling entities from **any database** to be displayed and used as comments It sounds intriguing, but I’m not sure I understand what you mean when you write “enabling entities … to be displayed and used as comments” or when you write “cross-referencing of entities used as comments” Is ‘Discussion View’ something close to a mashup of feed view and thread view? Where each ‘card’ in the feed shows a specific entity’s comment threads? Or is each ‘card’ a single thread (with potentially multiple cards per entity)? Alternatively, I wonder if there could be improvements achieved by enhancing the functionality of #mentions? At the moment, in any comment (or any rich text field or document) it is possible to #mention an entity. The entity will be displayed (with certain fields showing, depending on the configuration). At the moment the choice of fields to show is the same for all entities of the same type, no matter where the mention is occurring. What if the choice of fields to be displayed were more flexible (perhaps uniquely definable for each mention) or if it were even possible to embed a custom entity view? Would this be helpful, or is that just a tangential problem to be solved? Maybe this discussion is related to (should be moved to?) this thread: > [@Comment fields and inline comments to be entities with fields (comments database)](https://community.fibery.io/t/comment-fields-and-inline-comments-to-be-entities-with-fields-comments-database/4602): > > Collaboration is heavily dependent on the commenting system. As I see now, Fibery is not yet very focused on collaboration, more on data structure. There are in a few days already a number of my posts about UX and end user workflow issues. The comment field is currently not a database entity type with fields. Neither are the richt text inline comments. Both comment field and rich text inline comments are currently resulting in isolated items that cannot be organized in a way that I find useful … ? --- _[View the full topic](https://community.fibery.io/t/nov-9-2023-thread-view-experimental-grid-view-improvements/5392)._