Change to your content is in your hands

[Aleksandr Paren]

Folks all comment here and also votes for the features which needs to be migrated from the new editor is nothing.

That's one of the last answers about one of the features which needs in the new editor has a many votes, and it is mean that your votes is nothing also.

https://jira.atlassian.com/browse/CONFCLOUD-68501

Here the answer. read and enjoy.

--------------------

From: Phil Oye

Hi Aleksandr,

Sorry for the delay in responding, and I'm also sorry to cause frustration by the lack of moment on this issue.

I wish I had better news, but we do not have any plans to implement inline images in the new editor. We're always trying to strike a balance between power/flexibility and ease of use. Each additional feature is additional complexity for our customers to learn and understand. While inline images are valuable for some people, we've found that it is a hindrance to most.

The workaround is to upload custom emoji or use the various image wrapping options in the editor.

I understand this response isn’t great to hear.

Phil Oye
Atlassian — Group Product Manager

[Peter Kidson]

Table-handling in the new editor is hopeless (to put it politely;  limited and super-klunky)  for professional purposes. 

Rather than trying to fix it, why don't you just scrap it and put in the excellent table UI from the Legacy editor ?

[Peter Kidson]

Oh, and reverse the recent change in the Legacy editor that makes tables fixed width.  (Was that a salesman-inspired deliberate sabotaging so as to make the new editor's ridiculously amateurish table-handling look less ridiculous by comparison?)

[Susanne Schnitzer]

@Bruno: I think that's the idea behind "Data Center" solutions und third party providers, who offer Confluence Server hosting. According to their pricing schemes these might get rich ;-)

Cloud is affordable, but Atlassian made it completely useless for professional documentation solutions.

Honny soit qui mal y pense :-)

[Rodney Hughes]

Many Thanks Aleksandr

On what planet did Phil Oye come to the conclusion:

While inline images are valuable for some people, we've found that it is a hindrance to most.

Where did Users post any complaint  about inline images ... or any existing feature.

And what does "most" mean?

There is AMPLE evidence of MOST, if not ALL Users in this forum want these things back

SO a few people perhaps didn't understand so all of us who DID find it valuable go by the wayside!
Result it is LESS valuable to us.   🤷‍♂️

I think this "internal" Confluence Community User forum is just not of any interest or concern for Atlassian

Perhaps posting comments on a public location will set them straight ....

https://www.linkedin.com/posts/atlassian_learn-whats-different-activity-6830968476065239041-xwi-

[Artur Szalak]

@Rodney Hughes done

[Aleksandr Paren]

Do not forget that Atlassian is a public company on Nasdaq. I think any not good reviews from customers to the market and shares will go down. 

[Susanne Schnitzer]

Thanks Aleksandr, for publishing this answer.

Despite the incredibly sad information, we had such a good laugh in the office this morning!

Understanding the complexity of inserting an inline image into a wiki page is too complex for me ;-)

What is Atlassian's new target group? Age 5-8?

Are proper table functionality, image resizing and all the other needs of technical authors also too complex?

And I even don't dare to think about adding own HTML code where adequate...

Was this a real answer from Atlassian or just a fake to make some fun? :-)

We just can't believe this. It's so ridiculous and disrespectful. Sad.

Or, as my collegue said: "Phil, please find a better excuse for lack of useful functionality!"

[rod]

What? I think that Phil Oye's answer sums up the reasons we are struggling to do professional documentation with the new editor:

Each additional feature is additional complexity for our customers to learn and understand.

It is designed to have the least features possible (besides emojis and bling bling that seem to be so important) and (if I interpret a bit the answer) the least customization possibilities.

I can't underline enough how I am disappointed at the confluence design direction change from professional documentation use to "do a quick note page" use.

Since that direction did not seem to change within the many years for which we complained about the regression the new editor is, I guess it will not change in a foreseeable future... Maybe other tools out there are more fit for professional documentation. :(

[Artur Szalak]

Couldn't agree more with @Susanne Schnitzer and @rod . At the current state of Confluence, I will have more flexibility (and fewer issues in the process) to document functionality using the latest versions of Xmind. What's the current positioning of Confluence against Dropbox Paper? 

P.s. just hit "level 2" badge for commenting here. Seriously, gamification of comments on forum was in the product development cycle but not "image handling" for core product?

[Rodney Hughes]

Atlassian have created a new post promoting CLOUD probably trying to get rid of all the negative feedback ...

https://www.linkedin.com/posts/atlassian_whats-better-on-cloud-activity-6830968789899841536--Dmb/

[Joe Bloggs]

@Rodney Hughes still kudos to them for being reasonably communicative, and for example, not deleting this thread or the LinkedIn comments which they could easily do. IT does bother me though that they have not shared any plan as to what they intend to do and equally  with changing licensing structure for corporates I think we might yet gladly dust off MediaWiki at some point. That would be a shame, Confluence has been a great enabler for our company. 

[Florian Wanoschek]

We have thousands of pages and not a single page which does not have a more or less complex structure. As a standard, we structure pages by section and column macros and we nest panels and table of content macros inside. We also like to structure tabs in tabs or table in table. We also put macro in macro on 4 or 5 levels. Nesting of macros, handling of tables and images, having GOOD reports structures is possible in the server version and so it should be on cloud! 

I can only hope this is joke:

Each additional feature is additional complexity for our customers to learn and understand.

Well, if it is not: It depends on how additional features are made. If the handling is intuitive and if the features are useful to the users, additional features are not problems but chances!

There are professional writers here, who are trained to learn and use new features every day!!

[David Allyn]

Yep... hey if you find a replacement, be sure to comment here so we can all move to it.

[Peter Kidson]

Yes the new target audience is 5-8 years old now I gather.

[Kim Hirschman]

The 8 year-old users are already more sophisticated.

[rod]

If you have not seen it, @Christopher shared a Confluence survey that Atlassian is currently having in many items. It is another nice place to share your feeling with Atlassian: https://surveys.atlassian.com/jfe/form/SV_e4ifDIwspmBjJR3?aaid=557058:ae46244a-f6ed-48e8-9a5a-cb9b724908c2&confluence_cloud_id=ad38e4cb-2a53-47d4-acff-a167c0d3ed52&confluence_cohort=enduser

[Ian Kaplan]

I just filled out the survey.  I wanted to let Atlassian how unhappy I am that the new Cloud editor is worse than the old cloud editor. Altassian has ignored feed back on this issue for years. Perhaps they will ignore the survey results as well, but at least I tried.

[David Allyn]

I think the basis of their product is misplaced overall.  It's clear they're making the editing experience quicker for developers and project managers as they are programming and managing a project.

The problem is that programmers and project managers don't typically have the best skill set to write documentation and training materials, which is what we've been trying to use Confluence for.  I hire programmers to program code - it's quick, concise scripting not explanatory.

In order to write training materials and product documentation for a wider, business audience, you have to have impactful, eye-catching documents - and that takes time, attention to detail, and creativity.  When we were sold on Confluence (in 2016), the sales people assured me Atlassian was moving in the direction of business users with new, robust editing features on the horizon.

Instead, they reversed their development track.

Now, we're switching over to Google Sites.  It's a collaborative, robust editing experience that rivals any application out there.   Even Google Docs and Slides are as good as Word or PowerPoint. As soon as we've migrated, we'll be cancelling our Confluence subscription.

Check it out... https://sites.google.com/new?tgif=d

[Joe Bloggs]

@David Allyn That's an interesting take. I guess lot of the problems related to the "new" editor. Our (large) enterprise still runs on prem instance and my technical authors have been able to achieve look at feel they wanted - with customizations where appropriate. On Cloud - no such luck. I can live with on cloud for personal use, I think we'd also see a riot if Atlassian tried to do this in their enterprise product. MediaWiki might come handy yet :)

[MGI]

I don't get such a Page Template pop-up when I create a new page. It just goes to a new blank page.

[rod]

For me it's in a pane at the right hand side of the created blank page.

I don't know where this capture is coming from but the "(going away soon) In the upcoming weeks, the old editing experience will no longer be available" part really bothers me.

I do no see this in our site but it really does not fit the text of the current article (written in March 2020):

The legacy editor isn’t going anywhere

We know that many of you are concerned about all the changes and what they may mean for the future of the legacy editor. We have no plans to end-of-life it in the foreseeable future, and if and when we do, we’ll make sure to explicitly communicate it well in advance.

@Tiffany: do you have input on this?

[Aleksandr Paren]

Hey All. 

I wrote here that writing a comment here doesn't care Atlassians. And our pain is only our pain, they have only their strategic plans.

This true of life....

[chris]

Can someone please fast track me - how do I have the legacy template enabled as described in this article?

More specifically, when we hit the "create" button to create a new page, we don't want the new editor - we want the legacy editor to be default. Will that happen if "the legacy template" is "enabled"?

[Deleted user]

@chris You have to contact Atlassian Support to get the Legacy template enabled for your organisation.  We too enabled it for our site by raising a ticket with support. 

After you enable it, you will get a new template in the list called Legacy Editor, but you cannot make it default. You always have to Create a new page and select the template.

Hope this helps.

Thanks,

Pradnya