On 03.08.2012 03:06, Bob Harner wrote: > I have assumed I would be spending a bunch of time on this in the > second half of 2012 and am willing to get started now. But I was > hoping Uli was already working on it and just needs some help :-) > > I believe Uli is talking about the approach described at > http://www.dankulp.com/blog/2012/03/svnpubsub-for-confluence-sites/, > which I agree is the obvious way for us to proceed, at least for a > while. It allows us to keep our high-quality documentation intact with > little disruption. Any other approach (converting to another content > editing system, with a different markup language) will likely require > thousands of manual content tweaks of the sort that was done when the > docs were first moved *into* Confluence.
Exactly. I've been exploring this option and it seems quite straightforward and simple. No need to touch much, if anything. > > As for the javadocs, I'm wondering why there is talk of moving them. > What's wrong with the current process there? Our uninformed guess was that a switch to svnpubsub would make it impossible to manage website content other than through svn/git (speaking of which, does that even work after our switch to git? ;)). So the current process of simply copying it into the correct place on people would not work anymore. > >>> I like that it will be possible to navigate to a page and click an edit >>> button. AIUI this just works for content managed by the CMS. With our approach we'd just use svnpubsub, not the CMS, for the reasons stated above. Uli --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
