Confluence 4.0 introduces a new editor. We first made this announcement at Atlassian Summit in June 2010. This page contains answers to common questions about the move to the Confluence 4.0 editor. How can I stay informed about the progress of the new Confluence 4.0 editor? Why is Atlassian introducing a new editor in 4.0?The editor is the single most important feature in Confluence. Confluence 3.5 has two editors: the rich text editor and the wiki markup editor. Each has its strong points and weak points. - The rich text editor in particular has problems in stability and consistency, because it has to convert all content from rich text to wiki markup before storing content on the database. This leads to the so-called 'round-tripping' problems, where the page looks different in display mode than when created in edit mode.
- Many people find the wiki markup editor hard to use, particularly for long pages and complex layouts. We often hear from customers that the number one barrier to wiki adoption in their organisation is that people have to learn wiki markup.
Many customers have given us great feedback on the shortcomings of the current editors and the things they would like to see in a Confluence editor. We are introducing a single new editor to replace both the wiki markup editor and the rich text editor. The new editor will help us to solve the problems mentioned above and will provide a stable platform on which we can build high-demand features in future releases. |
|
What about features that were previously available only in wiki markup?
We have identified these features and will add support for as many as possible in the new editor. For example, the new editor will include superscript and subscript text formatting, which is currently not available in the Confluence 3.5 rich text editor.
So you are basically eliminating the wiki markup editor and keeping the rich text editor?
No. While the new editor is WYSIWYG like the current rich text editor, the new editor has a completely different architecture based on XHTML and is faster and significantly more reliable. Our goal is to incorporate the strengths of wiki markup with the richness and intuitiveness of the WYSIWYG editor to produce a rich, hybrid editing experience. In particular, we are introducing options that offer the speed of the old wiki markup editor, via new features such as autocomplete and shortcut keys.
Will you be able to paste wiki markup into the new Confluence editor?
There will be multiple ways to insert wiki markup in the new editor.
For those of you that have learned wiki markup and are used to the speed of wiki markup we are really excited to let you know that you will still be able to write wiki markup in the new editor. This wiki markup converts 'on the fly', providing one of the fastest editing experiences yet.
For those of you that have scripts that produce wiki markup, or often write wiki markup in meetings, the new Confluence 4.0 editor introduces an Insert > Wiki markup dialog which will let you paste wiki markup for a one-way conversion.
Will Confluence 4.0 support the Office Connector, including 'Edit Page in Word' functionality?
Most of the features of the Office Connector (the View File macros, Import from Word) already work in 4.0. However, the 'Edit in Word' feature will be removed in Confluence 4.0.
When speaking to customers about the use of the 'Edit in Word' functionality, the primary reason for using this feature was 'familiarity'. Business users in organisations have found the 3.5 editor and wiki markup hard to learn.
In Confluence 4.0, we have greatly simplified the new editor user interface. With extensive usability testing, we are confident the new editor will be easier to learn and more reliable to use. We also have a large majority of customers who do not use the 'Edit in Word' functionality.
Please Note: We are referring to the "Edit Page in Word" functionally - not the "Edit Attachment in Word" functionality. Editing attachments in Word will still work fine, i.e. launching Word to edit Word documents that are stored in Confluence.
In Confluence 4.0, will you be able to merge and split table cells?
Yes, you will be able to merge and split table cells. This is a brand new feature in Confluence 4.0.
When will the new editor appear in Confluence?
The new editor is in Confluence 4.0, scheduled for release in 2011.
What does the new editor look like?
Confluence 4 is currently available for download through our Early Access Program. You can download and try the new editor for yourself. This is a great opportunity to provide early feedback to us. More details about this here.
You can also watch a video preview of Confluence 4 from our Atlassian Summit in June 2011. Watch the video at this link (hhttp://www.youtube.com/watch?v=gVa_H3z_BTg#t=15m10s).
Will Confluence still have a wiki markup editor?
No. The vision is incorporating the best parts of the wiki markup editor into the new editor to provide the best of both worlds.
What format will Confluence use to store its page content?
XHTML. Up to now, Confluence has stored its content in the database as wiki markup. In Confluence 4.0, the content will be stored as XHTML. Basically, XHTML is like HTML but complies with stricter formatting rules. Where HTML is based on SGML, XHTML is based on XML, which is a subset of SGML. Because XHTML documents need to be well formed, they can be parsed using standard XML parsers.
Will you be able to edit the source XHTML code directly?
Confluence 4.0 will not have an "edit XHTML source" mode by default. More sophisticated macro placeholders, images and link handling in Confluence 4.0 entail a lot of custom XHTML which make the new storage format much more complex than standard HTML. Editing this storage format by hand could result in corrupt content and the loss of page data. Source editing will still be editable via the APIs and the WebDAV client. There will also be a plugin which allows users to edit the storage format of the page (see Specification - Confluence Advanced Editor for details).
Will there be a tool to convert existing content from wiki markup to the new XHTML format?
Yes. Where possible, Confluence will automatically upgrade existing content into the new XHTML storage format. There will be some API changes (we are trying to keep these to a minimum) and we will provide mechanisms to convert wiki markup to XHTML.
Read the Plugin Development Upgrade FAQ for 4.0 or Planning for Confluence 4.0 to learn more about API changes.
Will there be any API changes?
Yes. There will be some API changes (we are trying to keep these to a minimum) and we will provide mechanisms to convert wiki markup to XHTML.
Read the Plugin Development Upgrade FAQ for 4.0 or Planning for Confluence 4.0 to learn more about API changes.
How many Confluence 3.x releases will you have before 4.0?
There will be no more 3.x releases before 4.0. Confluence 3.5 is our last 3.x release.
Will the remote XML-RPC API still work in Confluence 4.0?
We currently plan to keep the existing XML-RPC API but only allow write access which will automatically convert wiki markup to XHTML. This will allow you to create new pages or update existing pages as usual. We can't allow read access, however, because we can only return XHTML, which will break the existing APIs contract of returning wiki markup. To cover those use cases and to have a fully XHTML capable API, we will introduce a new API available through a separate URL which will also have a new method to migrate wiki markup to XHTML.
Developers should read Preparing for Confluence 4.0 to learn more about API changes.
Will the new editor be included in JIRA?
At the moment we don't have any plans to do this. However, we are open to this idea and would welcome any customer feedback in this area.
Does the SharePoint Connector support Confluence 4.0?
The SharePoint Connector 1.5 is compatible with Confluence 4.x.
関連トピック
A developer's guide to preparing for Confluence 4.0