Small improvements based on feedback (#7142)

This PR restructures the sidebar for a better reader experience and adds
a note to the CORS docs to ensure folks don't get caught up when
specifying origins as strings. :)

Author: rkoron007

docs/source/config.json

@@ -1,7 +1,10 @@
 {
   "title": "Apollo Server",
   "version": "v4",
-  "algoliaFilters": ["docset:apollo-server", ["docset:apollo-client", "docset:federation"]],
+  "algoliaFilters": [
+    "docset:apollo-server",
+    ["docset:apollo-client", "docset:federation"]
+  ],
   "sidebar": {
     "Introduction": "/",
     "Get started": "/getting-started",
@@ -15,14 +18,16 @@
       "Custom scalars": "/schema/custom-scalars",
       "Directives": "/schema/directives"
     },
-    "Fetching Data": {
+    "Resolving Operations": {
       "Resolvers": "/data/resolvers",
-      "Fetching data": "/data/fetching-data",
-      "Fetching from REST": "/data/fetching-rest",
       "Error handling": "/data/errors",
       "Subscriptions": "/data/subscriptions"
     },
-    "Web frameworks": {
+    "Fetching Data": {
+      "Overview": "/data/fetching-data",
+      "REST APIs": "/data/fetching-rest"
+    },
+    "Web Frameworks": {
       "Integrations": "/integrations/integration-index",
       "Building integrations": "/integrations/building-integrations"
     },
@@ -60,18 +65,20 @@
       "@apollo/subgraph": "https://www.apollographql.com/docs/federation/api/apollo-subgraph/",
       "@apollo/gateway": "https://www.apollographql.com/docs/federation/api/apollo-gateway/"
     },
-    "Built-in Plugins": {
+    "Plugins": {
       "Overview": "/builtin-plugins",
-      "Usage reporting": "/api/plugin/usage-reporting",
-      "Schema reporting": "/api/plugin/schema-reporting",
-      "Inline trace": "/api/plugin/inline-trace",
-      "Drain HTTP server": "/api/plugin/drain-http-server",
-      "Cache control": "/api/plugin/cache-control",
-      "Landing pages": "/api/plugin/landing-pages"
-    },
-    "Custom Plugins": {
-      "Creating plugins": "/integrations/plugins",
-      "Event reference": "/integrations/plugins-event-reference"
+      "Built-in": {
+        "Usage reporting": "/api/plugin/usage-reporting",
+        "Schema reporting": "/api/plugin/schema-reporting",
+        "Inline trace": "/api/plugin/inline-trace",
+        "Drain HTTP server": "/api/plugin/drain-http-server",
+        "Cache control": "/api/plugin/cache-control",
+        "Landing pages": "/api/plugin/landing-pages"
+      },
+      "Custom": {
+        "Creating plugins": "/integrations/plugins",
+        "Event reference": "/integrations/plugins-event-reference"
+      }
     }
   }
 }

docs/source/data/fetching-data.mdx

@@ -1,9 +1,9 @@
 ---
-title: Fetching Data
+title: Fetching data
 description: Manage connections to databases and other data sources
 ---
 
-import TopLevelAwait from "../shared/top-level-await.mdx"
+import TopLevelAwait from '../shared/top-level-await.mdx';
 
 > Looking to fetch data from a REST API? Check out [Fetching from REST](./fetching-rest).
 

docs/source/security/cors.mdx

@@ -137,9 +137,9 @@ console.log(`🚀 Server ready at http://localhost:4000/graphql`);
 
 > Invoking the `cors` function with no arguments sets your server's `Access-Control-Allow-Origin` HTTP header to the wildcard value (`*`), allowing scripts on any origin to make requests. So, your server would have the same CORS behavior as `startStandaloneServer`.
 
-Using the `cors` package directly, we can configure the `Access-Control-Allow-Origin` header using the [`origin` option](https://github.com/expressjs/cors#configuration-options). The example above enables CORS requests from `https://www.your-app.example`, along with `https://studio.apollographql.com`.
+Using the `cors` package directly, we can configure the `Access-Control-Allow-Origin` header using the [`origin` option](https://github.com/expressjs/cors#configuration-options). The example above enables CORS requests from `https://www.your-app.example`, along with `https://studio.apollographql.com`. If you use a string to specify the URL of an allowed origin, that string must match your client's URL exactly (e.g., `http://example.com` is *not* the same as `http://example.com/`).
 
-> Note: if you plan to use [Apollo Studio Explorer](https://www.apollographql.com/docs/studio/explorer/explorer/) as a GraphQL web IDE, you should include `https://studio.apollographql.com` in your list of valid origins. However, if you plan to embed the [Explorer](https://www.apollographql.com/docs/studio/explorer/embed-explorer/) or use [Apollo Sandbox](https://www.apollographql.com/docs/studio/explorer/sandbox), you *don't* need to specify Studio's URL in your CORS origins because requests will go through the page embedding Studio.
+> If you want to use [Apollo Studio Explorer](https://www.apollographql.com/docs/studio/explorer/explorer/) as a GraphQL web IDE, you should include `https://studio.apollographql.com` in your list of valid origins. However, if you plan to embed the [Explorer](https://www.apollographql.com/docs/studio/explorer/embed-explorer/) or use [Apollo Sandbox](https://www.apollographql.com/docs/studio/explorer/sandbox), you *don't* need to specify Studio's URL in your CORS origins because requests will go through the page embedding Studio.
 
 If you're using another integration of Apollo Server, you can add and configure CORS for your server using your framework's standard functionality.