On Mon, 2018-02-05 at 23:39 -0700, Bindul Bhowmik wrote: ...
> > If I may ask as a user of the library, would the new site still have > parts of the site that are generated from releases? For example, > Javadocs? > Hi Bindul Yes, most certainly javadocs would still be there (given that javadoc content gets published to ASF Nexus / Maven Central with every release and therefore is available) but some Maven generated reports would likely be lost. I _personally_ never found them useful, so I do not see it as a big loss. > Also, irrespective of the site generation tool or content format > selection, would it help to move the generated site to git (use > gitpubsub) and have the site built/published from Jenkins? I happened > to see a discussion [1] on builds@a.o recently about it. Looks like > the tooling will also be able to provide a staging site (soon). > Absolutely. Being able to take a full advantage of better tooling is a primary motivating factor for me to consider migration to Jekyll or a similar content rendering engine. This is a great example of a good project web site http://struts.apache.org/getting-started/ What makes it massively better is not a prettier look but that 'Edit on GitHub' button. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
