Merge pull request #132 from jkonrath-postman/TW-1446-Redirect-labs-d…

…ocs-to-main-LC

TW-1446 Redirect labs docs to main Learning Center

redirects.json

@@ -2,5 +2,33 @@
     {
         "from": "/postman-flows/getting-started/flows-overview/",
         "to": "https://learning.postman.com/docs/postman-flows/flows-intro/flows-overview/"
+    },
+    {
+        "from": "/postman-api-client/graphql-client/graphql-client-overview/",
+        "to": "https://learning.postman.com/docs/sending-requests/graphql/graphql-overview/"
+    },
+    {
+        "from": "/postman-api-client/graphql-client/graphql-request-interface/",
+        "to": "https://learning.postman.com/docs/sending-requests/graphql/graphql-client-interface/"
+    },
+    {
+        "from": "/postman-api-client/graphql-client/first-graphql-request/",
+        "to": "https://learning.postman.com/docs/sending-requests/graphql/graphql-client-first-request/"
+    },
+    {
+        "from": "/postman-api-client/websocket-client/websocket-client-overview/",
+        "to": "https://learning.postman.com/docs/sending-requests/websocket/websocket/"
+    },
+    {
+        "from": "/postman-api-client/mqtt-client/mqtt-client-overview/",
+        "to": "https://learning.postman.com/docs/sending-requests/mqtt-client/mqtt-client-overview/"
+    },
+    {
+        "from": "/postman-api-client/mqtt-client/mqtt-request-interface/",
+        "to": "https://learning.postman.com/docs/sending-requests/mqtt-client/mqtt-request-interface/"
+    },
+    {
+        "from": "/postman-api-client/mqtt-client/first-mqtt-request/",
+        "to": "https://learning.postman.com/docs/sending-requests/mqtt-client/first-mqtt-request/"
     }
 ]

src/components/LeftNav/LeftNavItems.jsx

@@ -45,61 +45,30 @@ export const leftNavItems = [
   {
     name: "GraphQL Client",
     parentSlug: "graphql-client",
-    url: "/postman-api-client/graphql-client/graphql-client-overview/",
-    caret: true,
-    subMenuItems1: [
-      {
-        name: "GraphQL overview",
-        url: "/postman-api-client/graphql-client/graphql-client-overview/"
-      },
-      {
-        name: "Using GraphQL request interface",
-        url: "/postman-api-client/graphql-client/graphql-request-interface/"
-      },
-      {
-        name: "Making your first GraphQL query",
-        url: "/postman-api-client/graphql-client/first-graphql-request/"
-      },
-    ],
+    url: "https://learning.postman.com/docs/sending-requests/graphql/graphql-overview/",
+    caret: false,
+    subMenuItems1: []
   },
   {
     name: "gRPC Client",
     parentSlug: "grpc-client",
     url: "https://learning.postman.com/docs/sending-requests/grpc/grpc-client-overview/",
     subMenuItems1: [],
-    caret: false,
+    caret: false
   },
   {
     name: 'WebSocket Client',
     parentSlug: 'websocket-client',
-    url: '/postman-api-client/websocket-client/websocket-client-overview/',
-    caret: true,
-    subMenuItems1: [
-      {
-        name: 'Using WebSocket requests',
-        url: '/postman-api-client/websocket-client/websocket-client-overview/',
-      },             
-    ],
+    url: 'https://learning.postman.com/docs/sending-requests/websocket/websocket/',
+    caret: false,
+    subMenuItems1: []
   },
   {
     name: "MQTT Client",
     parentSlug: "mqtt-client",
-    url: "/postman-api-client/mqtt-client/mqtt-client-overview/",
-    caret: true,
-    subMenuItems1: [
-      {
-        name: "MQTT overview",
-        url: "/postman-api-client/mqtt-client/mqtt-client-overview/"
-      },
-      {
-        name: "Using MQTT request interface",
-        url: "/postman-api-client/mqtt-client/mqtt-request-interface/"
-      },
-      {
-        name: "Creating your first MQTT request",
-        url: "/postman-api-client/mqtt-client/first-mqtt-request/"
-      },
-    ],
+    url: "https://learning.postman.com/labs/postman-api-client/mqtt-client/mqtt-client-overview/",
+    caret: false,
+    subMenuItems1: [],
   }
 ];
 

src/pages/labs-overview.md

@@ -3,7 +3,7 @@ title: "Welcome to Labs!"
 order: 1
 page_id: "introduction-to-labs"
 warning: false
-updated: 2022-07-07
+updated: 2023-10-19
 contextual_links:
   - type: section
     name: "Prerequisites"
@@ -30,7 +30,7 @@ contextual_links:
     name: "WebSockets"
   - type: link
     name: "Using WebSocket Requests"
-    url: "/postman-api-client/websocket-client/websocket-client-overview/"
+    url: "https://learning.postman.com/docs/sending-requests/websocket/websocket/"
   - type: link
     name: "Github Issues"
     url: "https://github.com/postmanlabs/postman-app-support/issues"
@@ -46,13 +46,13 @@ Flows is a visual tool to create API workflows. You can use Flows to chain reque
 
 ## API Client
 
-The API Client team has diligently been working on supporting more protocols within Postman. We started out by addressing WebSockets (and Socket.IO) and continued on with gRPC. We will continue to support and evolve each of these protocols. GraphQL is our next target. If there are other protocols that you think we should address, please check out the [GitHub Issues](https://github.com/postmanlabs/postman-app-support/issues) discussions.
+The API Client team has diligently been working on supporting more protocols within Postman. We started out by addressing WebSockets (and Socket.IO) and continued on with gRPC. We will continue to support and evolve each of these protocols. If there are other protocols that you think we should address, please check out the [GitHub Issues](https://github.com/postmanlabs/postman-app-support/issues) discussions.
 
 ### GraphQL
 
-APIs made with GraphQL allow clients to ask the server for exactly the data they need. This is enabled by a powerful query interface and a runtime to execute those queries making it easier for developers to quickly explore and experiment with the client’s functionalities. Contrary to REST, which makes your chunks of data available on multiple endpoints, GraphQL makes working with data simpler and faster with a single endpoint. Plus, GraphQL is schema driven, which means more transparency in terms of API functionality and lower dependency between teams building the client and the server. So, a client can introspect the schema from the server to get an idea about the available data fields, send queries specifying fields to retrieve or manipulate the stored data. The server does exactly what was asked from it and returns only the data requested in the query. Combining these features, GraphQL provides users with a flexible, fast and predictable API experience, making it one of the most popular API technology.
+APIs made with GraphQL allow clients to ask the server for exactly the data they need. This is enabled by a powerful query interface and a runtime to execute those queries making it easier for developers to quickly explore and experiment with the client’s functionalities. Contrary to REST, which makes your chunks of data available on multiple endpoints, GraphQL makes working with data simpler and faster with a single endpoint. Plus, GraphQL is schema driven, which means more transparency in terms of API functionality and lower dependency between teams building the client and the server. A client can introspect the schema from the server to get an idea about the available data fields, send queries specifying fields to retrieve or manipulate the stored data. The server does exactly what was asked from it and returns only the data requested in the query. Combining these features, GraphQL provides users with a flexible, fast, and predictable API experience, making it one of the most popular API technology.
 
-[Read more here...](/postman-api-client/graphql-client/graphql-client-overview)
+[Read more here...](https://learning.postman.com/docs/sending-requests/graphql/graphql-overview/)
 
 ### gRPC
 
@@ -64,4 +64,4 @@ gRPC is a schema-driven Remote Procedure Call (RPC) framework often used to enab
 
 The WebSocket protocol provides a way to exchange data between a client and server over a persistent connection. The data can be passed in both directions with low latency and overhead, and without breaking the connection. WebSockets provide a bidirectional, full-duplex communications channel that operates over HTTP through a single TCP socket connection. This means the server can independently send data to the client without the client having to request it, and vice versa.
 
-[Read more here...](/postman-api-client/websocket-client/websocket-client-overview/)
+[Read more here...](https://learning.postman.com/docs/sending-requests/websocket/websocket/)