# Static text field-type

**URL:** <https://community.fibery.io/t/static-text-field-type/1757>\
**Category:** Ideas & Features\
**Created:** [July 5, 2021, 6:57pm UTC](https://community.fibery.io/t/static-text-field-type/1757 "2021-07-05T18:57:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jim\_Larsson](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jim_larsson/32/1489_2.png) [@Jim\_Larsson](https://community.fibery.io/u/Jim_Larsson)\
**Post date:** [July 5, 2021, 6:57pm UTC](https://community.fibery.io/t/static-text-field-type/1757/1 "2021-07-05T18:57:57Z")

</div>

Sometimes It would be helpful to have a descriptions or guidance for your team on how to use a type you created. A static text field-type would be useful and versatile for this. Other use cases could be to use static text for tooltips. Why not have two or more styling options for static field-type and a toggle between for example tooltip, rich-text and plain-text styling? It would be an easy way to provide clarity to others in tour team.

---

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [July 5, 2021, 7:45pm UTC](https://community.fibery.io/t/static-text-field-type/1757/2 "2021-07-05T19:45:17Z")

</div>

Can this be rolled into [Customize Entity Views](https://community.fibery.io/t/individual-layouts-for-a-node-hide-fields-etc/995)?

---

<div class="post-metadata">

**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:** [July 5, 2021, 9:34pm UTC](https://community.fibery.io/t/static-text-field-type/1757/3 "2021-07-05T21:34:36Z")

</div>

Personally, I’m not sure it’s a good idea to use fields as vehicles for explaining how the type should work. The content of a field is entity-dependent.  
It strikes me that what is perhaps more needed is a way to describe an app and its purpose (including how to use the types within it) which is more of a meta-level than the actual entities within an app.  
Perhaps there is something valuable in these other discussions:

> [@\[APPROVED\] Add "Description" area to apps created from Scratch](https://community.fibery.io/t/approved-add-description-area-to-apps-created-from-scratch/424):
>
> Hi, When creating an app from Scratch, I’d like to be able to add the third area called “description,” next to “Types” and “Access” that I’m seeing in the pre-loaded apps that are in the App Store. Unless this is something I’m missing, could you add this capability? It would be very useful to have a general overview type area with each app that explains its use to users. Thanks guys!

> [@Mention or links to types](https://community.fibery.io/t/mention-or-links-to-types/924):
>
> Can we please have the ability to mention/link to a type (rather than just linking to an entity or a specific view)? Sometimes, I want to write an explanation of how to use an app, and want to mention a type, rather than a single instance or a specific table/board. It might link nicely with some of the issues discussed here: