Update pages setting header
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
When setting up or modifying GitLab pages there is a disconnect between setting in the UI and setting done as part of the yaml file. This causes a lot of navigation for a user to perform. This is especially problematic during the initial set up. As part of the Experience Baselines and Recommendations initiative, it was determined this can lead to confusion on where to go next. Closing this loop would simplify the setup/modify process.
Intended users
Users with projects that use any static website generator or plain HTML that wish to leverage GitLab pages.
Proposal
Provide a connection between the setting page and the yaml file. If one has not been created it can link to the jumping-off point to create one, similar to the Set CI/CD quick link.
- Update Pages header to
Pages Configuration Settings - Update Pages header copy to:
- With GitLab Pages you can host your static websites on GitLab. Combined with the power of GitLab CI and the help of GitLab Runner you can deploy static pages for your individual projects, your user or your group. Here you can manage your configuration options. Pages deployments are controlled by your CI/CD configuration.
- Include a link (CI/CD configuration) to: https://gitlab.com/help/user/project/pages/getting_started_part_four.md
- Add
CI/CD configurationbutton- If the project has a .gitlab-ci.yml link to: /blob/master/.gitlab-ci.yml
- If the project does not link to: /new/master?commit_message=Add+.gitlab-ci.yml&file_name=.gitlab-ci.yml
- Thee is suggestion to move the existing
New domainbutton in #198567. Depending on the order these are done in or if #198567 ends up not being done,New Domainbutton should remain at the top, see #30574 (comment 302697742).
What does success look like, and how can we measure that?
Pages setup experience is improved.