Description

It appears to be every week or so that someone breaks the top-level module view of our nice rendered doc (see #8973 for the most current example). Main culprit most of the time is that they set @ingroup to a group that does not exist.

How about we provide a checker script that checks modules.html directly after the doc was build by the CI, if the list of modules is in line with a given list provided with that checker? If the author of a PR really intends to add a new top-level module (which should rarely happen anyway) they can just append there new module to that list.