Skip to content

Commit cac9d22

Browse files
Updates to most current Pages Get Started (#1665)
* updates to most current pages get started * Update products/pages/src/content/getting-started/index.md Co-authored-by: Luke Edwards <[email protected]> * Update products/pages/src/content/getting-started/index.md * Update products/pages/src/content/getting-started/index.md * Update products/pages/src/content/getting-started/index.md * updates 2 * Update products/pages/src/content/getting-started/index.md Co-authored-by: Luke Edwards <[email protected]>
1 parent 9b4ffc9 commit cac9d22

File tree

1 file changed

+23
-21
lines changed
  • products/pages/src/content/getting-started

1 file changed

+23
-21
lines changed

products/pages/src/content/getting-started/index.md

Lines changed: 23 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -5,91 +5,93 @@ pcx-content-type: getting-started
55

66
# Getting started
77

8-
In this guide, you'll get started with Cloudflare Pages, and deploy your first website to the platform.
8+
In this guide, you will get started with Cloudflare Pages, and deploy your first website to the platform.
99

1010
<Aside>
1111

12-
You'll be signing up for a Cloudflare account. You may also want a custom domain available, but it isn't required.
12+
You will be signing up for a Cloudflare account. You may also want to create a custom domain, but this is not required.
1313

1414
</Aside>
1515

1616
## Connecting your GitHub account
1717

1818
### Sign in to Cloudflare Pages
1919

20-
To begin, go to the [Cloudflare Pages site](https://pages.dev) and sign in with your Cloudflare account. If you don't have one yet, you can sign up for an account as you get started deploying your new site.
20+
To begin, go to the [Cloudflare Pages site](https://pages.dev) and sign in with your Cloudflare account. If you do not have an account yet, you can sign up as you get started deploying your new Pages site.
2121

2222
### Connect to GitHub
2323

24-
Signing in with GitHub allows [Cloudflare Pages](https://pages.dev) to deploy your projects, update your GitHub PRs with [preview deployments](/platform/preview-deployments), and more. When you sign in, you'll also have the option of specifying any GitHub organizations that you'd like to connect to Cloudflare Pages. This allows you to deploy both public and private repositories for your own account, as well as repositories for your company or organization.
24+
Signing in with GitHub allows [Cloudflare Pages](https://pages.dev) to deploy your projects, update your GitHub PRs with [preview deployments](/platform/preview-deployments), and more. After you sign in, select **Create a project**.
2525

2626
## Configuration and deployment
2727

2828
### Selecting a GitHub repository
2929

30-
You can select a GitHub project from your personal account or an organization you've given Pages access to. This allows you to choose a GitHub repository to deploy using Pages. Both private and public repositories are supported.
30+
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.
3131

3232
<Aside>
3333

34-
Don't have a project? [Check out our extensive How-To section](/how-to) to learn how to create and deploy common frameworks and tools to Cloudflare Pages.
34+
If you do not have a project, [refer to our extensive How To section](/how-to) to learn how to create and deploy common frameworks and tools to Cloudflare Pages.
3535

3636
</Aside>
3737

3838
### Configuring your deployment
3939

40-
Once you've selected a repository, you can customize your deployment in the "Deployment settings" page.
40+
Once you have selected a repository, select **Install & Authorize** and **Begin setup**. You can then customize your deployment in the "Set up builds and deployments" page.
4141

42-
Your **project name** will be used to generate your deploy's hostname. By default, this matches your GitHub project name.
42+
Your **project name** will be used to generate your project's hostname. By default, this matches your GitHub project name.
4343

44-
**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 _aren't_ your production branch will be used for [preview deployments](/platform/preview-deployments).
44+
"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](/platform/preview-deployments).
4545

4646
![Configuration](./images/configuration.png)
4747

4848
#### Build settings
4949

50-
Depending on the framework, tool, or project you're deploying to Cloudflare Pages, you'll need to specify the site's **build command** and **publish directory** to tell Cloudflare Pages how to deploy your site.
50+
Depending on the framework, tool, or project you are deploying to Cloudflare Pages, you will need to specify the site's **build command** and **publish directory** to tell Cloudflare Pages how to deploy your site.
5151

52-
Our deployment UI provides a number of "presets", pre-filling values for many common deployment scenarios. If you're unsure what the correct values are for this section, check out our documentation for [build configuration](/platform/build-configuration).
52+
Our deployment UI provides a number of "presets", pre-filling values for many common deployment scenarios. If you are unsure what the correct values are for this section, check out our documentation for [build configuration](/platform/build-configuration).
5353

5454
![Build settings](./images/build-settings.png)
5555

5656
#### Environment variables
5757

5858
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.
5959

60+
After you have chosen your _Framework preset_, configured Root directory (optional), and customized your Environment variables (optional), you are ready to deploy.
61+
6062
## Your first deploy
6163

62-
Once you've finished setting your build configuration, Cloudflare Pages will begin deploying your site! Your project build logs will output as Cloudflare Pages installs your project dependencies, build the project, and deploys it to Cloudflare's global network.
64+
Once 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.
6365

6466
![Deploy log](./images/deploy-log.png)
6567

66-
When your project has finished deploying, you'll receive a unique URL to view your deployed site. Congrats! You've deployed your first site with Cloudflare Pages 🚀
68+
When your project has finished deploying, you will receive a unique URL to view your deployed site.
6769

6870
## Managing your site
6971

70-
Selecting "Continue to project" after your first deploy, you'll see your project's configuration in the Cloudflare Pages dashboard. Here, you can see your project's current deployment status, the production URL and associated commit, and all past deployments.
72+
After your first deploy, select **Continue to project** to see 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.
7173

7274
![Site dashboard](./images/site-dashboard.png)
7375

7476
### Adding a custom domain
7577

76-
While every Cloudflare Pages site receives a custom subdomain during deployment, you may also wish to point custom domains (or subdomains) to your site. To do this, go to the "Domains" tab in your site dashboard.
78+
While every Cloudflare Pages site receives a custom subdomain during deployment, you may also wish to point custom domains (or subdomains) to your site. To do this, go to **Custom domains** in your site dashboard.
7779

7880
![Domains](./images/domains.png)
7981

80-
Click the "Set up a domain" button, and provide the domain that you'd like to serve your Cloudflare Pages site on. Depending on the domain, you'll need to configure nameservers or add a custom CNAME record to point the domain to your Cloudflare Pages site.
82+
Select **Set up a domain**, provide the domain that you would like to serve your Cloudflare Pages site on and select **Continue**. Depending on the domain, you will need to configure nameservers or add a custom CNAME record to point the domain to your Cloudflare Pages site.
8183

8284
#### Configure nameservers
8385

84-
Configure your nameservers to point to Cloudflare's name servers. If your nameservers are successfully pointed to Cloudflare, we'll proceed by creating a CNAME record for you!
86+
Configure your nameservers to point to Cloudflare's name servers. If your nameservers are successfully pointed to Cloudflare, Cloudflare will proceed by creating a CNAME record for you.
8587

8688
#### Add a custom CNAME record
8789

88-
If you don't want to point your nameservers to Cloudflare, you can still use a custom CNAME record to use a single domain with Cloudflare Pages.
90+
If you do not want to point your nameservers to Cloudflare, you can still use a custom CNAME record to use a single domain with Cloudflare Pages. You can configure your DNS settings in the **DNS** section of the Cloudflare dashboard.
8991

90-
| Domain | CNAME |
91-
| ------------ | ------------------ |
92-
| `domain.com` | `custom.pages.dev` |
92+
| Type | Name | Content |
93+
| ------------ | ------------------ | ------------------ |
94+
| `CNAME` | `domain.com` | `custom.pages.dev` |
9395

9496
## Advanced project settings
9597

0 commit comments

Comments
 (0)