Jetpack is ten years old. 🎂…
Jetpack is ten years old. 🎂 There's a birthday celebration site you can check out for “an interactive exploration of how Jetpack has helped WordPress sites over the last 10 years.”
Jetpack is ten years old. 🎂 There's a birthday celebration site you can check out for “an interactive exploration of how Jetpack has helped WordPress sites over the last 10 years.”
There are a few items from the last few days I’d like to follow up on, so figured I’d just lump them in here together. First off, Jetpack had a bit of a rocky update to 3.4. Version 3.4.1 came today with a bunch of fixes, including one that prevents a fatal for users that…
On the morning of April 19th (Monday) Automattic released a new plugin called Jetpack Boost on the WordPress.org repo. The plugin is focused on performance and SEO issues users might have with their sites. 🚀 Boost has three “performance modules:” Optimize CSS Loading generates critical CSS for your homepage, posts, and pages. This can make…
Jetpack 5.0 was released as a “spring cleaning” with a focus on stability and compatibility. You’ll want to update for cleaner code, faster execution, and a few bug fixes for PHP 7.1 that were causing some fatal errors.
Automattic has published their year in review, which gives a broad look at what happened with the company and the various brands in 2016. The page (which has a nice design, btw) covers Automattic’s corporate growth, diversity, and other points of interest. It then moves on to WooCommerce, Jetpack, WordPress VIP, and WordPress.org stats. Some…
Last week, Automattic introduced WooCommerce Connect, a Jetpack-esque suite of tools for WooCommerce, where modules could utilize the processing power of WordPress.com to run particular elements of eCommerce websites. WooCommerce Connect requires Jetpack, and therefore also a WordPress.com account, in order to run. Jetpack now has 35 modules, originally with the purpose of making publishing…
A few months ago, I enabled two-factor authentication for WordPress.com. There are a number of reasons I did so. For one, at Range, we sometimes work on WordPress VIP projects, where two step authentication is recommended for about anything that could interact with those projects (.com, email, etc). Second, it was required for me to…