Migrate one.dash.cloudflare.com links to dash.cloudflare.com#31669
Migrate one.dash.cloudflare.com links to dash.cloudflare.com#31669nikitacano wants to merge 1 commit into
Conversation
Review
Code ReviewThis code review is in beta and may not always be helpful — use your judgment. Warnings (2)
Style Guide Review✅ No style-guide issues found. CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
There was a problem hiding this comment.
14 inline suggestions posted.
HIGH — Redundant phrasing introduced by the bulk replacement:
- 7 instances of
Cloudflare [Cloudflare dashboard](e.g.,the Cloudflare [Cloudflare dashboard],your Cloudflare [Cloudflare dashboard]) - 5 instances of
[Cloudflare dashboard] dashboard(original[Cloudflare One] dashboardleft a duplicate word)
MEDIUM — Missing articles across ~93 files: every In [Cloudflare dashboard] and Log in to [Cloudflare dashboard] should include the before the link. Suggested fixes on 2 representative lines; apply the same pattern everywhere:
In [Cloudflare dashboard]→In the [Cloudflare dashboard]Log in to [Cloudflare dashboard]→Log in to the [Cloudflare dashboard]
|  | ||
|
|
||
| To access the new overview, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/) and find Browser Isolation in the side navigation bar. | ||
| To access the new overview, log in to your Cloudflare [Cloudflare dashboard](https://dash.cloudflare.com/) and find Browser Isolation in the side navigation bar. |
There was a problem hiding this comment.
Remove redundant word:
| To access the new overview, log in to your Cloudflare [Cloudflare dashboard](https://dash.cloudflare.com/) and find Browser Isolation in the side navigation bar. | |
| To access the new overview, log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and find Browser Isolation in the side navigation bar. |
| These application statuses can also be used in Gateway HTTP policies, so you can block, isolate, limit uploads and downloads, and more based on the application status. | ||
|
|
||
| Both the analytics and policies are accessible in the Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/), empowering organizations with better visibility and control. | ||
| Both the analytics and policies are accessible in the Cloudflare [Cloudflare dashboard](https://dash.cloudflare.com/), empowering organizations with better visibility and control. |
There was a problem hiding this comment.
Remove redundant word:
| Both the analytics and policies are accessible in the Cloudflare [Cloudflare dashboard](https://dash.cloudflare.com/), empowering organizations with better visibility and control. | |
| Both the analytics and policies are accessible in the [Cloudflare dashboard](https://dash.cloudflare.com/), empowering organizations with better visibility and control. |
| These metrics can be filtered by all available filters on the dashboard, including user, application, or content category. | ||
|
|
||
| Both the analytics and policies are accessible in the Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/), empowering organizations with better visibility and control. | ||
| Both the analytics and policies are accessible in the Cloudflare [Cloudflare dashboard](https://dash.cloudflare.com/), empowering organizations with better visibility and control. |
There was a problem hiding this comment.
Remove redundant word:
| Both the analytics and policies are accessible in the Cloudflare [Cloudflare dashboard](https://dash.cloudflare.com/), empowering organizations with better visibility and control. | |
| Both the analytics and policies are accessible in the [Cloudflare dashboard](https://dash.cloudflare.com/), empowering organizations with better visibility and control. |
|  | ||
|
|
||
| To access the new overview, log in to your Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/) and find Analytics in the side navigation bar. | ||
| To access the new overview, log in to your Cloudflare [Cloudflare dashboard](https://dash.cloudflare.com/) and find Analytics in the side navigation bar. |
There was a problem hiding this comment.
Remove redundant word:
| To access the new overview, log in to your Cloudflare [Cloudflare dashboard](https://dash.cloudflare.com/) and find Analytics in the side navigation bar. | |
| To access the new overview, log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and find Analytics in the side navigation bar. |
|  | ||
|
|
||
| Both features are accessible in the Cloudflare [Zero Trust dashboard](https://one.dash.cloudflare.com/), empowering organizations with better visibility and control. | ||
| Both features are accessible in the Cloudflare [Cloudflare dashboard](https://dash.cloudflare.com/), empowering organizations with better visibility and control. |
There was a problem hiding this comment.
Remove redundant word:
| Both features are accessible in the Cloudflare [Cloudflare dashboard](https://dash.cloudflare.com/), empowering organizations with better visibility and control. | |
| Both features are accessible in the [Cloudflare dashboard](https://dash.cloudflare.com/), empowering organizations with better visibility and control. |
| <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard"> | ||
|
|
||
| 1. In the [Cloudflare One](https://one.dash.cloudflare.com) dashboard, go to **Network visibility** > **Diagnostics**. | ||
| 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/) dashboard, go to **Network visibility** > **Diagnostics**. |
There was a problem hiding this comment.
Remove duplicate word:
| 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/) dashboard, go to **Network visibility** > **Diagnostics**. | |
| 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Network visibility** > **Diagnostics**. |
| <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard"> | ||
|
|
||
| 1. In the [Cloudflare One](https://one.dash.cloudflare.com) dashboard, go to ***Insights** > *Network visibility** > **Diagnostics**. | ||
| 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/) dashboard, go to ***Insights** > *Network visibility** > **Diagnostics**. |
There was a problem hiding this comment.
Remove duplicate word:
| 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/) dashboard, go to ***Insights** > *Network visibility** > **Diagnostics**. | |
| 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to ***Insights** > *Network visibility** > **Diagnostics**. |
| <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard"> | ||
|
|
||
| 1. In the [Cloudflare One](https://one.dash.cloudflare.com) dashboard, go to **Network visibility** > **Diagnostics**. | ||
| 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/) dashboard, go to **Network visibility** > **Diagnostics**. |
There was a problem hiding this comment.
Remove duplicate word:
| 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/) dashboard, go to **Network visibility** > **Diagnostics**. | |
| 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Network visibility** > **Diagnostics**. |
| To enable read-only mode: | ||
|
|
||
| 1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Settings** > **Admin controls**. | ||
| 1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Settings** > **Admin controls**. |
There was a problem hiding this comment.
Add missing article:
| 1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Settings** > **Admin controls**. | |
| 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Settings** > **Admin controls**. |
| ### Get started | ||
|
|
||
| 1. In [Cloudflare One](https://one.dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. | ||
| 1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. |
There was a problem hiding this comment.
Add missing article:
| 1. In [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. | |
| 1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to **Networks** > **Resolvers & Proxies** > **Proxy endpoints**. |
|
Review posted to PR #31669 with 14 inline suggestions. Labels applied: Issues found:
What looks good:
No commits were pushed. |
e5d0047 to
5d3d0c2
Compare
5d3d0c2 to
4e77114
Compare
|
CI run failed: build logs |
The Zero Trust dashboard is now embedded within the Core Cloudflare dashboard at dash.cloudflare.com/:account/one/. Update all 231 instances of one.dash.cloudflare.com across 136 files: - Bare links: [Cloudflare One](https://one.dash.cloudflare.com/) → [Cloudflare dashboard](https://dash.cloudflare.com/) - HTML links: <a href="https://one.dash.cloudflare.com/">Cloudflare One</a> → <a href="https://dash.cloudflare.com/">Cloudflare dashboard</a> - Deeplinks: one.dash.cloudflare.com/?to=/:account/<path> → dash.cloudflare.com/?to=/:account/one/<path> Intentionally left unchanged: - global-policies.mdx: one.dash.cloudflare.com appears as a literal DNS hostname in policy tables, not as a clickable link. - core.json: dash-routes registry entry. All deeplink paths validated against ztx-frontend route definitions.
4e77114 to
904e002
Compare
Summary
The Zero Trust dashboard is now embedded within the Core Cloudflare dashboard at
dash.cloudflare.com/:account/one/. This PR migrates allone.dash.cloudflare.comreferences across 136 documentation files.Changes
136 files, 225 line replacements (purely mechanical — same number of insertions and deletions):
[Cloudflare One](https://one.dash.cloudflare.com/)→[Cloudflare dashboard](https://dash.cloudflare.com/)<a href="https://one.dash.cloudflare.com/">Cloudflare One</a>→<a href="https://dash.cloudflare.com/">Cloudflare dashboard</a>one.dash.cloudflare.com/?to=/:account/<path>→dash.cloudflare.com/?to=/:account/one/<path>All deeplink paths validated against
ztx-frontendroute definitions (verified the/one/prefix maps correctly to internal ZT routes likeaccess-controls/apps,email-security/settings,networks/connectors,home).Intentionally unchanged
global-policies.mdx:one.dash.cloudflare.comappears as a literal DNS hostname in policy tables (not a clickable link).dash-routes/core.json: route registry entry (internal, not user-facing).How to verify
Search the rendered docs for any remaining
one.dash.cloudflare.comclickable links — there should be none. The only remaining instances should be the DNS hostname references in the global policies page.