Comments for Jetpack for WordPress

Comment on Let Users Showcase their Posts with Featured Content by Ryan Cowles

Ryan Cowles — Fri, 21 Feb 2014 01:14:45 +0000

Good question, Paul! Sticky posts are designed to keep posts at the top of the front page (#), whereas Featured Content is a little different. It allows theme authors to choose where and how the Featured Content is displayed. So, you might use sticky posts to keep an important announcement at the top of your blog page, and you might use Featured Content to create a post slider for your homepage. In addition to that, when using Featured Content, your front page will not be full of unnecessary sticky posts if you switch themes. I hope this helps clear things up!

Comment on Let Users Showcase their Posts with Featured Content by Ryan Cowles

Ryan Cowles — Wed, 19 Feb 2014 19:09:39 +0000

Howdy, Jann! Thanks for the feedback. It’s tough to say how often the Featured Content should be changed, as every site is different. It’s really up to the user to decide.

Comment on Let Users Showcase their Posts with Featured Content by Paul

Paul — Wed, 19 Feb 2014 14:45:07 +0000

What are the advantages to using featured content over sticky posts?

Comment on Jetpack 2.8: Introducing Markdown and Improving Monitor by Ryan Cowles

Ryan Cowles — Tue, 18 Feb 2014 18:49:00 +0000

Howdy, Khürt! I imagine it depends on how your current plugin stores its Markdown. Which plugin are you using? Just let me know, and I can look into it further.

Comment on Let Users Showcase their Posts with Featured Content by Jann @ Austin Details Art + Photo

Jann @ Austin Details Art + Photo — Tue, 18 Feb 2014 18:45:11 +0000

Thanks for another great idea for keeping it fresh. One question: How often do you recommend changing up the featured content?

Comment on Jetpack 2.8: Introducing Markdown and Improving Monitor by Khürt Williams

Khürt Williams — Thu, 13 Feb 2014 17:12:50 +0000

I currently use another plug-in for Markdown. If I disable that plugin and use the Jetpack Markdown feature will existing Markdown post be updated?

Comment on Jetpack 2.8: Introducing Markdown and Improving Monitor by stephenalec

stephenalec — Wed, 12 Feb 2014 01:37:28 +0000

Finally! Been waiting on the publicize for the CPT for the longest time!!!!!!!!

Comment on Jetpack 2.8: Introducing Markdown and Improving Monitor by Ryan Cowles

Ryan Cowles — Tue, 11 Feb 2014 23:11:41 +0000

Thanks for the feedback, Pedro! I'm not sure which plugin you are using, but I do know that SyntaxHighlighter Evolved is supported if it is active. If you'd like, you can open a new "support plugin x with code blocks" Issue here with your suggestion.

Comment on Jetpack 2.8: Introducing Markdown and Improving Monitor by Ryan Cowles

Ryan Cowles — Tue, 11 Feb 2014 22:59:54 +0000

Is Jetpack Markdown global for all users?

Yes, it is. We initially considered making this a user setting, but having multiple authors with/without Markdown enabled on a single document would cause a bit of trouble. Therefore, we decided that it would be better off as a global setting.

Can it be turned on for editing just one post and not another?

Enabling Markdown happens on a per-site basis. So, similar to my answer above, it’s a global setting for all posts.

Will it work on posts published through the post-by-email Jetpack module?

At this time it will not. However, it is definitely something that we’re looking into. I’d recommend keeping your eye out for future updates!

Comment on Jetpack 2.8: Introducing Markdown and Improving Monitor by Ryan Cowles

Ryan Cowles — Tue, 11 Feb 2014 22:50:57 +0000

What happens to existing articles if I enable Markdown?

Existing posts will not be affected when you activate the module. When you edit existing posts, they are then converted through Markdown. But, since Markdown ignores existing HTML, 99% of the time it will make no difference.

Can I control per post to use Markdown or not?

Enabling Markdown is a per-site setting. So, it is either on for the whole site or not. Let me know if you have any other questions!