Pages - Restrict file types/paths
Problem to solve
Users create Pages to build fully-fledged single page applications for a critical business function. They do not realize that the pages will be unavailable during maintenance windows.
Intended users
User experience goal
GitLab administrators should be able to restrict the content deployed to GitLab pages at a Group and instance level
Proposal
The ability to restrict the following usage of pages:
- Cross-origin calls that allow teams to source data from outside the Gitlab domain, e.g. pulling in data from one of their own business services to show in a grid
- Library use within pages, i.e. block users from hosting JavaScript libraries in their page deploy or cross-linking to an external CDN in a script block
- Restrict users from hosting HTML forms on the site, e.g. setting up support pages that link to other pages
Edited by Jackie Porter