To keep track of the fascinating and rapidly evolving Markdown ecosystem, I maintain an inventory¹ of Markdown dialects, editors, parsers, stylesheets, various tools, etc.
Kudos on Mkdown.com! It’s been added to the list.²
"Learning Haskell" is filled in the description of the gist. Descriptions can be fairly lengthy and not always suitable as titles. However, I think it would be awesome to support metadata in a form like in Jekyll posts or something similar.
Yeah, maybe for v2. The goal of this was to elegantly share .md files (hence the name), so other file types are outside the scope of what I wanted to build.
I don't think parent is talking about other file types exactly, but rather that on github itself, you can have code blocks within your .md that get syntax highlighted. Which, for some people, is a pretty key feature of github markdown.
On yours, as in parent's example, the code blocks don't even get put in a `<pre>`, which would be the minimal 'right thing' if you're not going to do syntax highlighting.
(Of course, yes, syntax highlighting code blocks within .md is pretty much going to use the same logic as handling other file types, it's true).
It looks like he just fed it a plain python gist, no Markdown, no nothing. On the site it says the service can be used "to elegantly share gists written in Markdown", so I don't know why he would expect that to work.
I guess a clear error message would be helpful, but then you would either have to rely on everyone using standard file endings, or do some pretty fancy (and unreliable) parsing to determine if it's actually Markdown.
Fenced code blocks do come through as expected — complete with syntax highlighting. Well done!
One suggestion though: I expect my code blocks to not wrap — they’re in <pre> tags, after all. The stylesheet should have them rendered either with horizontal scrolling, or with overflow.
I did something similar a while back with https://github.com/sntran/gists.io, but was too ambitious to include editor. That got me nowhere. Yours look very nice and simple.
Although http://gist.io has this already, I think I like mkdown's CSS a little better (though there doesn't seem to be <code> styling as of yet). In any case, great work!
I opened it and thought that pg would approve of the narrow column [0]. Then I looked who made it and saw that it's a founder of one of the best examples of YC (not just companies that are doing well but seem philosophically aligned with YC).
Edit: I was wrong, SeatGeek didn't go through YC. But the company is certainly well-liked around here, partly because of their open source: https://github.com/seatgeek/soulmate
Does it have to be limited to using a gist? Would it be possible to pass in any url to just raw markdown and have that parsed (i.e. like raw.github.com)
Great work though - I wish I saw this last week while showing markdown to others for the first time.
