Our wiki is used mainly with lots of scaffold formulars. They are mostly bound with the macro live-template, so the code comes from templates directly.
When moving to Confluence 4.x the wiki markup will just disappear. So users will be confronted with pages to resave with html code and no wikimarkup anymore.
I'm not familiar with this and would know what are the bests practices for this situation.
Normaly, we will pass from 3.4 to 3.5.13 (really shortly) and at last, with 4.2.2 in the same week.
People want a zero effort transistion, so please some advice will be really appreciate.
Michael
As you know, the bigest change in Confluence 4.x is that whr wiki markup editor is no longer available. You can find some reasons of why Atlassian decided to abandon the wiki markup editor in this link.
For the normal user, the new rich text editor is easy to use for everyone who has used a text processor. For the wiki markup die-hards, the rich text editor actually parses all wiki markup tokens and fortmat the text as you write. You can find more information in this link.
Hope you find this information useful.
Alex.
Hi Alex,
sorry for the delay.
thanks for the link. Was really helpfull to prepare a new migration plan.
SIncerly,
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.