From 966f30ae2fca122a9e6f1415ad16982c2cb299d6 Mon Sep 17 00:00:00 2001 From: Jack Carter <128555021+SunsetDrifter@users.noreply.github.com> Date: Wed, 13 May 2026 12:38:33 +0200 Subject: [PATCH] =?UTF-8?q?docs(site-to-vpn):=20move=20page=20under=20Netw?= =?UTF-8?q?orks=20=E2=86=92=20Use=20Cases?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The page describes a Networks-based setup; living under Network Routes mis-categorised it. - git mv to /manage/networks/use-cases/site-to-vpn.mdx (as a direct child of Use Cases, not under By Scenario) - Navigation: remove entry from Network Routes → By Scenario, add under Networks → Use Cases - Redirect old URL (/manage/network-routes/use-cases/by-scenario/site-to-vpn) to new URL, permanent - Update in-tree links in use-cases/site-to-site/index.mdx and network-routes/use-cases/by-scenario/site-to-site-office.mdx --- next.config.mjs | 5 +++++ src/components/NavigationDocs.jsx | 8 ++++---- .../use-cases/by-scenario/site-to-site-office.mdx | 2 +- .../by-scenario => networks/use-cases}/site-to-vpn.mdx | 0 src/pages/use-cases/site-to-site/index.mdx | 4 ++-- 5 files changed, 12 insertions(+), 7 deletions(-) rename src/pages/manage/{network-routes/use-cases/by-scenario => networks/use-cases}/site-to-vpn.mdx (100%) diff --git a/next.config.mjs b/next.config.mjs index c328a858..a41b55f7 100644 --- a/next.config.mjs +++ b/next.config.mjs @@ -31,6 +31,11 @@ const nextConfig = { destination: '/manage/networks', permanent: true, }, + { + source: '/manage/network-routes/use-cases/by-scenario/site-to-vpn', + destination: '/manage/networks/use-cases/site-to-vpn', + permanent: true, + }, { source: '/docs/getting-started/installation', destination: '/get-started/install', diff --git a/src/components/NavigationDocs.jsx b/src/components/NavigationDocs.jsx index 804e4810..f3160091 100644 --- a/src/components/NavigationDocs.jsx +++ b/src/components/NavigationDocs.jsx @@ -232,6 +232,10 @@ export const docsNavigation = [ }, ], }, + { + title: 'Site-to-VPN', + href: '/manage/networks/use-cases/site-to-vpn', + }, ], }, ], @@ -262,10 +266,6 @@ export const docsNavigation = [ title: 'Site-to-Site: Cloud', href: '/manage/network-routes/use-cases/by-scenario/site-to-site-cloud', }, - { - title: 'Site-to-VPN', - href: '/manage/network-routes/use-cases/by-scenario/site-to-vpn', - }, { title: 'Exit Nodes', href: '/manage/network-routes/use-cases/by-scenario/exit-nodes', diff --git a/src/pages/manage/network-routes/use-cases/by-scenario/site-to-site-office.mdx b/src/pages/manage/network-routes/use-cases/by-scenario/site-to-site-office.mdx index 775ed26b..583e9808 100644 --- a/src/pages/manage/network-routes/use-cases/by-scenario/site-to-site-office.mdx +++ b/src/pages/manage/network-routes/use-cases/by-scenario/site-to-site-office.mdx @@ -180,7 +180,7 @@ ping 10.0.0.100 # HQ server Some scenarios require office systems without NetBird to initiate connections to NetBird-connected peers (monitoring, backups, management -tools, etc.). See [Site-to-VPN](/manage/network-routes/use-cases/by-scenario/site-to-vpn) +tools, etc.). See [Site-to-VPN](/manage/networks/use-cases/site-to-vpn) for the full step-by-step guide, including DNS resolution and the per-service port-forwarding alternative. diff --git a/src/pages/manage/network-routes/use-cases/by-scenario/site-to-vpn.mdx b/src/pages/manage/networks/use-cases/site-to-vpn.mdx similarity index 100% rename from src/pages/manage/network-routes/use-cases/by-scenario/site-to-vpn.mdx rename to src/pages/manage/networks/use-cases/site-to-vpn.mdx diff --git a/src/pages/use-cases/site-to-site/index.mdx b/src/pages/use-cases/site-to-site/index.mdx index 5f3e780d..f3404dca 100644 --- a/src/pages/use-cases/site-to-site/index.mdx +++ b/src/pages/use-cases/site-to-site/index.mdx @@ -42,7 +42,7 @@ Office Server ──────► Routing Peer ──────► NetBird T - On-premise servers initiating backups to cloud peers - Legacy systems that must initiate outbound connections -**Implementation:** Use [Networks](/manage/networks) (recommended) or [Network Routes](/manage/network-routes). See the [Site-to-VPN guide](/manage/network-routes/use-cases/by-scenario/site-to-vpn). +**Implementation:** Use [Networks](/manage/networks) (recommended) or [Network Routes](/manage/network-routes). See the [Site-to-VPN guide](/manage/networks/use-cases/site-to-vpn). ### Site-to-Site @@ -82,7 +82,7 @@ Your Laptop ──────► NetBird Tunnel ──────► Exit Node |-------------|----------|----------------| | Access home devices from my laptop | VPN-to-Site | [Networks](/manage/networks/use-cases/by-scenario/access-home-devices) | | Access office resources while traveling | VPN-to-Site | [Networks](/manage/networks/use-cases/by-scenario/remote-worker-access) | -| Let an office server connect to my laptop | Site-to-VPN | [Networks](/manage/networks) or [Network Routes](/manage/network-routes/use-cases/by-scenario/site-to-vpn) | +| Let an office server connect to my laptop | Site-to-VPN | [Networks](/manage/networks/use-cases/site-to-vpn) or [Network Routes](/manage/network-routes) | | Connect two home networks together | Site-to-Site | [Network Routes](/manage/network-routes/use-cases/by-scenario/site-to-site-home) only | | Link branch offices | Site-to-Site | [Network Routes](/manage/network-routes/use-cases/by-scenario/site-to-site-office) only | | Bridge cloud VPC with on-premise network | Site-to-Site | [Network Routes](/manage/network-routes/use-cases/by-scenario/site-to-site-cloud) only |