I have already discarded Sphinx, even though I like it, it seems more
appropriate to use a tool that is standard in the Apache community.

I like the suggestion to distinguish between site, wiki, and docs. For the
site, I see that many projects use the maven site plugin to generate the
site, that seems to be the most self-contained and straight-forward
solution, because maven is a prereq for building Twill anyway. Is there a
clear advantage of using CMS over maven?

-Andreas.


On Tue, Dec 10, 2013 at 4:31 PM, Patrick Hunt <[email protected]> wrote:

> Take a look at what we did for whirr, there's alot of background here:
> https://issues.apache.org/jira/browse/WHIRR-19
>
> I'd strongly suggest you use (or at least seriously consider) Apache
> CMS. One question you should answer; what will be on the site, vs on
> the wiki, vs in docs that ship with the release. IMO keeping the site
> light, frequently updated docs in wiki, and apis in the release work
> well. See cassandra for an example in the extreme:
> http://cassandra.apache.org/
>
> Patrick
>
> On Tue, Dec 10, 2013 at 1:33 PM, Andreas Neumann <[email protected]> wrote:
> > Since I did not get a response on this, I will assign to myself and take
> a
> > first stab. I am gonna try a couple of tools including mvn and sphinx and
> > share the results.
> > -Andreas.
> >
> >
> > On Fri, Dec 6, 2013 at 11:40 AM, Andreas Neumann <[email protected]>
> wrote:
> >
> >> Everybody,
> >>
> >> bootstrapping the Twill podling is almost complete and the only
> remaining
> >> task is to create the website. (TWILL-14).
> >>
> >> A good way to start would be take the existing Weave introduction at
> >> github (https://github.com/continuuity/weave) and adapt it to Apache.
> But
> >> before we can do that, we need to agree on the tool that we want to use
> to
> >> create and maintain the website. We could use the Apache CMS, we could
> use
> >> the maven plugin, or we could choose a different tool as long as its
> >> license allows us to use it and check it in with the source.
> >>
> >> What do folks on the list suggest / prefer?
> >>
> >> Cheers -Andreas.
> >>
>

Reply via email to