Latest milestone
Looking for information about the latest Confluence EAP milestones?
Head to Confluence Development Releases
This documentation is intended for Confluence plugin developers. This documentation will walk through:
Both the content storage format and the user experience for adding macros will change in Confluence 4.0. This release will introduce a new WYSIWYG editor with a completely different architecture based on XHTML. Also, the end user experience will change as follows:
We provide a set of tools to help you test your macro:
See Confluence Storage Format.
If you are a plugin developer, an existing customer or partner you have access to the Confluence 4.0 release including the source from the usual locations.
Confluence will continue to support exporting content to Word, PDF and HTML. Additional to this, space and site administrators can export content to XML. Finally, the Universal Wiki Converter is a plugin that allows customers to move from one wiki to another.
Yes, they are. Macros will be placed within other macros using "Macro Placeholders". Macro Placeholders are a visual representation of a macro on a page. Below is an example of what two would look like in the new editor:
This question can be answered in two parts:
We acknowledge that would be very useful for things like security plugins, deciding if the end user can have the plugin rendered (even if they can view the page). However, we don't have this yet and are unsure if this will make it into the initial version of 4.0. We are focused on improving the editing experience rather than including more plugin points to the rendering subsystem (at this point). Your feedback for this would be appreciated.
Please see the editor FAQ page for this.
One of the main reasons to switch to an XHTML based storage format is that we can't convert from HTML to wiki markup in a reliable way. The remote API will offer an additional method that allows for one way conversion of wiki markup to the XHTML based storage format.
Rate this page: