This documentation is intended for Confluence developers who want to ensure that their existing plugins and add-ons are compatible with Confluence 5.3, and to learn about the new features for developing add-ons in Confluence 5.3.
Continuing on from the Blueprints API we introduced in Confluence 5.1, we will be introducing the concept of Space Blueprints. It will enable you to hook into the new create space dialog and allow users to easily create spaces of a certain type like Team Spaces (which will be a bundled Space Blueprint in 5.3).
To help you get started we have created a tutorial on Space Blueprints .
As previously announced, with Confluence 5.2 we introduced schema and API changes necessary to support the ability to change usernames. Users now have a new, unique, permanent key as well as the already-existing, unique, changeable username.
See Renamable Users in Confluence 5.2 and Writing a Plugin Upgrade Task to Migrate User Data to New User Keys for more information about migrating your plugin's existing data to user keys instead of usernames.
There have been some changes to the storage format for Macros. Macros that use a parameter type should now expect an < > in its field instead of a wikimarkup link, and macros using , , or parameter types will now contain the corresponding resource identifier element in its body. See Confluence Storage Format and Confluence Storage Format for Macros for examples of the changes.
The in-memory representation of macros has also changed in the following ways:
Milestone releases for developers
Please watch the Development Releases page for pre-release versions of Confluence 5.3 that you can use for testing purposes.
If you have any questions about preparing for Confluence 5.3, 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.