Back in September I wrote about the Markdown on Save plugin by Mark Jaquith. The plugin is still awesome, but there’s a few things about that I wish were done differently.
Last week I switched to Markdown through Jetpack, and I highly recommend it.
About Markdown on Save
What makes Markdown on Save so awesome is that it uses the undocumented
post_content_filtered database column to store your markdown. On save, it converts your content to HTML and saves it in the regular
If you ever remove the plugin, all of your content is already saved in regular HTML, right where it should be. And because it’s converted ahead of time, there’s no latency on the front-end like you might experience with some other plugins.
What always bugged me was that it required you to choose markdown as your writing format every single time. There was no way to make that the default, which is silly, because you can use markup in markdown. There’s no downside to making it the default.
Markdown on Save also hides the editor shortcuts, and only applies to posts, not comments.
Markdown in Jetpack
Jetpack, the uber-plugin from Automattic, includes an optional markdown extension. It works exactly the same way as Markdown on Save, so if you ever remove it, your left with valid HTML. You can also apply it to comments, which makes it a lot easier for visitors to share links, code and more.
The one downside for me is Jetpack itself. Jetpack does a lot of stuff, and most of it is turned on by default. Many of the default features are, from my perspective, site bloat—stuff like social sharing buttons and script heavy graphic treatments.
I would prefer to see those off by default, or even better, as standalone plugins that you can install and uninstall via Jetpack.
Jetpack also forces you to connect your site with WordPress.com, even if you’re not going to use any features that make that require that to function. Why not make that a requirement only when needed?
All that said, the plugin is worth it for markdown support alone. Check it out.