I am trying to love confluence v4, but it ain't happening. I have started using notepad again for my work in progress and other working documents.
I need to go back to a wiki system, that auto saves, has revision history, and those other good things.
Any suggested "traditional wiki" tools, preferably that are textile based?
Many things you mentioned, auto drafts, revision history etc are still available. Only thing that you are missing is wiki markup.
Confluence Source editor is the alternative for wiki markup and you might find it useful. You will surely need some time to adjust to the new XHTML syntax and will probably need some time to get over wiki markup!
Bob, Thank you!
This looks very cool. However I don't think it will help me since we already did the migration from 3.x to 4.2.
I would need, minimally, a plugin that lets me tag a (say a new page) page as "wiki markup forever" so all editing would always be done in wiki markup mode for that page.
I also need the editor to be fast, and to suppress all the wizbang stuff in the 4.2 RTE.
Bob, because it's a one-way trip. Entering text in the new editor is actually OK. It's a bit odd at first, but you get used to it after awhile.
The problems are things like
Atlassian have done a sterling job with the new editor, but we love(d) Confluence because it was a plain. text. editor. Relatively simple markup.
Kathleen, I certainly agree with those points too and those need fixing. I also think the new editor is (mostly) very nice and accomodates wiki markup quite nicely (compatibility mode and typing). And they had to do something to avoid the round tripping problems. I would have preferred if Atlassian actively supported a hybrid scenario - page content with both wysiwyg and wiki content. They built all the capability to do so (compatibility mode - insert wiki) except they forced conversion and talk about discontinuing. Complex macro pages are more difficult to edit in wysiwyg and wysiwyg provides no value in these cases since you always have to preview anyway.
I agree Bob. I am feeling the pain taking the large amount of complex scaffolding / reporting pages I have into Confluence 4.x. I am not looking forward to the expected pain I will be feeling converting these pages to be 4.x compatible - doing it in the new editor is also going to be a visual nightmare. All that aside ... I do believe for the general user the new editor is a BIG step forward ...
Yes, it's blasphemous, but sadly very valid. If the heretics don't ask, they silently go elsewhere. If they do ask, at least there's a chance to convert them back.
(And I speak as a heretic - I'm really struggling without wiki markup - it's simply not working for me)
Bob, you're my hero!
(Note to self: read whole post before firing off snippy reply).
For the last 3 months I've been telling people (who've been using Confluence for a long time in a random, unstructured way and were unimpressed) just how great it *can* be. I wasn't looking forward to the backlash when all my PR work gets tainted by the interestingly wacky learning curve on the new editor. Or editing XML. This plugin will give me some control over that.
Oh, and thank you, also for the table-plus macro. It's ace. :)
Edit: Sorry, samjones -- I was just trying to reply to Bob, not burble in a non-answer to your question. But while I'm on the subject, I've heard there's a github wiki but I don't know if it's textile-based.
Hi Community! 2018 was filled with changes for our team, both big and small, and we've taken a lot of time to both celebrate our wins and recognize areas of improvement. One thing that we're a...
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!
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