Not so serious GX error

One not so serious error was pointed out to my by Johanna here:

Besides this I spend on Monday some time on a RfC. Although it took me more hours to understand the proceedure than to produce the document itself. The basic problem is the size of the UM website. Thousands of pages with information that needs to be up to date and correct. While two eyes are certainly not enough to oversee the digital landscape many more would certainly help. But how to facilitate a conversation between people who browse through UM's websites and those people managing it?
In principle the solution is an integrated expertsystem. Integrated means only that it is contained within the GX content management system and not a third party app that is either embedded or runs on a seperate server somewhere in the cloud. Expertsystem might also need some qualifications here but it is fairly accurate to call it that.
What does the system do?
In a first step, it simply shows up as a link at the bottom of every page of the UM website and says something like "Hey, found a bug?"

If a visitor clicks on this link a window opens:

Nothing terribly complex happens then. The visitor is asked to specify the bug, describe it and indicate the size (or priority) of the bug observed. This information is recorded and distributed to the person responsible for the website. 

This system offers also staff members to easier notify the webeditors or coordinators about changes. The workflow here is that people copy and paste half of the webpage they want to make changes in an email. Copy also the URL and an explenation or description of the changes.

Although it is in princible simple some remarks have to be discussed. Such as, user and system management, visibility of the UI on the web and the workflow proceedure. Here is the link to the RfC document. 

Comments or remarks are very appreciated!