diff --git a/src/content/docs/fundamentals/setup/account/verify-email-address.mdx b/src/content/docs/fundamentals/setup/account/verify-email-address.mdx index 55c7c4cec3a049..d33087fc4da18c 100644 --- a/src/content/docs/fundamentals/setup/account/verify-email-address.mdx +++ b/src/content/docs/fundamentals/setup/account/verify-email-address.mdx @@ -6,48 +6,6 @@ sidebar: --- -For security reasons, Cloudflare attempts to verify the email address associated with your account. You cannot perform certain tasks within the Cloudflare dashboard - for example, [adding a new member](/fundamentals/setup/manage-members/manage/#add-account-members) or [updating your communication preferences](/fundamentals/setup/account/customize-account/communication-preference/) - without verifying your email. +import { Render } from "~/components" -## When creating your account - -When you first [create an account](/fundamentals/setup/account/create-account/), Cloudflare automatically sends a message to the email address you provided for your account. - -To verify your email: - -1. Log into your email provider and find your recent message from Cloudflare. If you cannot find the message, check your Spam folder. -2. Click the link in the email. -3. Log into Cloudflare to verify the email address associated with your account. - -:::note - - -If someone else used your email to sign up for a Cloudflare account, you can remove this account by going to our [unintended registration](https://dash.cloudflare.com/unintended-registration) page and entering the information at the end of your confirmation email. - - -::: - -*** - -## Resend verification emails - -If you cannot find your verification email or your email has expired, request another verification email: - -1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com). -2. Go to **My Profile**. -3. For **Email Address**, select **Send verification email** (if this option is not available, your email has already been verified). - -*** - -## Verification issues - -If you experience issues with your verification link, you might have already verified your email address. - -To check: - -1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com). -2. Go to **My Profile**. -3. For **Email Address**, your email address will have `(verified)` added after it. - -If your email is still not verified, try clicking the verification link in a different browser or an incognito window. - -If this still does not work, try [resending](#resend-verification-emails) the verification email to get a new verification link. + \ No newline at end of file diff --git a/src/content/docs/learning-paths/personal-website/concepts/create-account.mdx b/src/content/docs/learning-paths/personal-website/concepts/create-account.mdx new file mode 100644 index 00000000000000..3057caf307a6f2 --- /dev/null +++ b/src/content/docs/learning-paths/personal-website/concepts/create-account.mdx @@ -0,0 +1,15 @@ +--- +title: Create an account +pcx_content_type: overview +sidebar: + order: 1 + +--- + +import { Render } from "~/components" + + + +## Best practices + + diff --git a/src/content/docs/learning-paths/personal-website/concepts/index.mdx b/src/content/docs/learning-paths/personal-website/concepts/index.mdx new file mode 100644 index 00000000000000..f166423c7ba26f --- /dev/null +++ b/src/content/docs/learning-paths/personal-website/concepts/index.mdx @@ -0,0 +1,17 @@ +--- +title: Cloudflare account setup +pcx_content_type: overview +sidebar: + label: Cloudflare account setup + order: 1 +--- + +Before you can create your website, you will need to create and set up your Cloudflare account. + +## Objectives + +By the end of this module, you will: + +- Sign up for an account with Cloudflare +- Verify your email address +- Log in to your Cloudflare account diff --git a/src/content/docs/learning-paths/personal-website/concepts/verify-email-address.mdx b/src/content/docs/learning-paths/personal-website/concepts/verify-email-address.mdx new file mode 100644 index 00000000000000..c0c00b3aa25419 --- /dev/null +++ b/src/content/docs/learning-paths/personal-website/concepts/verify-email-address.mdx @@ -0,0 +1,12 @@ +--- +title: Verify email address +pcx_content_type: overview +sidebar: + order: 2 + +--- + +import { Render } from "~/components" + + + diff --git a/src/content/docs/learning-paths/personal-website/domain-setup/add-domain.mdx b/src/content/docs/learning-paths/personal-website/domain-setup/add-domain.mdx new file mode 100644 index 00000000000000..198da6141eebc5 --- /dev/null +++ b/src/content/docs/learning-paths/personal-website/domain-setup/add-domain.mdx @@ -0,0 +1,11 @@ +--- +title: Add a domain +pcx_content_type: overview +sidebar: + order: 1 + +--- + +import { Render } from "~/components" + + diff --git a/src/content/docs/learning-paths/personal-website/domain-setup/index.mdx b/src/content/docs/learning-paths/personal-website/domain-setup/index.mdx new file mode 100644 index 00000000000000..0614f628164bee --- /dev/null +++ b/src/content/docs/learning-paths/personal-website/domain-setup/index.mdx @@ -0,0 +1,16 @@ +--- +title: Add a domain +pcx_content_type: overview +sidebar: + order: 2 +--- + +Add your domain to Cloudflare to start receiving the benefits of the platform. + +## Objectives + +By the end of this module, you will: + +- Add your domain as a new site to Cloudflare +- Update your nameservers +- Minimize downtime for your site diff --git a/src/content/docs/learning-paths/personal-website/domain-setup/minimize-downtime.mdx b/src/content/docs/learning-paths/personal-website/domain-setup/minimize-downtime.mdx new file mode 100644 index 00000000000000..31c783ee04a601 --- /dev/null +++ b/src/content/docs/learning-paths/personal-website/domain-setup/minimize-downtime.mdx @@ -0,0 +1,11 @@ +--- +title: Minimize downtime +pcx_content_type: overview +sidebar: + order: 3 + +--- + +import { Render } from "~/components" + + diff --git a/src/content/docs/learning-paths/personal-website/domain-setup/update-nameservers.mdx b/src/content/docs/learning-paths/personal-website/domain-setup/update-nameservers.mdx new file mode 100644 index 00000000000000..44b88406bb3405 --- /dev/null +++ b/src/content/docs/learning-paths/personal-website/domain-setup/update-nameservers.mdx @@ -0,0 +1,11 @@ +--- +title: Update your nameservers +pcx_content_type: overview +sidebar: + order: 2 + +--- + +import { Render } from "~/components" + + diff --git a/src/content/docs/learning-paths/personal-website/index.mdx b/src/content/docs/learning-paths/personal-website/index.mdx new file mode 100644 index 00000000000000..69958a8e17c1cc --- /dev/null +++ b/src/content/docs/learning-paths/personal-website/index.mdx @@ -0,0 +1,15 @@ +--- +title: Build a personal website +type: developers-site +new_learning_path: true +pcx_content_type: learning-path +head: + - tag: title + content: Build a personal website +description: Utilize the Developer Platform to build a personal website for your portfolio or blog. + +--- + +import { LearningPath } from "~/components" + + diff --git a/src/content/docs/learning-paths/personal-website/pages-setup/connect-git-pages.mdx b/src/content/docs/learning-paths/personal-website/pages-setup/connect-git-pages.mdx new file mode 100644 index 00000000000000..01a294e81d57b4 --- /dev/null +++ b/src/content/docs/learning-paths/personal-website/pages-setup/connect-git-pages.mdx @@ -0,0 +1,12 @@ +--- +title: Connect your Git provider to Pages +pcx_content_type: overview +sidebar: + order: 1 +--- + +Get started with Cloudflare Pages and deploy your first website to the Pages platform through Git integration. + +import { Render } from "~/components" + + \ No newline at end of file diff --git a/src/content/docs/learning-paths/personal-website/pages-setup/git-configure-deployment.mdx b/src/content/docs/learning-paths/personal-website/pages-setup/git-configure-deployment.mdx new file mode 100644 index 00000000000000..299425105c66fd --- /dev/null +++ b/src/content/docs/learning-paths/personal-website/pages-setup/git-configure-deployment.mdx @@ -0,0 +1,10 @@ +--- +title: Configure your deployment +pcx_content_type: overview +sidebar: + order: 2 +--- + +import { Render } from "~/components" + + \ No newline at end of file diff --git a/src/content/docs/learning-paths/personal-website/pages-setup/git-manage-site.mdx b/src/content/docs/learning-paths/personal-website/pages-setup/git-manage-site.mdx new file mode 100644 index 00000000000000..d0acb3ffbfc746 --- /dev/null +++ b/src/content/docs/learning-paths/personal-website/pages-setup/git-manage-site.mdx @@ -0,0 +1,10 @@ +--- +title: Manage your site +pcx_content_type: overview +sidebar: + order: 3 +--- + +import { Render } from "~/components" + + \ No newline at end of file diff --git a/src/content/docs/learning-paths/personal-website/pages-setup/index.mdx b/src/content/docs/learning-paths/personal-website/pages-setup/index.mdx new file mode 100644 index 00000000000000..1a43a4e173f78d --- /dev/null +++ b/src/content/docs/learning-paths/personal-website/pages-setup/index.mdx @@ -0,0 +1,14 @@ +--- +title: Connect Git and Pages +pcx_content_type: overview +sidebar: + order: 3 +--- + +## Objectives + +By the end of this module, you will: + +- Connect your Git provider to Pages +- Configure the deployment for your site +- Learn how to manage your site diff --git a/src/content/docs/learning-paths/personal-website/select-themes/index.mdx b/src/content/docs/learning-paths/personal-website/select-themes/index.mdx new file mode 100644 index 00000000000000..8625ed237fb2bc --- /dev/null +++ b/src/content/docs/learning-paths/personal-website/select-themes/index.mdx @@ -0,0 +1,10 @@ +--- +title: Website themes +pcx_content_type: overview +sidebar: + order: 4 +--- + +If you are new to modifying the look and feel of a website, you can find a variety of free website themes online. + +For example, [Astro](https://astro.build/), used by Cloudflare's Developer Documentation, has a list of free and paid [themes](https://astro.build/themes/) you can use to customize your website. \ No newline at end of file diff --git a/src/content/docs/pages/get-started/git-integration.mdx b/src/content/docs/pages/get-started/git-integration.mdx index cd1fe938de0a75..85e7ba1ee544d2 100644 --- a/src/content/docs/pages/get-started/git-integration.mdx +++ b/src/content/docs/pages/get-started/git-integration.mdx @@ -8,144 +8,18 @@ description: Connect your Git provider to Pages. --- -import { Details } from "~/components" +import { Details, Render } from "~/components" In this guide, you will get started with Cloudflare Pages, and deploy your first website to the Pages platform through Git integration. ## Connect your Git provider to Pages -Pages offers support for [GitHub](https://github.com/) and [GitLab](https://gitlab.com/). To create your first Pages project: - -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. -2. In Account Home, select **Workers & Pages**. -3. Select **Create application** > **Pages** > **Connect to Git**. - -You will be prompted to sign in with your preferred Git provider. This allows Cloudflare Pages to deploy your projects, and update your PRs with [preview deployments](/pages/configuration/preview-deployments/). - -:::note - - -Signing in with GitLab will grant Pages access to all repositories on your account. Additionally, if you are a part of a multi-user Cloudflare account, and you sign in with GitLab, other members will also have the ability to deploy your repositories to Pages. - -If you are using GitLab, you must have the **Maintainer** role or higher on the repository to successfully deploy with Cloudflare Pages. - - -::: - -### Select your GitHub repository - -You can select a GitHub project from your personal account or an organization you have given Pages access to. This allows you to choose a GitHub repository to deploy using Pages. Both private and public repositories are supported. - -### Select your GitLab repository - -If using GitLab, you can select a project from your personal account or from a GitLab group you belong to. This allows you to choose a GitLab repository to deploy using Pages. Both private and public repositories are supported. + ## Configure your deployment -Once you have selected a Git repository, select **Install & Authorize** and **Begin setup**. You can then customize your deployment in **Set up builds and deployments**. - -Your **project name** will be used to generate your project's hostname. By default, this matches your Git project name. - -**Production branch** indicates the branch that Cloudflare Pages should use to deploy the production version of your site. For most projects, this is the `main` or `master` branch. All other branches that are not your production branch will be used for [preview deployments](/pages/configuration/preview-deployments/). - -:::note - - -You must have pushed at least one branch to your GitHub or GitLab project in order to select a **Production branch** from the dropdown menu. - - -::: - -![Set up builds and deployments page with Project name and Production branch filled in](~/assets/images/pages/get-started/configuration.png) - -### Configure your build settings - -Depending on the framework, tool, or project you are deploying to Cloudflare Pages, you will need to specify the site's **build command** and **build output directory** to tell Cloudflare Pages how to deploy your site. The content of this directory is uploaded to Cloudflare Pages as your website's content. - -:::caution[No framework required] - - -You do not need a framework to deploy with Cloudflare Pages. You can continue with the Get started guide without choosing a framework, and refer to [Deploy your site](/pages/framework-guides/deploy-anything/) for more information on deploying your site without a framework. - - -::: - -The dashboard provides a number of framework-specific presets. These presets provide the default build command and build output directory values for the selected framework. If you are unsure what the correct values are for this section, refer to [Build configuration](/pages/configuration/build-configuration/). If you do not need a build step, leave the **Build command** field blank. - -![Build setting fields that need to be filled in](~/assets/images/pages/get-started/build-settings.png) - -Cloudflare Pages begins by working from your repository's root directory. The entire build pipeline, including the installation steps, will begin from this location. If you would like to change this, specify a new root directory location through the **Root directory (advanced)** > **Path** field. - -![Root directory field to be filled in](~/assets/images/pages/get-started/root-directory.png) - - -
- -The build command is provided by your framework. For example, the Gatsby framework uses `gatsby build` as its build command. When you are working without a framework, leave the **Build command** field blank. - -The build output directory is generated from the build command. Each [framework](/pages/configuration/build-configuration/#framework-presets) has its own naming convention, for example, the build output directory is named `/public` for many frameworks. - -The root directory is where your site's content lives. If not specified, Cloudflare assumes that your linked Git repository is the root directory. The root directory needs to be specified in cases like monorepos, where there may be multiple projects in one repository. - -Refer to [Build configuration](/pages/configuration/build-configuration/) for more information. - - -
- -### Environment variables - -Environment variables are a common way of providing configuration to your build workflow. While setting up your project, you can specify a number of key-value pairs as environment variables. These can be further customized once your project has finished building for the first time. - -Refer to the [Hexo framework guide](/pages/framework-guides/deploy-a-hexo-site/#using-a-specific-nodejs-version) for more information on how to set up a Node.js version environment variable. - -After you have chosen your *Framework preset* or left this field blank if you are working without a framework, configured **Root directory (advanced)**, and customized your **Environment variables (optional)**, you are ready to deploy. - -## Your first deploy - -After you have finished setting your build configuration, select **Save and Deploy**. Your project build logs will output as Cloudflare Pages installs your project dependencies, builds the project, and deploys it to Cloudflare's global network. - -![Deployment details in the Cloudflare dashboard](~/assets/images/pages/get-started/deploy-log.png) - -When your project has finished deploying, you will receive a unique URL to view your deployed site. - -:::caution[DNS errors] - - -If you encounter a DNS error after visiting your site after your first deploy, this might be because the DNS has not had time to propagate. To solve the error, wait for the DNS to propagate, or try another device or network to resolve the error. - - -::: - -## Manage your site - -After your first deploy, select **Continue to project** to see your project's configuration in the Cloudflare Pages dashboard. On this page, you can see your project's current deployment status, the production URL and associated commit, and all past deployments. - -![Site dashboard displaying your environments and deployments](~/assets/images/pages/get-started/site-dashboard.png) - -### Delete a project - -To delete your Pages project: - -1. Go back to the **Account Home** or use the drop-down menu at the top of the dashboard. -2. Select **Workers & Pages**. -3. Select your Pages project > **Settings** > **Delete project**. - -:::caution - - -For projects with a custom domain, you must first delete the CNAME record associated with your Pages project. Failure to do so may leave the DNS records active, causing your domain to point to a Pages project that no longer exists. Refer to [Deleting a custom domain](/pages/configuration/custom-domains/#delete-a-custom-domain) for instructions. - -For projects without a custom domain (any project on a `*.pages.dev` subdomain), your project can be deleted in the project's settings. - - -::: - -## Advanced project settings - -In the **Settings** section, you can configure advanced settings, such as changing your project name, updating your Git configuration, or updating your build command, build directory or environment variables. + -## Related resources +## Manage site -* Set up a [custom domain for your Pages project](/pages/configuration/custom-domains/). -* Enable [Cloudflare Web Analytics](/pages/how-to/web-analytics/). -* Set up Access policies to [manage who can view your deployment previews](/pages/configuration/preview-deployments/#customize-preview-deployments-access). + diff --git a/src/content/learning-paths/personal-website.json b/src/content/learning-paths/personal-website.json new file mode 100644 index 00000000000000..bb0f4b632b29d5 --- /dev/null +++ b/src/content/learning-paths/personal-website.json @@ -0,0 +1,8 @@ +{ + "title": "Build a personal website", + "path": "/learning-paths/personal-website/", + "priority": 4, + "description": "Utilize the Developer Platform to build a personal website for your portfolio or blog.", + "products": ["Pages"], + "product_group": "Developer platform" +} diff --git a/src/content/partials/fundamentals/add-site.mdx b/src/content/partials/fundamentals/add-site.mdx index ef2d58ffb21d20..465dfc471018b7 100644 --- a/src/content/partials/fundamentals/add-site.mdx +++ b/src/content/partials/fundamentals/add-site.mdx @@ -1,19 +1,16 @@ --- {} - --- -import { GlossaryTooltip, Render } from "~/components" +import { GlossaryTooltip, Render } from "~/components"; 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login). 2. Select **Add a domain**. -3. Enter your website’s apex domain ('example.com'), choose how you would like to add your [DNS records](/dns/manage-dns-records/), and select **Continue**. - +3. Enter your website's apex domain (for example, `example.com`), choose how you would like to add your [DNS records](/dns/manage-dns-records/), and select **Continue**. :::note - If Cloudflare is unable to identify your domain as a registered domain, make sure you are using an existing [top-level domain](https://www.cloudflare.com/learning/dns/top-level-domain/) (`.com`, `.net`, `.biz`, or others). - Cloudflare requires your `apex domain` to be one level below a valid TLD defined in the [Public Suffix List (PSL)](https://github.com/publicsuffix/list/blob/master/public_suffix_list.dat). Enterprise customers can onboard lower-level subdomains using [Subdomain setup](/dns/zone-setups/subdomain-setup/). + Cloudflare requires your apex domain to be one level below a valid TLD defined in the [Public Suffix List (PSL)](https://github.com/publicsuffix/list/blob/master/public_suffix_list.dat). Enterprise customers can onboard lower-level subdomains using [Subdomain setup](/dns/zone-setups/subdomain-setup/). ::: 4. Select a [plan](https://www.cloudflare.com/plans/#compare-features). @@ -26,7 +23,5 @@ import { GlossaryTooltip, Render } from "~/components" 2. If you find any missing records, [manually add](/dns/manage-dns-records/how-to/create-dns-records/) those records. - 3. Depending on your site setup, you may want to adjust the [proxy status](/dns/manage-dns-records/reference/proxied-dns-records/) for certain `A`, `AAAA`, or `CNAME` records. - 4. Select **Continue**. diff --git a/src/content/partials/fundamentals/create-account.mdx b/src/content/partials/fundamentals/create-account.mdx index 4cc4a7232d6b8e..9a84281ce71e58 100644 --- a/src/content/partials/fundamentals/create-account.mdx +++ b/src/content/partials/fundamentals/create-account.mdx @@ -7,6 +7,6 @@ To create a Cloudflare account: 1. Go to the [Sign up page](https://dash.cloudflare.com/sign-up). 2. Enter your **Email** and **Password**. -3. Click **Create Account**. +3. Select **Create Account**. Once you create your account, Cloudflare will automatically send an email to your address to [verify that email address](/fundamentals/setup/account/verify-email-address/). diff --git a/src/content/partials/fundamentals/minimize-downtime.mdx b/src/content/partials/fundamentals/minimize-downtime.mdx index 7e70c9b8cc2fbc..f256ce9b03f10e 100644 --- a/src/content/partials/fundamentals/minimize-downtime.mdx +++ b/src/content/partials/fundamentals/minimize-downtime.mdx @@ -1,18 +1,16 @@ --- {} - --- -When making any change to the routing of an Internet application, there is always a possibility of downtime due to certificate issuance, misconfigured settings, or limitations at your origin server. To avoid downtime when going live, it's important to review the most common configurations. +When making any change to the routing of an Internet application, there is always a possibility of downtime due to certificate issuance, misconfigured settings, or limitations at your origin server. To avoid downtime when going live, it is important to review the most common configurations. ## Update and review DNS records - Before activating your domain on Cloudflare (exact steps depend on your [DNS setup](/dns/zone-setups/)), review the DNS records in your Cloudflare account. ### Start with unproxied records -With a new domain, make sure all your DNS records have a [proxy status](/dns/manage-dns-records/reference/proxied-dns-records/) of **DNS-only**. +With a new domain, make sure all of your DNS records have a [proxy status](/dns/manage-dns-records/reference/proxied-dns-records/) of **DNS-only**. This setting prevents Cloudflare from proxying your traffic before you have an active edge certificate or before you have allowed Cloudflare IP addresses. @@ -20,42 +18,31 @@ This setting prevents Cloudflare from proxying your traffic before you have an a Take extra time to confirm the accuracy of your DNS records before activating your domain, paying special attention to: -* [Zone apex records (`example.com`)](/dns/manage-dns-records/how-to/create-zone-apex/) -* [Subdomain records (`www.example.com` or `blog.example.com`)](/dns/manage-dns-records/how-to/create-subdomain/) -* [Email records](/dns/manage-dns-records/how-to/email-records/) +- [Zone apex records (`example.com`)](/dns/manage-dns-records/how-to/create-zone-apex/) +- [Subdomain records (`www.example.com` or `blog.example.com`)](/dns/manage-dns-records/how-to/create-subdomain/) +- [Email records](/dns/manage-dns-records/how-to/email-records/) If you add DNS records to your authoritative DNS provider between onboarding your domain and activating your domain, you may need to also add these records within Cloudflare. - - ## Activate your domain Finish the [DNS setup](/dns/zone-setups/) for your domain, moving the [domain status](/dns/zone-setups/reference/domain-status/) to **Active**: -* [Full setups](/dns/zone-setups/full-setup/setup/): Update the authoritative nameservers at your registrar and wait for that change to be authenticated. -* [Partial setups](/dns/zone-setups/partial-setup/setup/): Add the verification TXT record to your authoritative DNS and wait for that change to be authenticated. - +- [Full setups](/dns/zone-setups/full-setup/setup/): Update the authoritative nameservers at your registrar and wait for that change to be authenticated. +- [Partial setups](/dns/zone-setups/partial-setup/setup/): Add the verification TXT record to your authoritative DNS and wait for that change to be authenticated. ## Verify SSL/TLS edge certificates - Before proxying your traffic through Cloudflare, [verify](/ssl/reference/certificate-statuses/#monitor-certificate-statuses) that Cloudflare has an active **Edge Certificate** for your domain. For more details about timing and certificate recommendations, refer to [Certificate issuance](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/#full-dns-setup). - ## Optional - Test configuration - You may want to test your configuration using your local machine or proxying traffic from a development domain or subdomain. If you experience issues, you should make sure that you have [allowed Cloudflare IP addresses](/fundamentals/concepts/cloudflare-ip-addresses/) at your origin server. - ## Update proxy status - Once you have verified that your SSL/TLS edge certificate is active and you have allowed Cloudflare IP addresses, change the [proxy status](/dns/manage-dns-records/reference/proxied-dns-records/) of appropriate DNS records to **Proxied**. - - - diff --git a/src/content/partials/fundamentals/verify-email-address.mdx b/src/content/partials/fundamentals/verify-email-address.mdx new file mode 100644 index 00000000000000..2928c335311bb6 --- /dev/null +++ b/src/content/partials/fundamentals/verify-email-address.mdx @@ -0,0 +1,49 @@ +--- +{} +--- + +For security reasons, Cloudflare attempts to verify the email address associated with your account. You cannot perform certain tasks within the Cloudflare dashboard -- for example, [adding a new member](/fundamentals/setup/manage-members/manage/#add-account-members) or [updating your communication preferences](/fundamentals/setup/account/customize-account/communication-preference/) -- without verifying your email. + +## When creating your account + +When you first [create an account](/fundamentals/setup/account/create-account/), Cloudflare automatically sends a message to the email address you provided for your account. + +To verify your email: + +1. Log in to your email provider and find your recent message from Cloudflare. If you cannot find the message, check your Spam folder. +2. Go to the link in the email. +3. Log in to Cloudflare to verify the email address associated with your account. + +:::note + + +If someone else used your email to sign up for a Cloudflare account, you can remove this account by going to our [unintended registration](https://dash.cloudflare.com/unintended-registration) page and entering the information at the end of your confirmation email. + + +::: + +*** + +## Resend verification emails + +If you cannot find your verification email or your email has expired, request another verification email: + +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com). +2. Go to **My Profile**. +3. For **Email Address**, select **Send verification email** (if this option is not available, your email has already been verified). + +*** + +## Verification issues + +If you experience issues with your verification link, you might have already verified your email address. + +To check your verification: + +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com). +2. Go to **My Profile**. +3. For **Email Address**, your email address will have `(verified)` added after it. + +If your email is still not verified, try clicking the verification link in a different browser or a private window. + +If this still does not work, try [resending](#resend-verification-emails) the verification email to get a new verification link. diff --git a/src/content/partials/pages/get-started-git-configure-deployment.mdx b/src/content/partials/pages/get-started-git-configure-deployment.mdx new file mode 100644 index 00000000000000..5e5c3ba70808ec --- /dev/null +++ b/src/content/partials/pages/get-started-git-configure-deployment.mdx @@ -0,0 +1,79 @@ +--- +{} +--- + +import { Details } from "~/components" + +Once you have selected a Git repository, select **Install & Authorize** and **Begin setup**. You can then customize your deployment in **Set up builds and deployments**. + +Your **project name** will be used to generate your project's hostname. By default, this matches your Git project name. + +**Production branch** indicates the branch that Cloudflare Pages should use to deploy the production version of your site. For most projects, this is the `main` or `master` branch. All other branches that are not your production branch will be used for [preview deployments](/pages/configuration/preview-deployments/). + +:::note + + +You must have pushed at least one branch to your GitHub or GitLab project in order to select a **Production branch** from the dropdown menu. + + +::: + +![Set up builds and deployments page with Project name and Production branch filled in](~/assets/images/pages/get-started/configuration.png) + +### Configure your build settings + +Depending on the framework, tool, or project you are deploying to Cloudflare Pages, you will need to specify the site's **build command** and **build output directory** to tell Cloudflare Pages how to deploy your site. The content of this directory is uploaded to Cloudflare Pages as your website's content. + +:::caution[No framework required] + + +You do not need a framework to deploy with Cloudflare Pages. You can continue with the Get started guide without choosing a framework, and refer to [Deploy your site](/pages/framework-guides/deploy-anything/) for more information on deploying your site without a framework. + + +::: + +The dashboard provides a number of framework-specific presets. These presets provide the default build command and build output directory values for the selected framework. If you are unsure what the correct values are for this section, refer to [Build configuration](/pages/configuration/build-configuration/). If you do not need a build step, leave the **Build command** field blank. + +![Build setting fields that need to be filled in](~/assets/images/pages/get-started/build-settings.png) + +Cloudflare Pages begins by working from your repository's root directory. The entire build pipeline, including the installation steps, will begin from this location. If you would like to change this, specify a new root directory location through the **Root directory (advanced)** > **Path** field. + +![Root directory field to be filled in](~/assets/images/pages/get-started/root-directory.png) + + +
+ +The build command is provided by your framework. For example, the Gatsby framework uses `gatsby build` as its build command. When you are working without a framework, leave the **Build command** field blank. + +The build output directory is generated from the build command. Each [framework](/pages/configuration/build-configuration/#framework-presets) has its own naming convention, for example, the build output directory is named `/public` for many frameworks. + +The root directory is where your site's content lives. If not specified, Cloudflare assumes that your linked Git repository is the root directory. The root directory needs to be specified in cases like monorepos, where there may be multiple projects in one repository. + +Refer to [Build configuration](/pages/configuration/build-configuration/) for more information. + + +
+ +### Environment variables + +Environment variables are a common way of providing configuration to your build workflow. While setting up your project, you can specify a number of key-value pairs as environment variables. These can be further customized once your project has finished building for the first time. + +Refer to the [Hexo framework guide](/pages/framework-guides/deploy-a-hexo-site/#using-a-specific-nodejs-version) for more information on how to set up a Node.js version environment variable. + +After you have chosen your *Framework preset* or left this field blank if you are working without a framework, configured **Root directory (advanced)**, and customized your **Environment variables (optional)**, you are ready to deploy. + +## Your first deploy + +After you have finished setting your build configuration, select **Save and Deploy**. Your project build logs will output as Cloudflare Pages installs your project dependencies, builds the project, and deploys it to Cloudflare's global network. + +![Deployment details in the Cloudflare dashboard](~/assets/images/pages/get-started/deploy-log.png) + +When your project has finished deploying, you will receive a unique URL to view your deployed site. + +:::caution[DNS errors] + + +If you encounter a DNS error after visiting your site after your first deploy, this might be because the DNS has not had time to propagate. To solve the error, wait for the DNS to propagate, or try another device or network to resolve the error. + + +::: \ No newline at end of file diff --git a/src/content/partials/pages/get-started-git-connect-pages.mdx b/src/content/partials/pages/get-started-git-connect-pages.mdx new file mode 100644 index 00000000000000..d87be1f7bf5765 --- /dev/null +++ b/src/content/partials/pages/get-started-git-connect-pages.mdx @@ -0,0 +1,29 @@ +--- +{} +--- + +Pages offers support for [GitHub](https://github.com/) and [GitLab](https://gitlab.com/). To create your first Pages project: + +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. +2. In Account Home, select **Workers & Pages**. +3. Select **Create application** > **Pages** > **Connect to Git**. + +You will be prompted to sign in with your preferred Git provider. This allows Cloudflare Pages to deploy your projects, and update your PRs with [preview deployments](/pages/configuration/preview-deployments/). + +:::note + + +Signing in with GitLab will grant Pages access to all repositories on your account. Additionally, if you are a part of a multi-user Cloudflare account, and you sign in with GitLab, other members will also have the ability to deploy your repositories to Pages. + +If you are using GitLab, you must have the **Maintainer** role or higher on the repository to successfully deploy with Cloudflare Pages. + + +::: + +### Select your GitHub repository + +You can select a GitHub project from your personal account or an organization you have given Pages access to. This allows you to choose a GitHub repository to deploy using Pages. Both private and public repositories are supported. + +### Select your GitLab repository + +If using GitLab, you can select a project from your personal account or from a GitLab group you belong to. This allows you to choose a GitLab repository to deploy using Pages. Both private and public repositories are supported. \ No newline at end of file diff --git a/src/content/partials/pages/get-started-git-manage-site.mdx b/src/content/partials/pages/get-started-git-manage-site.mdx new file mode 100644 index 00000000000000..5cb7cf0b02d066 --- /dev/null +++ b/src/content/partials/pages/get-started-git-manage-site.mdx @@ -0,0 +1,35 @@ +--- +{} +--- + +After your first deploy, select **Continue to project** to see your project's configuration in the Cloudflare Pages dashboard. On this page, you can see your project's current deployment status, the production URL and associated commit, and all past deployments. + +![Site dashboard displaying your environments and deployments](~/assets/images/pages/get-started/site-dashboard.png) + +### Delete a project + +To delete your Pages project: + +1. Go back to the **Account Home** or use the drop-down menu at the top of the dashboard. +2. Select **Workers & Pages**. +3. Select your Pages project > **Settings** > **Delete project**. + +:::caution + + +For projects with a custom domain, you must first delete the CNAME record associated with your Pages project. Failure to do so may leave the DNS records active, causing your domain to point to a Pages project that no longer exists. Refer to [Deleting a custom domain](/pages/configuration/custom-domains/#delete-a-custom-domain) for instructions. + +For projects without a custom domain (any project on a `*.pages.dev` subdomain), your project can be deleted in the project's settings. + + +::: + +## Advanced project settings + +In the **Settings** section, you can configure advanced settings, such as changing your project name, updating your Git configuration, or updating your build command, build directory or environment variables. + +## Related resources + +* Set up a [custom domain for your Pages project](/pages/configuration/custom-domains/). +* Enable [Cloudflare Web Analytics](/pages/how-to/web-analytics/). +* Set up Access policies to [manage who can view your deployment previews](/pages/configuration/preview-deployments/#customize-preview-deployments-access). \ No newline at end of file