We would love to have some Rich Text formatting options supported natively for string properties. Implementing markdown support for string properties would significantly improve text capabilities. We suggest a lightweight formatting option compatible with markdown to enable more expressive, readable, and structured content across the system.
Key Benefits:
Enhanced Communication Markdown allows users to add structure, emphasis, and clarity to text through simple formatting.
Seamless Compatibility Native support ensures consistent rendering across different products and interfaces while staying generally backward compatible.
Flexible Documentation From technical notes to project descriptions, markdown enables more nuanced and effective communication to be captured in ontology.
Low-Complexity Implementation Markdown provides a simple, widely-understood approach to rich text with minimal system overhead.
Improved User Experience Better text formatting leads to more engaging and easier-to-read content.
This functionality is already offered in an Action Type’s configuration in the Form tab and is not limited to just string properties. Check out the annotated screenshots below, but also curious if you had something else in mind with this proposal?
I didn’t phrase it clearly. I meant to suggest an actual WYSIWYG editor for it within the action type forms. Something like the screenshot attached. It takes a lot of overhead to implement a user friendly option and requires a different submission strategy to make it work. I was suggesting markdown as a bare minimum compatible option set. It would still lack things like underline or image attachment but it would greatly help end users that aren’t necessarily familiar with markdown syntax.
