Here are some examples:

# This is an H1
## This is an H2
###### This is an H6
------------------------------

This is [an example](http://example.com/ "Title") inline link.
[This link](http://example.net/) has no title attribute.

Will produce:

<p>This is <a href="http://example.com/" title="Title">
an example</a> inline link.</p>
<p><a href="http://example.net/">This link</a> has no
title attribute.</p>
------------------------------
_single underscores_
**double asterisks**
__double underscores__

will produce:

<em>single asterisks</em>
<em>single underscores</em>
<strong>double asterisks</strong>
<strong>double underscores</strong>

Absolutely a necessity these days. Maybe if someone wants to make a site about their npm or github package they could just copy and paste their markdown docs as a collection and run it through that.

Really need this. Looking at systems like Contentful and Static Site Generators, everything else supports Markdown, it's the new standard for content portability!

Love everything I see in Webflow but Markdown seems like a must-have in order to: (1) properly format rich text (2) export text out of Dropbox / Medium ...etc.

Unless of course, is there a way to style elements inside a rich text blog, but I haven't found a way to do it.

Hey Kirill, it is possible to style elements inside Rich Text blocks - check out this tutorial: https://university.webflow.com/article/rich-text

This is definitely a must. 

So much content in markdown format for creators of apps and services that the lack of markdown support is actually a problem.

We currently are splitting our site between Readme.io and WebFlow for just this reason.  Pages on Readme.io are easily editable by our product team, none of which know or understand CSS or can really in any practical way use the WebFlow editor for updating or adding new pages.

I'm 100% behind this. This addition would be incredible for us. We could keep all of our markdown inside of our git repo and make pull requests for review. Things like showing code snippets or tables are make the sites that much better.

Surprisingly absent

Due to markdowns recent popularity spike, i fully support this!
Take care when implementing the syntax though, due to various common "flavors" or "interpretations".

Would be awsm if CMS compatible!

Completely a must-have as we can spread the same text on several different platforms

Helps when drafting on iOS and other text editors or when collaborating...