[Docs Site] Update pinned api-schemas commit#7
Open
github-actions[bot] wants to merge 1 commit intoproductionfrom
Open
[Docs Site] Update pinned api-schemas commit#7github-actions[bot] wants to merge 1 commit intoproductionfrom
github-actions[bot] wants to merge 1 commit intoproductionfrom
Conversation
…b9d757530cd059067ea
fb1337
pushed a commit
that referenced
this pull request
Mar 16, 2026
…shooting (cloudflare#28780) * [Registrar] Rewrite transfer page and add registration limits troubleshooting Restructure the transfer-domain-to-cloudflare page into two clear phases (add domain to Cloudflare, then transfer registration) instead of the previous flat 10-step list. Inline partials, add DNSSEC/nameserver provider links, explain why each step is needed, and add registration limits content with actionable guidance. Add new troubleshooting section for transfers rejected due to registration period limits (10-year max for most TLDs, 5-year for .co). Clarify vague language throughout: specific WHOIS status explanations, concrete 45-day expiration rule, ICANN contact-change lock details. * [Registrar] Simplify transfer timeline language in opening paragraph * [Registrar] Address PR review feedback and restore grace period transfer scenario - Break opening paragraph into scannable bullet list (#1) - Lead with action instead of comparison to other registrars (#2) - Replace IDN jargon with plain language and example (#3) - Lead with actionable advice in Restrictions block (#5) - Cross-link 'active on Cloudflare' to full-setup docs (#6) - Replace inlined DNSSEC links with dnssec-providers partial (#7) - Slim 'Add your domain' section to cross-link full-setup page (#8) - Reorder unlock section to put action before context (#9) - Restore 45-day grace period scenario with concrete date example and ICANN refund entitlement, matching FAQ content (#10) * [Registrar] Simplify transfer page, move details to troubleshooting - Simplify opening: shorter total time bullet, one-line prereq - Move Restrictions block content to troubleshooting page - Move registration limits and 'domain not available' Details blocks to troubleshooting page as standalone sections with full examples - Add 45-day grace period note in Before you begin with FAQ link - Update TLD page to link to troubleshooting instead of removed anchor - Simplify approve-transfer section for non-technical audience - Convert caution to note for Active status requirement - Make authoritative DNS requirement a bullet in Before you begin - Remove redundant 'Go to Transfer Domains page' text (DashButton CTA) * [Registrar] Restore auth code callout in opening note block
fb1337
pushed a commit
that referenced
this pull request
Mar 16, 2026
…28876) * [Cloudflare One] Add network-to-network get-started page Add get-started page for the Replace VPN network-to-network wizard (PCX-20917). Covers the 6-step WARP Connector site-to-site flow: define segments, deploy connectors, forward traffic, verify. Also adds the network-to-network card to the Replace VPN index page. * [Cloudflare One] ELI5 clarity pass on network-to-network Replace jargon with plain language for non-technical audience: - bidirectionally -> send and receive traffic in both directions - Add inline definition for IP range on first use - Explain why IP ranges must not overlap - Add consequence statement for skipping Step 5 - Add IPv4 address examples to help identify correct format - Define Split Tunnel Exclude list inline * [Cloudflare One] Remove unvalidated SSH troubleshoot bullet The SSH drop during install is already covered by the caution box in Step 2. The troubleshoot bullet added Split Tunnel workaround advice that has not been fully validated. The install partial documents this separately for the manual setup flow. * [Cloudflare One] Remove IP forwarding persistence troubleshoot bullet Post-setup hardening concern, not relevant to the quick-start flow. Already documented in the WARP Connector install partial. * [Cloudflare One] Simplify troubleshoot section to reference links only Remove first-party firewall bullet — duplicates advice already in the WARP Connector install partial. Matches the device-to-network sibling pattern of linking to reference docs instead of inlining troubleshoot steps. * [Cloudflare One] Replace technical examples with relatable use case Database replication and cross-site administration are not relatable for the SMB target audience. Use file server and internal application examples instead. * [Cloudflare One] Align WARP Connector intro with dashboard terminology The dashboard introduces 'network connector' as a concept before naming WARP Connector. Mirror the device-to-network sibling pattern ('is a network connector that...'). * [Cloudflare One] Clarify WARP Connector role in How it works Explain why only one device per network needs the install: that device handles traffic for the entire network. Drop gateway jargon and redundant second paragraph about security policies (already covered in Recommended next steps). * [Cloudflare One] Remove unvalidated IP range examples and inline definition Drop the inline IP range definition (Sam either knows their range or needs to check their router, not read a parenthetical). Drop the common ranges list and IPv4 pattern examples from the note — we have not validated these as appropriate recommendations and the step instructions already show the expected format. * [Cloudflare One] Drop IPv6 note — UI already validates for IPv4 Confirmed the wizard rejects IPv6 input with an error message. The note was redundant with UI validation. Keep the 'check your router' tip since that is genuinely useful for users who do not know their IP range. * [Cloudflare One] Remove unvalidated SSH caution from Step 2 Consistent with earlier decision to remove the SSH troubleshoot bullet. The behavior has not been fully validated. * [Cloudflare One] Make Access application description more concrete Align with device-to-network pattern: specify what 'destinations' means in this context (services or hosts on connected networks). * [Cloudflare One] Fix anchor text to match destination page title 'WARP Connector site-to-site' is the sidebar label, not the page title. Use the actual title: 'Connect two or more private networks'. * [Cloudflare One] Fix anchor text for WARP Connector tips link Match destination page title: 'Tips and best practices' not 'WARP Connector tips'. * Update src/content/docs/cloudflare-one/setup/replace-vpn/network-to-network.mdx Co-authored-by: Caley Burton <caley@cloudflare.com> * Update src/content/docs/cloudflare-one/setup/replace-vpn/network-to-network.mdx Co-authored-by: Caley Burton <caley@cloudflare.com> * [Cloudflare One] Address reviewer feedback on network-to-network page - Fix empty product bullet in frontmatter from Caley's suggestion - Add printer to intro use cases (Alexa #3) - Rephrase Step 1 to clarify dashboard creates config but user still installs the connector (Alexa #5) - Replace 'wizard generates' with 'dashboard provides' in Step 5 (Alexa #6) - Reframe device profile bullet to focus on independent routing control for connectors vs user devices (Alexa #7) --------- Co-authored-by: Caley Burton <caley@cloudflare.com>
Author
|
Hey there, we've marked this pull request as stale because there's no recent activity on it. This label is helps us identify PRs that might need updates (or to be closed out by our team if no longer relevant). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates the api-schemas commit reference to the latest version (c905c41fc030428956041b9d757530cd059067ea).