Add the ability to disable or re-enable a GitLab Pages static website
TL;DR
Add the ability to disable and re-enable a static website on a project, served via GitLab Pages.
Overview
Adding the ability to disable and re-enable a GitLab Pages static-website would allow Trust and Safety to appropriately respond to takedown requests (e.g.: DMCA, Spam Website) targeting content served using GitLab Pages.
Context
- As an admin, there is no option to disable or re-enable a static website to its original state.
- Any project owner has the ability to manually reinstate a webpage without restrictions.
- An admin can only block an account to prevent a user from reinstating the webpage.
- A blocked account prevents a user from accessing their account, which could negatively impact a customer's ability to perform other tasks unrelated to the work targeted in the takedown request.
- There is no ability to easily restore a webpage to its original state after it has been removed and has to be manually reinstated by the project owner.
Edited by Westley