Robert Burrell Donkin ha scritto: > On Tue, May 12, 2009 at 10:25 PM, Stefano Bagnara <[email protected]> wrote: >> Robert Burrell Donkin ha scritto: >>> james has a confluence instance at http://cwiki.apache.org/JAMES/ >>> which looks to be used only for experimentation. i'd like to start >>> using it to develop higher quality user centered documentation. >> 1 year ago I replicated our website in confluence because I thought it >> was better to generate the website using a wiki than mvn+svn, > > i find that creating content in confluence is much easier and faster
+1 > IMHO maven works fine for more developer centered content but > confluence would work better for the project and server documentation +1 mixing them should give the best result. > http://cwiki.apache.org/DIRxDEV/exporting-a-confluence-space-as-a-website.html > gives some details of how to customise the autoexport template. this > would allow the navigation bar etc to be I already did it (created the template for the autoexport plugin). As you can see this one is generated by confluence and has navigation and style: http://cwiki.apache.org/JAMES/ The autoexport was already exporting en exact copy of our james-project website. But there was not consensus on the use of cwiki because some PMC required that we had the generated website in svn. Maybe something has changed today (that work is from 2 years ago, cwiki was the new kid on the block at that time). On people.apache.org we already have a /www/confluence-exports/JAMES folder with the automatic export. It just require consensus + rsync to the website folder. Both CWIKI and websites are backupped nowadays, so writing it to svn and checking it out to people is a big waste of time. I don't thing that anyone is reviewing diff files on site-dev because they simply are hundreds of diffs for each minor website change, so the review process should only be done on the sources. Having one more step is simply more error-prone and even less "secure". I bet if I regenerate the whole website and then in the generated sources I put a "Stefano is the best PMC committer" somewhere in the pages no one will notice it, if I instead do this in sources I think someone will notice it. james/site/trunk/[email protected] is a waste of time, resources, developer-time, review-time, security. >> but at that time we had no consensus on the workflow, so it simply was a >> testo >> to see how it worked. > > switching away from the subversion based site to direct autoexport > would be a big process change and we'd probably need consensus. > perhaps ti might be able to compromise by autoexporting to a different > location and then manually checking in... I'm all about making it easier. The easier is to keep things updated the more probable we'll keep it updated. The last step into a fully automated website would be to automatically export the website for projects from the hudson builds. I did some research in this (a lot ago) but I failed (I don't remember what was the blocking issue.. maybe something related to the mvn site deployment). Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
