Support » Plugins and Hacks » How about adopting the Commons in a box approach for Jetpack?

How about adopting the Commons in a box approach for Jetpack?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Jeremy Herve


    I believe Jetpack’s approach is already a bit similar to the CBOX plugin: once you have installed the plugin, you can use all the modules, or only some of them. If you don’t need one of the modules, you can deactivate it, and it won’t be called or used on your site. Its settings won’t appear anywhere in your dashboard.

    If you want to use Jetpack without having to connect your site to your WordPress.com account, we have added a development mode to Jetpack to enable modules that don’t require a connection. This feature is not available in Jetpack 2.2, but you can already test it by downloading the development version of the plugin. Once the development mode is active, only the modules that don’t require a WP.com connection can be activated. See r676269 for more details.

    You can develop add-ons and plugins on top of Jetpack (see my profile for some examples, or search the plugin repository). Some people have actually forked some of the Jetpack modules into stand-alone plugins.
    You can also contribute code and submit patches through Trac:

    I hope that answers some of your questions. We’re open to feedback, and I’m always happy to read what people have to say about our plugin!

    Thank you very much, that’s some very useful information. The development mode you describe however is basically the same as installing “Slim Jetpack”, and is still problematic. I think the plugins that can be used in development mode without authentication should always be possible to use without authentication. There’s no good reason why my site should lose its twitter widget, gallery, comment form etc. just because some connection with a third party server was lost. It’s especially infuriating when these features fail to gracefully fall back to a working solution, such as the comment form that simply prevents your users from commenting altogether instead of at least disabling itself to give way to the native comment forms.

    Jetpack and CBOX might have some things in common, but the key feature of CBOX is the very elegant decoupling/decentralization of features, avoiding any form of unnecessary lock-in.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘How about adopting the Commons in a box approach for Jetpack?’ is closed to new replies.