Can someone explain why this is useful? I thought the point of Markdown is that is easy enough on the eyes that you can comfortably edit the.source (and I certainly think it succeeds in that). Why would anyone abandone the comfort of their favorite editor to edit Markdown?
I'm looking for something kind of like this. Our company website is generated from Markdown, which is great for the devs on the team, but the marketing folks still struggle with it from time to time. So I'd really love to provide them with something that (1) forces UTF-8 on Windows, (2) eases writing in Markdown, and (3) shows the folder structure.
I'm currently setting them up with Sublime Edit, but it's not quite ideal as it's overly complex for what they need and I still have to manually configure it to default to UTF-8.
You can look at markdown et al. from another point of view: it's a file format that is human readable (text) and therefore "safe".
Many people care more about rendered markdown than about raw markdown, and would prefer to edit closer to the rendered result than to the human readable but not what they're interested in text. For those people, this eliminates the "write - render - check" cycle.
I don't even understand how wysiwyg can possibly apply to markup. Markup depends on a renderer for wyg. It could be PDF, plain text, HTML, RTF, XML, anything.
Comments
Can someone explain why this is useful? I thought the point of Markdown is that is easy enough on the eyes that you can comfortably edit the.source (and I certainly think it succeeds in that). Why would anyone abandone the comfort of their favorite editor to edit Markdown?
I'm looking for something kind of like this. Our company website is generated from Markdown, which is great for the devs on the team, but the marketing folks still struggle with it from time to time. So I'd really love to provide them with something that (1) forces UTF-8 on Windows, (2) eases writing in Markdown, and (3) shows the folder structure.
I'm currently setting them up with Sublime Edit, but it's not quite ideal as it's overly complex for what they need and I still have to manually configure it to default to UTF-8.
You can look at markdown et al. from another point of view: it's a file format that is human readable (text) and therefore "safe".
Many people care more about rendered markdown than about raw markdown, and would prefer to edit closer to the rendered result than to the human readable but not what they're interested in text. For those people, this eliminates the "write - render - check" cycle.
I'm not sure how useful it is as a desktop application. I suppose it depends on your organization's workflow.
If there was an equivalent of ckeditor or tinymce that could output markdown or textile instead of html, I'd find that extremely useful.
I don't even understand how wysiwyg can possibly apply to markup. Markup depends on a renderer for wyg. It could be PDF, plain text, HTML, RTF, XML, anything.
You are right, WYSIWYM is more correct term. Formatting in the editor shows document structure and not exact rendering.