Wasseem Khayrattee

<p>This is a simple plugin to help you write posts or pages in plain-text Markdown syntax. And even allowing plaint-text Markdown for comments as well. It will also switch-off the Visual Editor, as you don’t need distractions. This plugin sits on top of a giant’s shoulder, namely Jetpack.</p>
<p>This plugin is also installable via composer, see: https://github.com/7php/MarkItDownWordpress</p>
<h3>Roadmap</h3>
<ul>
<li>By default, toggle the checkbox to true for Settings > Writing > ‘Use Markdown for posts and pages’</li>
<li>By default, toggle the checkbox to true for Settings > Discussion > ‘Use Markdown for comments’</li>
<li>In plain-tex editor mode, remove the short-formatting buttons, e.g [b, i, link, b-quote, del].. etc. Make the editor, distraction free.</li>
<li>Make an effort to provide Markdown buttons for the equivalent of [b, i, link, b-quote, del], just like bbcodes.</li>
</ul>


Mark It Down WordPress!

I just replaced JP Markdown (which is abandoned by now) with this plugin. The switch was easy and painless: 


Install this plugin and activate it
Deactivate JP Markdown
Set the flags under "Settings => Writing" and "Settings => Comments"
Done!


The posts written in Markdown are still written in markdown and still rendered as HTML as before, so a smooth transition from my POV.

Thanks!

Works as replacement for the abandoned JP Markdown

Helping you write posts/pages in plain-text Markdown syntax, while switching-off Visual Editor. It sits on the shoulders of a giant, namely Jetpack.

<p>Powerful, flexible, XHTML-compliant, server-side code highlighting, credits for everything<br />
but ‘making it a plugin’ go to <a href="http://jpipes.com/index.php?/archives/216-Syntax-Highlighting-and-Allowing-HTML-in-Comments.html" rel="nofollow ugc">Jay Pipes</a><br />
and <a href="http://geshi.org/" rel="nofollow ugc">GeSHi</a>.</p>
<h4>Features</h4>
<ul>
<li>Highlight sources of any language</li>
<li>automatically, server-side (no javascripts)</li>
<li>XHTML-Compliant, <code><div></code>, <code><ul></code>, <code><span></code> with class-attributes and a css-file are used for styling    </li>
<li>optionally add a heading for every code-block</li>
<li>optionally specify line-number offset (BREAKS XHTML COMPLIANCE)</li>
<li>optionally don’t display line-numbers</li>
<li>set per-codeblock if the code is html_entity_encoded or not</li>
<li>only parses <code><pre></code>-tags with the <code>lang=</code>-attribute, thus does not interfere with any regular preformatted contents you might have</li>
<li>degrades beautifully through <code><pre></code>-tags (if you keep the sources clean, that is)</li>
<li>all settings through logical, valid arguments for the main container</li>
<li>comes with generic cross-browser CSS (tested: IE5.5+, FF, Safari, Opera)</li>
</ul>
<h4>Version History</h4>
<ul>
<li>1.3: Thanks to a tipp now the link-path to the stylesheets is correct, sorry for the inconvenience</li>
<li>1.2: Leading whitespace isn’t stripped anymore (indents as well as newlines), when there’s no title the title-div is not being generated anymore</li>
<li>1.1: Solved the issue with single-quotes being changed to typographical quotes</li>
</ul>
<h4>Known Issues</h4>
<p>While the plugin is basically XHTML 1.0 Strict compliant there’s just no way of getting the offset-based line-numbering to display without inadequate (ab)use of javascript and css hacks, so be warned that <em>IF you use the line-number offset, your documents will <strong>NOT</strong> validate</em> because of the forbidden <code>start=</code>-attribute for the <code><ol></code>!</p>
<h3>Documentation</h3>
<p>More on the <a href="http://blog.kno.at/tools/highlight-source-pro/" rel="nofollow ugc">Highlight Source Pro Page</a></p>


Highlight Source Pro

Powerful, XHTML-compliant, server-side code highlighting for pretty much all languages

Mark It Down WordPress! vs Highlight Source Pro