by tibastral2 on 4/10/15, 2:46 PM with 88 comments
by rachelandrew on 4/10/15, 5:25 PM
I'm one of the founders of Perch (http://grabaperch.com) and we have almost 6 years of experience with Perch - and many more of creating custom CMS solutions before launching Perch. We've always tried to get people to write Textile or Markdown.
When we were developing custom solutions we actually had pretty good success with getting our clients to use Textile, once we'd explained the benefits. With Perch we ship our default templates (which are really just samples) using the MarkItUp editor and set to use Markdown, and not allow HTML. However it's all configurable and we offer editor plugins so people can switch to using Redactor, CKEditor, TinyMCE or create their own editor plugin.
In discussing this stuff with our customers who are developing sites for clients, it's not something that inserts HTML that they want. They just don't want the end client to see the Markdown as they don't think they will cope. I think there is often an assumption that they won't cope, but for whatever reason they end up installing CKEditor or whatever and it allows in a load of junk markup. This makes me sad.
So, an editor that created Markdown yet allowed for some sort of preview of how things will look I can see the benefit of, if just to encourage confidence in not using things that allow inserted HTML.
by rspeer on 4/10/15, 3:13 PM
I've seen too many double-pane markdown editors, which strike me as an uninspired, bloated interface.
Markdown is already readable! You don't need to waste half your interface on a preview that's visible all the time, when you can just syntax-highlight the Markdown to be its own preview.
by raldu on 4/10/15, 4:21 PM
by debaserab2 on 4/10/15, 4:13 PM
So far any time Ive released a content editing text area that uses markdown to the mass public, it's resulted in everyone treating it like a normal text box because they don't want to learn markdown. Wysiwyg editors, as much as we hate them, always gets much better adoption.
by Stoo on 4/10/15, 3:55 PM
I would consider switching over to it, as it would mean less code for me to manage, but I'd need the CodeMirror extensibility exposed.
(disclosure, I built Storytella)
by vortico on 4/10/15, 3:17 PM
by fny on 4/10/15, 5:29 PM
by gpmcadam on 4/10/15, 2:59 PM
But, why not make a simple WYSIWYG -> Markdown editor? I've never found an elegant and mature editor which does this
by rhythmvs on 4/10/15, 6:01 PM
I did a similar project¹, with strong focus on editing math, inline, and “real time” wysiwyg. It failed. The problem is that most such approaches treat Markdown as _code_ instead of _text_, and inevitably mistake syntax highlighting for semantic, text-driven styling (as if one would style nouns, verbs, adjectives, instead of <h1>, <p>, <em>, etc.). Thus they use a code editor such as CodeMirror (like this one does, too). And then you must style `.cm-` syntax markers instead of the eventual (html) nodes that would be the output of a real Markdown parser. Which makes it impossible to just throw in any arbitrary html5 css-stylesheet. Which is imho the whole point of wysiwyg Markdown editing.
What you’d really want instead is true Markdown parsing, which normalizes the user’s input into a parse tree, then renders to clean html. But syncing input and output over an AST is quite impossible as long as Shadow DOM is not available in browsers. Cfr interesting discussion, over at Github (re: Quill editor).²
As for Markdown parsers: there’s many of them. The OP’s project uses @chjj’s marked.js³: wouldn’t harm to mention that on the homepage or in the README, since behavior (markdown interpretation) is very different from parser to parser. (I used to maintain a repo which lists all available Markdown parsers, apps, etc.)⁴
Meanwhile there’s CommonMark⁵, of course, which has already some really fast implementations in JavaScript. (Plus, they’re “Standard” ;-)⁶ Would be nice to see one of the CommonMark reference implementations incorporated into a WYSIWYG editor like this one.
¹ https://github.com/rhythmus/mathdown ² https://github.com/quilljs/quill/issues/74#issuecomment-4294... ³ https://github.com/chjj/marked ⁴ https://github.com/rhythmus/markdown-resources ⁵ http://commonmark.org ⁶ https://news.ycombinator.com/item?id=8264733
by ben336 on 4/10/15, 3:11 PM
Not a fan of wysiwyg, but a bit arrogant no?
by fiatjaf on 4/10/15, 6:45 PM
by amelius on 4/10/15, 3:26 PM
by tumbling_stone on 4/10/15, 4:48 PM
by thebouv on 4/10/15, 8:37 PM
by luchosrock on 4/10/15, 3:47 PM
by dheera on 4/10/15, 9:43 PM
by camillomiller on 4/11/15, 8:33 AM
by marcinbejm on 4/10/15, 3:13 PM
by wodenokoto on 4/11/15, 4:43 AM
by buro9 on 4/10/15, 4:15 PM
**foo*f**f*
The WYSIWYG should be closer to the Preview for these messy cases.by fortawesome on 4/10/15, 3:25 PM
by enupten on 4/11/15, 1:38 PM