One of the most exciting aspects of working on an open-source platform is how fast things can change. And if you want to make something happen you can just do it. This happened just last week and I couldn't be happier.
I received a strange question today. A user was telling me how critical it is that their analytics plugin, Jetpack Stats, works in a specific way with WooCommerce. This got me thinking – wait – why do you need Jetpack Stats? What happens if you ever switch away from WordPress? What if you continue to use WordPress but WordPress.com goes out of business? Am I the only one that worries about these issues?
Yesterday I talked a bit about why I love Jetpack. Today I want to talk about a couple things we can do to make it better. People's biggest concerns with Jetpack aren't that it doesn't do enough or that it doesn't do it right, their concerns are that Jetpack is too big. This isn't exactly news in the WordPress community and there's already a Jetpack Lite plugin which only includes two out of 20+ modules.
I like the idea of the lite version but there's just way too many useful modules to use the lite version. How can you give up a free image CDN (Photon), email subscriptions (Subscriptions), and perhaps the easiest to set up social media sharing tool (Publicize)? As I said yesterday I Love Jetpack and wouldn't want to go without all of that functionality. To this effort rather than creating another Jetpack lite plugin I've created a plugin which removes some of the less used modules.
One of my favorite plugins in the entire WordPress blogosphere is JetPack. JetPack is plugin built by Automattic that brings in all the features of WordPress.com to your own WordPress.org site. The thing that I love so much about this plugin is that they offer some incredible free cloud services as well as a few really great simple modules (think of them as mini plugins) built the right way.