Moving to Markdown

A few days ago I received an email from a developer asking for help with Markdown files on Jekyll.

Giving him some assistance on this reminded me how good and agnostic this language is for writing, so from now on my posts will be Markdown files. Here is why I'm doing this and some tips about it.

Having to write all my posts in HTML wasn't bad but it made me lose a lot of time and it felt more like working, instead of just writing. So the main reason was to improve my writing experience.

The other reason was writing code samples. Trying to find a good way to show and style them on HTML can be a not that pleasant task.

The code tag

The best way to achieve this while following the standards is to write a <pre> tag and a <code> one inside it. What happens here is that spaces, tabs and line breaks are interpreted, the opposite behaviour of a normal HTML document.

<pre><code>function doSomething(){
  var anything = 'string';
  <span class="comment">// do something</span>

As any line break or space is parsed we have to concat lines and tags. While this isn't pretty all at and it's also a struggle to read or mantain since what you're seeing is way different from the final result.

Markdown to the rescue

When I was reading some documentation to help this developer I remembered how easy is to achieve this in Markdown. When you want to use a code tag the only thing you need to do is wrap it inside three grave accent (`) characters followed by the language, for example ```js for JavaScript.

Choose a parser

There are a lot of Markdown interpreters that you can use, most of them respect the normal standards of the language. I chose redcarpet because it slices the code adding span tags with classes that make easier to style, for example cl for comments in JavaScript. You can inspect the following code to see what's the result.

function doSomething() {
  var anything = 'string';
  // do something


Of course for consistency I would like to have the same generated markup in my old HTML posts for styling and mantainance. What I did was to create a draft in Jekyll using Markdown with all the code snippets from my old posts, using titles to separate and identify them.

After doing this I just had to build my site using the --drafts flag, opened the file and copied every piece of HTML inside every post.


If you have the chance try it. If your blogging engine is Jekyll you have some good parsers for your choice and it will speed up your writing, and it's nice to feel that I'm actually writing a post instead of working.

There's a nice article in Wikipedia about Markdown and its syntax, which is pretty straight forward and easy to learn. If you're using SublimeText as your IDE there are lots of packages to improve the highlighting for this extension.