docs: add connectors reference/link (#6697)

docs/source/reference/router/configuration.mdx

@@ -865,6 +865,10 @@ To configure the shape of traffic between clients, routers, and subgraphs, see [
 
 See [Configuring CORS in the router](/router/configuration/cors).
 
+### Connectors support
+
+See [Working with Router](/graphos/schema-design/connectors/router) in the Apollo Connectors documentation.
+
 ### Defer support
 
 See [router support for `@defer`](/router/executing-operations/defer-support/#disabling-defer).

docs/source/routing/about-router.mdx

@@ -22,6 +22,13 @@ As the runtime of the [GraphOS platform](/graphos/get-started/concepts/graphos),
 
 Unlike API gateways that offer capabilities to manage API endpoints, the router isn't based on URLs or REST endpoints. Rather, the router is a GraphQL-native solution for handling client APIs.
 
+### Enables Apollo Connectors
+
+Apollo Connectors are a core part of the router, enabling API orchestration with REST APIs.
+
+<img src='../../img/connectors/connector.svg' class="dark:hidden"/>
+<img src='../../img/connectors/connector-dark.svg' class="hidden dark:block"/>
+
 ### Subgraph query planner
 
 Whenever your router receives an incoming GraphQL operation, it needs to figure out how to use your subgraphs to populate data for each of that operation's fields. To do this, the router generates a _query plan_:
@@ -42,6 +49,7 @@ You can use the following tools for inspecting query plans:
 
 The GraphOS Router is the gateway and entry point to a federated supergraph. Clients send GraphQL operations to your router's public endpoint instead of directly to your APIs.
 
+
 ## GraphOS Router deployment types
 
 As the entry point to your supergraph, a GraphOS Router must be able to process the expected load of client operations. The scalability and performance of a router, or a fleet or router instances, can be influenced by their deployment infrastructure.