This documentation is intended for Confluence developers who want to ensure that their existing plugins and add-ons are compatible with Confluence 5.1, and to learn about the new features for developing add-ons in Confluence 5.1.
Confluence 5.1 introduces blueprints - add-ons which create different types of content.
In Confluence 5.0 we introduced the new Create experience. Add-on developers can make use of this create experience by creating add-ons which create different types of content. The goal of Confluence Blueprints is to:
We know that Confluence is awesome for building 'mini applications', like meeting notes, release notes, image galleries, even lists of documents and files. But customers don't always know how to create these things. Confluence Blueprints helps "bootstrap" the page creation process. It creates content that is consistently formatted, automatically organized, and easy to find.
A typical blueprint would
Calling all add-on developers! Confluence blueprints means that you can build these as well and exchange them through the Atlassian Marketplace, either as an enhancement to your existing plugin or as a standalone plugin.
To help you get started we have a few tutorials available. See Confluence Blueprints for details.
Blueprints (and other add-ons) can make use of the new "Instructional Text" feature for templates. The purpose of instructional text is to:
Learn more about how to create instructional text.
Confluence 5.1 also introduces a new pluggable image properties dialog. If you are building an add-on which extends an image in any way (such as an image map, image manipulation etc..) you should consider using the image properties dialog for this. See extending the Image Properties Dialog for details.
We have simplified and improved the labels code, and added some REST resources:
Following on from Confluence 5.0, this release includes further improvements to the Confluence UI. In Confluence 5.0, we introduced the new Atlassian Design Guidelines (ADG) which included a major upgrade of AUI (the Atlassian User Interface) and jQuery that Confluence supports.
Please watch the Development Releases page for pre-release versions of Confluence 5.1 that you can use for testing purposes.
Below are notices for future release consideration for plugin developers:
If you have any questions about preparing for Confluence 5.1, please register for an account on Atlassian Answers, our community Q&A resource, and ask a question. We'll be keeping an eye on things to help out as soon as possible.