wundergraph · mintlify · Apr 11, 2025 · Apr 16, 2025 · Apr 16, 2025 · Apr 16, 2025
diff --git a/docs/graph_pruning.png b/docs/graph_pruning.png
diff --git a/docs/images/overview_screen.png b/docs/images/overview_screen.png
diff --git a/docs/images/router/ART.png b/docs/images/router/ART.png
diff --git a/docs/images/studio/audit-logs.png b/docs/images/studio/audit-logs.png
diff --git a/docs/images/studio/check_information.png b/docs/images/studio/check_information.png
diff --git a/docs/images/studio/create_new_api_key.png b/docs/images/studio/create_new_api_key.png
diff --git a/docs/images/studio/create_webhook.png b/docs/images/studio/create_webhook.png
diff --git a/docs/images/studio/graph_pruning.png b/docs/images/studio/graph_pruning.png
diff --git a/docs/images/studio/image-28.png b/docs/images/studio/image-28.png
diff --git a/docs/images/studio/image-29.png b/docs/images/studio/image-29.png
diff --git a/docs/images/studio/image-30.png b/docs/images/studio/image-30.png
diff --git a/docs/images/studio/lint_check.png b/docs/images/studio/lint_check.png
diff --git a/docs/images/studio/metrics.png b/docs/images/studio/metrics.png
diff --git a/docs/images/studio/new_api_key.png b/docs/images/studio/new_api_key.png
diff --git a/docs/images/studio/operations_check.png b/docs/images/studio/operations_check.png
diff --git a/docs/images/studio/schema_checks.png b/docs/images/studio/schema_checks.png
diff --git a/docs/images/studio/schema_registry_cdl.png b/docs/images/studio/schema_registry_cdl.png
diff --git a/docs/images/studio/scim/generate-scim-key.png b/docs/images/studio/scim/generate-scim-key.png
diff --git a/docs/images/studio/scim/image-7.png b/docs/images/studio/scim/image-7.png
diff --git a/docs/images/studio/sso/add-claims-tab.png b/docs/images/studio/sso/add-claims-tab.png
diff --git a/docs/images/studio/sso/api-menu.png b/docs/images/studio/sso/api-menu.png
diff --git a/docs/images/studio/sso/connect-oidc-dialog.png b/docs/images/studio/sso/connect-oidc-dialog.png
diff --git a/docs/images/studio/sso/connect-oidc-success.png b/docs/images/studio/sso/connect-oidc-success.png
diff --git a/docs/images/studio/sso/connect_oidc.png b/docs/images/studio/sso/connect_oidc.png
diff --git a/docs/images/studio/sso/copy-client-credentials.png b/docs/images/studio/sso/copy-client-credentials.png
diff --git a/docs/images/studio/sso/create-app-integration.png b/docs/images/studio/sso/create-app-integration.png
diff --git a/docs/images/studio/sso/image-1.png b/docs/images/studio/sso/image-1.png
diff --git a/docs/images/studio/sso/image-10.png b/docs/images/studio/sso/image-10.png
diff --git a/docs/images/studio/sso/image-12.png b/docs/images/studio/sso/image-12.png
diff --git a/docs/images/studio/sso/image-17.png b/docs/images/studio/sso/image-17.png
diff --git a/docs/images/studio/sso/image-18.png b/docs/images/studio/sso/image-18.png
diff --git a/docs/images/studio/sso/image-2.png b/docs/images/studio/sso/image-2.png
diff --git a/docs/images/studio/sso/image-3.png b/docs/images/studio/sso/image-3.png
diff --git a/docs/images/studio/sso/image-4.png b/docs/images/studio/sso/image-4.png
diff --git a/docs/images/studio/sso/image-5.png b/docs/images/studio/sso/image-5.png
diff --git a/docs/images/studio/sso/image-6.png b/docs/images/studio/sso/image-6.png
diff --git a/docs/images/studio/sso/image-7.png b/docs/images/studio/sso/image-7.png
diff --git a/docs/images/studio/sso/image-8.png b/docs/images/studio/sso/image-8.png
diff --git a/docs/images/studio/sso/image-9.png b/docs/images/studio/sso/image-9.png
diff --git a/docs/images/studio/sso/integration-assignments.png b/docs/images/studio/sso/integration-assignments.png
diff --git a/docs/images/studio/sso/integration-name.png b/docs/images/studio/sso/integration-name.png
diff --git a/docs/images/studio/sso/map-oidc-groups.png b/docs/images/studio/sso/map-oidc-groups.png
diff --git a/docs/images/studio/sso/metadata-uri.png b/docs/images/studio/sso/metadata-uri.png
diff --git a/docs/images/studio/webhooks.png b/docs/images/studio/webhooks.png
diff --git a/docs/images/tutorial/github-integration.png b/docs/images/tutorial/github-integration.png
diff --git a/docs/router/advanced-request-tracing-art.mdx b/docs/router/advanced-request-tracing-art.mdx
@@ -6,7 +6,7 @@ icon: stars
 
 
 <Frame>
-   <img src="/images/router/image-6.png" />
+   <img src="/images/router/ART.png" />
 </Frame>
 
 <Note>

diff --git a/docs/studio/alerts-and-notifications/webhooks.mdx b/docs/studio/alerts-and-notifications/webhooks.mdx
@@ -77,12 +77,12 @@ const isVerified = verifySignature(JSON.stringify(req.body), req.headers['x-cosm
   <Step title="Navigate to the notifications page on Cosmo"/>
   <Step title="In the Webhooks tab, click on the Create button.">
 <Frame>
-  <img src="/images/studio/image-40.png" />
+  <img src="/images/studio/webhooks.png" />
 </Frame>
 </Step>
 <Step title="Provide the endpoint of the webhook, and the webhook secret for verification and then select the events you want to be notified of.">
 <Frame>
-  <img src="/images/studio/image-41.png" />
+  <img src="/images/studio/create_webhook.png" />
 </Frame>
 </Step>
 <Step title="Lastly, click on the Create button."/>

diff --git a/docs/studio/analytics/metrics.mdx b/docs/studio/analytics/metrics.mdx
@@ -5,7 +5,7 @@ description: "Metrics give a general overview of the performance of your federat
 ---
 
 <Frame caption="The Metrics overview">
-    <img src="/images/studio/image-27.png" />
+    <img src="/images/studio/metrics.png" />
 </Frame>
 
 ### Request rate

diff --git a/docs/studio/api-keys.mdx b/docs/studio/api-keys.mdx
@@ -17,7 +17,7 @@ The API keys are used to authorize the user to perform actions using [wgc](/cli/
 * Give the API key a name, select the expiry, and then click on "Generate API key".
 
 <Frame>
-    <img src="/images/studio/image-29.png" />
+    <img src="/images/studio/create_new_api_key.png" />
 </Frame>
 
 * Once the API key is generated, it will be displayed for the user to copy it.
@@ -27,5 +27,5 @@ The API keys are used to authorize the user to perform actions using [wgc](/cli/
 </Info>
 
 <Frame>
-    <img src="/images/studio/image-30.png" />
+    <img src="/images/studio/new_api_key.png" />
 </Frame>
diff --git a/docs/studio/audit-log.mdx b/docs/studio/audit-log.mdx
@@ -9,5 +9,5 @@ Audit logs are crucial for several reasons. First, they provide a detailed recor
 Navigate to your organization's page and click on "Audit Log." You will see all audit logs arranged in descending order by their creation date. Each log entry is annotated with information about who performed the action, what was done, and when it occurred. Based on the icon next to the actor, you can determine if the action was performed directly by a user or through their API key. Additionally, several events generated from the Cosmo Platform can be identified accordingly.
 
 <Frame caption="Audit Log View">
-  <img src="/images/studio/image-50.png" />
+  <img src="/images/studio/audit-logs.png" />
 </Frame>
diff --git a/docs/studio/graph-pruning.mdx b/docs/studio/graph-pruning.mdx
@@ -1,68 +1,56 @@
 ---
 title: "Graph Pruning"
 description: "**Graph Pruning Linter** helps manage the cleanliness and efficiency of your GraphQL schema by running various checks on the schema. When enabled, the lint check will be performed on every [check](https://cosmo-docs.wundergraph.com/cli/subgraph/check) operation of that namespace."
-icon: broom-wide
+icon: "broom-wide"
 ---
 
-
 <Frame>
-  <img src="/images/studio/image-52.png" />
+  ![Graph Pruning Pn](/docs/images/studio/graph_pruning.png)
 </Frame>
 
 ## Rules
 
-1. UNUSED\_FIELDS
-
-   * Identifies and lists all fields that are not being used in the schema.
-
-2. DEPRECATED\_FIELDS
-
-   * Detects fields that have been deprecated but have not yet been removed from the schema.
-
-3. REQUIRE\_DEPRECATION\_BEFORE\_DELETION
-
-   * Identifies fields that were deleted without being marked as deprecated beforehand.
+1. UNUSED_FIELDS
+   - Identifies and lists all fields that are not being used in the schema.
+2. DEPRECATED_FIELDS
+   - Detects fields that have been deprecated but have not yet been removed from the schema.
+3. REQUIRE_DEPRECATION_BEFORE_DELETION
+   - Identifies fields that were deleted without being marked as deprecated beforehand.
 
 ## Rule Configurations
 
 ### Severity Level
 
-* Error:- If any configured rules are violated, it causes the check operation to fail.
-
-* Warning:- If any configured rules are violated, they are flagged as warnings, but they don't cause the check operation to fail.
+- Error:- If any configured rules are violated, it causes the check operation to fail.
+- Warning:- If any configured rules are violated, they are flagged as warnings, but they don't cause the check operation to fail.
 
 ### Grace Period
 
 This is the time period provided to the fields modified on schema publications, allowing time before enforcing these rules during checks.
 
 ### Schema Usage Check Period (Enterprise only)
 
-* This is the time period used to check the usage of the field.
-
-* For non-enterprise customers, the value is determined by the limits imposed on the organization according to its current billing plan.
+- This is the time period used to check the usage of the field.
+- For non-enterprise customers, the value is determined by the limits imposed on the organization according to its current billing plan.
 
 ## How to configure graph pruning linter
 
 <Steps>
-<Step>
-Navigate to the Lint Policy page on Cosmo.
-</Step>
-<Step>
-Select the namespace.
-</Step>
-<Step>
-Enable the graph pruning linter.
-</Step>
-<Step>
-Configure the linter rules:
-
-  * Check the checkbox to enable each rule.
-
-  * Select the **severity level** (Warning or Error) for each rule.
-
-  * Set the **grace period** for fields that are modified upon schema publication, allowing time before enforcing these rules during checks.
-
-  * Configure the **schema usage check period** (available only for enterprise customers).
-
-</Step>
-</Steps>
+  <Step>
+    Navigate to the Lint Policy page on Cosmo.
+  </Step>
+  <Step>
+    Select the namespace.
+  </Step>
+  <Step>
+    Enable the graph pruning linter.
+  </Step>
+  <Step>
+    Configure the linter rules:
+
+    - Check the checkbox to enable each rule.
+    - Select the **severity level** (Warning or Error) for each rule.
+    - Set the **grace period** for fields that are modified upon schema publication, allowing time before enforcing these rules during checks.
+    - Configure the **schema usage check period** (available only for enterprise customers).
+  </Step>
+</Steps>
diff --git a/docs/studio/overview-page.mdx b/docs/studio/overview-page.mdx
@@ -5,7 +5,7 @@ icon: map
 ---
 
 <Frame caption="Federated Graph Overview">
-  <img src="/images/image-7.png" alt="Overview Page" />
+  <img src="/images/overview_screen.png" alt="Overview Page" />
 </Frame>
 
 ## Graph details

diff --git a/docs/studio/schema-checks.mdx b/docs/studio/schema-checks.mdx
@@ -34,7 +34,7 @@ This view lists all the checks performed, showing the timestamp of each check, t
 
 
 <Frame caption="Schema Checks View">
-  <img src="/images/studio/image-5.png" />
+  <img src="/images/studio/schema_checks.png" />
 </Frame>
 
 ### Overview
@@ -46,7 +46,7 @@ Have a glance at your check. Understand why the check succeeded or failed, and w
 </Info>
 
 <Frame>
-  <img src="/images/studio/image-6.png" />
+  <img src="/images/studio/check_information.png" />
 </Frame>
 
 #### Manual overrides
@@ -74,7 +74,7 @@ You can override certain changes as safe for future checks. Learn more by clicki
 </Info>
 
 <Frame>
-  <img src="/images/studio/image-7.png" />
+  <img src="/images/studio/operations_check.png" />
 </Frame>
 
 ### Operation Details
@@ -86,6 +86,6 @@ If you click on a specific operation, you can view all the changes that have imp
 Lists all the lint errors/warnings found in the proposed schema.
 
 <Frame>
-  <img src="/images/studio/image-8.png" />
+  <img src="/images/studio/lint_check.png" />
 </Frame>
 
diff --git a/docs/studio/schema-registry.mdx b/docs/studio/schema-registry.mdx
@@ -5,7 +5,7 @@ icon: atom
 ---
 
 <Frame caption="Schema Registry SDL view">
-  <img src="/images/studio/image-4.png" />
+  <img src="/images/studio/schema_registry_cdl.png" />
 </Frame>
 
 ## Latest Schema State

diff --git a/docs/studio/scim/okta.mdx b/docs/studio/scim/okta.mdx
@@ -76,7 +76,7 @@ Navigate to the API Keys page on WunderGraph Cosmo and click on New API Key.
 Provide the key with a name, select **Never** for **Expires,** then select  **SCIM**under **Permissions, t**hen click on **Generate API key.**
 
 <Frame>
-  <img src="/images/studio/scim/image-7.png" />
+  <img src="/images/studio/scim/generate-scim-key.png" />
 </Frame>
 </Step>
 <Step>

diff --git a/docs/studio/sso/auth0.mdx b/docs/studio/sso/auth0.mdx
@@ -34,28 +34,28 @@ description: "Setting up SSO with Auth0"
 * Click on **Connect.**
 
 <Frame>
-  <img src="/images/studio/sso/image-16.png" />
+    <img src="/images/studio/sso/connect_oidc.png" />
 </Frame>
 </Step>
 <Step>
   Give the connection a name, the **Discovery Endpoint** will be  `https://YOUR_AUTH0_DOMAIN/.well-known/openid-configuration` **,** and paste the **Client ID** and  **Client secret**copied before into the **Client ID** and  **Client Secret fields respectively,**&#x61;nd then click on **Connect.**
 
 <Frame>
-  <img src="/images/studio/sso/image-17.png" />
+  <img src="/images/studio/sso/connect-oidc-dialog.png" />
 </Frame>
 </Step>
 <Step>
  Configure the mapping between the roles in Cosmo and the user roles in Auth0. The field **Group in the provider** can be populated with the name of the role or a regex to match the user roles. Once all the mappers are configured, click on **Save**.
 
 <Frame>
-  <img src="/images/studio/sso/image-18.png" />
+  <img src="/images/studio/sso/map-oidc-groups.png" />
 </Frame>
 </Step>
 <Step>
  Copy the sign-in and sign-out redirect URIs displayed in the dialog.
 
 <Frame>
-  <img src="/images/studio/sso/image-19.png" />
+  <img src="/images/studio/sso/connect-oidc-success.png" />
 </Frame>
 </Step>
 <Step>

diff --git a/docs/studio/sso/keycloak.mdx b/docs/studio/sso/keycloak.mdx
@@ -49,28 +49,28 @@ icon: "key"
   Click on **Connect.**
 
   <Frame>
-    <img src="/images/studio/sso/image-27.png" />
+    <img src="/images/studio/sso/connect_oidc.png" />
   </Frame>
   </Step>
   <Step>
   Give the connection a name, paste the **OpenID Endpoint Configuration** copied before, into the  **Discovery Endpoint,**&#x61;nd paste the **Client ID** and  **Client secret**copied before into the **Client ID** and  **Client Secret fields respectively,**&#x61;nd then click on **Connect.**
 
   <Frame>
-    <img src="/images/studio/sso/image-28.png" />
+    <img src="/images/studio/sso/connect-oidc-dialog.png" />
   </Frame>
   </Step>
   <Step>
   Configure the mapping between the roles in Cosmo and the user groups in Keycloak. The field **Group in the provider** can be populated with the name of the group or a regex to match the user groups. Once all the mappers are configured, click on **Save**.
 
   <Frame>
-    <img src="/images/studio/sso/image-29.png" />
+    <img src="/images/studio/sso/map-oidc-groups.png" />
   </Frame>
   </Step>
   <Step>
   Copy the sign-in and sign-out redirect URIs displayed in the dialog.
 
   <Frame>
-    <img src="/images/studio/sso/image-30.png" />
+    <img src="/images/studio/sso/connect-oidc-success.png" />
   </Frame>
   </Step>
   <Step>

diff --git a/docs/studio/sso/microsoft-entra.mdx b/docs/studio/sso/microsoft-entra.mdx
@@ -63,7 +63,7 @@ Copy the **value(client secret)** and store it, as it won't be shown again.
 Navigate to the settings page on Cosmo.
 
 <Frame>
-  <img src="/images/studio/sso/image-39.png" />
+    <img src="/images/studio/sso/connect_oidc.png" />
 </Frame>
 </Step>
 <Step>

diff --git a/docs/studio/sso/okta.mdx b/docs/studio/sso/okta.mdx
@@ -15,44 +15,44 @@ icon: "user-shield"
     Click on **Create App Integration**.
   </Step>
   <Step>
-    A dialog appears, select OIDC - OpenID Connect as the sign-in method.
+    A dialog appears, select **OIDC - OpenID Connect** as the sign-in method.
   </Step>
   <Step>
-    Now select the type of application and click on **Next.**
+    For the application type, select **Web Application** and click on **Next**.
 
 <Frame>
-  <img src="/images/studio/sso/image-1.png" />
+  <img src="/images/studio/sso/create-app-integration.png" />
 </Frame>
 </Step>
 <Step>
-  Now give the app a name and scroll down to **Assignments.**
+  Now give the app a name.
 
 <Frame>
-  <img src="/images/studio/sso/image-2.png" />
+  <img src="/images/studio/sso/integration-name.png" />
 </Frame>
 </Step>
 <Step>
   For **Grant Type,** keep the defaults.
 </Step>
 <Step>
-  For **Assignments,** select one of the options based on your choice and then click on **Save.**
+  Scroll down to the **Assignments** section and select one of the options based on your choice and then click on **Save.**
 
   <Frame>
-    <img src="/images/studio/sso/image-3.png" />
+    <img src="/images/studio/sso/integration-assignments.png" />
   </Frame>
 </Step>
 <Step>
   Copy the **Client ID** and **Client Secret.**
 
   <Frame>
-    <img src="/images/studio/sso/image-4.png" />
+    <img src="/images/studio/sso/copy-client-credentials.png" />
   </Frame>
 </Step>
 <Step>
-  Navigate to Security -> API.
+  Navigate to **Security** -> **API**.
 
   <Frame>
-    <img src="/images/studio/sso/image-5.png" />
+    <img src="/images/studio/sso/api-menu.png" />
   </Frame>
 </Step>
 <Step>
@@ -62,36 +62,36 @@ icon: "user-shield"
   Copy the **Metadata URI.**
 
   <Frame>
-    <img src="/images/studio/sso/image-6.png" />
+    <img src="/images/studio/sso/metadata-uri.png" />
   </Frame>
 </Step>
 
 <Step>
   Navigate to the settings page on Cosmo.
 
   <Frame>
-    <img src="/images/studio/sso/image-7.png" />
+    <img src="/images/studio/sso/connect_oidc.png" />
   </Frame>
 </Step>
 <Step>
   Give the connection a name, paste the **Metadata URI** copied before, into the  **Discovery Endpoint,**&#x61;nd paste the **Client ID** and  **Client secret**copied before into the **Client ID** and  **Client Secret fields respectively,**&#x61;nd then click on **Connect.**
 
   <Frame>
-    <img src="/images/studio/sso/image-8.png" />
+    <img src="/images/studio/sso/connect-oidc-dialog.png" />
   </Frame>
 </Step>
 <Step>
   Configure the mapping between the roles in Cosmo and the user groups in Okta. The field **Group in the provider** can be populated with the name of the group or a regex to match the user groups. Once all the mappers are configured, click on **Save**.
 
   <Frame>
-    <img src="/images/studio/sso/image-9.png" />
+    <img src="/images/studio/sso/map-oidc-groups.png" />
   </Frame>
 </Step>
 <Step>
   Copy the sign-in and sign-out redirect URIs displayed in the dialog.
 
   <Frame>
-    <img src="/images/studio/sso/image-10.png" />
+    <img src="/images/studio/sso/connect-oidc-success.png" />
   </Frame>
 </Step>
 <Step>
@@ -106,7 +106,7 @@ icon: "user-shield"
   Navigate to Security-> API, and click on the **default** auth server. Navigate to the **claims** tab and then click on **Add Claim.**
 
   <Frame>
-    <img src="/images/studio/sso/image-12.png" />
+    <img src="/images/studio/sso/add-claims-tab.png" />
   </Frame>
 </Step>
 <Step>
-Original file line number
+Diff line change
@@ Expand Up / @@ -6,7 +6,7 @@ icon: stars @@
     <Frame>
-       <img src="/images/router/image-6.png" />
+       <img src="/images/router/ART.png" />
     </Frame>
     <Note>
@@ Expand Down @@