Allow administrators control over Pages usage
Problem to solve
GitLab pages allows arbitrary users to post arbitrary content on web property controlled by the site administrator. This can make some administrators nervous.
Open source projects.
GitLab's Pages feature can be very useful as it can simplify the deployment process for web assets. This can be very appealing to open source projects (e.g. the Haskell installation, #55039), who generally want to focus on things other than the deployment of their website.
However, GitLab instances which host FOSS projects are typically open to public sign-ups. Enabling Pages in this case would mean that arbitrary users (e.g. spammers) could post content on a domain controlled by the project.
Allow the site administrator to grant the ability to enable Pages to only a subset of site users. This might be accomplished by introducing a magic "Pages users" group. Members of this group would be able to enable Pages on projects that they control.
What does success look like, and how can we measure that?
Users can enable Pages on a public GitLab instance without fear that their web property will be abused.