A quick test

MarkDown experiments

Please ignore this post. I’m just learning about [MarkDown syntax](http://daringfireball.net/projects/markdown/basics).

MarkDown is:
* a syntax for writing structured text which is more readable and more writable than straight HTML
* a tool for converting the text into proper HTML on posting

In general, I’d rather store my posts in HTML, I think, but MarkDown seems to be sufficiently widespread (and available as a Perl command-line conversion tool) that I don’t anticipate any problem in getting my data out again if I decide to store it in MarkDown format. Mmmm…

Certainly much easier to write than HTML. And it’s a standard WordPress plugin. You just have to enable it…

Follow-up – I found that the plugin was also used on comments, which confused some people. So I’ve disabled it for now, which is why you can probably see the above as raw markdown source. Fortunately, that’s pretty readable too!

Enjoyed this post? Why not sign up to receive Status-Q in your inbox?

Got Something To Say:

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax


© Copyright Quentin Stafford-Fraser