Paul Tingle

Hi Amisha Sharma.

Yes overall we would like markdown composing and functionality to operate in the same way as currently. In my own brief testing I found that basic markdown was converted live in the composer and worked correctly, but features such as markdown hyperlinks were non-functional (they were not converted from the markdown syntax when published). So we either need a composer that live converts and works for all markdown, or one that does not convert live, but has a preview button (and again works for all markdown). I think the latter is preferable.

Thanks!

Paul.

Hey @..., that's great news, much appreciated!

I was directed here by Support after opening a ticket regarding lack of full markdown support in Workspace. We've been selected for automatic migration in August and being forced into losing markdown support (which we do use) in exchange for integrated chat support (which we do not use) is disappointing to say the least.

We'd appreciate a delay in any forced migration until markdown support is fully functional.

Ironically I see the Master Subscription Agreement has been updated to state:

• We have added an explicit commitment that we will not materially decrease the overall functionality of the Services during a subscription term;