1.[Fork a sample project](../../../gitlab-basics/fork-project.md) from the [Pages group](https://gitlab.com/pages)
<tdstyle="width: 10%">
1. Trigger a build (push a change to any file)
<strong>
1. As soon as the build passes, your website will have been deployed with GitLab Pages. Your website URL will be available under your project's **Settings** > **Pages**
1. Optionally, remove the fork relationship by navigating to your project's **Settings** > expanding **Advanced settings** and scrolling down to **Remove fork relationship**:
**<i class="fa fa-youtube-play youtube" aria-hidden="true"></i> Watch a [video tutorial](https://www.youtube.com/watch?v=TWqh9MtT4Bg) with all the steps below.**
1.[Fork](../../../gitlab-basics/fork-project.md) a sample project from the [GitLab Pages examples](https://gitlab.com/pages) group.
1. From the left sidebar, navigate to your project's **CI/CD > Pipelines**
and click **Run pipeline** to trigger GitLab CI/CD to build and deploy your
site to the server.
1. Once the pipeline has finished successfully, find the link to visit your
website from your project's **Settings > Pages**.
You can also take some **optional** further steps:
- _Remove the fork relationship._ The fork relashionship is necessary to contribute back to the project you originally forked from. If you don't have any intentions to do so, you can remove it. To do so, navigate to your project's **Settings**, expand **Advanced settings**, and scroll down to **Remove fork relationship**:
To turn a **project website** forked from the Pages group into a **user/group** website, you'll need to:
- _Make it a user or group website._ To turn a **project website** forked
from the Pages group into a **user/group** website, you'll need to:
- Rename it to `namespace.gitlab.io`: navigate to project's **Settings** > expand **Advanced settings** > and scroll down to **Rename repository**
- Rename it to `namespace.gitlab.io`: navigate to project's **Settings** >
- Adjust your SSG's [base URL](#urls-and-baseurls) from `"project-name"` to `""`. This setting will be at a different place for each SSG, as each of them have their own structure and file tree. Most likely, it will be in the SSG's config file.
expand **Advanced settings** > and scroll down to **Rename repository**.
- Adjust your SSG's [base URL](#urls-and-baseurls) from `"project-name"` to
> **Notes:**
`""`. This setting will be at a different place for each SSG, as each of them
>
have their own structure and file tree. Most likely, it will be in the SSG's
> Why do I need to remove the fork relationship?
config file.
>
> Unless you want to contribute to the original project,
@@ -8,8 +9,8 @@ description: 'Learn how to use GitLab Pages to deploy a static website at no add
...
@@ -8,8 +9,8 @@ description: 'Learn how to use GitLab Pages to deploy a static website at no add
directly from a repository in GitLab.**
directly from a repository in GitLab.**
You can use it either for personal or business websites, such as
You can use it either for personal or business websites, such as
portfolios, documentation, manifestos, and business presentations,
portfolios, documentation, manifestos, and business presentations.
and attribute any license to your content.
You can also attribute any license to your content.
<tableclass="borderless-table center fixed-table">
<tableclass="borderless-table center fixed-table">
<tr>
<tr>
...
@@ -91,52 +92,28 @@ site under the HTTPS protocol.
...
@@ -91,52 +92,28 @@ site under the HTTPS protocol.
## Getting started
## Getting started
To get started with GitLab Pages, you can either [create a project from scratch](getting_started_part_two.md#create-a-project-from-scratch),
To get started with GitLab Pages, you can either:
use a [bundled template](getting_started_part_two.md#use-one-of-the-popular-pages-templates-bundled-with-gitlab), or copy any of our existing example projects:
1. Choose an [example project](https://gitlab.com/pages) to [fork](../../../gitlab-basics/fork-project.md#how-to-fork-a-project):
-[Create a project from scratch](getting_started_part_two.md#create-a-project-from-scratch).
by forking a project, you create a copy of the codebase you're forking from to start from a template instead of starting from scratch.
-[Copy an existing example project](getting_started_part_two.md#fork-a-project-to-get-started-from).
1. From the left sidebar, navigate to your project's **CI/CD > Pipelines** and click
- Use a bundled project template that is ready to go ([introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/47857)
**Run pipeline** so that GitLab CI/CD will build and deploy your site to the server.
in GitLab 11.8), as follows:
1. Once the pipeline has finished successfully, find the link to visit your website from your
project's **Settings > Pages**.
<tableclass="borderless-table center fixed-table middle width-80">
1. From the top navigation, click the **+** button and select **New project**.
Your website is then visible on your domain, and you can modify your files
as you wish. For every modification pushed to your repository, GitLab CI/CD will run
a new pipeline to publish your changes to the server.
You can also take some optional further steps:
- Remove the [fork relationship](getting_started_part_two.md#fork-a-project-to-get-started-from)
1. From the left sidebar, navigate to your project's **CI/CD > Pipelines**
(_You don't need the relationship unless you intent to contribute back to the example project you forked from_).
and click **Run pipeline** to trigger GitLab CI/CD to build and deploy your
- Make it a [user/group website](getting_started_part_one.md#user-and-group-websites)
site to the server.
1. Once the pipeline has finished successfully, find the link to visit your
website from your project's **Settings > Pages**.
**<i class="fa fa-youtube-play youtube" aria-hidden="true"></i> Watch a [video tutorial](https://www.youtube.com/watch?v=TWqh9MtT4Bg) with all the steps above!**
Your website is then visible on your domain, and you can modify yourfiles
as you wish. For every modification pushed to your repository, GitLab CI/CD
will run a new pipeline to publish your changes to the server.
