Jetpack Rebrands with New Logo, Adds Custom Post Types in 3.1 Release

jetpack-logo

Jetpack is sporting a new logo in the 3.1 release announced today as part of a re-branding inspired by its growth. “Jetpack is ever-evolving and is a major part of Automattic and WordPress. It’s grown a lot since its introduction in 2011, and its branding should grow too. Something better, faster, stronger,” Enej Bajgoric explained with the unveiling of the new logo.

Jetpack 3.1 also introduces custom post types and adds the long-awaited portfolio content type, which is likely to be the first of many. The Portfolio Custom Post Type allows users to manage and showcase projects and is easily displayed using the [portfolio] shortcode. WordPress theme developers can elect to support Jetpack’s portfolio post type by styling it to match the theme, instead of building their own.

portfolio-content-type

Theme developers will also enjoy the new responsive video support built into Jetpack. It can be enabled with one simple line of code:

<?php add_theme_support( 'jetpack-responsive-videos' ); ?>

With that code in place, all videos on the site will respond nicely to mobile devices with no extra markup. Jetpack users who were previously using other plugins to get responsive videos will now be able to eliminate those.

The 3.1 release also introduces additional JSON API endpoints for viewing updates and managing plugins and themes. You can check it out by playing with the WordPress.com developer console.

Many smaller improvements in 3.1 make Jetpack easier to use and its features more accessible:

  • Jetpack Settings have improved keyboard accessibility.
  • Improved RTL support for After the Deadline, Carousel, Contact Form, Comics CPT, Custom CSS, Omnisearch, Publicize, Related Posts, Slideshow short code, Tiled Gallery, Widget-Visibility and Widgets Gallery.
  • Contact Form: Add an “Empty Spam” option.
  • i18n: Change the priority of where plugin_textdomain is hooked so that the plugins can better translate Jetpack.
  • Monitor: Displays how often the site is checked for downtime.
  • Shortcode: Added Mixcloud shortcode and oEmbed support.
  • Social Links: Improved handling of customizer hooks in non-admin context.
  • Stats: The smiley image is gone by default.
  • Stats: Added link to the configure page for stats so that the stats settings page is easier to find.
  • Theme Tools: Added the responsive videos to theme tools so that themes can support responsive videos more easily.
  • Updated Genericons to version 3.1, new icons for website, ellipsis, foursquare, x-post, sitemap, hierarchy and paintbrush.

The Jetpack team further iterated on the admin overhaul that added bulk module management in 3.0. This release includes a number of tweaks to module management, allowing you to activate, configure, and deactivate Jetpack features in the feature description box. The update notice should already be available in your admin. Update now to take advantage of all the enhancements in 3.1.

21 Comments


  1. Jetpack: Automattic’s “y’all takin’ too damn long to build this stuff” plugin. (I, for one, welcome the new Custom Content Type feature. Thank you, a8c crew!)

    Report


    1. That’s funny, I was just thinking: “Thank goodness that smiley image is gone by default now.”

      Report


      1. That was my favorite part. No more img#wpstats { display: none; } in the stylesheets.

        Report


    2. Don’t worry there is a way to add it back :) just go to Stats and click on the configure link. You were able to hide the smile for a while but the config page was hard to find.

      Report


  2. It bugs me that they enable significant new features by default. At least with the portfolio dealio it is only “half” enabled. You still have to go to Settings –> Writing to enable the portfolios for real so I was able to deactivate the Custom Content Type module before it messed anything up on my site.

    It’s very kind of Automattic to make so many WP.com features available to the entire WP community. But I still don’t understand why they chose to roll everything under the sun into one Borg of a plugin instead of releasing individual plugins for each feature.

    Report


    1. Chris — we don’t auto-activate all new features, only the ones that won’t actually affect the front-end of your site for users, and we consider (after evaluating carefully) to be worth auto activating. Some, like Sharing Buttons and Custom Post Types — although they are active, they don’t actually do anything unless an admin configures it to. Others, like Photon or the Comment Form we intentionally leave off, as turning them on by default and taking over some of your front end without realizing it would be discourteous! :)

      Report


      1. Several months ago, my contact form stopped working because Jetpack override the shortcode from Contact Form 7 and I didn’t realize until a few months after that. End up losing a lot of leads in the process.

        Report


      2. Since Jetpack 2.6 (which shipped November of 2013), we don’t actually activate our internal contact forms module if you’re using any of the other popular contact form plugins already:

        https://github.com/Automattic/jetpack/blob/2.6/class.jetpack.php#L70

        https://github.com/Automattic/jetpack/blob/3.1/class.jetpack.php#L83

        But beyond that, it looks like Contact Form 7 uses the [[contact-form-7]] shortcode — which we don’t touch. Can you detail how we overrode it?

        Report


      3. Ah, see, I was confused. You’d said ‘a few months ago’ and that issue is from over two years ago — published May 17th, 2012. And it looks like we fixed it promptly.

        Commits dated May 18th and 22nd:

        https://github.com/Automattic/jetpack/commit/a24c4ada33943d82477918e6df58575d6287adb4#diff-ba2abc1889d79bcf7293e6748302450bL644
        https://github.com/Automattic/jetpack/commit/28714c31395618ea9b1077bf979c44a924bc5e90#diff-ba2abc1889d79bcf7293e6748302450b

        Both of which shipped out in 1.3.1, dated May 22nd:

        https://github.com/Automattic/jetpack/releases/tag/1.3.1

        Report


  3. Will be waiting for a slim “Jetpack Custom Content Type without Jetpack” version on WP.org :P

    Report


    1. We’re planning on it. If it continues with the steam it’s picked up so far, we’ll certainly structure our custom post types to work well with it. :)

      Report


  4. So late with custom post types and portfolio. All the while I had been adding projects as normal blog posts but under a category named ‘portfolio’. Would there be anyway to migrate the existing blog posts published under ‘portfolio’ category to new portfolio custom post type. I have a feeling that I will need to swim through lot of mess if I have to use this new feature. I don’t think i can delete existing posts as it will result it 404 errors when people reach my site through google search.

    Report


      1. Thanks for the link George :) . But, I wonder if it affects the existing URL and permalinks to the post. For example, as mentioned above, I had created a parent category called ‘Portfolio’. Under which I had other categories for specific genre of projects like ‘multimedia’ , portraits or weddings. I have this URL http://nishantratnakar.com/portfolio/multi-media/fistful-of-dreams/ – Now, if I switch the post type, wouldn’t it affect the permalink? I am asking this because the wordpress.com documentation on portfolio gives a different permalink for portfolio projects with project slugs and project-type slugs.

        Report


  5. Now, I may considered using jetpack if it doesn’t prevent my site to load faster..

    Report

Comments are closed.