More Efficient Markup with Markdown

Introduction In the last few months I’ve been working on a website where I was encouraged to use Markdown for writing content. While Markdown has been around for quite some time, I haven’t used it, and have plodded on writing full markup. This is usually a tedious chore, especially for long pages of content, even with just basic formatting.

Markdown to the rescue!

What is Markdown? Markdown was introduced by

John Gruber as an alternative to writing full HTML. Markdown syntax is simple, and can be converted into HTML via software tools. It is used primarily to simplify the writing and formatting of text; as such, it allows for most common use cases but does not cater to all. Where some specific HTML does not have a Markdown equivalent, the HTML can be written directly as needed. One driver behind Markdown is readability. Full HTML can quickly become difficult to read, since content can get drowned in a sea of angle brackets. Markdown symbols are simple and generally stay out of the way; once the syntax is understood, they convey the intended meaning rather clearly. Quoted from Markdown: Syntax:

The idea for Markdown is to make it easy to read, write, and edit prose. HTML is a publishing format; Markdown is a writing format. Paragraphs are marked by two consecutive new lines, which finish the previous paragraph, if any, and begin a new one. A line break is inserted by typing two spaces at the end of a line followed by a single new line. Text formatting is done by surrounding the given text by particular characters: <em>emphasis</em> renders emphasized text, while <strong>strong</strong> renders strong text. Three consecutive underscores (___) render a horizontal rule. And > quoted text renders a blockquote. There’s more to Markdown than these brief examples, but they do show how simple it can be. Note that a Markdown character can be excluded from conversion by prefixing it with a single backslash (“), as follows: &#35;2 => #2 (the escaped version leading to the generated output) Note that in the following case, two backslashes are needed, one for each of the leading asterisks: &#42;&#42;strong** => **strong** In the case of a heading, say an h2, a single backslash at the start of the line seems to be enough to prevent conversion, possibly since the symbols need to be at the start of the line to work as intended.

Some Sample Snippets Following are a number of commonly-used Markdown snippets. Emphasized text:

*emphasis*, _emphasis_
 Strong text: 

**strong**, __strong__

# heading level 1

## heading level 2

### heading level 3

#### heading level 4

##### heading level 5

###### heading level 6
 Inline code blocks for use within e.g. paragraphs 

 Block-level code samples, usually for longer listings, indented with 4 spaces or a tab. The block-level snippets in this post are written using this syntax: 

 Horizontal rule (three consecutive underscores): 


> blockquote

[a link to Google](
 Unordered list: 

* list item
* list item
* list item
 Ordered list: 

1. list item
2. list item
3. list item
 This is not a complete list, and is just scratching the surface. As stated earlier, these are what I consider the most common uses. Here is 

a full listing of Markdown syntax.

Useful Tools Being a simple syntax, Markdown can be written by even a basic text editor. There are tools available to speed the process of writing as well as viewing the converted result. I mention three such tools below.


MarkPad is a Metro-style app, first made available earlier this year. It is rather minimal, which to me is fine for the purpose. The appearance is very tidy, and the interface stays out of the way, There is a floating toolbar that appears when text is selected, and offers buttons to format text or create links. The left pane is the raw Markdown and text, while the right pane shows the result.

]5 MarkPad is a Windows-based Markdown editor using the modern UI

MarkPad is developed on GitHub and appears to be actively maintained.


MarkdownPad is a more conventional Windows app, with the standard window chrome and toolbar. The premise is the same is MarkPad, however. Like MarkPad, the left pane is the Markdown view and the right pane is the converted view. The toolbar has buttons for common formatting and linking features, but those are hardly needed when writing Markdown, as the syntax is so simple.

]7 MarkdownPad is an app with a typical Windows interface and toolbar.

It’s good to have choices, and mine is MarkPad, mostly for the simpler interface. Oddly though, it doesn’t have a search function, which MarkdownPad does.


The above editors are useful for writing Markdown locally, but there will be a point where content needs to go online. Since WordPress is my web tool of choice, I started using the

WP-Markdown plugin. Installing the plugin doesn’t add a distinct menu item for configuration; the plugin’s options are added to the bottom of the Settings -> Writing administration section. There are a small number of settings to choose from, none very complicated.

WP-Markdown settings
]10 WP-Markdown provides some basic settings for controlling where Markdown is supported

Once the plugin is configured, it can be seen in action by creating (or editing) an existing post or page. Entering text in the content box will cause a “markdown view” box to appear immediately below with a live preview. Saving the entry and viewing it will show the rendered version in all its glory. In fact, this very post was written using Markdown – see for yourself the result!

WP-Markdown at work
WP-Markdown adds a live preview box below the post content field

Interestingly, the plugin extracts inline link references and lists them at the bottom, as can be done in Markdown, and references each from the corresponding linked text: 1: 2: 3: 4: 5: 6: 7: Link text referencing a link in the list:

[John Gruber][2]
[Markdown: Syntax][3]

Conclusion Markdown is simple enough to grasp, yet it can do a surprising amount of work. Its biggest use is handling basic formatting, which is likely 90% of what HTML is used for in content writing, at least for my uses. I believe I will be using Markdown much more to simplify my writing processes, whether directly into WordPress or in one of the editors mentioned above. I can see the potential for great savings in typing time when creating future web content.