Skip to content

[APO] Use DashButton component #25758

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: production
Choose a base branch
from
+16 −14
Open

[APO] Use DashButton component #25758

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions ...tent/docs/automatic-platform-optimization/get-started/activate-cf-wp-plugin.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,9 +39,9 @@ The Cloudflare APO WordPress plugin does not support multisite WordPress install

<DashButton url="/?to=/:account/:zone/speed/optimization" />

3. Go to **Content Optimization**.
4. For **Automatic Platform Optimization for WordPress**, select **Purchase**.
5. Enter your payment information and select **Confirm payment**.
2. Go to **Content Optimization**.
3. For **Automatic Platform Optimization for WordPress**, select **Purchase**.
4. Enter your payment information and select **Confirm payment**.

## Install and activate the Cloudflare WordPress plugin

Expand Down
20 changes: 11 additions & 9 deletions ...ontent/docs/automatic-platform-optimization/get-started/confirm-dns-records.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,21 +1,23 @@
---
title: Confirm DNS Records
title: Confirm DNS records
pcx_content_type: how-to
sidebar:
order: 6
head:
- tag: title
content: Confirm DNS records

---

Before you change your nameserver, confirm your DNS records are displaying correctly.
import { DashButton } from "~/components";

Before you change your nameservers, confirm your DNS records are displaying correctly.

1. In the Cloudflare dashboard, go to the DNS **Records** page.

<DashButton url="/?to=/:account/:zone/dns/records" />

1. Open your Cloudflare dashboard and select your account.
2. Select your domain from the dropdown.
3. Select the **DNS** > **Records** tile. DNS management for your domain displays.
4. To add a record, select **Add record.**
5. To edit an existing record, select **Edit** for the appropriate record.
6. After making your changes, select **Save**.
2. To add a record, select **Add record**.
3. To edit an existing record, select **Edit** for the appropriate record.
4. After making your changes, select **Save**.

After you confirm your DNS records, [change your nameservers](/automatic-platform-optimization/get-started/change-nameservers/).
4 changes: 2 additions & 2 deletions src/content/docs/automatic-platform-optimization/get-started/verify-apo-works.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ You can check whether or not APO is working by verifying APO headers are present
- `cf-edge-cache` | `cache, platform=wordpress`
- The `cf-edge-cache` headers confirms the WordPress plugin is installed and enabled.

In a terminal, use the following cURL. The header `'accept: text/html'` is important
In a terminal, use the following cURL. The header `'accept: text/html'` is important.

```sh
curl -svo /dev/null -A "CF" 'https://example.com/' -H 'accept: text/html' 2>&1 | grep 'cf-cache-status\|cf-edge\|cf-apo-via'
Expand All @@ -42,4 +42,4 @@ As always, `cf-cache-status` displays if the asset hit the cache or was consider

## Verify the APO integration and WordPress integration work

Open your WordPress site and publish a change. When the integration is working, the page is cached with `cf-cache-status: HIT` and `cf-apo-via: tcache`
Open your WordPress site and publish a change. When the integration is working, the page is cached with `cf-cache-status: HIT` and `cf-apo-via: tcache`.
Loading