I.e. this one.

Because I think it should be.

I'll contribute some new ideas for markdown. can I joint with your markdown team? Please send me an invitation to [email protected]

I've uploaded a basic Sans vector logo for Markdown based on the markdown.github.com avatar.

http://www.yellosoft.us/logos#md

sidenote: not sure where should i post issues about markdown rendering engine which is used on github itself
here is the example:

w/o extra newline after the <details>:

with extra newline after the <details>:

Describe what markdown is for, and how it's more of an idea that has been copied into numerous individual spin-offs, rather than one single standard.

I think of Markdown as a more intuitive version of MediaWiki syntax. Either way, the goal as I see it is to produce rich text documents in a syntax that's nearly as powerful as HTML but much easier to use.

I think we should also include a hyperlink to the historical "official" Markdown website, Daring Fireball. And if we're really productive, once the github markdown page is functional, try to get the Daring Fireball page to include a link at the top along the lines of Markdown has moved to ...

Hyperlink to the web pages for each implementation.

For each implementation, link to the documentation for its supported syntax. These are often hard for normal users to find, and confusion abounds when people are unaware that markdown is diffused through several implementations, not one single standard.

Include a basic table of features supported.

Include a bullet list of markdown users (e.g. GitHub, Stack Overflow), and which implementation and version they use.

Hello,

is there any way to reference *ToMarkdown converters on the site ? I happen to be the dev of http://upndown.netgusto.com, and I think that converters like this might find their place somewhere in your website.

Thanks

If we implement this website itself in MD, conflicts may arise between syntax on the site's documentation web pages vs. the syntax for the site itself.

But if we implement this in HTML it won't be as cool.

The CommonMark project provides a specification to help multiple implementations resolve conflicts.

http://commonmark.org/

I just created the basic skeleton of a draft welcome page at http://markdown.github.com.

Not sure if my approach is the best, but it is always easier to build off of something that exists. I suspect we'll need to build the resources before we can link to them from this page though.

There seems to be several competing Markdown parsers (GitHub, Git Lab, Stack Overflow, Reddit...), each with their own set of accepted/rejected syntax. It would be helpful if there was a mdlint CLI / Web tool that could warn for syntax that isn't commonly accepted. Kind of like lint back in the day before C was standardized, helping coders write their .c files more portably.