Jetpack 2.8 Introduces Markdown Module and Adds Publicize Support for Custom Post Types

Markdown has finally made its way to Jetpack after it was added to a couple months ago. The new Markdown module in Jetpack 2.8 gives you the option to write and edit rich text without having to write code or reach for your mouse. If you’re not familiar with Markdown, here’s what it looks like:


That transforms on the front end to look something like this:


Markdown fans will also be glad to know that this feature works on mobile, so you can continue using Markdown when blogging on the go.

The Markdown module in Jetpack also includes all the same features available on, which allows fenced code blocks, inspired by GitHub Flavored Markdown. This produces code blocks within your content, nicely formatted to the language you specify. Jetpack users may even be able to do away with their syntax highlighting plugins in favor of using the new Markdown module.

Publicize Adds Support For Custom Post Types

The other major new feature in Jetpack 2.8 is the expansion of the Publicize module to support custom post types. This should be a relief for users who often publish new entries as a custom post type. Now you can automatically share those new posts to your social networks with one small tweak to the CPT’s ‘supports’ array. The Jetpack team demonstrates the following example to enable the title, editor, Publicize and Markdown:

'supports' => array( 'title', 'editor', 'publicize', 'wpcom-markdown' ),

Improvements to Monitor Module

Lastly, Jetpack’s Monitor module now includes the ability for you to add multiple email addresses for notifications of downtime on your site. This is very helpful for sites that have multiple people available to offer support. With more people getting the notices, you’re much more likely to to be able to tackle your downtime issues in a timely manner.


5 responses to “Jetpack 2.8 Introduces Markdown Module and Adds Publicize Support for Custom Post Types”

  1. Agreed, publicize and markdown are great additions. However, if I publicize to twitter from a CPT there seem to be problems with accessing the post from the shortened address in the tweet – it has https and I get messages from browsers saying they can’t access because of an SSL problem (record too long). A similar tweet from a standard Post is fine and has http not https. Is there something other than setting the ‘supports’ to ‘publicize’ which needs to be added to get round this?


Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

%d bloggers like this: