fix: expand network-security primer (closes #55)#479
Open
frameworks-volunteer wants to merge 1 commit intosecurity-alliance:developfrom
Open
fix: expand network-security primer (closes #55)#479frameworks-volunteer wants to merge 1 commit intosecurity-alliance:developfrom
frameworks-volunteer wants to merge 1 commit intosecurity-alliance:developfrom
Conversation
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
scode2277
approved these changes
May 6, 2026
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
2 participants
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.
Summary
Expands the existing
infrastructure/network-security.mdxfrom a thin 9-bullet list into a proper primer following the repo template structure. The page now covers:Architecture decision: keep Network under Infrastructure
On the question from @mattaereal about a separate Network domain: the current structure already places DDoS, DNS, and network security under Infrastructure, which is where they belong. A separate top-level "Network Security" category would duplicate content and fragment the reader's journey (DDoS is both a network and an infrastructure concern; DNS is both network and domain management).
Instead, this PR expands the existing
infrastructure/network-security.mdxinto a proper hub that cross-references:/infrastructure/ddos-protection/infrastructure/domain-and-dns-security/overview/infrastructure/cloud/infrastructure/zero-trust-principles/privacy/vpn-servicesThe VPN content in privacy/ covers the individual privacy use case (hiding metadata, choosing providers, public Wi-Fi). The network-security page covers the infrastructure use case (VPN gateways for team access to management plane). These are distinct concerns that naturally live in different frameworks, with cross-references connecting them.
Closes #55