The Legacy Editor is being deprecated in Confluence Cloud: Here’s what you need to know

[Ole Nymoen]

It's good that pages with nested macros won't fail after being moved to Confluence.cloud. And it's not a fundamental problem that the legacy editor in Confluence.cloud dies.

But, as a user and administrator of both Datacenter and Cloud sites, Confluence.cloud is still painful, the editor included. It's also painful that new features like whiteboards and databases isn't available on Datacenter.

I have also moved a space from Datacenter to Cloud to test the experience, about 4 months ago. Lots of pages had to be edited as nested macros made rendering challenging. Very good that this is solved.
But I had to edit the pages in Confluence.datacenter before exporting/converting the space in the moving process. Editing hundreds of pages in the new editor was just too painful. 

The design criteria of the new editor is clearly much more geared towards new/inexperienced users as to being an efficient and snappy editor.

Maybe the new editor could get a less WYSIWYG mode that focuses of efficiency for experienced users?

[Kristof Thomys]

Feedback on the new editor. Tables are unusable for compact work.

The new Confluence editor has made table-based content almost unusable for technical or organizational workflows.

Table cells are too large, the line height is fixed, the padding cannot be adjusted, and there is no way to choose a compact layout as there was in the legacy editor.

In longer tables, it is no longer possible to see an overview at a glance. Even with the narrow layout and “Normal text” formatting, tables remain oversized. Important content that used to fit on a single screen now requires constant scrolling. This causes unnecessary friction in many teams.

My request is simple. Please bring back an option for compact table layout. This could be a formatting preset, a macro, or simply a smaller font with tighter spacing.

Thank you.

[Martina Guth]

Hi @Elle Ky , 

one question concerning the legacy templates. Currently I only have the option to create a new template and if I am lucky, I can copy and paste some things from the old to the new template. There are quite a lot of old templates in use in our company. Will we get the opportunity to switch from old to new like on pages even for templates? Otherwise it is really a mess to create all of them new.

Kind regards,

Martina

[Kent Chiu]

Hi @Elle Ky ,

How can we determine whether the Confluence Cloud template is still in the legacy editor or the new editor? I just checked our global templates, and no indicators are showing if it is still in the legacy editor.

Thank you,
--Kent

[John Medalen]

"Eligible legacy pages will be automatically converted ..."
So, which pages are not eligible?

[Kevin Robinson]

I have several issues with the legacy editor to Cloud editor conversion.

1. Note Panels have been converted to Info Panels.
2. Warning Panels have been converted to Error Panels.
3. Note Panels, Info Panels and Warning Panels have been converted as Header 1 which affects the Page Index.
4. Images have an error message: "This macro was added to a page that was converted from the legacy editor. It can’t be edited because it is now incompatible with the current editor".
5. Some images need to be manually converted to pixels.

These are issues that should have been address before my documents were converted the the cloud editor.  I have several hundred documents that are affected.

[Elle Ky]

Hi @Martina Guth!

 Will we get the opportunity to switch from old to new like on pages even for templates?

Yes, you can convert eligible legacy templates today. To convert a legacy template:

1. Open the sidebar in Confluence Cloud.

2. Select More (•••), then Templates.

3. Select Manage Templates (button near the top right corner)

4. Under User created templates, you will see the option to Convert for eligible legacy templates

Where needed, we’ll use the legacy content macro to help ensure your content is preserved and converted as smoothly as possible. This macro wraps any content that isn’t natively supported in the new editor, so you can continue working with your templates without losing important information.

We’re actively working to make this transition even more seamless and our goal is to minimize manual effort and disruption on your part, allowing you to continue to use your templates (in their converted form).

[Elle Ky]

Hi @Kent Chiu! 

How can we determine whether the Confluence Cloud template is still in the legacy editor or the new editor? I just checked our global templates, and no indicators are showing if it is still in the legacy editor.

Currently, the best way to determine this is by looking for the option to Convert the template. However, one caveat is that this only appears for legacy templates that are eligible for conversion. As we're continuing to add support for more use cases, not all templates or pages are eligible for conversion yet. If the template contains unsupported content that we're not able to convert yet, this Convert option will not appear yet. 

We understand this is not the most intuitive or complete information you are seeking. We are actively exploring better ways to provide this information to admins. As there are several top-of-mind questions related to legacy templates, we'll plan to share an update in the Legacy Editor Deprecation Community as we make more progress. 

1. Open the sidebar in Confluence Cloud.

2. Select More (•••), then Templates.

3. Select Manage Templates (button near the top right corner)

4. Under User created templates, you will see the option to Convert for eligible legacy templates

[Martina Guth]

Hi @Elle Ky what happens to the legacy content macro later on? Will that stay forever or will then there be a phase, where you say, this is deprecated, please rework your content. As you now say, that a lot of macros will be deprecated. 

I am currently thinking it is better to tell my users to rework their pages now, instead of rework now a little, and 6 month later - now rework further more. 

We migrated to cloud last year in June and in fact it was hard work for our users to keep their content living because of big disruptions between server and cloud. A lot of links were broken, macros didn´t work. Now the next wave comes and I want to prevent them from a third wave.

I fully agree on the cloud is cool and moving forward. I appreciate a lot of functionalities the cloud has. However what I need to critize is the way Atlassian is doing big changes without having a full scope of the impact on the users and a full hand of help for the admins.

In our company we build combisteamers for professional kitchens. All of our sales guys have been chefs before to know about the topics our customers have. All of our office staff has to do an apprenticeship day in our production, to see how our units are built. Maybe it would be good, if Atlassian colleagues would make an apprenticeship at your customers to see, how your products are used, what they are used for and what impact it has, if you change such huge things and what your customers need to support their teams.
Greetings,
Martina