Markdown: The Ins and Outs

Markdown: The Ins and Outs

Tutorial Details

Markdown is a shockingly simple markup language that allows you to write, using an easy-to-read, easy-to-write, plain text format. This format can then, in seconds, be converted into another markup language, such as HTML!

If you’re not familiar with it, let me teach you about it today!

Markdown does a fantastic job of getting out of the way.

Markdown does a fantastic job of getting out of the way. I'm sure everyone has, at some point, emphasised text in a plain-text document by surrounding the phrase with an asterisk, *like so*. That's exactly how it works in Markdown! Providing extra emphasis (bolding a word) is as simple as **doubling up on the asterix**.

It's no surprise that Markdown's philosophy is to produce content, which can be "published as-is, without looking like it's been marked up with tags."

The benefits should be obvious to anyone who's tried writing web-based content and had to worry about formatting it, too. <em>text here</em> is simply too hard to type, once you're brain is in its flow – not to mention how the frenzy of HTML tags which plague a document can ruin readability while you're proofing a document.

A number of Markdown editors exist, both web and desktop-based, but you can, of course, use any old text editor. The only benefit that specific Markdown editors provide is a live-preview of the generated HTML, and, typically, some level of syntax highlighting.

If you want to try out the examples below, refer to the official Dingus browser-based converter.


The Markup

Paragraphs

With Markdown, text is automatically converted into paragraphs where blocks of text are separated by a blank line. And not just by several <br> tags like WYSIWYG's of days-gone-by, but real semantic <p> paragraphs. It's almost like black magic.

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed
do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris
nisi ut aliquip ex ea commodo consequat.

Duis aute irure dolor in reprehenderit in voluptate velit
esse cillum dolore eu fugiat nulla pariatur. Excepteur sint
occaecat cupidatat non proident, sunt in culpa qui officia
deserunt mollit anim id est laborum.

Simply becomes:

<p>Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed
do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris
nisi ut aliquip ex ea commodo consequat.</p>

<p>Duis aute irure dolor in reprehenderit in voluptate velit
esse cillum dolore eu fugiat nulla pariatur. Excepteur sint
occaecat cupidatat non proident, sunt in culpa qui officia
deserunt mollit anim id est laborum.</p>

One small oddity with Markdown is how single line breaks are handled. The Markdown philosophy is that the browser should handle line breaks, and no-one else. So the following text:

Lorem ipsum dolor sit amet, consectetur.
Adipisicing elit, sed do eiusmod tempor incididunt.

Becomes, quite jarringly:

<p>Lorem ipsum dolor sit amet, consectetur. Adipisicing elit, sed do eiusmod tempor incididunt.</p>

If you absolutely must insert a line break, a work-around is provided: simply add two spaces to the end of the previous line, like so:

Lorem ipsum dolor sit amet, consectetur.<space><space>
Adipisicing elit, sed do eiusmod tempor incididunt.

A number of Markdown "flavors" can handle line breaks in ways you'd expect, but more on that later.

Headings

Begin a paragraph with a #, and that paragraph becomes a header. The number of # signifies the heading level number (<h1>, <h2> etc.)

# Heading One
This is a paragraph. Lorem ipsum dolor sit amet, consectetur
adipisicing elit, sed do eiusmod tempor incididunt ut labore
et dolore magna aliqua. Ut enim ad minim veniam.

## Heading Two

This is a paragraph. Lorem ipsum dolor sit amet, consectetur
adipisicing elit, sed do eiusmod tempor incididunt ut labore
et dolore magna aliqua. Ut enim ad minim veniam.

### Heading Three
#### Heading Four
##### Heading Five
###### Heading Six

Becomes:

<h1>Heading One</h1>
<p>This is a paragraph. Lorem ipsum dolor sit amet, consectetur
adipisicing elit, sed do eiusmod tempor incididunt ut labore
et dolore magna aliqua. Ut enim ad minim veniam.</p>

<h2>Heading Two</h2>

<p>This is a paragraph. Lorem ipsum dolor sit amet, consectetur
adipisicing elit, sed do eiusmod tempor incididunt ut labore
et dolore magna aliqua. Ut enim ad minim veniam.</p>

<h3>Heading Three</h3>
<h4>Heading Four</h4>
<h5>Heading Five</h5>
<h6>Heading Six</h6>

An alternative syntax is also provided for <h1> and <h2>, like so:

Heading One
===========
This is a paragraph. Lorem ipsum dolor sit amet, consectetur
adipisicing elit, sed do eiusmod tempor incididunt ut labore
et dolore magna aliqua. Ut enim ad minim veniam.

Heading Two
-----------
This is a paragraph. Lorem ipsum dolor sit amet, consectetur
adipisicing elit, sed do eiusmod tempor incididunt ut labore
et dolore magna aliqua. Ut enim ad minim veniam.

Blockquotes

One of Markdown's major influences is plain-text email, and this is blaringly obvious, when you see that blockquotes are formatted exactly as they are in email: prefixed with a >:

This is a normal paragraph.

> This is a blockquote paragraph.

> And the blockquote continues here, too.

…Which converts to:

<p>This is a normal paragraph.</p>

<blockquote>
    <p>This is a blockquote paragraph.</p>
    <p>And the blockquote continues here, too.</p>
</blockquote>

Code

You can deliminate small inline code snippets, using the ` character around code.

Larger blocks of code can be defined by simply indenting the code up a level (at least one tab/four spaces) – the indentation level will be removed. Markdown automatically escapes all special characters inside a block of code, meaning that you can safely just copy in blocks of code without manually escaping < to &lt; and > to &gt; etc.

This is a paragraph with a bit of `<strong>CODE</strong>` in it.

    <?php
    $name = $_GET['name'] ?: 'World';
    echo "Hello $name & everyone else!";
    ?>

Another paragraph, but with a code block above it.

<p>This is a paragraph with a bit of `<strong>CODE</strong>` in it.</p>

<pre><code>&lt;?php
$name = $_GET['name'] ?: 'World';
echo "Hello $name &amp; everyone else!";
?&gt;
</code></pre>

<p>Another paragraph, but with a code block above it.</p>

Lists

Another true example of how Markdown just comes naturally is in how you specify a list. Simply start a paragraph with a * (or +, -) to create an unordered list. Use numbers, 1., 2. etc. for ordered lists:

I will need:

* Snakes
* Scorpions
* Hamsters

Then, I can begin my plan to rule the world:

1. Aquire hamsters  
2. Train snakes to ride hamsters  
3. Rule the world

<p>I will need:</p>

<ul>
    <li>Snakes</li>
    <li>Scorpions</li>
    <li>Hamsters</li>
</ul>

<p>Then, I can begin my plan to rule the world:</p>

<ol>
    <li>Aquire hamsters</li>
    <li>Train snakes to ride hamsters</li>
    <li>Rule the world</li>
</ol>

Inline Text Elements

We already covered italicising and bolding text at the start of this article (* and **), however, you can also swap the astericks for underscores, if that's more your thing:

Here's some *italic* text, and more _italic_ text. Some **bold stuff** here; plus a __little__ bit more.

Links are nice and simple in Markdown (if you can commit to memory whether it's the square and round brackets which come first…):

[Google](http://google.com)
<a href="http://google.com">Google</a>

To display an image, prefix the link code with a !:

![The Google Logo](http://google.com/logo.png)
<img src="http://google.com/logo.png" alt="The Google Logo">

Markdown Doesn't Get In Your Way

Markdown is very lenient, when it comes to breaking out of its markup and just using HTML instead. If you need to include a table, include it in HTML. Or, if you'd rather write your links in HTML-format, you can do so. Markdown is smart enough to know when you mean to include HTML, and it works around it.

Markdown also auto-escapes characters, such as &, < and > into the HTML entity form. It even intelligently converts common character combinations into what you really mean.

  • Three dots will automatically become an ellipsis: …
  • Two hyphens will become an en-dash: –
  • Quote marks will become the "fancy", curled versions of themselves.

Flavours & GitHub Flavoured Markdown

A number of alternative Markdown "flavours" exist, which extend the default set of Markdown rules. A common extension is easy line-breaking, as described above. One of the most well-known Markdown flavours is GitHub's Flavoured Markdown. This is used to markup user input everywhere on their site. As well as including improved line-breaking support and a number of customisations specific to GitHub, my favourite feature is their alternative to code fencing, which also allows you to specify a syntax for highlighting. Simply surround a code block with ``` on either side, including the language at the start, like so:

```php
<?php
$name = $_GET['name'] ?: 'World';
echo "Hello $name & everyone else!";
?>
```

Conversion

The Tuts+ Markdown converter can be found here.

The official converter is written in Perl, and is available for download on the Markdown homepage at Daring Fireball. Several other Markdown converters also exist, for a multitude of different languages – from C…to Ruby… to JavaScript… to PHP. A full list of implementations can be found on Wikipedia.

One popular Ruby implementation is RedCarpet, based on the C library, Sundown, which provides a very simple way to customise the output of the generated HTML to produce your own "flavour" of Markdown.

Recently, I used this library to created a Markdown converter, which accepts GitHub Flavoured Markdown (to allow specifying a code language for syntax highlighting), and outputs the converted HTML in the specific style required by the Tuts+ sites. The Tuts+ Markdown converter can be found here. If you’ve ever written a tutorial for this site, definitely use it!

In fact, this article was written in Markdown, using the popular Mou Markdown editor for OSX.

Dan Harper is danharper on Themeforest
Tags: markdown
Note: Want to add some source code? Type <pre><code> before it and </code></pre> after it. Find out more
  • Zach

    Hello! There appears to be a small problem with the example for headers.

    This markdown:
    ### Heading Three
    #### Heading Four
    ##### Heading Five
    ###### Heading Six

    Would not produce this markup:

    <h3>### Heading Three</h3>
    <h4>#### Heading Four</h4>
    <h5>##### Heading Five</h5>
    <h6>###### Heading Six</h6>

    Otherwise great article. I have been using markdown for several client projects, and they seem to prefer it to learning the html they would need otherwise.

    Cheers!

    • http://dagrevis.lv/ daGrevis

      # H1

      Should produce:

      H1

      And so…

      That’s how it should work.

      If you want to get header with contents of ‘# H1′, just type:

      # # H1

  • Robert Smith

    Nice one. Good review on the basics.

  • http://blog.sklambert.com/ Steven

    Good article. If you’ve used a Wiki before, the syntax of Markdown should be fairly familiar. It’s nice to be able to have something clients can easily use to create new pages and content without needing them learn HTML.

  • http://grantpalin.com Grant Palin

    I recently started writing web content in markdown to handle the bulk of the basic text formatting. Yes markdown is basic, but it probably covers 90% of most text formatting needs for the web. It is possible to intermingle raw HTML with markdown, as needed, to handle e.g. tables and forms. That aside, formatting text in markdown is waaaay faster than HTML.

    I also found a couple of nice Windows-based editors. One is Markpad (http://code52.org/DownmarkerWPF/), a metro-style app. It offers a basic toolbar with common formatting options, and not a lot else. Though it can apparently connect to remote blogs. Features a split view, with a markdown view and a live preview.

    The other is MarkdownPad (http://markdownpad.com/), a more conventional app that offers more formatting buttons. Though with markdown, there’s not much point! Also has the split-view editor.

    The apps are both good, but I like the former simply because it’s simpler, and writing in markdown doesn’t require much assistance anyway.

  • http://www.jeffscottward.com jeffscottward

    Thanks for the article, but no thanks for markdown. Why would I ever bother learning this? Unless I’m writing a blog post I have absolutely zero need for this. And even at that I would still prefer HAML/JADE to make it functional. In this day and age, I don’t see a need to write stuff out in anything other than HTML or a pre-compiler.

    • http://envexlabs.com Matt Vickers

      Closeminded-ness aside, You can alos use this to allow users to format posts/comments without having to input html.

    • Pat

      So obviously Github is doing it wrong? Each and every project on Github has a README.md file to describe it.

  • http://wouterj.nl Wouter J

    Nice for beginners!

    But you forget to talk about a thing which I find very useful: HTML code. Markdown allows you to use HTML code in you Markdown syntax. For instance, a line break can also be done like this:

    Lorem ipsum dolor sit amet, consectetur.<br>
    Adipisicing elit, sed do eiusmod tempor incididunt.

    And other HTML tags can also be used inside the MarkDown.

  • Mark Out

    Nice tut … thanks. But … why does the comment area *not* allow Markdown? That woulda been _sweet_!

  • Sebastian

    Hi,

    nice articel – I have used markdown for some month now to right everything and now I can give people a well formated PDF instead of my self-markuped texts :)

    In the Code section the generated HTML can’t be right.

    The first paragraph is not generated – the “`” arround the strong-Tags wouldn’t make any sense.
    My markup generator gets for this input:

    this is a paragraph with a bit of `CODE` in it.

    this output:

    this is a paragraph with a bit of <strong>CODE</strong> in it.

    Another paragraph, but with a code block above it.

  • Felix

    _markdown is awesome_

    *fo real*

    not working?

  • http://www.bluedotsdesign.com Alberto Villalobos

    Awesome if this works is goint to speed my code time a lot !!! thanks!

    • http://28inch.co.uk 28inch

      Markdown isn`t a replacement for html but helps people to write formatted documents in a less “geeky” fashion. If you want something similar for development use haml or zen coding.

    • http://www.techna2.com/blog Neerav

      If you really want to speed up your coding, try zen coding instead. I use sublime text 2 with zen coding package and it is really worth try.

      Markdown is not for coders its for end users who are not as comfortable with HTML as coders, IMO.

      • LaPingvino

        But surely for coders too. In combination with Pandoc you can for example write your documentation in it ;).

  • http://www.leachcreative.com Andrew

    Thanks for sharing this with us. This seems to be a pretty interesting bit of code, I’ll hold off on using it for now though.

  • Giuliano

    To me this looks more like tool for content editors, not developers. Cool concept though.

    • http://dagrevis.lv/ daGrevis

      It is for content editing.

  • http://dagrevis.lv/ daGrevis

    Please fix your article! Markdown will not replace, as you did state, ‘–’ to ‘—’ and so. The tool that does that is called SmartyPants (http://daringfireball.net/projects/smartypants/).
    It’s created by the same author though.

    • http://danharper.me Dan Harper
      Author

      Ah, I’ll sort that. For some reason I thought they were the same.

  • http://dankruse.com Furley

    There is also a great OSX app for writing markdown call Mou.

    • http://danharper.me Dan Harper
      Author

      That’s my favourite editor. Mentioned it in the article :)

  • http://www.seelooh.com Chris

    Interesting..but that’s about it. My train of thought flows just fine formatting stuff with HTML as I type it. Sure it could help save a few seconds on things like lists. But in the end it’s just another thing you have to teach yourself that doesn’t really seem to be of that great of a benefit.

    I guess it depends on who you are, but for me…this is interesting and that’s it.

    • http://inkwell.dotink.org Matthew J. Sahagian

      Markdown is extremely useful for those who don’t totally grasp HTML but want to create content for a web page. Furthermore, one of the ideas behind MarkDown as far as I know is that it’s much more naturally readable.

      I find it particularly useful for documentation as you produce both text and HTML documentation in one go.

      Extended versions of Markdown for example support table creation… looking at an ASCII style table in Markdown beats the hell out of staring at it in non-rendered HTML. I can train someone in markdown in about 5 minutes, HTML would take days… so building a CMS and avoiding the nasty code outputted by WYSIWYG HTML editors makes things both lighter and easier for users.

    • http://danharper.me Dan Harper
      Author

      I find it very hard to believe that anyone is completely comfortable writing HTML as they’re writing. When you’re writing and in the flow, you’re getting words down as fast as possible. When you stop to add in, for example, your train of thought slows down.

      For that reason many authors will forgo any formatting to just get the words down. Then go back and format later. I find Markdown to be a perfect middle ground. For example, everyone has emphasised words with a * at some point. And 1 character beats 8 any day.

  • http://inkwell.dotink.org Matthew J. Sahagian

    Markdown is great, except standard markdown is pretty limited. GitHub flavored Markdown was what got me to really love Markdown. Once I started loving it, primarily by working with it for the Wiki to my main project I decided to write my own little wiki system with it.

    The markdown is nearly 100% compatible using PHP Markdown Extended and PHP Markdown Extended Extra to come almost feature complete with GitHub’s flavor (which I think is implemented in Ruby).

    The wiki system uses highlight.js, google fonts, and fam3 iconset to produce a simple, usable, and nice looking wiki. You can literally have it running locally on your system in about 30 seconds if you have PHP 5.4:

    git clone -b kwiki –recursive git://github.com/dotink/inKWell.git kwiki
    php -S localhost:8080 -t ./kwiki/

    Visit: http://localhost:8080/wiki/

    • http://inkwell.dotink.org Matthew J. Sahagian

      Looks like the comment system replaced the *two* dashes in front of recursive with a long dash, so if anyone is having trouble getting the git command working above it’s two dashes in front of the recursive argument.

    • http://wouterj.nl Wouter J

      Or use -r and not –recursive.

      • http://inkwell.dotink.org Matthew J. Sahagian

        I think that’s only available as an alias in newer versions of git. At least, it’s not documented in the version I’m running on my mac, 1.7.8.2.

  • http://webduos.com WEBDUOS

    What’s up to every one, it’s truly a fastidious for me to pay a visit this site, it includes priceless Information.
    Thanks for this

  • http://wouterj.nl/ Wouter J

    If you want to write an article for Nettuts+ and you prefer to use Markdown: Use the Tuts+ Markdown Converter, created by Dan Harper, which convert MarkDown syntax to a HTML syntax which support all classes, styles and elements to create a nice Tuts+ article.

  • FilipBenes

    It looks very similar to Texy! http://texy.info/en/
    IMHO Texy! can offer more options :)

  • wafiq

    My first thought is more unnecessary garbage that’s supposed to speed up your workflow. The download link says 2004 on their site, is it really that old? if so i cant be that helpful cause i never heard of it before now.

  • David D’hont

    I prefer BBCode over Markdown any day.

    • http://danharper.me Dan Harper
      Author

      BBCode still sticks to the concept of “tags”. [b] == <b>

  • FireDart

    This honestly sounds like more work. Not say it’s bad, some people may like it more. The way it handles php (converting it so it’s in tags) is cool but past that am not really impressed.

    Anyone else agree?

    • http://danharper.me Dan Harper
      Author

      I fail to see how this is possibly more work?

      • http://inkwell.dotink.org Matthew J. Sahagian

        @Dan, 100% in agreement that it is *not* more work.

        Markdown has allowed me to seriously write documentation at nearly 10 times the speed, for no other reason than fenced code blocks means I don’t have to worry about encoding my HTML Entities.

        But much more importantly, it just flows. The one thing I wish I could do which I can’t (at least with the implementation I use) is put markdown indented in some structural HTML. I can keep it all left aligned and it works so long as I have line breaks between the HTML and the markdown.

        I think there might be some confusion on @FireDart’s part as to what the purpose of this is (as well as some confusion of others here).

        For those that think BBCode is easider… it’s simply not. BBCode might as well be HTML. As far as I can tell it was created because people lacked a way to safely pull HTML from a comment system into their site. HTMLPurifier is perfectly fine for this now, so as far as I’m concerned the choice is simple.

        If you want something more flexible and full featured and are OK with the complexity, allow HTML and filter it with something like HTMLPurifier. If you want something that is simple, natural, and intuitive (so much so that people might use it without even realizing it — as is the case with lists), go with Markdown.

  • Mario

    This is extremely pointless and offers little to no benefit over simply writing your own markup, like HTML. Just my opinion.

  • http://mufid.github.com Mufid

    Nice article! I agree for practically markdown could make writing markup easier than before, and could be done without any tools. And the good side: it will be beautifully converted into rich text format.

    But for me, markdown need some improvement. For example, markdown can’t deal with table. I prefer REST Markup for this case.

    http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html

    • http://inkwell.dotink.org Matthew J. Sahagian

      Standard Markdown cannot… however, Markdown Extra can:

      http://michelf.com/projects/php-markdown/extra/

      Pretty much any modern implementation of Markdown should be able to support this. The markdown parser I use in “kwiki” (see comment above) is a combination of standard Markdown, Markdown Extra, and Markdown Extra Extended.

      Outside of structural markup and newer HTML5 elements, I’m not really sure there’s anything I can’t do with Markdown.

      • http://mufid.github.com Mufid

        Thanks matthew! I just know about it!

  • http://github.com/willemmulder Willem Mulder

    Nice introduction to Markdown!

    But what will the scorpions be used for in taking over the world?

  • Jonny

    If there’s one thing I still struggle with, constantly, it’s with strange non-standard characters. I can never seem to completely strip or replace whacky characters, and people like to paste in copy from strange places with strange encoding.

    An extensive tutorial on that subject would be invaluable.

  • Jonathan

    I have started using Markdown as an alternative to WYSIWYG editors in content management systems. It’s a little bit of extra learning for the user, but in the end product makes it worthwhile.

    To do the conversion to HTML I use PHP Markdown—I highly recommend it.

  • David

    Where is the MarkDown source for this article?

  • http://hizup.com Anton

    Thanks!

  • MIke

    I am surprised no one has mentioned Multimarkdown, which does tables etc as well (mentioned above) and a number of extra features, including footnotes etc. It includes Markdown as a subset, so you can use it just with Markdown.

    Also, Multimarkdown is Windows-friendly. The text to html executable runs out of the box on Windows, no need to have PHP or Perl or anything else installed. I have found most other Markdown extensions are not Windows-friendly, and are a hassle to get working in Windows

  • RoelErick

    Personally, I prefer txt2tags above markdown. Having said that, both (and there are a lot of others too) do basically the same thing. Helped me very much, I use it to write documentation for my computer programs.
    Some people here seem to think this is to replace web programming. It is not.
    But it is very good for writing static documents. It lets you concentrate on the contents without worrying about formatting, because you specify what sth is, not how to display it; and in a very simple and non- intrusive way. It really does not get in your way.

    I like txt2tags better because it does tables, can produce more output formats (laTeX! and indirectly, PDF), and is more extensible.

  • minot

    Sorry, html is *not* that hard that it requires anything like this… what a waste.

    • http://inkwell.dotink.org Matthew J. Sahagian

      Try telling people without an ounce of technical skill that. Even for coders, however, while HTML is “not that hard”, it can still be a kink in a smooth workflow.

      Some people here are missing the boat. The irony of your post is that if these comments supported markdown your “not” would have been emphasized — without you having even thought about it.

      Again, it’s a question speed and intuitiveness, not difficulty.

  • http://twitter.com/teaneedz teaneedz

    I’m using Markdown everywhere. It really is for everyone, including coders – when the entire user experience matters. Writing documentation, blogging, communicating with clients, simplifying the work flow. For me, it makes writing anything more enjoyable. It keeps me focused on the content.

    # Anytime, Anyplace
    If there’s a text box, with a quick keystroke, I pull up BBEdit and start writing away. Markdown is my default language for BBEdit now. Then CMD-S and what I’ve written is placed into the text box.

    Even when I’m handcrafting HTML, *markdown* is never too far away.

    I’m addicted.

  • chrismccoy

    good article, i must admit i been doing it by cheating, doing it up in html code then using the html2markdown linux util ;)

  • http://@nicholascamp Nicholas Camp

    What if I want a different , doctype, scripts at the bottom, etc?
    Does exists a way to convert only the text between somewhere I define, like ?
    Thanks!

  • Ian Perkins

    Markdown is very useful – for certain things.

    Example – I’m moving house so all my packing lists are written in Markdown on an iPad using Texttastic and syncd to Dropbox.

    The lists are perfectly readable in any text editor with almost no effort required to add the simple formatting I need (headers and lists and some emphasis). Maybe one day I’ll convert them to html, maybe not – the point is that I could and the more stuff I have in Markdown, the more stuff I have that is portable – the clue is in your opening paragraph where you say “…be converted into another markup language, **such as HTML**” (emphasis mine). So I could take my Markdown files and convert them to [insert future markup language name here].

    My view is, if I am writing text then I don’t want non-portable formats like .doc, I just want plain text files and Markdown _is_ just plain text.

    Some folks here seem to have the impression that it is something to consider when coding html – IMO this is specifically what it is not for and indeed would be an unnecessary hurdle. If your only need is html and the only way you will see it is in a browser then just write html. Easy as that.

  • http://www.agilewebsitedev.com/ Pali Madra

    Personally I think Markdown is a big help if you are writing lot of documentation or blogging.

    I had a question. If I wanted to insert a link is it possible to add the “target=_blank” attribute? If not then is there a way I can I create a flavor of Markdown which allows me to do that?

    I did see that there are other alternatives like Multimarkdown. Is that any better?

    Thanks

  • http://www.bluesmoke.ro Daniel

    I just don’t get it! Why would anyone need Markdown? I’ve read several articles and I still can’t understand what is it used for… Maybe I’m too noob to understand. Would someone explain to me?