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.
Can this be rolled into Customize Entity Views?
1 Like
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:
1 Like