They present the document as WYSIWYG with markdown hidden, but unhide any markdown surrounding or directly adjacent to the cursor. (So the markup from an italic or link span are only visible if you are adjacent to or within the span.)
It's a nice balance between looking pretty and letting me edit markdown directly. I'd love to have an open source editor library that acts like this.
The default mode is WYSIWYG since Markdown syntax frustrates people who don't know Markdown well.
Thanks for mentioning Typora! It's an interesting implementation. I've thought about that approach (in-place real-time preview as you type Markdown text) before, but inside a browser, it's too cumbersome to fight against the inconsistent contenteditable behavior.
There was a project in Finland to reform keyboard layout ("Kotoistus"), only thing they managed to do is to add more dead-key accents and make the keyboard even more annoying to technical users. In all their great wisdom they decided to add non-breaking space character to altgr-spacebar key combination. In isolation that might seem like a good idea, but when also | character required the use of altgr-modifier it was a mess: working with the command line, you tend to have stuff like ... | grep foo. Soon enough there were plenty of users wondering why bash complains that grep is not found: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/218637
Personally, I have abandoned national keyboard layout and adapted US layout instead. Makes both programming and general use much more comfortable. Its amazing how much less I need to use modifier keys now, especially the painful altgr.
Symbols used for code would be hidden behind several layers like altgr combinations. While, imo, archaic symbols (ÇÀÉÈàçê, etc) would be on the first layer.
I'm planning on doing the same as parent, using the US layout, but I can't change my keyboard at work, and although I can type in qwerty, I don't know all the layers like I do azerty, so I can't just type without looking.
I can't even use another text editor than the one I have. All those 'vim vs emacs' war-jokes make me laugh. What I wouldn't give to use vim...
I can change the software layout, but as I said, I don't know enough the sublayers of the qwerty layout to be able to type without looking.
While also not having keyboard layout change, when SSHing to a server and not being able to make a slash
e.g. / [ ] requires shift key and a number on most.
aren't these rather crazy terms for a text editor ?
The code has three parts: Markdown to HTML text, HTML DOM to Markdown, and the editor. The total size is about 30KB uncompressed (27KB JS + 3KB CSS). It didn't use any icon font or images.
It has all the markup showing, and italize, boldens and changes size of text according to the tags, as well as color coding.
My goal is to make Markdown and HTML editors working together. I want to support Markdown because it's very productive for long-form article writing.