Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues

Re:Atlassian Cloud ToS section 3.3(I) prohibits discussing p... by saagarjha on Saturday January 02, 2021 @02:46PM (#25615781)

As a programmer, being able to have something like what GitHub does (Markdown text, you can preview what the rendered version looks like) would be great. I assume that people who are less technical would like a more WYSIWYG editor but as long as the ability to write straight Markdown is there I am sure that I wouldn’t care. Oh, and make sure it’s actually a reasonable subset of Markdown, not like Discord or Slack where you support bold and italics but mot much else.

[ Parent | on HN ]

Re:Atlassian Cloud ToS section 3.3(I) prohibits discussing p... by confluence_perf on Saturday January 02, 2021 @02:51PM (#25615834)

Thanks! I'm not sure this is the most doable thing (I'm not familiar with the technical aspects of the editor storage format) but can definitely discuss with that team.

The "reasonable subset of Markdown" is also a very useful specific detail, exactly the kind of specificity that helps us do our jobs.

[ Parent | on HN ]

Re:Atlassian Cloud ToS section 3.3(I) prohibits discussing p... by Kinrany on Saturday January 02, 2021 @04:59PM (#25616956)

There's CommonMark, a standard for Markdown. You could make that your goal, instead of feature parity with any of the proprietary implementations like Github.

[ Parent | on HN ]

Re:Atlassian Cloud ToS section 3.3(I) prohibits discussing p... by TeMPOraL on Sunday January 03, 2021 @06:43AM (#25621233)

FWIW, check out the new Reddit interface. For all the well-deserved hate it's getting (some of which for the same reasons Jira is), it showcases that you can have a dual WYSIWYG/Markdown editor that works, and allows switching back and forth between modes during editing.

[ Parent | on HN ]