One of the greatest plugins you can find for WordPress is JetPack. Basically, the ultimate goal of JetPack is to eventually implement all of the cool features that WordPress.com has that you don’t normally get in a WP.org site. There are a few things to know about JetPack before diving in, though.
JetPack and Multisite
Because WordPress Multisite is really intended to set up multiple siloed sites, JetPack has to be set up individually on each site within your installation. If you have 200 sites in your network, and you want to use JetPack to its full capacity, you will have to go into each individual site and “connect” JetPack to WordPress.com. JetPack is designed this way in order to allow each separate site to be connected with a different WP.com account, but it can be extremely time-consuming if you want them all to be connected to the same account.
However, if you just want to play with some of the JetPack features (the ones that aren’t dependent on WP.com), you can get around this requirement by placing a new constant in your wp-config.php file.
Which Modules Work In Dev Mode?
If you do use the constant above to put JetPack in developer/debug mode, some of the JetPack modules won’t be available for you to use, since they require a connection to an existing WP.com account in order to function. Below is a table showing which modules (as of JetPack 2.3) work in developer mode and which don’t.
|Module Name||Does it Work?|
|Post By Email||No|
|Spelling and Grammar||No|
|Extra Sidebar Widgets||Yes|
|Mobile Push Notifications||No|
Which Modules Are Worth Playing With?
Honestly, I have not had the opportunity to play with all of the modules built into JetPack, yet (some are too new for me to have played with them, others just don’t apply to anything I’m doing), but there are a few that I’ve played with that are really cool:
This module isn’t nearly as full-featured as Google Analytics, but it does offer some cool information about your site. The best part is that the stats can be easily included in your site’s Dashboard. With that feature, the admins of each individual site can get a quick glimpse of what’s happening on their sites without you having to give them access to Analytics or generate a report for them.
Once activated, JetPack will begin tracking some basic information about visits and pageviews on the site. JetPack will count the total number of pageviews, keep track of referrers, track keywords used to find the site, etc.
You can easily configure this module to determine which user roles have the ability to view the stat reports (the Dashboard module and the full report), as well as telling JetPack whether to track logged in users (by user role). This module is also configured, by default, to add a small chart to the Admin Bar for logged-in users, so they can see a really basic bar graph showing recent activity (past 48 hours) on the site or page that they’re viewing.
The Carousel module is fairly new, but it can be absolutely brilliant for use on your site. Instead of fiddling with a bunch of different plugins to implement a nice modal image carousel, you can simply activate this module. The Carousel module automatically hooks into the native WordPress gallery shortcode, causing any clicks within the gallery (which would normally open either the original image file, or take the user to the “Attachment” page for that image) to open a nicely-styled modal window with an image carousel in it. The users can then click forward/backward to view the other image in the gallery.
There are two configuration options for this module:
- What background color do you want to use for the modal window (Black or White)
- Do you want to display EXIF data (if present) with the image
There are a few caveats that go along with this module, though. At the moment, it automatically includes a comment area for the attachments. There is no way to turn this off. If you use this module, users will have the ability to comment on your images (of course, those comments still go through the normal comment-moderation process) and to view comments that have already been published. There are a few issues with this behavior:
- The comment functionality uses AJAX to retrieve the form and to check for comments each time you switch between images. This might start to take a toll on server resources if you’re not careful.
- This can be a little confusing for the user; many users may think that they’re seeing a form they can use to comment on the post/page they’re currently viewing, but they’ll actually end up commenting on the attachment.
- The comment form takes up real estate that could otherwise be used to show a slightly larger version of the image.
If you’re interested in seeing how this module works, you can click on any of the images in the galleries within this post.
This is a fairly new module, so I haven’t played with it extensively. However, it does seem to offer some pretty cool functionality. Basically, instead of displaying a boring grid of images when you insert a gallery into your post or page, the images will be automatically arranged into a nice mosaic-style layout. At the bottom of this post, I’ve inserted a gallery with all of the images from the post so you can see how the Tiled Galleries module lays out the images. You can see more samples of the three different layouts available by checking out the official demo post on WP.com.
Unfortunately, it does not allow you to specify whether the sharing buttons should go above or below the post, but there are a few other nice configuration options.
- Drag and drop services that should be available for sharing
- WP PressThis
- Drag and drop services into a separate area to create one “Share” button that opens a dialog with the available sharing options (like those annoying AddThis buttons)
- Specify what types of buttons are shown
- Icon + Text
- Icon only
- Text only
- Official buttons
- Specify what types of pages and content types should use the sharing buttons (archives, posts, pages, other content types, etc.)
This module can be a real lifesaver. Basically, it adds a new menu item under the “Appearance” menu that allows you to edit CSS. When you visit the new admin page for Custom CSS, you will be greeted with a blank CSS file. You can add your own CSS rules to that stylesheet, and they will be added to your site when the
wp_head() action is fired.
Recently, Automattic added support for LESS and SASS to this module, so you can even write your CSS in one of your favorite pre-processor flavors.
In addition to being able to choose a pre-processor to use with the Custom CSS you write, you can also choose whether you want the custom CSS added to your existing styles (the custom stylesheet will be output after your theme’s stylesheet(s)), or to replace your theme’s CSS (the theme stylesheet(s) will not be output on the page, relying entirely on your custom rules).
Unfortunately, as of right now, it’s difficult to specify which users actually have access to this module. If you are running WordPress Multisite, only Super Admins will be able to use the Custom CSS module; it would be much more useful if there was a way to allow normal site admins the ability to modify the CSS. With that being the case, the same users that have access to the Custom CSS module also have access to edit the original theme files and to install new themes and plugins (and, more than likely, have the ability to upload custom mu-plugins if necessary). However, if normal site admins had the ability to make these changes, you could easily turn on a common theme and allow them to make minor changes to the appearance of their sites.
In the case of the University of Mary Washington, we’re using a custom child theme of Genesis, which also allows us to add some custom CSS. The difference is, within Genesis, the site admins themselves have access to these settings, so it’s much more extensible than the JetPack module. In a pinch, though, especially if you’re used to using SASS or LESS, the Custom CSS module in JetPack can be extremely useful.
The portions of this module that aren’t already implemented through WordPress’ native oEmbed support are:
- Audio – with this module, you can now embed an audio file (mp3, etc.) and have it rendered on the front-end as a player, rather than just a link to the file
- Ted – embed TedTalk videos (does not yet seem to be supported through native oEmbed support)
- Bandcamp – embeds audio from Bandcamp.com
- Gallery slideshows – allows you to turn a native WordPress gallery into a nice slideshow/carousel (different from the “Carousel” module mentioned above – this actually replaces the gallery grid with a slideshow, rather than requiring the user to click on one of the gallery items to open a carousel)
- Archives – allows you to embed an archive of posts within a page or post
- GoogleMaps – embeds a Google map
Extra Sidebar Widgets
This module adds a handful of new widgets that you can place in your widgetized areas. At this time, there are three new widgets implemented by this module:
- RSS Links Widget – displays links to your site’s RSS feeds
- Twitter Widget – displays your Twitter timeline (requires configuration on Twitter before using – thanks to the new Twitter API)
- Image Widget – allows you to display an image from your media gallery within your sidebar
In my opinion, the only widget in this pack that’s really worth using is the Twitter widget. There aren’t a lot of situations in which I can envision needing the RSS Links widget (there are probably much easier ways to implement this if you really want it), and the Image Widget currently lacks some functionality you can find in other similar plugins. However, with the rapid pace at which Twitter changes its requirements, a Twitter widget officially supported by Automattic might be worth its weight in gold.
Below are four different samples of how you can implement native WordPress galleries with the JetPack plugin. The first three are the three layouts made available through the Tiled Galleries module, the last one is the Slideshow made available through the Shortcode Embeds module.
Slideshow (implemented by Shortcode Embeds)
What Say You?
Notice a module that I missed while reviewing JetPack? Have something more to say about a module I discussed? Want to yell at me for getting something wrong? Let us know in the comments what you think.