Categories: jetpack sdk

Announcing Add-on SDK 1.6!

The Jetpack team is proud to announce the release of Add-on SDK version 1.6! This version of the SDK is mostly a bug-fix release yet with one very important update, the documentation.

The SDK documentation has been updated for easier navigation and more information, including tutorials on using a few community-built modules that aren’t in the core SDK. You can always find the latest documentation here:

In addition to the documentation, this release has quite a few bug fixes. You can read more details of these fixes as well as some known issues in the release notes.

As always, we’d love to hear from you about your experiences with this release. You can contact us in a variety of ways:

post to our discussion group
chat with us on #jetpack
report a bug
check out the source and contribute bug fixes, enhancements, or documentation

For more information on the Jetpack Project check out our wiki

6 comments on “Announcing Add-on SDK 1.6!”

  1. Igor wrote on

    Regarding the new documentation, I can’t find list of all the modules in one place, in last version it was right there in the sidebar which was perfect. To me it looks worse than before :/

    1. Igor wrote on

      I stand corrected, it’s not worse than before, from Firefox it looks good.
      But there is a bug in Chrome, “High-Level APIs” and “Tools Reference” are not visible.

      1. Dave Mason wrote on

        Oh hmmm – that’s odd. We’ll take a look at it – thanks for telling us Igor, I’ll point to a bug when its created

      2. Dave Mason wrote on

        Actually Igor, I just tested it in Chrome and I’m not seeing that at all – everything shows up just fine. Perhaps if you are able to reproduce it and have some more details on platform, versions, etc, you can file a bug and we can get others to try to reproduce it. Here is a helpful link to file an Add-on SDK documentation bug. Thanks again!

        1. Igor wrote on

          I just tried from incognito mode and it worked as expected, now all of a sudden it always works properly. Maybe I had old css in cache, I really don’t know what happened.

          I apologize for introducing confusion. 🙁

  2. Jim wrote on

    Is there a plan for websockets api?