[Cloudflare One] Traffic Policies Root-Level ELI5#28947
Open
Oxyjun wants to merge 3 commits intoproductionfrom
Open
[Cloudflare One] Traffic Policies Root-Level ELI5#28947Oxyjun wants to merge 3 commits intoproductionfrom
Oxyjun wants to merge 3 commits intoproductionfrom
Conversation
Add missing context and definitions across all four egress policy pages: - Frame the problem (shared IPs) before introducing the solution (dedicated egress IPs) - Define jargon on first use: source IP anchoring, CGNAT ranges, L3/L4, BYOIP - Break dense paragraphs into smaller conceptual units (load balancing section) - Move IPv4/IPv6 behavior explanation before the reference table - Clarify geolocation consequences of missing catch-all policy - Explain why host selectors need additional configuration (L4 visibility) - Fix 'Traffic and DNS mode mode' typo in host-selectors.mdx
Revert the 'for geographic redundancy' addition to the two-city minimum statement. The original text states the minimum without explaining why, and the rationale was inferred without a verified source.
Apply ELI5 analysis to all 11 root-level pages in traffic-policies/. Add missing cross-links, define Cloudflare-specific terms on first use, fix typos (sysctl, messaging, grammar), expand acronyms (GRE, CIPA, SIP, XMPP), restructure dense paragraphs, add caution for QUIC/UDP requirement, distinguish security risks from threats, explain global policy actions, and clarify hostname vs support hostname enforcement behavior.
Oxyjun
changed the title
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
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
1 participant
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.
Applies ELI5 (Explain Like I'm 5) clarity analysis to all 11 root-level pages in
src/content/docs/cloudflare-one/traffic-policies/. The goal is to reduce jargon barriers and missing context for IT admins and security engineers who are new to Cloudflare-specific concepts.:::cautionfor QUIC/UDP requirement${managed_ruleset_id}→<MANAGED_RULESET_ID>placeholder, fix phase name inconsistency, add Rulesets Engine preamble, restructure disable instructionsallow_child_bypassdefault behavior, fix "messaing" → "messaging" typoallowandresolveaction definitions, add Network and HTTP inspection policy intro paragraphs with action definitions (bypass,allow,block,noisolate,noscan)