Add SDK examples content

Author: ethanpalm

api-playground/customization/adding-sdk-examples.mdx

@@ -0,0 +1,49 @@
+---
+title: "Adding SDK examples"
+description: ""
+---
+
+If your users interact with your API using an SDK rather than directly through a network request, you can use the `x-codeSamples` extension to add code samples to your OpenAPI document and Mintlify will display them in your OpenAPI pages.
+
+This property can be added within any request method and has the following schema.
+
+<ParamField body="lang" type="string" required>
+  The language of the code sample.
+</ParamField>
+
+<ParamField body="label" type="string">
+  The label for the sample. This is useful when providing multiple examples for a single endpoint.
+</ParamField>
+
+<ParamField body="source" type="string" required>
+  The source code of the sample.
+</ParamField>
+
+Here is an example of some code samples for a plant tracking app, which has both a Bash CLI tool and a JavaScript SDK.
+
+```yaml
+paths:
+  /plants:
+    get:
+      ...
+      x-codeSamples:
+        - lang: bash
+          label: List all unwatered plants
+          source: |
+            planter list -u
+        - lang: javascript
+          label: List all unwatered plants
+          source: |
+            const planter = require('planter');
+            planter.list({ unwatered: true });
+        - lang: bash
+          label: List all potted plants
+          source: |
+            planter list -p
+        - lang: javascript
+          label: List all potted plants
+          source: |
+            const planter = require('planter');
+            planter.list({ potted: true });
+```
+

api-playground/customization/managing-page-visibility.mdx

@@ -6,11 +6,11 @@ description: "Control which endpoints from your OpenAPI specification appear in
 
 You can control exactly which parts of your OpenAPI specification get published and how they're organized. Hiding pages can be useful when you're documenting internal APIs, beta features, or other endpoints that shouldn't appear in navigation.
 
-If your pages are autogenerated from an OpenAPI document, you can control which endpoints get published and how they appear in your documentation with the `x-hidden` and `x-excluded` properties.
+If your pages are autogenerated from an OpenAPI document, you can control which endpoints get published and how they appear in your documentation with the `x-hidden` and `x-excluded` extensions.
 
 ## `x-hidden`
 
-The `x-hidden` property creates a page for an endpoint, but hides it from navigation. The page is only accessible by navigating directly its URL.
+The `x-hidden` extension creates a page for an endpoint, but hides it from navigation. The page is only accessible by navigating directly its URL.
 
 Common use cases for `x-hidden` are:
 
@@ -21,7 +21,7 @@ Common use cases for `x-hidden` are:
 ## `x-excluded`
 
 
-The `x-excluded` property completely excludes an endpoint from your documentation.
+The `x-excluded` extension completely excludes an endpoint from your documentation.
 
 Common use cases for `x-excluded` are:
 
@@ -31,7 +31,7 @@ Common use cases for `x-excluded` are:
 
 ## Implementation 
 
-Add the `x-hidden` or `x-excluded` property under the HTTP method in your OpenAPI specification.
+Add the `x-hidden` or `x-excluded` extension under the HTTP method in your OpenAPI specification.
 
 Here are examples of how to use each property in an OpenAPI schema document for an endpoint and a webhook path: