While the configuration does somehow resemble MacDown’s, they are still different, and at times incompatible with each other. I host my own personal site/blog, and it uses a custom renderer to process Markdown. One particular instance is when I got asked whether I can recommend a blogging platform that supports extensions MacDown has. Some of them have been added as FAQ, but there are more that don’t fit, and they need a good place to the public. For those I can answer (not a lot, really), many are common enough that I got asked multiple times. But I am by no means an expert on Markdown, let alone many other topics people ask me about, and I’m sorry I can’t answer many of your questions. I love them, and have tried (and will continue to try) answering them the best I could. I have also received a lot of emails/tweets/DMs recently for MacDown. So I figured that it’d be better to find somewhere else in the future. And the post doesn’t really fit well with other posts there either, as my personal blog targets more toward Chinese audience.

But it seems a bit queer, to say at least, to use my personal blog for that purpose. Back when I released MacDown 0.2 I felt that we have too much to fit inside the release note, so I wrote a blog post for it.

Macdown code highlighted in editor