Highlighted

Try out the new editing experience

Hi team,

I’m Avinoam, a product manager on Confluence Cloud, and today I’m really excited to let the Community know that all customers can now try out the new editing experience and see some of the improvements and features we’ve been working on first hand.

We’re rolling this out gradually, and over the coming weeks you’ll see your new pages, templates, and eventually even your existing pages open in the new experience. But for now, we’ve made it available as a template ("Try the new editing experience"), so you can use it and get familiar with it in your own time.

image (11).png

Some highlights:

  • Live macro previews: No more grey placeholders! Most of your macros now look the same while editing as they do when published - and some are even fully interactive.

  • A single autocomplete shortcut: Type / to open a menu and add macros, tables, emojis, mentions and more to your page as you go.

  • Typography improvements to provide a more readable line length. No more w i d e text on large monitors.

  • New image controls so you can now easily wrap text around images to the left or right, or even go wide with banner images.

  • Add 🌶to your page with emoji. Hundreds available, but you can even upload your own.

  • Prefer to work in markdown? Type or paste markdown onto your page and it'll automatically convert to rich text.

  • Need to add code to your page? Add a code block, which now features bracket autocompletion, indentation support, and line numbers. We'll even detect code on paste, and create a code block for you.

Our documentation has more details about other features and improvements, as well as info about the rollout process. There’s more improvements to come, and we’ll keep iterating based on customer feedback - so please use the Feedback link in the bottom right corner of the editor, and tell us what you think.

We hope these changes will help you - and any new members of your team - get up and running with Confluence fast, create pages that look better and are easier to read (even on other devices), and feel confident about the content you’re creating. Thanks as always for your patience and for helping us build this.

 

Cheers,

Avinoam

28 comments

Joe Zhu I'm New Here Feb 06, 2019

When the new editing experience will be available to confluence server? 

Like 4 people like this

Sadly, the server version of Jira and Confluence don't seem to get the same amount of love. I wouldn't expect it for a couple of minor version from now.

Like 1 person likes this

Funny, I have exactly the opposite perspective. My company was Confluence server-based, and I was charged to move it to the cloud. There are so many plugins that aren't offered for the Cloud version, we had to change the way we did some things, and give others up entirely.

As you're seeing, there are some challenges with the new editor. You might be better off observing from the sidelines for a while so that either more enhancements are introduced, or users have come up with clever work-arounds for making things work the way they need them to.

Like 1 person likes this
GSU DDI I'm New Here yesterday

Is this new UX available in the Data Center version?

Avinoam Zelenko Atlassian Team yesterday

Hi @GSU DDI - this is only available for Confluence Cloud.

Manon Soubies-Camy Community Champion Feb 07, 2019

Hi @Avinoam Zelenko,

I've just tried it out and I love it! It's far more intuitive, and the macro live preview is great. I also like that the { shortcut to insert a macro has been replaced with / 👍

Like 4 people like this
Avinoam Zelenko Atlassian Team Thursday

Thanks for the positive feedback @Manon Soubies-Camy ! Will let the team know!

It is a great start! However, how do I disable it on confluence cloud? I can't find it under global templates.  I would prefer testing the feature myself before promoting it to the users

Found it. "Fabric Editor Blueprint". 

Oh! I wondered what that was. It just appeared out of nowhere. (As a sometime costumer, I was intrigued by the idea of editing fabric!) But I have almost no admin rights on this contract job, so the last thing I need is experimental stuff I can't delete.

Like 1 person likes this

I would like to disable the whole thing altogether until they fixed at least the basic bugs.  Although I don't mind using it for new content, it messes up my existing content after editing. Can I opt-out or roll back somewhere?

Avinoam Zelenko Atlassian Team Thursday

@Maurice Pasman would love to hear some examples of how it's messed up existing content and how we can improve that! Also would be more than happy to jump on a call and discuss in detail. 

@Avinoam Zelenko That would be great, I would be happy to show you the problem, just drop me an email and we'll set it up. I am sure you can get my contact details from my profile.

Also, check https://jira.atlassian.com/browse/CONFCLOUD-65650 :-)

It took a while for me to find that The anchor macro is temporarily unavailable, looking forward to it being restored :) So far looks good, love the / 

Like 2 people like this

Has there been confirmation that it's coming back? I use this macro a lot!

It will be back but there is no deadline for that. I have used workarounds mentioned here

https://confluence.atlassian.com/confcloud/confluence-editing-improvements-945107733.html

to get anchor for headings for now.

We use the anchor macro all the time, so it's very disappointing to have it removed, because we'd love to use the new editor.

Because of a long-existing bug where the TOC macro is broken when viewing Confluence articles through the Jira Service Desk Help Center, we can't use that workaround. 

Would be great if Confluence development team would talk to Jira Service Desk development team about how their new product changes interact with each other?

Avinoam Zelenko Atlassian Team Thursday

@Inga N. thank you for the feedback! We're working on making these changes easier to learn about and discover in our documentation. Sorry it took a while to find it.

@Sharon Helms we'll definitely follow up internally on that TOC bug.

I'm not seeing the "change comment" box at the bottom of the new editing page. Does this functionality still exist? 

Like 1 person likes this

I'm not seeing it, either.

Along those lines, just noticed that Publish without notifying watchers is a selection in More actions (the three buttons on the top right) instead of the check box to select/unselect. I use that functionality a lot, and having to use a dropdown to find that option is not optimal, in my opinion. Would love to see that action tied to a keyboard shortcut, at the very least.

Like 3 people like this
Avinoam Zelenko Atlassian Team Thursday

@Darryl St. Pierre the change comment box is one of the features we've removed from the fabric editor for the time being and are looking to get more feedback on. 

@Dan Winkler having that as a keyboard shortcut is a great suggestion. Rationale to it being slightly more hidden was that in its previous state it didn't get much usage but we still found it to be useful so we wanted to bring it back in a bit of a more subtle manner and wait for feedback before we replicate existing behavior all together.

@Avinoam Zelenko having it hidden in a dropdown makes it more likely that I will forget to use it when making a minor page edit. Don't want to overwhelm page watchers with notifications!

Avinoam Zelenko Atlassian Team Thursday

Thank you for the feedback @JoAnna Black . We have early explorations on how we'd reintroduce this in a more prominent way but are at this point still collecting more feedback on it. 

@Avinoam Zelenko I think the change comment box is an essential part of Confluence.  I always add a comment, no matter how big or small the change, and find it invaluable when I need to go back to one of our internal release pages and find out the why/when/who of a significant change we made to our software documentation.

I can't imagine developers checking in code without being required to add a comment to their commit, and that's how I feel about the change comment box. I wish there was a way to make that a mandatory step of all page edits, so I think losing that ability would be a major whiff in the new editor.

I totally and completely agree with @Dan Winkler about the change comment box. Just seeing version numbers is not very helpful if review is needed.

Definitely require that change comment box in the company as it helps especially for audit purposes.

Like 1 person likes this
Avinoam Zelenko Atlassian Team Thursday

Thanks @Dan Winkler , @JoAnna Black and @Patricia Jee for that feedback - it's great context to have and take back to the team.

Agree @Patricia Jee and @Dan Winkler . We've used this as part of our documentation process for a while now. If not the comment box in its current form, maybe a macro that, if placed on a template or page, becomes required.

Hey, I can't seem to figure out how to insert an image from another page!  When I /file, it just lets me upload new images from my computer.  Any help?

Thanks for your response, I tried that and it seems to make a new (identical) image, which is pretty useless for my application.. We need a shared instances of a diagram so subsequent diagram updates propagate across every related page.. as it stands with the new editor we would have to update each individually.. I will play around more with that, maybe I can trick the editor into linking an existing image.. is there a source editor available?

Sorry, read you question as a different need.

So what you'll want is either a link to the source document, or a live preview of the document. 

Hyperlink for the first, and I believe you'll need a plug-in for the second.

Like 1 person likes this

Put the image on a single page, and re-use it using the page include macro (would be my solution).

It's very nice but seems quite limited. What happened to the "page layout" section where you could select columns and how they are placed. Sometimes you want the left colum to be bigger than the right. 

 

Either way I have started to use it since it is the new experience so why not? I have used it to update the meeting notes blueprint. 

What I can't seem to figure out is how to use the new editor with the GLOBAL templates. I want to create one using this. Am I missing something or is it not implemented yet?

Like 1 person likes this

Page layout option still exists, it's called Columns now. You can either pull it up as /columns or from the drop-down macro menu.

Like 3 people like this

It appears that the new editor is not available for Global Templates yet. I would suggest using the Feedback option at the bottom of a page you've already created with the new editor and asking/commenting about it. I'm not convinced yet that Atlassian is actively watching the comments on this page (yet).

Like 1 person likes this

Darryl, Yes I have seen that but columns seem to be a very very simplified version of what I am looking for. A little too simplified. I played with it and it will have to do but it's definitely not as robust.

I see what you mean. I hadn't played with it enough, and I thought I had read that things were adjustable. Apparently not.

Only two columns!!!!!!!!!!!!!, 2 or 3 and all equal size. SO we are missing quite a few column options.

Yeah, wondering how they arrived at that design choice. Maybe they reviewed the macro usage and determined that it wasn't used much...?

Hoping it changes.

As I mentioned in another post here, it's unclear that Atlassian is reviewing this page, so use the Feedback option at the bottom of pages using new editor to let them know you want it.

Like 1 person likes this

Feedback has been given trust me!!!!!!!!!!!!!!

Like 1 person likes this
Avinoam Zelenko Atlassian Team Thursday

Hi all! 

Thank you for all the feedback regarding Columns (formerly known as Sections or Page Layouts).

I'll try and provide some rationale as to why we've rolled out with 2 and 3 columns. 

@Darryl St. Pierre touched on the usage aspect which is part of the motivation, as the 2 and 3 columns absolutely get used the most. Additional motivation is to take an iterative approach and learn how in the future we can make columns even better than they used to be vs. copying them as is - so all this feedback is extremely useful!

One of the main reasons is the desire, based on old editor feedback over the years, to help everyone make great looking pages by default which are easily consumable across all devices - something which the old sections layouts doesn't really do well, especially on mobile. The new ones are responsive and will stack vertically on smaller screens to maintain the intent of the content wherever it's being viewed.

We also made a point of making the 2 and 3 columns have the ability to break out of fixed width and go into either wide or full width to help with maintaining the high information density nature of the content that usually is added to them.

By all means, though, we don't have our heels dug in the ground and are eagerly waiting for this kind of feedback, so thank you for raising it!

Avinoam

Like 1 person likes this

@Avinoam Zelenko thanks for giving some background to the changes with columns. It makes sense, especially making it work better on mobile devices.

We really only have two problems with the columns as it is now:

  1. We need to have an option where you can have two columns, but where the right column is narrow and the left is wide (sort of a main section with a right sidebar). We use this setup for almost all documents, and this is now broken.
  2. It should be more intuitive how you add and remove columns. and how you can have two/three columns in part of your document and one (none) in other parts.
Avinoam Zelenko Atlassian Team yesterday

@Thomas Ohrbom I'll try to address your great feedback as best as I can:

1. I hear you on this as it's something we debated long and hard about as to the tradeoff between easily creating beautiful and highly legible content vs. catering to the side panel use case. We ended up landing on an approach where we wanted to gain more feedback first and early so we can rethink columns from the ground up and make them even better than they were vs. replicating them as is. With this in mind, like for many other key features we're actively seeking feedback just like this to inform the future iterations of columns. Would be wonderful if you could add a suggestion for this - or let me know if you'd me to do so on your behalf!

2. Would love to hear more details on this - today you can add columns either via the + menu -> columns or by typing "/columns" into the page. I actually didn't follow what you meant by "how you can have two/three columns in part of your document and one (none) in other parts." - could you please elaborate?

@Avinoam Zelenko For many pages I have used the three column section where left and right are tighter.

 

I think @Thomas Ohrbom is saying he wants to use different section types on one page. I use this too. Many of my pages use the side sections to add graphics that correspond to text in the section. Then I use a full page section to put a line that visually distinguishes the sections.

Like 3 people like this

I guess an interesting question here would be: What will happen to templates (and existing documents) created with the "old" column options once the rollout is complete? Will they be unusable until modified, or can the user community maintain their old style formatting until a document refresh occurs? It might be an easier pill to swallow if users could control this until ready to reformat a particular set of documentation.

However, I understand this may be easier said than done, and if there's not a cutoff some will continue to keep the old forever...

This decision has really crippled me. More severe than column width is the loss of sections, enabling the number of columns to change throughout the document. I challenge you to create the something that resembles Wikipedia pages with the new editor; you just can't do it. 

Regarding your statement that 2 and 3 columns were used most extensively; I suspect that this is because page formatting and sections was not easily discovered. I can't tell you how many times people have come to me wanting to know how I created pages with differing columns throughout. 

And then there are frames with custom formatting of colors. 

All gone in the new editor. 

@Avinoam Zelenko  I realize that the new editor has to have included a lot of trade-offs. I realize that compromises had to be made, but I need to emphasize how serious the situation is with the new editor. It has so crippled our ability to create useful content and has created such a massive backlog of content editing as a result of losing sections with different numbers of columns that I am forced to consider a recommendation that we abandon the use of Confluence at the corporate level, just as I was on the verge of recommending that we create a federation of the dozens of independent licenses across the company and move gradually to a large single cloud license. You have literally wiped away every argument I was making in convincing our IT department to accept Confluence as a corporate standard as opposed to the many small independent instances that they have been trying to kill. I honestly don't think you understand the gravity of the situation that I and many others like me are in.

Like 2 people like this
Avinoam Zelenko Atlassian Team yesterday

@Mike Thompson I want to thank you for the open and honest feedback - we don't take that lightly and I apologize that this is the sentiment - it's absolutely not an outcome we want for our customers.

I'd like to propose jumping on a call to discuss this more in depth and learn more specifically if there's anything we can learn/do to help alleviate this situation.

Would you be open to that?

@Avinoam Zelenko I'll try to elaborate on my two issues with respect to columns:

  1. We use Confluence as the technical platform for our management system (ISO 9001, ISO 14001, ISO 27001) documentation. All governing documents like procedures are setup with a right side panel today. The main content of the procedure will be in the main (left hand) portion of the page, while the right side panel contains details on related roles and definitions used in the document. All roles and definitions are pulled in through the use of Excerpt Include. All definitions and roles are defined in a separate space. Now this is all impossible to use, as two equally sized columns looks really bad and puts more emphasis on what is intended as extra info in a side panel. Also, since Excerpt Include is broken in the Fabric Editor we are effectively left without a single working governing document. This effectively stops our Confluence Cloud implementation project.
  2. Yes, my use case is as described by JoAnna Black above.

Hope this helps.

I really want this to be sorted out, and I still believe it will be. But time will run out in a few short weeks. I have sold in Confluence Cloud as the new solution on a corporate level at my employer. With the introduction of the Fabric Editor quite a few of the key functionalities that made us choose Confluence Cloud have been broken or simply disappeared. This is, in a word, challenging.

Like 2 people like this

@Thomas Ohrbom Cool to read how you are using Confluence for this purpose. I did the same thing a few years ago, and now it's the main product of my company (instant27001.com) with 30+ customers now using it. And they are all about to enter the same world of hurt after their instances are going to be upgraded.

I really hope Atlassian will fix the most blatant bugs before they push it onto them.

Like 1 person likes this

@Maurice Pasman that is interesting. I'm implementing this setup in my third company now. Started working with Confluence like this about five years ago. Would love to exchange ideas and experience going forward.

And yes, you should hold off on switching to the Fabric Editor as long as you can with the setup you describe.

Thank you for elaborating @Thomas Ohrbom !

 

The bug of excerpt include macro not working is a top priority issue and is very close to being resolved - I will be sure to update as soon as it's fixed asap! 

The new emoji tools are nice, finally the smile convention I'm used to with other apps.

Like 1 person likes this

We opted to have the new editor (fabric editor) enabled on our new Confluence Cloud instance. We have started a project introducing Confluence to 500 users in stage 1, and then later this year we will expand to 2500 users. We figured since this change is coming anyways within a few weeks (from what we understand), it would be better to have the users be onboarded using this new editor right away, rather than using the old editor first for a few weeks, then learn a new editor shortly thereafter.

Turns out the new fabric editor is very far from ready to be used as a full replacement for the old. We have found a lot of serious issues, and so far these issues are at the "Atlassian Investigating" stage. Here is a shortlist of major issues:

  1. Images - any images on a page that are wider than they are high will once the page is converted (opened in new fabric editor) be changed to squares, which in our case means a lot of added white space above and below the actual image. The only work around for now is to remove all images , and then adding them one by one. Vote for CONFCLOUD-65597
  2. Import Word Document - images appear to be imported as before, but once you open the editor all imported images are gone, replaced by a placeholder stating "Inline-media-image". Vote for CONFCLOUD-65580
  3. Uploaded files - attachments could previously be displayed on a page as different size thumbnails or text. Now only as fixed thumbnail. Also any files uploaded before converting to fabric editor will after conversion the page only download to your PC when clicked. No more preview in browser. To fix this, the files must be uploaded again. Vote for CONFCLOUD-65624
  4. Page Property macro | Hidden parameter ignored - this parameter is now ignored, which means any page propertis table on a page will always display. Vote for CONFCLOUD-65596
  5. Excerpt include macro broken - If you use one or more instances of the Excerpt Include on a page, all will look good and render OK in the editor, but once published none of the page content will display. All you see is a placeholder stating "Unsupported content". Vote for CONFCLOUD-65582
  6. Sections now very limited - we used the Section functionality a lot, typically with a right "sidebar" in documents. When converting a page to new editor experience this will always change to two-column mode (50/50 split). There is no way we can change this. Vote for CONFCLOUD-65581
  7. Navitabs add-on broken - it is no longer possible to place the Localtab macro inside the Localtab Group macro, rendering the add-on rather useless. Reported to vendor of Navitabs.

All in all this is very frustrating and we have had to (temporarily) stop our project.

PS! I've now added links to the bug reports.

Like 6 people like this

Wow. Lots of information here, thanks for sharing.

We're trying to rebuild our documentation processes and are currently in a holding pattern due to some other priorities. I saw this as a great opportunity to get this functionality turned on while usage was at a minimum. After being told we couldn't opt-in early (contrary to the announcement page), we suddenly had it available.

I'm still kicking the tires, but some of the comments on this page have been eye-opening. I haven't found much yet that's going to have a huge impact on us, just some annoyances, but it's only been two working days...

Basically any macro that accepts a rich contents get's broken

We are affected by this for both of our cloud plugins - ConfiForms (where you can define your custom layouts for the forms, with using any other macros to build a truly custom and user friendly forms) and with ConfiTemplates, where you can include content and excerpts from other pages and Confluence templates and mix them with page properties to create dynamic pages

 

We have spend so much time and efforts to make these plugins to work the same way in server and in the cloud and allow our users even to copy and re-use the configuration with copy-paste... but now - we have no idea what to do.

New editor just does not provide enough flexibility for us

Like 1 person likes this

We have tested a few more days now, and the list of broken/missing functionality keeps growing day by day. Here are some additional highlights

  • In browser preview of uploaded attachments broken - this goes for Chrome and IE. Clicking on an attachment listed in line on a page no longer brings up a preview. In IE nothing happens, in Chrome the progress indicator spins forever. Workaround is to use Incognito Mode or restart browser. Vote for CONFCLOUD-65624

  • Cannot create "undefined page link" anymore - this is a key wiki function in my mind. You create a new page and while typing it up you know you need additional pages, so you create links to these as yet not created pages. Previously this worked, and when clicking on these links Confluence created the new page and opened the editor on that page. Now you just get nothing.  Vote for CONFCLOUD-65634
  • Pages with certain macros won't be converted to the new editor - if you page contains a panel macro (incl. Info, Warning etc), or a Status macro, the page will not convert to the Fabric Editor when you edit it. Workaround is to remove all such macros, and then re-add them later. Vote for CONFCLOUD-65604
  • Edit Files functionality broken - if you want to edit Office files through the use of the Atlassian Companion app you now have to open the file through the Attchment List (... - page menu) and then selecting View on the relevant file. Vote for CONFCLOUD-65583

I've now added links to registered bugs. Please help vote for resolution of these bugs.

Like 3 people like this

My company's main product is content created using Confluence. Customers purchase a space export and take it from there. After I have seen what the fabric editor does to my existing content (we make extensive use of page properties, page includes. excerpt and info panels), I am very much fearing for the future. My customers are not going to be happy.

Incidentally, my customers are also Atlassian's customers.

Like 1 person likes this

So, I just created my space yesterday and I got into these 500 users? Can I not participate in this test please? I really need the old editor.

Will there also be a way to have somehow more than just 4 colors (red, yellow, green, blue... gray is no color) to colorize e.g. tablecells or status badges?

That would really help for a lot of things to be addressed. How about adding colors like orange,violet,cyan,pink, etc.

Like 1 person likes this

I dream of the day they let us set our own colour scheme. There are very few colours to chose from and a lot of them are a bit ridiculous. The status colours dont bother me to much but the rest of the colours do. To just be able to add a few colours of my own would be amazing. or define 4 colours for a colour scheme. anything really.

Like 1 person likes this
Avinoam Zelenko Atlassian Team Thursday

@Helge Staedtler can you please share more info as the new tables in the new editor have 8 color selection and status has 6.

Completely hear you @Dominic Jalsevac on custom color selection! I've passed that feedback to the team.

I don't understand all the positive feedback. Here is what I see in the new editor:

  • Adding columns moved from page layout button to macro and the number of available layouts reduced. Three columns with middle column wider is gone and two columns where either left or right is wider gone.
  • Text formatting and alignment; One button press for many common needs now requires two presses, with lots of real estate on the ribbon unused. 
  • Where is indent?

You added some cool new features but made the basics worse. 

The basics are important. I'll gladly trade all the improvements for the old experience.

Like 8 people like this

Absolutely agree with Mike! Old experience is way better than this "new"

I also find it very difficult (and unpredictable) to copy "stuff" around when editing the page.

Like 1 person likes this

Yes, cutting and pasting is a pain

I'm wondering what you consider "old experience". In my view, the prior experience was editor hell. You can go back and read all the massive complaints with none or very little response from Atlassian (other than tough, live with it). At least here you have someone responding to the posts with assurances that some if not most of the concerns are being looked at (not that they will be addressed.

I agree that the old editor sucks and an update was needed, but to do so and remove very basic functionality in the process seems ill conceived. One of the reasons I resisted our IT department's demand that we move to Microsoft Teams Wiki's was the argument that being able to set narrow column widths with a large center column and being able to create new sections with different numbers of columns is critical to being able to effectively organize information. It can be done with Teams, but not without programming. Confluence claim to fame was how it enabled non-technical creators of content to create attractive pages without any programming. Atlassian has taken away a very fundamental feature of Confluence with no warning and no recourse. 

Like 1 person likes this

From an aesthetics point of view, the new editor is better, but that's about it, it's like a poorly executed clone of Dropbox Paper.
There are fewer features and the features that are still there don't really work very well.

Trying to add images is an absolute pain before I could copy text including images from other sources and it would add it all in and upload the images whilst retaining some of the formattings at least, now just get image not found.

Once I managed to get the images in, there is no way to move them around, the scaling thing works nicely until you try getting 2 or more images horizontally.
Two is just about manageable using the left and right wrap options, but if there is so much as a space in between them it will freak out, but want to move an image up a row nothing happens, try to do a cut and paste that doesn't work.

There's even less control when trying to add images into an Expand macro

The code block macro doesn't Syntax highlight very well, if at all and there is no choice in the theme like before.

Once you get to the bottom of the screen it jaggedly tries to expand, maybe having a bottom margin would help. Also, get a double scroll window so the task-panel at the top scrolls up out of view, but scrolling up just scrolls the text area.

I can see what they are going for but it just makes things more awkward really, really hope it gets some much-needed improvements.

Like 2 people like this

@Avinoam Zelenko

Hi,

Confluence is a great tool in general, but since the more recent updates to the way tables are managed (in the cloud version), all my projects are broken.

We use tables extensively, and due to the column sizing not working anymore, they are a complete mess.

I spoke with support, and the issues are known. However I don't feel they are going to get love any time soon.

Disappointed.

Richard

Like 4 people like this

I'd love to vote it up, since I am also bugged by this, but there does not seem to be a bug related to this on https://jira.atlassian.com/browse/CONFCLOUD.

I have pages using a 2 column table, the first column being too small (single words are broken up) and the second (containing a page include) ending up so wide, a horizontal scroll bar is added to the published page.

They have just created https://jira.atlassian.com/browse/CONFCLOUD-65650 after investigating my support request. Please vote it up :-).

Avinoam Zelenko Atlassian Team Thursday

@Richard Franke I'm so sorry to hear about your experience with tables lately!

I can assure you that we're looking into this on two fronts as a top priority:

1. Tables on new pages created using the new editor. Column sizing bugs are top priority and we're working to resolve these asap.

2. Tables on migrated pages - would love if you could share some examples with us so we can learn how to improve this, aside from bugs of course. Would be happy to jump on a call.

Can content that is created on a "new" instance (using Fabric editor) still be exported and be used on an "older" or "server" instance?

The storage format seems to be the same - have not tried the export/import though. REST API calls and storage parsing still works in our plugins, so assuming, the format is the same.

What you cannot do is to copy from cloud to server (and from server to cloud) editors anymore. Is totally possible with old editor and works well for many cases (when you have same macros / plugins).

WHAT? Really? Is this introduced with the Fabric Editor? What have they done!

How can I insert a web link image?  Here is the old way... Ironically, clicking the camera icon in this editor is similar, allowing reference to a URL...

Screen Shot 2019-02-17 at 11.31.56 PM.png

Like 1 person likes this

Is there a way to get the old page format back?  This would be left-aligned text.  I'm now looking at 1/3 of the available browser width.  It feels very restricted.  There is a lot of wasted screen real-estate.

A major benefit of having the page left-aligned is that many times I have several browser windows open and I will move the browser windows themselves so I can view content on each page easier.  I can't do that very well with text that is aligned in the center of the page. 

Like 5 people like this

That would be nice yeah. While it looks nice and clean at first sight, it is just not so suitable for most use cases for Confluence where lots of text are involved (wiki, documentation).

Like 2 people like this

Looks like the UX architects behind this changes were only "mobile first" thinking. I can't explain this centering idea other than that.

Hello!

 

This is really a great improvement. Some things I couldn't figure out:

  1. How can I make us of the full screen width of a page, because now the standard behavior is just 70% usage of full width
  2. CMD + / is not working for me. I can't access all keyboard shortcuts in Chrome.
Like 3 people like this

The restricted page width looks and feels like a bug to me.  It is very odd to have the text floating in the middle of the page.  It makes the product unusable for me.  I will file a bug report.

Like 2 people like this

Agreed. Full width as an option is a must.

Hello!

How can I add multiple images into a page publication? Before the changes I used macro with just 2 or 3 clicks: like macro, add (or insert) images, then a system window where I could add several images at once, then they appeared as thumbs in the macro window and when uploaded - publishing. Then I could organize them on the page as I wanted - change their width, break them with a new line etc.

 

Now I have to click on Macro icon, then there is no according tool in the drop-down menu - you have to click on View More (!!!!!), then you see a Gallery macro, where you supposedly can add several images at once but you have to specify the number of columns!!!

I'm really frustrated! You ever heard a saying "Better is the enemy of the good"?

 

I need to add many images and organize them easily like it was before. But looks like even if you decide to bring it back, months will pass.

Also, this width... 

Something's different/broken since about 10 days, perhaps related with this update. 

 

We cannot indent whole bullet list using the indent button. Bullet list stays locked to the left side. Only second/subsequent items in the bullet list can be indented but that is not what we are looking for.

 

Any idea?

Like 1 person likes this

I'm working with a lot of legacy pages and creating new ones. Fortunately the existing bullet lists are untouched. If I copy/paste a bullet and the list indented under it, the indent comes with it. But what a pain.

Yes it's a workaround. But what a pain. I hope it gets resolved soon.

I suggest that Atlassian spend less time on new features, and more time on fixing bugs or use case flaws in the features which exist thus far. Once stability / use-ability is returned, they can go back to the fun and sparkly side of development.

Like 4 people like this

People have been suggesting this for years, but it seems that just keep going in the opposite direction

I'm really digging the new editing experience, especially the addition of Action Items, Decisions, and the improved table interface.

 

I'm curious when this new editing experience will be available for creating templates. Our project is looking to leverage templates much more to speed up documentation, but when creating templates there's not an option for choosing the editing experience. When is this planned to be released for templates?

Avinoam Zelenko Atlassian Team Thursday

@Aaron Cheney as we're rolling out gradually, this will reach most customers within the next few weeks, so stay tuned. We'll be announcing it with emails and in-product banners so you won't miss it (hopefully)!

Has anyone found a way or workaround to add the collapse and expand feature to a code block or any other part of a page? This was available before, but now I can't find it. 

Avinoam Zelenko Atlassian Team Thursday

@Christian Elbe you can add expand either via the + menu or "/expand" on the page, but you currently can't nest it into other block content like tables and code block. That is something we're working on enabling in the future, so stay tuned.

Like 1 person likes this

How can I add a link to an image?

Do you mean add an image to a page and have it load a page or something when clicked? Doesn't seem to be an obvious way to do that.

If you mean adding a link to a page that brings up a picture when clicked, that's just the Link macro on the toolbar

Yes, add an image to a page and it loads a page when clicked, it was possible before.

Yes, this functionality is broken in the new Fabric Editor. See CONFCLOUD 65640.

I see, thanks!

The Task Report macro is now also broken. It is no longer possible to edit settings of the Task report macro in the Fabric Editor (see CONFCLOUD-65666).

The list of major issues with this new editor keeps growing day by day. 

So far not a single issue we have reported has been resolved.

Avinoam Zelenko Atlassian Team Thursday

@Thomas Ohrbom thank you for logging that! We just resolved it!

@Avinoam Zelenko thanks!

I'm crossing my fingers and hoping you will get to all the other issues I've logged on the Fabric Editor also soon :-)

Some of you know this, some may not...

This page is (seemingly) not actively monitored by Atlassian. If you discover issues or limitations, there are two things you can do:

  • While creating a new page in your own Cloud instance, use the Feedback option at the bottom of the page to submit info to the developers, or
  • Submit a Bug Report with Support. @Thomas Ohrbom  has been awesome with this!
Like 1 person likes this
Avinoam Zelenko Atlassian Team Thursday

Hi all,

 

Apologies if this page went feeling unmonitored - it absolutely is and you should have seen a bunch of comments by me both here and to the bugs/suggestions you've logged.

 

Generally though, @Darryl St. Pierre 's recommendation above is spot on since it helps us get better and we look at all the bugs/issues logged either via support or directly within the editor on a daily basis.

 

Thank you!

Avinoam

Senior Product Manager, Confluence Cloud

Like 2 people like this

@Avinoam Zelenko , thank you for all the feedback! I can't speak for anyone else, but it was feeling a little quiet in here since the page was originally published. On the plus side, it's been great seeing what people have been running up against,  especially since my org has a a lull in new content creation recently.

Like 1 person likes this

Comment

Log in or Sign up to comment

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you