<story><title>EpicEditor: An Embeddable JavaScript Markdown Editor</title><url>http://oscargodson.github.com/EpicEditor/</url><text></text></story><parent_chain><item><author>cwilson</author><text>I&apos;d love to implement this instead of a WYSIWYG into our platform, but the problem is our users (non-technical) are not going to take the time to learn markdown. Even if we had a guide on the right I have a hunch they would still be super confused.&lt;p&gt;Idea: Add buttons to the top (optional) that LOOK like a WYSIWYG (something they are familiar with), that simply apply markdown around text.&lt;p&gt;I think you&apos;d see such much wider adoption with that addition, which is something I&apos;d love to happen, because WYSIWYG&apos;s do indeed suck.</text></item></parent_chain><comment><author>lazerwalker</author><text>Agreed 100%. GitHub&apos;s wiki UI (example: &lt;a href=&quot;http://cl.ly/2T2718220P1Y3h0M330r&quot; rel=&quot;nofollow&quot;&gt;http://cl.ly/2T2718220P1Y3h0M330r&lt;/a&gt;) would be a great place to take inspiration from, since that&apos;s almost exactly what you&apos;re talking about.</text></comment>
<story><title>EpicEditor: An Embeddable JavaScript Markdown Editor</title><url>http://oscargodson.github.com/EpicEditor/</url><text></text></story><parent_chain><item><author>cwilson</author><text>I&apos;d love to implement this instead of a WYSIWYG into our platform, but the problem is our users (non-technical) are not going to take the time to learn markdown. Even if we had a guide on the right I have a hunch they would still be super confused.&lt;p&gt;Idea: Add buttons to the top (optional) that LOOK like a WYSIWYG (something they are familiar with), that simply apply markdown around text.&lt;p&gt;I think you&apos;d see such much wider adoption with that addition, which is something I&apos;d love to happen, because WYSIWYG&apos;s do indeed suck.</text></item></parent_chain><comment><author>subpixel</author><text>Your suggestion might be a good default for handling image insertion. I know markdown, but in instances where I&apos;m specifying an image (e.g. a blog, a CMS page) I&apos;d rather have a button that lets me select from available images than have to type it out using markedown (which would require that I know the filename and explicit path). Not to mention image alignment.</text></comment>