Hi, As we discussed yesterday the way our website is created from multiple repos and branches is somehow incoherent: some parts of the website have separate repos, other parts have a branch in a code repo, other parts have a branch in a website repo.
For example: * the `/log4j/jakarta` directory is published from the `asf-site` branch of the `logging-log4j-jakarta` repo (which also contains the code of Log4j Jakarta), * the `/cyclonedx` directory is published from the `cyclonedx` branch of the `logging-site` repo, * the `/log4j` directory is published from the `asf-site` branch of the `logging-log4j-site` repo (dedicated site repo). This is getting confusing and we need some kind of list to find the repo/branch combination responsible for each part of the site. I think we should bring some order to it. Since not all the parts of the website are connected to a code repo, my personal preference would be to have everything in `logging-site`, with branches named like: asf-site cyclonedx/asf-site log4j/asf-site log4j/2.x/asf-site log4j/jakarta/asf-site Putting an `asf-site` (or another suffix) is a Git requirement since Git does not allow us to have both `asf-site` and `asf-site/log4j` branches. Anyway, any other convention is good for me, as long as the rules to find the correct branch are not too convoluted. Piotr
