Skip to content

Commit 2c75398

Browse files
dcpenadcpena
committed
Create new partials
1 parent 7db67ae commit 2c75398

File tree

4 files changed

+192
-0
lines changed

4 files changed

+192
-0
lines changed

‎src/content/partials/fundamentals/verify-email-address.mdx‎

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
---
2+
{}
3+
---
4+
5+
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.
6+
7+
## When creating your account
8+
9+
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.
10+
11+
To verify your email:
12+
13+
1. Log into your email provider and find your recent message from Cloudflare. If you cannot find the message, check your Spam folder.
14+
2. Click the link in the email.
15+
3. Log into Cloudflare to verify the email address associated with your account.
16+
17+
:::note
18+
19+
20+
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.
21+
22+
23+
:::
24+
25+
***
26+
27+
## Resend verification emails
28+
29+
If you cannot find your verification email or your email has expired, request another verification email:
30+
31+
1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com).
32+
2. Go to **My Profile**.
33+
3. For **Email Address**, select **Send verification email** (if this option is not available, your email has already been verified).
34+
35+
***
36+
37+
## Verification issues
38+
39+
If you experience issues with your verification link, you might have already verified your email address.
40+
41+
To check:
42+
43+
1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com).
44+
2. Go to **My Profile**.
45+
3. For **Email Address**, your email address will have `(verified)` added after it.
46+
47+
If your email is still not verified, try clicking the verification link in a different browser or an incognito window.
48+
49+
If this still does not work, try [resending](#resend-verification-emails) the verification email to get a new verification link.

‎src/content/partials/pages/get-started-git-configure-deployment.mdx‎

Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
---
2+
{}
3+
---
4+
5+
import { Details } from "~/components"
6+
7+
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**.
8+
9+
Your **project name** will be used to generate your project's hostname. By default, this matches your Git project name.
10+
11+
**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/).
12+
13+
:::note
14+
15+
16+
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.
17+
18+
19+
:::
20+
21+
![Set up builds and deployments page with Project name and Production branch filled in](~/assets/images/pages/get-started/configuration.png)
22+
23+
### Configure your build settings
24+
25+
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.
26+
27+
:::caution[No framework required]
28+
29+
30+
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.
31+
32+
33+
:::
34+
35+
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.
36+
37+
![Build setting fields that need to be filled in](~/assets/images/pages/get-started/build-settings.png)
38+
39+
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.
40+
41+
![Root directory field to be filled in](~/assets/images/pages/get-started/root-directory.png)
42+
43+
44+
<Details header="Understanding your build configuration">
45+
46+
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.
47+
48+
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.
49+
50+
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.
51+
52+
Refer to [Build configuration](/pages/configuration/build-configuration/) for more information.
53+
54+
55+
</Details>
56+
57+
### Environment variables
58+
59+
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.
60+
61+
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.
62+
63+
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.
64+
65+
## Your first deploy
66+
67+
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.
68+
69+
![Deployment details in the Cloudflare dashboard](~/assets/images/pages/get-started/deploy-log.png)
70+
71+
When your project has finished deploying, you will receive a unique URL to view your deployed site.
72+
73+
:::caution[DNS errors]
74+
75+
76+
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.
77+
78+
79+
:::

‎src/content/partials/pages/get-started-git-connect-pages.mdx‎

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
{}
3+
---
4+
5+
Pages offers support for [GitHub](https://github.com/) and [GitLab](https://gitlab.com/). To create your first Pages project:
6+
7+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
8+
2. In Account Home, select **Workers & Pages**.
9+
3. Select **Create application** > **Pages** > **Connect to Git**.
10+
11+
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/).
12+
13+
:::note
14+
15+
16+
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.
17+
18+
If you are using GitLab, you must have the **Maintainer** role or higher on the repository to successfully deploy with Cloudflare Pages.
19+
20+
21+
:::
22+
23+
### Select your GitHub repository
24+
25+
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.
26+
27+
### Select your GitLab repository
28+
29+
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.

‎src/content/partials/pages/get-started-git-manage-site.mdx‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
{}
3+
---
4+
5+
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.
6+
7+
![Site dashboard displaying your environments and deployments](~/assets/images/pages/get-started/site-dashboard.png)
8+
9+
### Delete a project
10+
11+
To delete your Pages project:
12+
13+
1. Go back to the **Account Home** or use the drop-down menu at the top of the dashboard.
14+
2. Select **Workers & Pages**.
15+
3. Select your Pages project > **Settings** > **Delete project**.
16+
17+
:::caution
18+
19+
20+
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.
21+
22+
For projects without a custom domain (any project on a `*.pages.dev` subdomain), your project can be deleted in the project's settings.
23+
24+
25+
:::
26+
27+
## Advanced project settings
28+
29+
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.
30+
31+
## Related resources
32+
33+
* Set up a [custom domain for your Pages project](/pages/configuration/custom-domains/).
34+
* Enable [Cloudflare Web Analytics](/pages/how-to/web-analytics/).
35+
* Set up Access policies to [manage who can view your deployment previews](/pages/configuration/preview-deployments/#customize-preview-deployments-access).

0 commit comments

Comments
 (0)