php-markdown-extra-extended - my humble attempt at extending php-markdown

Egil Hansen egil at
Thu Jul 14 16:26:50 EDT 2011

I guess it is always a case of keeping Markdown "pure" or adding
support for attributes/classes when it is practical.

In my scenario, I had a customer who did not like to use any HTML in
their input, but still wanted to be able to tell the CMS back-end that
a specific paragraph was a disclaimer, that a specific paragraph
should be centered, that an image should be left or right floated,
etc. So the solution was to use the syntax {disclaimer} after a
paragraph, or {center}, {left}, {right}.

Its a compromise, that stays true to the Markdown syntax, and don't
introduce a new confusing html syntax in the mix.

That was my original motivation.

- Egil

>    The rule of thumb I try to follow when doing extensions can be found

> at the very top of the Markdown project page

> (


> "Markdown is a text-to-HTML conversion tool for web writers. Markdown allows

> you to write using an easy-to-read, easy-to-write plain text format, then

> convert it to structurally valid XHTML (or HTML)."


>    I do not think that the :{ words } extension is easy to read or write.

>  And I can't see how claiming it's the Latest Craze in Port Royal (tm Capt

> Bogg & Salty) addresses those concerns.     If I want power, why shouldn't I

> just write a chunk of raw html?   Markdown supports that natively and it's

> no less readable than :{ words } is.


>    -david parsons

> _______________________________________________

> Markdown-Discuss mailing list

> Markdown-Discuss at



More information about the Markdown-Discuss mailing list