Skip to content

Improvements in GitLab Pages setup and usage

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Overview

I've consulted with various GitLab internal employees who have been using GitLab Pages. Based on these discussions, I've created this issue to gather and consolidate general feedback, bugs, and UX improvement suggestions. The goal is to enhance the overall user experience and address existing pain points in GitLab Pages.

Visibility level

  • When a group's visibility is set to private, all child projects inherit this setting, which means GitLab Pages can't be used if private. This limitation should be communicated to users.
    • It's currently possible to change the visibility of pages to 'Everyone' in the settings, but public pages are broken on GitLab Pages. This issue needs to be resolved to ensure a consistent user experience.

GitLab Pages wizard

  • After setting up GitLab Pages, the wizard is displayed even if a .yml file is already present. This can be confusing and time-consuming for users who have already configured their .yml file. The wizard should not appear if a .yml file is detected in the repository.

Default setting for 'Use unique domain'

  • The default setting for 'Use unique domain' needs to be reviewed. Why is this set by default, and what are the benefits or drawbacks? It would be helpful to clarify this choice in the documentation or within the UI.

GitLab Pages accessibility issues

  • Several accessibility issues were noted:
    • The entire section is clickable, which is not ideal for accessibility.
    • There is no visible focus state when navigating with a keyboard.
    • It's not possible to expand or collapse sections using keyboard.

Root directory

  • The root directory is set to /public, and users cannot change this. If this setting is fixed, the UI should not present it as a configurable option, or there should be an explanation for why it cannot be changed.

Ambiguity in the 'Include stopped deployment' option:

  • The term 'Include stopped deployment' is unclear. Is this meant to be a filter? More descriptive text or a tooltip would help clarify this feature's purpose.
Edited by 🤖 GitLab Bot 🤖