[Terretta]

I want to love this, but this is terrible. It introduces yet another markdown useless to edit for GitHub, Jekyll, Scrivener, AirMail, or the like.

Use pandoc markdown (now aka common markdown) for broadest compatibility and reasonably professional publishing, or github markdown for a developer audience, or let the user choose among engines.

Don't introduce another rando format. Phabricator did that and it's terrible too.

(Btw, www.texts.io supports both visual rich text style controls and markdown typing at the same time, rendered wysiwyg, and is cross platform. Also supports multiple dialects, with pandoc as the default: http://www.texts.io/support/0009/)

[steveneo]

TextNut markup is nearly same with common markdown and you can switch between them. The existed text is also automatically converted. Actually, only 2 major differences. One is ~emphasis~ as emphasis. Another is header uses textile format, i.e., h1. h2. ... format.

[Terretta]

"Nearly the same" means translation is required.

Also, the point of Markdown is to look formatted as plaintext. The atx headers or == headers accomplish that. I like textile, but its headers don't accomplish the same goal.

[steveneo]

In texts.io, it looks all typing render to rich format but no way to get back the markdown in text.