Hi Morgan, Thanks so much for the detailed clarification and for sharing the screenshot—this really helps us understand your use case better.

At the moment, having an HTML view/editor inside the decision tree content area is not part of our immediate roadmap. However, we’ve added this to our feature backlog and will evaluate its priority based on broader customer traction and demand.

In parallel, we’ll also assess the technical feasibility of supporting HTML editing in a safe and scalable way, especially considering accessibility and media embedding requirements.

We truly appreciate your input—it’s insights like this that help us shape a more inclusive and powerful product experience. We’ll keep you posted on any updates related to this enhancement.

Hi Shakeer!

Yep - That is exactly it. Having an HTML view/editor within the content editing area similar - I'm having trouble viewing your screenshot so I also added one to extra confirm. :)

We are looking to be able to toggle on a HTML view so that we can ensure accessibility elements can/are applied properly. For instance, an accessibility requirement is that headings have a specific ID name that matches the text of the actual heading. Normally in the system today, an ID is added but it is a generated ID not specific text.

Embedding content is also a major plus as we want to potentially use these for customer onboarding and we often have videos and other media that goes along with them.

Hi Morgan

Thanks for your feedback on enhancing the decision tree experience.

To better understand your request, could you please confirm if you're referring to having an HTML view/editor within the content editing area—similar to the one shown in the attached screenshot (where we currently support formatting options like bold, lists, links, etc.)?

Are you looking to:

Toggle between rich text and raw HTML?

Add custom HTML elements (e.g., inline styles, tables, code blocks)?

Or embed structured content like media or reusable templates?

Your clarification will help us explore the best implementation path. Looking forward to your input!