fix: replace duplicate learn-more components with deploy-to-pages

This commit is contained in:
Pat Browne 2026-01-06 23:00:48 -05:00
parent cee9a4313e
commit 18607c8518
10 changed files with 16 additions and 62 deletions

View file

@ -29,11 +29,7 @@ brunch new proj -s es6
## Deploy with Cloudflare Pages
<Render
file="framework-guides/learn-more"
product="pages"
params={{ name: "Brunch" }}
/>
<Render file="deploy-to-pages-steps-no-preset" product="pages" />
<PagesBuildPreset framework="brunch" />

View file

@ -94,14 +94,12 @@ Inside of `hello-world.md`, add some initial content to create your post. Remove
## Deploy with Cloudflare Pages
<Render
file="framework-guides/learn-more"
product="pages"
params={{ name: "Hugo" }}
/>
<Render file="deploy-to-pages-steps-no-preset" product="pages" />
<PagesBuildPreset framework="hugo" />
While `public` is the default build directory for Hugo sites, this setting can be configured with the [`publishDir` setting](https://gohugo.io/configuration/all/#publishdir).
:::note[Base URL configuration]
Hugo allows you to configure the `baseURL` of your application. This allows you to utilize the `absURL` helper to construct full canonical URLs. In order to do this with Pages, you must provide the `-b` or `--baseURL` flags with the `CF_PAGES_URL` environment variable to your `hugo` build command.

View file

@ -65,11 +65,7 @@ If you are migrating an existing Jekyll project to Pages, confirm that your `Gem
## Deploy with Cloudflare Pages
<Render
file="framework-guides/learn-more"
product="pages"
params={{ name: "Jekyll" }}
/>
<Render file="deploy-to-pages-steps-no-preset" product="pages" />
<PagesBuildPreset framework="jekyll" />

View file

@ -74,17 +74,13 @@ git push -u origin main
### Create a Pages project
<Render
file="framework-guides/learn-more"
product="pages"
params={{ name: "Nuxt.js" }}
/>
<Render file="deploy-to-pages-steps-no-preset" product="pages" />
<PagesBuildPreset framework="nuxt-js" />
Optionally, you can customize the **Project name** field. It defaults to the GitHub repository's name, but it does not need to match. The **Project name** value is assigned as your `*.pages.dev` subdomain.
4. After completing configuration, select the **Save and Deploy**.
7. After completing configuration, select the **Save and Deploy**.
Review your first deploy pipeline in progress. Pages installs all dependencies and builds the project as specified. Cloudflare Pages will automatically rebuild your project and deploy it on every new pushed commit.

View file

@ -35,15 +35,11 @@ This is the directory name that you will set in the build command.
## Deploy with Cloudflare Pages
<Render
file="framework-guides/learn-more"
product="pages"
params={{ name: "Pelican" }}
/>
<Render file="deploy-to-pages-steps-no-preset" product="pages" />
<PagesBuildPreset framework="pelican" />
4. Select **Environment variables (advanced)** and set the `PYTHON_VERSION` variable with the value of `3.7`.
7. Select **Environment variables (advanced)** and set the `PYTHON_VERSION` variable with the value of `3.7`.
For the complete guide to deploying your first site to Cloudflare Pages, refer to the [Get started guide](/pages/get-started/).

View file

@ -41,11 +41,7 @@ npm start
### Deploy via the Cloudflare dashboard
<Render
file="framework-guides/learn-more"
product="pages"
params={{ name: "Qwik" }}
/>
<Render file="deploy-to-pages-steps-no-preset" product="pages" />
<PagesBuildPreset framework="qwik" />

View file

@ -34,18 +34,10 @@ To use `create-cloudflare` to create a new Vue project, run the following comman
### Deploy via the Cloudflare dashboard
<Render
file="framework-guides/learn-more"
product="pages"
params={{ name: "Vue" }}
/>
<div>
<Render file="deploy-to-pages-steps-no-preset" product="pages" />
<PagesBuildPreset framework="vue" />
</div>
After configuring your site, you can begin your first deploy. You should see Cloudflare Pages installing `vue`, your project dependencies, and building your site, before deploying it.
:::note

View file

@ -49,11 +49,7 @@ git push -u origin main
### Create a Pages project
<Render
file="framework-guides/learn-more"
product="pages"
params={{ name: "Angular" }}
/>
<Render file="deploy-to-pages-steps-no-preset" product="pages" />
<PagesBuildPreset framework="angular" />
@ -64,7 +60,7 @@ Change the `Build directory` to `dist/cloudflare/browser`
Optionally, you can customize the **Project name** field. It defaults to the GitHub repository's name, but it does not need to match. The **Project name** value is assigned as your `*.pages.dev` subdomain.
4. After completing configuration, select the **Save and Deploy**.
7. After completing configuration, select the **Save and Deploy**.
Review your first deploy pipeline in progress. Pages installs all dependencies and builds the project as specified. Cloudflare Pages will automatically rebuild your project and deploy it on every new pushed commit.

View file

@ -60,18 +60,10 @@ npm run astro add cloudflare
### Deploy via the Cloudflare dashboard
<Render
file="framework-guides/learn-more"
product="pages"
params={{ name: "Astro" }}
/>
<div>
<Render file="deploy-to-pages-steps-no-preset" product="pages" />
<PagesBuildPreset framework="astro" />
</div>
Optionally, you can customize the **Project name** field. It defaults to the GitHub repository's name, but it does not need to match. The **Project name** value is assigned as your `*.pages.dev` subdomain.
After completing configuration, select **Save and Deploy**.

View file

@ -37,15 +37,11 @@ You have successfully created a GitHub repository and pushed your MkDocs project
## Deploy with Cloudflare Pages
<Render
file="framework-guides/learn-more"
product="pages"
params={{ name: "MkDocs" }}
/>
<Render file="deploy-to-pages-steps-no-preset" product="pages" />
<PagesBuildPreset framework="mkdocs" />
4. Go to **Environment variables (advanced)** > **Add variable** > and add the variable `PYTHON_VERSION` with a value of `3.7`.
7. Go to **Environment variables (advanced)** > **Add variable** > and add the variable `PYTHON_VERSION` with a value of `3.7`.
After deploying your site, you will receive a unique subdomain for your project on `*.pages.dev`.