Rename /devtools-protocol-chromium/ to /devtools/protocol/ (#3481)

* elim ~/devtools-protocol-chromium/

* linkfix

* linkfix & See

* start /devtools/ dir

* linkfix after /devtools/

* suppress EdgeHTML

Author: mikehoffms

.openpublishing.redirection.json

@@ -154,6 +154,11 @@
         "redirect_url": "/microsoft-edge/devtools-guide-chromium/sensors/#simulate-device-orientation",
         "redirect_document_id": false
       },
+      {
+        "source_path": "./microsoft-edge/devtools-protocol-chromium/index.md",
+        "redirect_url": "/microsoft-edge/devtools/protocol/index",
+        "redirect_document_id": false
+      },
 // /Microsoft Edge DevTools
 // ============================================================================
 // Microsoft Edge extensions

microsoft-edge/developer/index.yml

@@ -210,7 +210,7 @@ landingContent:
             url: ../test-and-automation/test-and-automation.md
 
           - text: DevTools Protocol
-            url: ../devtools-protocol-chromium/index.md   # https://learn.microsoft.com/microsoft-edge/devtools-protocol-chromium/
+            url: ../test-and-automation/devtools-protocol.md  # jump page
 
           - text: Use Playwright to automate and test in Microsoft Edge
             url: ../playwright/index.md

…edge/devtools-protocol-chromium/index.md microsoft-edge/devtools/protocol/index.mdmicrosoft-edge/devtools-protocol-chromium/index.md renamed to microsoft-edge/devtools/protocol/index.md microsoft-edge/devtools-protocol-chromium/index.md renamed to microsoft-edge/devtools/protocol/index.md

@@ -9,12 +9,7 @@ ms.date: 04/06/2021
 ---
 # Microsoft Edge DevTools Protocol
 
-Use the DevTools Protocol to instrument, inspect, debug, and profile browsers including Microsoft Edge.  The Microsoft Edge DevTools Protocol matches the APIs of the Chrome DevTools Protocol.  For reference documentation, go to [Chrome DevTools Protocol Viewer](https://chromedevtools.github.io/devtools-protocol/tot).
-
-> [!NOTE]
-> With the shift in the underlying web platform of Microsoft Edge to Chromium, the [Microsoft Edge (EdgeHTML) DevTools Protocol](/archive/microsoft-edge/legacy/developer/devtools-protocol/index) won't be receiving any further updates.  Going forward, the Microsoft Edge DevTools Protocol will match the APIs of the Chrome DevTools Protocol.
->
-> Any methods that were prefixed with `ms` in the [Microsoft Edge (EdgeHTML) DevTools Protocol](/archive/microsoft-edge/legacy/developer/devtools-protocol/index) are no longer supported in the Microsoft Edge DevTools Protocol.
+Use the DevTools Protocol to instrument, inspect, debug, and profile browsers including Microsoft Edge.  The Microsoft Edge DevTools Protocol matches the APIs of the Chrome DevTools Protocol.  For Reference documentation, see [Chrome DevTools Protocol Viewer](https://chromedevtools.github.io/devtools-protocol/tot).
 
 
 <!-- ====================================================================== -->
@@ -133,11 +128,11 @@ String("Target is closing")
 
 You can install the [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) from the [Microsoft Store](https://apps.microsoft.com).  This app enables you to remotely debug Microsoft Edge running on a Windows 10 or later device from your development machine.
 
-To learn how to set up your Windows device and connect to it from your development machine, see [Get started with remote debugging Windows devices](../devtools-guide-chromium/remote-debugging/windows.md).
+To learn how to set up your Windows device and connect to it from your development machine, see [Remotely debug Windows devices](../../devtools-guide-chromium/remote-debugging/windows.md).
 
-The [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) uses the same Microsoft Edge DevTools Protocol as [DevTools](../devtools-guide-chromium/overview.md) to communicate with Microsoft Edge running on the Windows 10 or later device you want to debug.  This app just prepends `/msedge/` and a process ID (`pid`) before each call to the protocol.  It supports the following HTTP endpoints.
+The [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) app uses the same Microsoft Edge DevTools Protocol as used by Microsoft Edge DevTools, to communicate with Microsoft Edge running on the Windows 10 or later device you want to debug.  This app just prepends `/msedge/` and a process ID (`pid`) before each call to the protocol.
 
-The following Reference sections are for Remote Tools for Microsoft Edge.
+The Remote Tools for Microsoft Edge app supports the following HTTP endpoints; the Reference sections below are for Remote Tools for Microsoft Edge.
 
 
 <!-- ====================================================================== -->
@@ -161,7 +156,7 @@ None.
 <!-- ====================================================================== -->
 ## /msedge/json/list
 
-Provides a candidate list of all Microsoft Edge and WebView2 Runtime processes running on the connected device (including [PWAs](../progressive-web-apps-chromium/index.md)) and all tabs or targets in each process available for debugging.
+Provides a candidate list of all Microsoft Edge and WebView2 Runtime processes running on the connected device (including PWAs) and all tabs or targets in each process available for debugging.
 
 **Parameters**
 
@@ -201,6 +196,9 @@ None.
 ]
 ```
 
+See also:
+* [Overview of Progressive Web Apps (PWAs)](../../progressive-web-apps-chromium/index.md)
+
 
 <!-- ====================================================================== -->
 ## /msedge/
@@ -273,9 +271,17 @@ None.
 JSON object which represents the available API surface for the version of the protocol that the Microsoft Edge instance that matches the provided `[pid]` is using.
 
 
+<!-- ====================================================================== -->
+## EdgeHTML DevTools Protocol
+
+With the shift in the underlying web platform of Microsoft Edge to Chromium, the [Microsoft Edge (EdgeHTML) DevTools Protocol](/archive/microsoft-edge/legacy/developer/devtools-protocol/index) won't be receiving any further updates.  Going forward, the Microsoft Edge DevTools Protocol will match the APIs of the Chrome DevTools Protocol.
+
+Any methods that were prefixed with `ms` in the [Microsoft Edge (EdgeHTML) DevTools Protocol](/archive/microsoft-edge/legacy/developer/devtools-protocol/index) are no longer supported in the Microsoft Edge DevTools Protocol.
+
+
 <!-- ====================================================================== -->
 ## See also
 
 * [Chrome DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/)
-* [Chrome DevTools Protocol (CDP)](../webview2/concepts/overview-features-apis.md#chrome-devtools-protocol-cdp) in _Overview of WebView2 APIs_
-* [Use the Chrome DevTools Protocol (CDP) in WebView2 apps](../webview2/how-to/chromium-devtools-protocol.md)
+* [Chrome DevTools Protocol (CDP)](../../webview2/concepts/overview-features-apis.md#chrome-devtools-protocol-cdp) in _Overview of WebView2 APIs_.
+* [Use the Chrome DevTools Protocol (CDP) in WebView2 apps](../../webview2/how-to/chromium-devtools-protocol.md)

microsoft-edge/index.yml

@@ -368,7 +368,7 @@ conceptualContent:
               itemType: overview
 
             - text: DevTools Protocol
-              url: ./test-and-automation/devtools-protocol.md
+              url: ./test-and-automation/devtools-protocol.md  # jump page
               itemType: how-to-guide
 
             - text: Use Playwright to automate and test in Microsoft Edge

microsoft-edge/test-and-automation/devtools-protocol.md

@@ -11,4 +11,4 @@ ms.date: 1/30/2023
 
 Use the DevTools Protocol to instrument, inspect, debug, and profile browsers, including Microsoft Edge.  By building Microsoft Edge on the Chromium open-source project, the Microsoft Edge DevTools Protocol matches the APIs of the Chrome DevTools Protocol.  For information about how Microsoft Edge uses the Chromium open-source project, see [Microsoft Edge and Chromium Open Source: Our Intent](https://github.com/MicrosoftEdge/MSEdge/blob/master/README.md).
 
-See [Microsoft Edge DevTools Protocol overview](../devtools-protocol-chromium/index.md).
+See [Microsoft Edge DevTools Protocol](../devtools/protocol/index.md).

microsoft-edge/toc.yml

@@ -983,7 +983,7 @@
           displayName: IE mode
 # DevTools Protocol -----------------------------------------------------------
         - name: Microsoft Edge DevTools Protocol
-          href: devtools-protocol-chromium/index.md
+          href: ./devtools/protocol/index.md
           displayName: DevTools Protocol
 # Contact ---------------------------------------------------------------------
         - name: Contact the Microsoft Edge DevTools team

microsoft-edge/webview2/how-to/chromium-devtools-protocol.md

@@ -179,7 +179,6 @@ The Chrome DevTools Protocol is maintained by the open source Chromium project,
 
 <!-- ====================================================================== -->
 ## See also
-
-* [Microsoft Edge DevTools Protocol overview](../../devtools-protocol-chromium/index.md)
+* [Microsoft Edge DevTools Protocol](../../devtools/protocol/index.md)
 * [WebView2Samples repo](https://github.com/MicrosoftEdge/WebView2Samples)
 * [Chrome DevTools Protocol (CDP)](../concepts/overview-features-apis.md#chrome-devtools-protocol-cdp) in _Overview of WebView2 APIs_