As the Amarok<\/a> team have discovered, it’s a whole new ball-game. \u00a0You start with a Contents page, listing all the pages you think you’ll need, and you start to build. \u00a0Before you finish I’ll guarantee that you’ve thought of something that would have been better on a page of its own. \u00a0As it happens, that’s not a big problem – you can edit the contents page and create a new page that way. \u00a0But wait – what seemed good organisation to start with is less convincing now, and maybe it would be better to move things around, re-organise a little. \u00a0Hmm – not so bad! \u00a0There’s a little icon for Move – ah yes, it moves the page to the structure you want and even leaves a re-direct behind, in case someone uses the old link.<\/p>\n Sounds pretty good, doesn’t it? \u00a0Unfortunately this is where it starts to come unstuck. \u00a0Once you’ve finished, the Translators move in – and where should their links point? \u00a0If they translate from the original they probably will use the original link, which is now a re-direct. \u00a0That’s not good. \u00a0We have to clean up re-directs, in that case, and that’s when we find that moved pages have been moved yet again, causing double-redirects – an even bigger job for cleaning up. \u00a0You see, we can’t just delete them – there could be a number of pages that link to the old page, so we have to track all links, and in the case of the double-redirect we have to do that for both levels of old pages. \u00a0It can be quite difficult to follow, but it’s a necessary part. \u00a0Happily we have almost finished the double-redirects – heaven preserve us from triple-redirects!<\/p>\n We think so. \u00a0It’s experimental, yes, but it should help anyone starting new documentation. \u00a0Most of what you see on UserBase is in the “Main” namespace, but today we have opened up a new namespace called “Draft”. \u00a0You can start your documentation there without worrying about the issues I’ve just talked about. \u00a0Move things around as much as you like – just remember that in the end any page links will need sorting!<\/p>\n The idea is that when the pages are ready we can simply move the whole structure into the Main namespace if any redirects have been dealt with, but if it has proved more complex and things have been moved around a lot we can use Copy\/Paste to create the Main pages from the Draft ones, fixing links as we go and losing all the redirects on the way.<\/p>\n One last thing – you have to be the main writer for your documentation, and you are used to an entirely different kind of mark-up, finding that attempting Mediawiki mark-up gets you utterly confused. \u00a0We can handle that too – and again the Draft namespace is the best place to do it. \u00a0Put your plain text there. \u00a0Add any markup that will be obvious to us, for instance <bullets>, \u00a0and we will help you get it looking the way you want.<\/p>\n Using Draft\u00a0<\/a> should remove a good deal of anxiety and hassle, but we need you to try it out. \u00a0Take a look at Draft<\/a> and let us know what you need to make it even better for you to draft your documentaion. \u00a0See you there!<\/p>\n <\/p>\n“So you said I could make it easy for myself?”<\/h1>\n
![\"\"](\"http:\/\/lydgate.org\/blogs\/wp-content\/uploads\/2011\/06\/UserBaseLogo.png\" "\\"UserBaseLogo\\"")
<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"