Le vendredi 18 novembre 2022, 07:57:59 CET Slawomir Jaranowski a écrit : > Hi, > > some my thoughts > - site looks can be changed be skins - so can be more modern yes it seems people don't understand the menu generation with it's "decoration model", then we don't see many people doing more skins
Having graphic people being able to do skins would be awesome, that's one of the benefits I see in Tamas proposal: I still need to understand how the other static generation tools manage the menu creation and overall "decoration" of the main content of a page > - long time on build site is caused by multiple executing the same Maven > phase for many reports [1] true thinking at "why": because the maven-site-plugin does the report goals invocation, it's not Maven core that's one of the reasons why I love Tamas idea about having Maven generate "*-reports.jar" then the new site rending process just rendering to HTML I don't like some words of Tamas on the topic, but there are also very good ideas that could halp a better new site generation architecture :) > - some reports, like tests result, static code analize is not usable for > static documentation - such reports should be generated by CI nowadays as you know, I disagree: it is usable for some use cases, which are not the use cases you are interested in > > [1] https://issues.apache.org/jira/browse/MSHARED-1044 > > śr., 16 lis 2022 o 11:19 Tamás Cservenák <[email protected]> napisał(a): > > 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]
