Explore improvements to Unique pages site domain feature
Context
This Issue can give us a place to discuss ways to improve unique pages site domain.
We released Unique pages site domain (&9347 - closed) for GitLab Pages. We removed the feature flag for this in %16.3.
Unique domain is a feature to avoid leaking cookies between pages on the same namespace for this reason it is enabled by default.
Feedback for Improvement
There has been feedback around challenges default enablement has created and ideas around how we could proceed differently. Some feedback is the following:
- "It can have a pretty significant UX impact, both for the creator as there is no visibility why the domain becomes a random string, as well as for visitors (one user had the impression it was a phishing/scam at first glance, which I understand). I wonder if we can find smarter ways to do this, e.g. something like not changing anything when it's the first Page for a namespace, and then adding a banner for the creation of the second namespace."
- "Is there a way to globally change the default or change via the public API on a per-project basis?"
- "Similarly to the existing question about changing the global default, we have a GitLab Dedicated customer who is asking (
🎫 internal) if it is possible to disable the option entirely, i.e. an instance-level setting that would prohibit enabling unique domains in any projects."
Edited by Matthew Macfarlane