It’s worth acknowledging you all are passionate about Markdown for various reasons. Opportunities to improve the Editor moving forward Here are some examples for macros which allow creation and rendering of Markdown in Confluence and Jira: Worth noting that there are also apps available on the Atlassian Marketplace which extend our editor’s native functionality, and may help provide the editing experience you’re after. There are no plans to support this for the editor in our cloud products. " Text" selector at the bottom of the editor. In some server instances of Jira (such as this one), you may still see a " Visual" vs.Copying from the browser search bar is one example of where plain text can be accessed. Note that the text pasted needs to be plain text in order to trigger the transformation. Markdown transformation on paste: We let you type/paste plain markdown/markup text into our editor to help with markdown authoring happening outside our editor.You can see these shortcuts in the Editor help menu, accessible via the Cmd/Ctrl + / keyboard shortcut.We used to use wikimarkup syntax but we switched to markdown because it is an industry standard. Autoformatting: We allow people to type to make things bold. ![]() That being said, we do offer support for markdown in the cloud editor in a few ways: Unfortunately it wasn’t/isn’t feasible for us to support both experiences, and in balancing the tradeoffs opted to support the majority. We recognise that a number of users such as yourself would much prefer plain-text markup authoring, but the overwhelmingly majority of our customers requested a more modern, rich-text, WYSIWYG editing experience. Markdown/markup vs rich-text WYSIWYG) when moving across our products resulted in overall confusion and frustration for our users. Over the years, our team has made efforts to build towards a consistent, familiar, and performant editing experience in all our cloud products. We performed extensive research into how our users use our many products together, and found that an inconsistent editing experiences (i.e. My team and I however are open to better understanding where the editor falls short for you, and exploring ways in which your core use cases can be supported without necessarily relying on a plain text editor. Some context regarding this decision is shared below. I will be closing this ticket as “Won’t Do.” I know this isn’t the outcome you were hoping for. ![]() TLDRĪt this point in time, we have no plans to provide users with a plain text editor. Hey folks, I am a Product Manager working on our cross-product cloud editor and want to provide an update to this request.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |