Do you watch a lot of movies or TV Shows? Do you have a WordPress site? You will love Traktivity!
This plugin allows you to log everything you watch inside your WordPress site. You may then use that data for anything you want.
You could display the last few shows you watched in a widget in your sidebar, you could automatically post on Facebook or Twitter whenever you are watching something, or you could just keep that data to find out more about the genres you watch the most, or how many hours you spent in front of the TV last month or last year.
Most importantly, that data is yours, saved in your WordPress site for good.
Working for Automattic is pretty great. Not only is the work fun and challenging, I also get to travel quite a bit. In the past few years, I’ve discovered San Francisco, Pune, Kauai, Dublin, and many other interesting places.
This month I added two more cities to my list: Madrid, Spain, and Albuquerque, New Mexico. I didn’t take many pictures in Madrid, but I know my colleague Donncha will keep adding more pictures from our trip to his photo blog in the next few months. 😊
I did, however, take a few pictures in Albuquerque.
You’ve probably heard about Jetpack’s new Ads module: it allows you to insert ads in your posts, in your sidebar, and in the header of your WordPress site without having to worry about finding the right ad network, managing ad inventory, or worrying about the quality of the ads. It’s available to Jetpack Premium and Professional users.
To use the feature, all you have to do is to click on the toggle under the Jetpack menu in your dashboard. Jetpack takes care of the rest.
However, sometimes you may not be happy with the default placement of the in-post ads: they appear right below the post content. That’s great, but sometimes you may be using other plugins to insert elements in there, like sharing buttons, related posts, subscription forms, …
The code snippet below will allow you to move the ad box exactly where you want it to appear.
Jetpack’s Photon module is a free image CDN that doesn’t require any configuration; as soon you activate it, all the images in your posts and pages will be downloaded, optimized, cached, and served from WordPress.com’s CDN. Magic!
Photon is applied to all images on your site, including images that may hosted somewhere else; if you one day added an image to one of your posts without actually uploading it to your Media Library, that image will be served through Photon too.
However, sometimes you’d rather not serve external images through Photon. After all, these images may already be served via another CDN! Luckily, Jetpack includes a filter to allow you to control which images get served by Photon. In the example below, we’ll only use Photon for images belonging to our site, and make sure none of the images that are not hosted on our site get processed by Photon.
When sharing posts on Facebook, you may have realized that sometimes you can play a video right on Facebook, without having to click and go to another site.
This is possible thanks to Open Graph Meta Tags. When you share a post on Facebook, or when Jetpack Publicize publishes a post to your Facebook page, Facebook crawls the page and looks for Open Graph meta tags in the head to build a complete post preview. That post preview will often include an image, a title, a description, and sometimes a video like on the screenshot above.
Jetpack automatically creates these Open Graph Meta tags for you unless you already use another Open Graph plugin, in which case we let the other plugin handle things.
This is once again a Jetpack add-on, and it’s also another good example of the things you can accomplish with the WordPress.com REST API: Post Views for Jetpack pulls data about your site’s stats, as well as stats for each one of your posts.
This is still a work in progress; I would love to know what you’d like in this plugin, and where you would like to display those post views. Open a new thread in the support forums to let me know!
If you follow WordPress news, you’ve probably heard about the REST API already. We’ve been talking about it for years, and it’s been presented as a revolution within WordPress. That’s all great, but what does it mean in practice?