Site generation

[Stefan Bodewig <bo...@apache.org>]

On 2013-11-03, Dominik Psenner wrote:

> On 11/02/2013 10:41 AM, Stefan Bodewig wrote:
>> On 2013-11-01, Dominik Psenner wrote:

>>> 2013/11/1 Stefan Bodewig <bo...@apache.org>
>>>> I'd like restructure our codebase a little as it feels a bit scattered
>>>> to me, in particular I'd like to move
>>>> src/* => src/main/* (except for site)
>>>> tests => src/tests
>>>> examples => src/examples
>>>> extensions => src/extensions
>>> And maybe src/site to some other place like doc/website and split the
>>> build process so that site and src are no longer tightly bound to each
>>> other?
>> OK, this will take some POM massage - or moving away from maven for the
>> website build, which I wouldn't mind at all.
> The smaller the required tool set, the better it would be. I'm sure
> you know which way's the best.

Not really.

I think the docs used to be static HTML files and were switched to Maven
in order to make it easier to share the L&F with the rest of Logging.
But in fact, much of logging (main site, log4j and log4php) is using a
different skin by now.

The other benefit was removing the boilerplate HTML required for each
and every page.

I'm not sure which tool would be easier for us, not sure whether there'd
be some markdown => html solution that could be run from within NAnt or
what else NAnt could offer in that space.  XSLT would certainly work but
not really simplifies anything.

Another option might be to use the Apache CMS for our static
documentation and only add the API docs from our build - that would
imply we'd no longer ship the documentation pages with the log4net
distribution.

Stefan