You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 3, 2024. It is now read-only.
It can be challenging to know what each type of field is when choosing from them in the field picker when creating a form. For example, the "Text Constant" field can be particularly tricky to understand. It would be useful to add some sort of inline help next to each field to help clarify what the field is.
I'm thinking rich text would work well (perhaps displayed when clicking a "Learn More" link or something of that sort). That way, an image could be part of the rich text (a screenshot of the field). The more conceptual fields could have just text describing the behavior and use cases, and they could even have diagrams.
The text was updated successfully, but these errors were encountered:
Another idea would be to embed this inline help into the area that displays the field in the back office. We already sort of do that for some fields (by displaying a read only version of the field). That has the downside that the field actually needs to be created before seeing the help; that's an extra barrier somebody has to pass to get the help they need, and they probably wouldn't even know that they need to do that to get the help. So not ideal, but could work in a pinch.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It can be challenging to know what each type of field is when choosing from them in the field picker when creating a form. For example, the "Text Constant" field can be particularly tricky to understand. It would be useful to add some sort of inline help next to each field to help clarify what the field is.
I'm thinking rich text would work well (perhaps displayed when clicking a "Learn More" link or something of that sort). That way, an image could be part of the rich text (a screenshot of the field). The more conceptual fields could have just text describing the behavior and use cases, and they could even have diagrams.
The text was updated successfully, but these errors were encountered: