Yes, the new editor is good, and better than the old one. However, my existing editor is already excellent for handling, navigating and editing text, especially when the text size increases past a few paragraphs. Therefore I am much more productive with my existing editor and always will be, no matter how many shortcuts and such you put in and I learn, until you have basically duplicated everything my current editor has. And I see no point in you doing that.
A more significant reason is that now I can't edit pages offline. Sure, I can type in markup and it will be converted when I put it in, but I won't be able to edit existing pages that way. That takes out a lot of opportunities and time during which I can write, further degrading my productivity. Also, given that there already is a workaround in wrapping my text in a non-renderable macro, thus enabling me to read and write the wiki markup, there is no reason not to make this an "official" feature that will appease the many (if not most) of us that prefer the wiki markup option.
Yet another reason is related to session timeouts. When this happens, say during a long meeting or other reason, for the most part Confluence is able to handle it and bring the content back after re-logging in. Sometimes, however, it fails, and it is frustrating to lose work and the wasted time it is typing it back in.
Will you bring back the wiki markup option as an official feature, or will we have to continue using the kludge to get aronud it? After all, it is still a wiki, or are you going to rebrand it as a CMS? ;)
Thanks,
Bjorn.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.