post-page

Faster blogging through Markdown

8
responses
by
 
on
April 11th, 2007
in
LinkyLoo, WordPress Tips

Faster blogging through Markdown takes you through writing posts using Markdown. Markdown is an easy to use plugin that lets you use simple text to automatically generate HTML for ordered lists, italics, bold, blockquotes etc.

heading
heading
8
Responses

 

Comments

  1. LiewCF (8 comments.) says:

    one of the reasons I do not use this kind of plugin is because my blog have to stick with it in the rest of the lifetime. Else, the post is unreadable.

  2. Shayne Power (1 comments.) says:

    I disagree. While it might look a little strange if you have the plugin turned off, it is definitely _not_ unreadable. In face, that is the whole point of markdown.

    From [daringfireball.net][1]:

    > The overriding design goal for Markdown’s formatting syntax is to make it as readable as possible. The idea is that a Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions. While Markdown’s syntax has been influenced by several existing text-to-HTML filters, the single biggest source of inspiration for Markdown’s syntax is the format of plain text email.

    I am assuming that you were able to read this post, marked (down, not up) completely in markdown syntax.

    [1]: http://daringfireball.net/projects/markdown/

  3. LuckyLily (1 comments.) says:

    this look like a useful plugin, just hope things could b much more easier than this….in dealing with html…of course..

  4. Ben M says:

    Too bad the link above is for the version bundled with Turbocharged. Almost all of the Turbocharged plugins are available for free from the developers’ websites, such as Markdown at michelf.com.

  5. m0n5t3r (1 comments.) says:

    unfortunately, Markdown is not a very good choice… or I’ve only met bad parsers until now (including the one at wordpress.org/extend/plugins):
    * the way it uses indentation is inconsistent (you _may_ indent your lists, and I’d rather do that because it improves readability, but then you risk having them identified as code)
    * the formatting syntax is reasonable (I’ve seen much worse), but quite not at the level of elegance the Trac/MoinMoin wiki syntax has
    * the url syntax looks funny
    * lists formatted like this one are parsed into a total mess (again bad indentation processing)
    * poor nested list support (have to change the marker, instead of simply indenting stuff at the appropriate level, and then can’t really indent things to make things visible because of the 4-space-indent-means-code thing…)

    Oh, and of course, once you’ve chosen one of these alternative markups you would have to stick with them… or get a smart plugin that can tell the difference (textcontrol should do, it has a per-post custom field that tells it what to employ for rendering, it would be hard to automatically determine whether a bunch of text is Markdown, Textile 1 or 2, HTML or some wiki-style syntax)

    Maybe I’m too much affected by the Python mindset about the indentation thing and the decision to make Markdown like it is now was actually reached after a lot of thinking (<troll> a lot of drinking and a lot of thinking</troll>).

  6. David Russell (32 comments.) says:

    Any theoretical speed advantages of using this are outweighed by the speed disadvantage of having to learn an entirely new markup system. I can look at basic (X)HTML formatting and tell you what the end result will look like – I couldn’t make the same promise for Textile or Markdown.

    Besides which, LiewCF’s point stands: you are locked into using this plugin, and WordPress, for the rest of your life (or at least, the lifetime of your blog). Sure, Markdown-formatted posts presented without the Markdown plugin will be readable, but they will lose all formatting (therefore one is less likely to want to read them).

  7. Rudd-O (5 comments.) says:

    Well, from my point of view, Markdown is pretty good. The cheat sheet for markdown fits in one screenful, while … have you ever seen a cheat sheet for HTML? HTML authors also run the risk of writing invalid HTML. And the greater-than/less-than signs are definitely in an awkward spot on the keyboard.

  8. Ryan B (1 comments.) says:

    I was all for this when I saw this plugin. I am not the world’s fastest typer and don’t always trust the RTE. But the way some things are done make me uneasy.
    As somebody else said, you have to stick with this for life. People (who don’t know the syntax) will get the dashes for lists but will get confused with the bold and italic markings.



Obviously Powered by WordPress. © 2003-2013

page counter
css.php