Thanks Marco!
I also do think that multi-version documentation generation is a necessary feature. And that the current "gh-pages" branch approach is a bit limiting/awkward.
So if we would have some automated system, which takes a Git repository, processes relevant branches and renders those documents in a way that they can be hosted on an HTTP server, then we would have a solution?
When it comes to templating, I think Eclipse IoT could provide a default template which project can either ditch or customize.
Now I am just brainstorming ...
If we would have some sort of Maven plugin, which takes an input file for a project and renders out (using other tools) a full set of documenation for all branches of a project, using some template, then we could simple render this is a local directory which "
docs.eclipse.org" would pick up. Such a job could run on "HIPP" instances and re-use the file permissions of the Eclipse infrastructure. If the plugin is smart enough, it will generate documentation for each branch and render this is in sub-directories like "
doc.eclipse.org/kura/2.1.0".