On 4/2/07, Anil Gangolli <[EMAIL PROTECTED]> wrote:
Confluence autogeneration seems to be based on Velocity templates. We can probably start by cloning one and doing some edits.
I did a little poking around over the weekend too, but I started by looking at Matt's post and the Wicket site. http://raibledesigns.com/rd/entry/slick_looking_confluence_sites I don't want to delay our "we've graduated" announcements forever so I went ahead and put the basic site in place at http://roller.apache.org using our existing mechanism. See the readme in ./site for details. I'd like to switch to Confluence auto-export just as soon as we can figure it out.
Several teams seem to have decided to use multiple Confluence spaces in their auto-generated site. The Geronimo team has a pretty good writeup here ( http://cwiki.apache.org/geronimo/geronimo-cwiki-documentation-architecture.html ) on how they've organized their site. The different spaces can have different access rights; so, for example, some portions we could have limited to committers/CLAs on file while allowing edits by the public in other areas. This affects what we can ship in distributions. However, looking at the Geronimo or Apache Directory sites, I'm not sure if I understand all of the reasons for all of the separated spaces. It seems like something we should decide on before we start dumping a lot into the single Roller space.
I don't understand why they have so many spaces either. A lot of their spaces seem to be for different versions of Geronimo docs. Since we're using Open Document format for our "official" docs, I think we only need two spaces. We need a committer access only area for the Roller website and a less restrictive space for new feature proposals. I haven't yet found a step-by-step guide to setting up auto-export and the cron-jobs necessary to make it work. Anybody have any pointers? - Dave
