info:To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
info:To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
---
---
# New Pages website from a forked sample
# Create a Pages website from a forked sample
To get started with GitLab Pages from a sample website, the easiest
GitLab provides [sample projects for the most popular Static Site Generators](https://gitlab.com/pages).
way to do it is by using one of the [bundled templates](pages_bundled_template.md).
You can fork one of the sample projects and run the CI/CD pipeline to generate a Pages website.
If you don't find one that suits your needs, you can opt by
forking (copying) a [sample project from the most popular Static Site Generators](https://gitlab.com/pages).
Fork a sample project when you want to test GitLab Pages or start a new project that's already
configured to generate a Pages site.
<tableclass="borderless-table center fixed-table middle width-80">
<tr>
<iclass="fa fa-youtube-play youtube"aria-hidden="true"></i> Watch a [video tutorial](https://www.youtube.com/watch?v=TWqh9MtT4Bg) of how this works.
**<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.**
- _Change the URL to match your namespace._ If your Pages site is hosted on GitLab.com,
you can rename it to `<namespace>.gitlab.io`, where `<namespace>` is your GitLab namespace
1.[Fork](../../../../gitlab-basics/fork-project.md) a sample project from the [GitLab Pages examples](https://gitlab.com/pages) group.
(the one you chose when you forked the project).
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
- Go to your project's **Settings > General** and expand **Advanced**. Scroll down to
site to the server.
**Change path** and change the path to `<namespace>.gitlab.io`.
1. Once the pipeline has finished successfully, find the link to visit your
website from your project's **Settings > Pages**. It can take approximately
For example, if your project's URL is `gitlab.com/gitlab-tests/jekyll`, your namespace is
30 minutes to be deployed.
`gitlab-tests`.
You can also take some **optional** further steps:
If you set the repository path to `gitlab-tests.gitlab.io`,
the resulting URL for your Pages website is `https://gitlab-tests.gitlab.io`.
- _Remove the fork relationship._ The fork relationship 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**: