diff options
Diffstat (limited to 'doc/user/project/pages')
8 files changed, 37 insertions, 13 deletions
diff --git a/doc/user/project/pages/custom_domains_ssl_tls_certification/index.md b/doc/user/project/pages/custom_domains_ssl_tls_certification/index.md index dc23540bd1b..2f814bb0e65 100644 --- a/doc/user/project/pages/custom_domains_ssl_tls_certification/index.md +++ b/doc/user/project/pages/custom_domains_ssl_tls_certification/index.md @@ -165,7 +165,8 @@ If you're using Cloudflare, check Once you have added all the DNS records: -1. Go back at your project's **Settings > Pages**. +1. Go back at your project's **Settings > Pages** (Note: this may also be + located at **Deployments > Pages**, [more information](../index.md#menu-position-test)). 1. Locate your domain name and select **Details**. 1. Select the **Retry verification** button to activate your new domain. @@ -287,10 +288,15 @@ meet these requirements. #### Steps - To add the certificate at the time you add a new domain, go to your - project's **Settings > Pages > New Domain**, add the domain name and the certificate. + project's **Settings > Pages > New Domain** (Note: this may also be + located at **Deployments > Pages**, [more information](../index.md#menu-position-test)), add the domain name and the + certificate. - To add the certificate to a domain previously added, go to your project's **Settings > Pages**, locate your domain name, select **Details** and **Edit** to add the certificate. +NOTE: +The Pages menu entry may also be located at **Deployments > Pages**, [more information](../index.md#menu-position-test) + 1. Add the PEM certificate to its corresponding field. 1. If your certificate is missing its intermediate, copy and paste the root certificate (usually available from your CA website) @@ -313,7 +319,8 @@ domain (as long as you've set a valid certificate for it). To enable this setting: -1. Navigate to your project's **Settings > Pages**. +1. Navigate to your project's **Settings > Pages** (Note: this may also be + located at **Deployments > Pages**, [more information](../index.md#menu-position-test)). 1. Tick the checkbox **Force HTTPS (requires valid certificates)**. If you use Cloudflare CDN in front of GitLab Pages, make sure to set the SSL connection setting to diff --git a/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md b/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md index e9e6e5a9a3c..770fb4f450a 100644 --- a/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md +++ b/doc/user/project/pages/custom_domains_ssl_tls_certification/lets_encrypt_integration.md @@ -42,7 +42,8 @@ For **self-managed** GitLab instances, make sure your administrator has Once you've met the requirements, enable Let's Encrypt integration: -1. Navigate to your project's **Settings > Pages**. +1. Navigate to your project's **Settings > Pages** (Note: this may also be + located at **Deployments > Pages**, [more information](../index.md#menu-position-test)). 1. Find your domain and select **Details**. 1. Select **Edit** in the top-right corner. 1. Enable Let's Encrypt integration by switching **Automatic certificate management using Let's Encrypt**: @@ -69,7 +70,8 @@ associated Pages domain. GitLab also renews it automatically. If you get an error **Something went wrong while obtaining the Let's Encrypt certificate**, first, make sure that your pages site is set to "Everyone" in your project's **Settings > General > Visibility**. This allows the Let's Encrypt Servers reach your pages site. Once this is confirmed, you can try obtaining the certificate again by following these steps: -1. Go to your project's **Settings > Pages**. +1. Go to your project's **Settings > Pages** (Note: this may also be + located at **Deployments > Pages**, [more information](../index.md#menu-position-test)). 1. Select **Edit** on your domain. 1. Select **Retry**. 1. If you're still seeing the same error: @@ -83,7 +85,8 @@ If you get an error **Something went wrong while obtaining the Let's Encrypt cer If you've enabled Let's Encrypt integration, but a certificate is absent after an hour and you see the message, "GitLab is obtaining a Let's Encrypt SSL certificate for this domain. This process can take some time. Please try again later.", try to remove and add the domain for GitLab Pages again by following these steps: -1. Go to your project's **Settings > Pages**. +1. Go to your project's **Settings > Pages** (Note: this may also be + located at **Deployments > Pages**, [more information](../index.md#menu-position-test)). 1. Select **Remove** on your domain. 1. [Add the domain again and verify it](index.md#1-add-a-custom-domain). 1. [Enable Let's Encrypt integration for your domain](#enabling-lets-encrypt-integration-for-your-custom-domain). diff --git a/doc/user/project/pages/getting_started/pages_ci_cd_template.md b/doc/user/project/pages/getting_started/pages_ci_cd_template.md index 339ab239588..e0448621c6a 100644 --- a/doc/user/project/pages/getting_started/pages_ci_cd_template.md +++ b/doc/user/project/pages/getting_started/pages_ci_cd_template.md @@ -28,7 +28,8 @@ If everything is configured correctly, the site can take approximately 30 minute To view the pipeline, go to **CI/CD > Pipelines**. When the pipeline is finished, go to **Settings > Pages** to find the link to -your Pages website. +your Pages website. (Note: this may also be +located at **Deployments > Pages**, [more information](../index.md#menu-position-test)) For every change pushed to your repository, GitLab CI/CD runs a new pipeline that immediately publishes your changes to the Pages site. diff --git a/doc/user/project/pages/getting_started/pages_forked_sample_project.md b/doc/user/project/pages/getting_started/pages_forked_sample_project.md index 9841e52a089..e1a245851cb 100644 --- a/doc/user/project/pages/getting_started/pages_forked_sample_project.md +++ b/doc/user/project/pages/getting_started/pages_forked_sample_project.md @@ -24,7 +24,9 @@ To fork a sample project and create a Pages website: GitLab CI/CD builds and deploys your site. The site can take approximately 30 minutes to deploy. -When the pipeline is finished, go to **Settings > Pages** to find the link to your website from your project. +When the pipeline is finished, go to **Settings > Pages** to find the link +to your website from your project. (Note: this may also be +located at **Deployments > Pages**, [more information](../index.md#menu-position-test)) For every change pushed to your repository, GitLab CI/CD runs a new pipeline that immediately publishes your changes to the Pages site. diff --git a/doc/user/project/pages/getting_started/pages_from_scratch.md b/doc/user/project/pages/getting_started/pages_from_scratch.md index ebadf39a984..82e544b0701 100644 --- a/doc/user/project/pages/getting_started/pages_from_scratch.md +++ b/doc/user/project/pages/getting_started/pages_from_scratch.md @@ -27,7 +27,7 @@ To create a GitLab Pages website: ## Prerequisites -You must have a [blank project](../../working_with_projects.md#create-a-blank-project) in GitLab. +You must have a [blank project](../../index.md#create-a-blank-project) in GitLab. ## Create the project files @@ -176,7 +176,8 @@ deploy your website: 1. Save and commit the `.gitlab-ci.yml` file. 1. Go to **CI/CD > Pipelines** to watch the pipeline. 1. When the pipeline succeeds, go to **Settings > Pages** - to view the URL where your site is now available. + to view the URL where your site is now available. (Note: this may also be + located at **Deployments > Pages**, [more information](../index.md#menu-position-test)) When this `pages` job completes successfully, a special `pages:deploy` job appears in the pipeline view. It prepares the content of the website for the diff --git a/doc/user/project/pages/getting_started/pages_new_project_template.md b/doc/user/project/pages/getting_started/pages_new_project_template.md index a0f9753a40c..a9988b1fb99 100644 --- a/doc/user/project/pages/getting_started/pages_new_project_template.md +++ b/doc/user/project/pages/getting_started/pages_new_project_template.md @@ -24,7 +24,8 @@ configured to generate a Pages site. site. When the pipeline is finished, go to **Settings > Pages** to find the link to -your Pages website. +your Pages website. (Note: this may also be +located at **Deployments > Pages**, [more information](../index.md#menu-position-test)) For every change pushed to your repository, GitLab CI/CD runs a new pipeline that immediately publishes your changes to the Pages site. diff --git a/doc/user/project/pages/getting_started/pages_ui.md b/doc/user/project/pages/getting_started/pages_ui.md index a6069b473e6..984c8e5c619 100644 --- a/doc/user/project/pages/getting_started/pages_ui.md +++ b/doc/user/project/pages/getting_started/pages_ui.md @@ -34,8 +34,10 @@ a pipeline deploys your Pages website. To complete the setup and generate a GitLab Pages deployment: 1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > Pages**. A **Get Started with Pages** form appears. - If this form is not available, see [Troubleshooting](#if-the-get-started-with-pages-form-is-not-available). +1. On the left sidebar, select **Settings > Pages** (Note: this may also be + located at **Deployments > Pages**, [more information](../index.md#menu-position-test)). + A **Get Started with Pages** form appears. If this form is not available, + see [Troubleshooting](#if-the-get-started-with-pages-form-is-not-available). 1. For **Step 1**, enter an image name and verify that your files are in a `public` folder. 1. Select **Next**. 1. For **Step 2**, enter your installation steps. If your framework's build process does not diff --git a/doc/user/project/pages/index.md b/doc/user/project/pages/index.md index 9305b92bf7d..89d8fd093b2 100644 --- a/doc/user/project/pages/index.md +++ b/doc/user/project/pages/index.md @@ -34,6 +34,13 @@ Pages does not support dynamic server-side processing, for instance, as `.php` a Learn more about [static websites compared to dynamic websites](https://about.gitlab.com/blog/2016/06/03/ssg-overview-gitlab-pages-part-1-dynamic-x-static/). +## Menu Position Test + +NOTE: +We are currently conducting an A/B test where some users may see the Pages +Menu entry under "Deployments" instead of "Settings". We think that this may +be a more accurate position. Feel free to add any feedback to [the experiment issue](https://gitlab.com/gitlab-org/gitlab/-/issues/373547). + ## Getting started To create a GitLab Pages website: |