Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Add WYSIWYG editor to "Composer" probably markdown! #569
Sending and receiving HTML email is a polarizing issue, some people love it, some people despise it. Personally, I fall into the later category most of the time. I say that as a designer & visual oriented person. Sure, I like seeing colorful, well designed emails from interesting sources as much as the next person, but for my daily correspondence I HATE the chaos of HTML emails nasty formatting, colors, and font sizes that marke it harder for me to simply read messages from people that matter to me. Additionally, HTML emails open up a whole slew of security issues that need to be taken into account properly. That said, HTML emails is something we must support.
What I propose is using a WYSIWYG markdown editor like http://epiceditor.com which does the following things:
This should allow users to do basic h1, h2, h3, strong, em, p style elements, but work seamlessly with the larger mailpile design.
For more design heavy emails (mailing lists, marketing, etc...) we should explore more creative nicer ways to display these messages a la what Gmail is planning to do http://gmailblog.blogspot.ca/2014/03/a-new-more-visual-way-to-view-your.html
I don't care about this one, but I think a lot of users do. Then I also think this is important.
I came here in the mailpile bugtracker just to suggest this.
It may be of interest to this discussion: http://blog.codinghorror.com/standard-flavored-markdown/
I disagree about this feature. You're assuming that all text will render nicely with MarkDown. You're assuming that all email users will use software similar to mailpile to be ensure nice format in MarkDown. You're assuming the HTML part doesn't have elements that are important and unrenderable in the text/plain counterpart. Not only all that, but you're hiding the real content from the user. If this is implemented, there should be an option to disable it.
I like the idea of live preview like advocated by Bret Victor on the Inventing on Principle talk.
EpicEditor doesn't have a live preview, but the Ghost blogging platform does:
After playing with epic editor in the past I realized my workflow was suboptimal, then I configured Emacs to "preview" MarkDown as I type and I noticed I no longer lose time on the "edit, preview, edit, look for the point where I stop before changing to preview" tasks.
Neat! The discussion software Discourse has a similarly well designed solution as well. If WYSIWYG, then +1 for (the option of) such a split-view approach.
However, I can imagine that longer writing can be disctracted by the constant updating in your peripheral vision. IMHO, a contrast-reducing overlay that is removed on mouse-over or after a few seconds delay could counter that problem, if it arose.
This is a great feature request.
There seems to be a few leading lightweight markups and so an extensible interface perhaps supporting Markdown (many variants thereof), Asciidoc and RestructuredText would be very cool.
I'd be very keen to see a side-by-side preview (providing user feedback) rather than a tabbed view.
There is recently a Thunderbird Asciidoc plugin to allow writing Asciidoc in the compose window and also a Firefox Asciidoctor plugin (using Asciidoctor.js) which may assist. Also there is the Docgist which offers a similar WYSIWIG interface (although not quite as cool as those above).