Oh, the mark of down is really down marked

That was supposed to be a song. It did not work out. šŸ˜›

I was looking through my WordPress dashboard the other week to see what changes they have made that I was unaware of (I should follow their changes blog). It is good to do this every now and then, as you may find something you like or dislike. While looking around, I noticed there were two, brand new check boxes. If checked, they would allow posts and comments to be written in Markdown. In case you do not know what that is, Markdown is a simple text formatting “language”, kinda like HTML but simpler. I use Markdown to format any prose documents on GitHub, so enabling it was a no-brainer for me. I mean, why would I want to convert a single document between HTML, BBCode, and Markdown when I can use Markdown and only have to convert it to BBCode? šŸ˜€

But alas, things are not always what they appear to be. Although this is a standard Markdown format, WordPress choose to use an extended version called Markdown Extra to enhance functionality (a quick reference sheet can be found here). GitHub uses its own extended version too, called GitHub Flavored Markdown (GFM for short). While it seems I will have no issues taking GFM and posting it here (and I doubt I will begin to touch all of Extra’s features), WordPress has just helped increase the already large fragmentation in Markdown extensions.

StandardsSo while Markdown is now enabled for posts and comments on here, I will probably be sticking to good ‘ol HTML for posting and continue this HTML –> BBCode –> Markdown when I have to do it (which honestly is not too often). But for the fun of it, I wrote this post using Markdown. šŸ˜›

Markdown formatted post