it looks like one key issue you're facing is specific to https://maven.apache.org site, = our own site that is: 1. an aggregation of near 100 subsites representing each one Maven subproject (see https://maven.apache.org/scm.html#maven-sources-overview) 2. that uses Apache infra's svnpubsub engine to push the html to live site, then adds some delays and quirks that bite you
good news, I wrote documentation on these 2 aspects: https://maven.apache.org/developers/website/index.html https://maven.apache.org/developers/website/deploy-component-reference-documentation.html with a "component helper" to ease component deployment without really understanding all the nitty gritty details under the hood: https://maven.apache.org/developers/website/component-reference-documentation-helper.html I'd be pleased to have as much as Maven maintainers read these docs, try to understand and tell me what I need to explain more, because it seems I wrote doc that nobody reads and even understand that they are hit by some quirks at this Apache publication and sub-projects sub-sites aggregation level all other discussions about one project site publication (Doxia, formats, reporting, etc) are also valid, and even more impactful because they impact any project that uses Maven Site Plugin to generate their website It's just 2 distinct discussions to have (and at some point converge back) Le vendredi 18 novembre 2022, 23:56:37 CET Hervé Boutemy a écrit : > +1000 > this evaluation is much more fair > > it does not mean that looking at rearchitecturing a new site generation > would not be useful > > key is > > > I like some parts of this. I don't agree with others. > > I suppose the good ideas from the Wiki should be prototyped: > - on a basic mono-module project > - on a multi-module project > - and eventually on an aggregation of sites (seeing if it can scale to the > Maven site itself) > > Le mercredi 16 novembre 2022, 13:08:08 CET Elliotte Rusty Harold a écrit : > > I like some parts of this. I don't agree with others. I agree that > > maven site isn't competitive with other site builders, but that was > > never really its purpose. I think it's OK for generating a site for a > > Maven project. I wouldn't expect it to be used for anything else. As a > > maintainer of one such site <http://www.cafeconleche.org/jaxen/> it > > would be very inconvenient for me if this plugin disappeared or > > changed in a major way. > > > > The old site design just works. We don't need so-called modern, > > responsive sites. For our purposes — documenting code — the 20 year > > old classic HTML we use is just fine. In fact, I'd say it's superior > > to modern designs as implemented in practice. > > > > I do wish Maven hadn't gone its own way with NIH components like > > Plexus, APT, and Doxia that are all essentially used today by maven > > and no one else. However in fairness this all happened twenty years > > ago when alternatives that have become de facto standards was not > > obviously better or simply did not exist. We should modernize our > > dependencies where possible, but I don't think a rewrite is worth the > > effort and I would oppose anything that broke existing sites, links, > > and workflows. > > > > When counting "wasted engineering hours spent on it", these are at > > least a couple of orders of magnitude lower than would be spent on a > > radical replacement of the sort being proposed. It's like proposing we > > build a new Lamborghini to save the money we spend on oil changes for > > our 2002 Ford pickup. Of course this is open source, so if anyone has > > the time and money to spend on an alternative site plugin that > > scratches their itch, by all means they can do it. However this should > > be a new plugin projects can adopt or not at a time that's convenient > > for them. It should not replace the existing plugin so many projects > > already use. > > > > On Wed, Nov 16, 2022 at 5:19 AM Tamás Cservenák <[email protected]> wrote: > > > Howdy, > > > > > > This is really just a brainstorming thread I'd like to spin, regarding > > > Maven Site stuff. > > > > > > Again, the message is in wiki > > > https://cwiki.apache.org/confluence/display/MAVEN/Quo+Vadis+Maven+Site > > > > > > But I would like to make discussion happen here on dev ML. > > > > > > Thanks > > > T > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
