[DEMO] Desite

[cstamas]

"De-site", try to reproduce all the Jaxen site had without using maven-site-plugin.

Check DESITE.txt for progress.

In this PR, to build all (artifacts and site), you need only one Maven invocation:
mvn clean install -P site

Checpoint No1: lays down foundations, and renders page, but just basics, no CSS, no proper templates, no nothing yet, just a "welcome" page that contains all the content that CURRENT jaxen site has (generated ones, authored needs to be translated from XDoc to Markdown).

[elharo]

This seems massively more complex than using the Maven site plugin. A lot of things the site plugin provides out of the box have to be manually written with this approach. That's good if you want to customize everything, but not so good if you just want to get a usable site for a project without excess effort.

[elharo]

That these are the same is a coincidence. They are not semantically equivalent and shouldn't be linked with a variable.

[cstamas]

This change is not needed, i was just lost about directory names, artifactIds and <name> names...

[cstamas]

This seems massively more complex than using the Maven site plugin. A lot of things the site plugin provides out of the box have to be manually written with this approach. That's good if you want to customize everything, but not so good if you just want to get a usable site for a project without excess effort.

Unsure what you refer to "have to be manually written", as basically all that maven site provides here is "skin", nothing more, but that one could be just zipped up for jbake and reused, and using unpack-dependency pulled down and done.

[elharo]

By my count this adds eight non-empty files to make this work for things like sidebars that come for free with the maven site plugin. The existing jaxen site only includes custom jaxen specific content.