Cloud Editor - Where is it heading to?

Deleted user September 25, 2020

Hello Atlassian and fellow Confluence Cloud users,

Since the advent of the New Confluence (Fabric?) Editor, the issues have been aplenty and the complaints shared amongst users.

One big question, what is the long-term plan for the Editor co-existence?

  • Will the legacy editor be kept for the foreseeable future without a rough timeline for when its fate changes?
  • Will there finally be a cut between the new and the legacy, resulting in the latter being ultimately removed?
  • Will there be a point in time where features between the two match so much that old pages can safely be moved to the new editor?
  • What is the matching plan for the 3 different Editors: Server (markdown is diff), Cloud and Cloud-legacy?
  • Is there any intention of giving the choice of editor to the authors while keeping the backend information compatible?

I don't mean to say that the decisions taken so far for the New Editor have been the most well received ones, along with improvements, there have been a lot of regressions (performance with table sizes, adding links of any page in confluence, nesting of objects). The transition process was very clunky, the backlash coming from customers must have burned more than a couple of ears at the Atlassian offices.

The New Editor is what Confluence needed in order to evolve, it can't stick to the old that long (or can it?) at the cost of damaging the look of so much older documentation.

What can we expect for Confluence?

Confluence has been such a great tool, it would be great to hear about what to expect.

Cheers,

Norberto

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events