# Views are a little confusing right now **URL:** \ **Category:** Misc\ **Created:** [August 19, 2025, 9:45am UTC](https://community.fibery.io/t/views-are-a-little-confusing-right-now/9421 "2025-08-19T09:45:51Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [August 19, 2025, 12:18pm UTC](https://community.fibery.io/t/views-are-a-little-confusing-right-now/9421/2 "2025-08-19T12:18:53Z")
> [@RonMakesSystems](#): > > Context views in smart folders. > **Embeddable** : Nowhere Smart folder context views are embeddable in docs/rich text, no? What do you mean by > [@RonMakesSystems](#): > > Context views by creating an embedded view in an entity. ? Do you mean a view embedded in an entity’s rich text field? I note that the cons for #3 included that they can’t be mirrored, but the cons for #4 includes that they are always mirrored. Doesn’t that mean, at least for this problem (of mirroring) there is a solution with one or the other? - if you want a mirrored view, use a relation view; if you don’t want a mirrored view, create a rich-text embedded view. I agree that they also have other weaknesses (like relation views require a relation field, and rich-text embedded views require a rich text container, which might otherwise not be necessary). It feels like the solution is what is discussed [here](https://community.fibery.io/t/add-views-to-entities/8986), no? --- _[View the full topic](https://community.fibery.io/t/views-are-a-little-confusing-right-now/9421)._