7 February 2010
[Click to cite this article]
[hide academic citations]
AMA citation:
Jiang W. WordPress Text Flow vs. Markdown. Stone Studio. 2010. Available at: http://wei-jiang.com/it/software/wordpress-text-flow-vs-markdown. Accessed March 12, 2010.
APA citation:
Jiang, Wei. (2010). WordPress Text Flow vs. Markdown. Retrieved March 12, 2010, from Stone Studio Web site, http://wei-jiang.com/it/software/wordpress-text-flow-vs-markdown
Chicago citation:
Jiang, Wei, "WordPress Text Flow vs. Markdown", Stone Studio, posted February 7, 2010, http://wei-jiang.com/it/software/wordpress-text-flow-vs-markdown (accessed March 12, 2010).
Harvard citation:
Jiang, W 2010, WordPress Text Flow vs. Markdown, Stone Studio. Retrieved March 12, 2010, from <http://wei-jiang.com/it/software/wordpress-text-flow-vs-markdown>
MLA citation:
Jiang, Wei. "WordPress Text Flow vs. Markdown." Stone Studio. 7 Feb. 2010. 12 Mar. 2010 <http://wei-jiang.com/it/software/wordpress-text-flow-vs-markdown>
Thank you for your interest.
Michel Fortin reviewed his analysis in how to make PHP Markdown works with WordPress.
It works since a year now, but there have always been many glitches. All this relates to the text flow model WordPress has adopted, which is very powerful but badly adapted to a writing syntax different from HTML. To work correctly, the Markdown plugin must in some way mess with the inner working of WordPress by moving many filters out the way.
Here is his documentation.