producing well-formed HTML. This means that em and strong nesting is important, as is the ability to output as both HTML and XHTML
having an intermediate representation to allow processing of parsed data (we in fact have two, both JsonML: a markdown tree and an HTML tree)
being easily extensible to add new dialects without having to rewrite the entire parsing mechanics
having a good test suite. The only test suites we could find tested massive blocks of input, and passing depended on outputting the HTML with exactly the same whitespace as the original implementation
The simple way to use it with CommonJS is:
var input = "# Heading\n\nParagraph"; var output = require( "markdown" ).toHTML( input ); print( output );
If you want more control check out the documentation in lib/markdown.js which details all the methods and parameters available (including examples!). One day we'll get the docs generated and hosted somewhere for nicer browsing.
We're yet to try it out in a browser, though it's high up on our list of things to sort out for this project.
Internally the process to convert a chunk of markdown into a chunk of HTML has three steps:
Parse the markdown into a JsonML tree. Any references found in the parsing are stored in the attribute hash of the root node under the key
Convert the markdown tree into an HTML tree. Rename any nodes that need it (
ulfor example) and lookup any references used by links or images. Remove the references attribute once done.
Stringify the HTML tree being careful not to wreck whitespace where whitespace is important (surrounding inline elements for example).
Each step of this process can be called individually if you need to do
some processing or modification of the data at an intermediate stage.
For example, you may want to grab a list of all URLs linked to in the
document before rendering it to HTML which you could do by recursing
through the HTML tree looking for
Released under the MIT license.