check out how to add usage / installation documentation as markdown to the maven site (see e.g. here)
set up an ist-dresden.github.io project to avoid 404 when somebody enters that site, add a robots.txt and put in some links to the other sites. Possibly that can be a real maven site, too.
There are other variants to create sites for the projects like using mkdocs itself or employ Jekyll as Github Actions do normally for .md files, but having maven sites is already set up for many of our projects, and those can look surprisingly good and be nicely functional.
Currently some documentation is at https://www.composum.com/home/blog/pages/composumAI.html / https://www.composum.com/home/pages/editing/Composum-AI.html and https://www.composum.com/home/blog/AEM/composumAI-AEM.html , and various .md files in the project itself. It is probably better to put that into a real site.
One way is to brush up the https://ist-dresden.github.io/composum-AI/ site on github. Things to do:
There are other variants to create sites for the projects like using mkdocs itself or employ Jekyll as Github Actions do normally for .md files, but having maven sites is already set up for many of our projects, and those can look surprisingly good and be nicely functional.