Hi there! I’m Avinoam, a Product Manager working on the new Confluence Cloud editing experience. I want to thank everyone who attended our recent webinar, New Confluence features for improved team productivity.
We shared ways that our exciting new features in Confluence can make your team more productive, like how to:
-
Create captivating content with tables, templates, integrations.
-
Organize spaces, pages, and profiles to be more easily found.
-
Scale Confluence as your organization grows.
You can watch the recorded webinar right now!
We had 235 questions submitted during the webinar, so I wanted to publicly answer the top ten most frequent questions we heard about the new Confluence Cloud editing experience.
Q1: How far out are we from being able to use images as links in the new editor?
A: Using images as links is not yet supported in the new editor. It will be supported for pages that eventually get migrated from the legacy editor to the new one to make sure that flow remains in tact. To follow our roadmap which includes this item and any related public facing tickets, please visit this page.
--
Q2: When is this all fully rolling out? I don't see any of the new editor features yet.
A: The editor is rollout out gradually to all Confluence Cloud instances. For each rollout group we make sure to send emails and show in-product notifications in advance, so once this becomes available for your site we'll be sure to notify you in advance. If you'd like to accelerate your sites' roll out of the new editor you can open a support ticket.
--
Q3: Will you make the old editor available until the new one is working
A: As mentioned above, we rollout the editor gradually across and within sites. This means that when the editor starts getting rolled out to your site you'll get heads up that it will become the default experience for your new pages, during which time you'll have access to a template for blank pages using the legacy editor. After several week, which we'll communicate, the legacy editor template will be removed. Your existing pages will continue to be edited for now in the old editor, and we're going to start rolling out soon with page opt in migrations to the new editors you'll be able to do on your own. But, more on that in a separate post soon!
--
Q4: Can you have nested tables?
A: Nested tables have been disabled as per https://jira.atlassian.com/browse/CONFCLOUD-58656 since late 2017. Currently, we have no plans to bring this functionality back due to the reliability, predictability, and stability issues it presents.
--
Q5: Can you create a link to an anchor on a specific section of a separate page?
A: Yes! This feature is rolling out gradually as we've mentioned on this blog post!
--
Q6: Is there a way to change a legacy page format into the new page format?
A: This is a capability we've actively working on and which we're doing internal testing with as a tool for users to control directly first at the page level, then at the space level, and ultimately at the site level. In the meantime, if you'd like to convert all your sites' pages to the new editor, you can do so by opening a support ticket.
--
Q7: What happened to the ability to create a link to a future page?
A: We're currently gathering more feedback on this feature and you can track and add your feedback by visiting our public roadmap page.
--
Q8: Your full page examples show very wide side margins. can you show a page with smallest side margins possible?
A: Yes! Full width is fully available as we've mentioned on this blog post!
--
Q9: How do we center the header to the page?
A: Pages have two main modes now: 1. Fixed width - default, and 2. Full width.
Fixed width pages have centered titles while full width pages have left aligned titles.
--
Q10: Will you be discussing the changes to the editor and when the missing or broken features will be addressed?
A: We've put in a lot of effort recently to update and rehaul our public roadmap for increased granularity and transparency by updating this page.
--
If you have additional feedback or feature suggestions for the new Editor, please don’t hesitate to let us know.
Thank you all and see you next time!
Avinoam
