WordPress to be bundled in Jetpack with mission to power 50% of the web

edit: hopefully you recognize this, but this post is an April Fools’ joke.

WordPress just can’t do it on its own. Jetpack makes WordPress great, and without it WordPress is just boring. Jetpack makes WordPress more secure, offers great stats, and everybody recognizes Jetpack when they see all that stuff at the bottom of blog posts.

WordPress will be the 37th Jetpack module added to date. Matt said in a private email to me, “I think this will be our best module since Beautiful Math.”

The inclusion of WordPress as a Jetpack module was inevitable, looking back. I mean, it is larger than WordPress already. Jetpack weights in at 8.4 megabytes, zipped; whereas WordPress is only 6.4 megabytes.

Also, the move allows the transition to Github based development to be more seamless. WordPress has notoriously been developed with SVN and using Trac, whereas Jetpack has been on Github for a while now. With the move to being a WordPress module, it’ll fit right in with the rest of Jetpack’s Github repo.

WordPress.com versus WordPress.org has long been debated as well, and the move to make WordPress.org part of Jetpack finally settles the issue. Now self-hosted installs will be known as Jetpack, and WordPress will represent the awesome cloud power that Automattic brings to the table.

While there was some controversy over the decision to make WordPress a Jetpack module, in the end the leaders of the respective organizations prevailed to make it happen. The CEO of Automattic worked with the co-founder of WordPress directly, mediated by the head of the WordPress Foundation. Matt Mullenweg said the meetings were very productive.

As Matt said at PressNomics, Jetpack is really the only way WordPress can move forward to capture 50% marketshare of the web. This move was the right one, and everybody came together to make it happen.

One remaining issue is that much of the commercial industry around Jetpack will have the legacy WP prefix in their names and domains. But Matt has registered .jetpack has a new TLD, and pending approval, they will be able to rename their companies to fit the new brand for the popular CMS.

Similar Posts


  1. Matt said to me recently that he felt I would appreciate some of the upcoming changes in JetPack. I guess this is what he was referring to.

    But I think they should include Drupal instead. I hear it’s better.

  2. Damn it, you got me. I started telling our team that we all needed new business cards. This was the first thing I read this morning and I wasn’t quite awake yet. 😛

    Post Status 1: Steven 0

  3. This is my favorite: “The CEO of Automattic worked with the co-founder of WordPress directly, mediated by the head of the WordPress Foundation. Matt Mullenweg said the meetings were very productive.” I also heard that that the blogger from the popular Ma.tt website was there taking photos to document this historic event. 🙂

  4. Well played sir, well played. I LOL’d 🙂

    If we can get Jetpack pre-installed as a plugin within the WordPress module… it’s Jetpacks all the way down (and up!)

  5. Hmmm, looks I’ll be needing a new domain name, how does WinningJetpack.com sound? No ring to it? Thought not… 🙁

    1. Use of the “jetpack” word in the domain name will not be allowed, just like using “wordpress” isn’t, so you’ll have to settle with winningjp.com or something.

  6. Seriously though, what happens if this new JetPack is installed on a legacy version of WordPress?

    It could cause a parallax or an infinite scroll in the space-time continuum.

  7. Well, I can say that I started to use Jetpack on my blog about two weeks ago after an email from Google about my mobile-friendly version.
    Since I installed it, things work much smoother.

  8. Haaaa. No foolin’ though, WordPress does feel like a Jetpack module these days, given the relative size of the two. I’m pretty sure if every WP user activated all their Jetpack modules at once the internet would need a hard reset.

Comments are closed.