Sync open source content 🐝 (from 3ffc8387f74bd2c7c97b1e7c35b854f318217d1c)

Author: beezythebot

api-design/request-body.mdx

@@ -28,7 +28,7 @@ Key components:
 
 Requests can also have a "request body", which is a payload of data being sent
 the API for processing. It is very frowned upon to use a request body for the
-HTTP method `GET`, but expected for `POST`, `PUT`, `PATCH`, and `QUERY. 
+HTTP method `GET`, but expected for `POST`, `PUT`, `PATCH`, and `QUERY`.
 
 The request body can be in a variety of formats, but the most common are JSON,
 XML, and form data.
@@ -59,68 +59,76 @@ when receiving it.
 Most of you will interact with APIs using a programming language, and the code
 to send a request will look something like this:
 
-<CodeWithTabs>
-    ```typescript !!tabs main.js
-    import axios from 'axios';
-
-    const response = await axios.post('https://api.example.org/places', {
+<CodeWithTabs
+  tabs={[
+    {
+      label: "main.js",
+      language: "typescript",
+      code: ` import axios from 'axios';
+
+  const response = await axios.post('https://api.example.org/places', {
+    name: 'High Wood',
+    lat: 50.464569783,
+    lon: -4.486597585,
+  });`,
+    },
+    {
+      label: "main.py",
+      language: "python",
+      code: `  import json
+  import requests
+
+  headers = {
+      'Content-Type': 'application/json',
+  }
+  payload = {
+      'name': 'High Wood',
+      'lat': 50.464569783,
+      'lon': -4.486597585,
+  }
+  req = requests.post(
+    'https://api.example.org/places',
+    data=json.dumps(payload),
+    headers=headers
+  )`,
+    },
+    {
+      label: "main.php",
+      language: "php",
+      code: `$client = new Guzzle\\Http\\Client('https://api.example.org');
+
+  $headers = [
+      'Content-Type' => 'application/json',
+  ];
+  $payload = [
+      'name' => 'High Wood',
+      'lat' => 50.464569783,
+      'lon' => -4.486597585,
+  ];
+  $req = $client->post('/places', [
+    'headers' => $headers,
+    'json' => $payload,
+  ]);`,
+    },
+    {
+      label: "main.rb",
+      language: "ruby",
+      code: `conn = Faraday.new(
+    url: 'https://api.example.org',
+    headers: { 'Content-Type' => 'application/json' }
+  )
+
+  response = conn.post('/places') do |req|
+    req.body = {
       name: 'High Wood',
       lat: 50.464569783,
       lon: -4.486597585,
-    });
-    ```
-
-    ```python !!tabs main.py
-    import json
-    import requests
-
-    headers = {
-        'Content-Type': 'application/json',
-    }
-    payload = {
-        'name': 'High Wood',
-        'lat': 50.464569783,
-        'lon': -4.486597585,
-    }
-    req = requests.post(
-      'https://api.example.org/places',
-      data=json.dumps(payload),
-      headers=headers
-    )
-    ```
-
-    ```php !!tabs main.php
-    $client = new Guzzle\Http\Client('https://api.example.org');
-
-    $headers = [
-        'Content-Type' => 'application/json',
-    ];
-    $payload = [
-        'name' => 'High Wood',
-        'lat' => 50.464569783,
-        'lon' => -4.486597585,
-    ];
-    $req = $client->post('/places', [
-      'headers' => $headers,
-      'json' => $payload,
-    ]);
-    ```
-
-    ```ruby !!tabs main.rb
-    conn = Faraday.new(
-      url: 'https://api.example.org',
-      headers: { 'Content-Type' => 'application/json' }
-    )
-
-    response = conn.post('/places') do |req|
-      req.body = {
-        name: 'High Wood',
-        lat: 50.464569783,
-        lon: -4.486597585,
-      }.to_json
-    end
-    ```
-</CodeWithTabs>
+    }.to_json
+  end`,
+}
+
+]}
+/>
 
 HTTP tooling is essentially the same thing no matter the language. It's all
 about URLs, methods, body, and headers. This makes REST API design a lot easier,
@@ -206,13 +214,12 @@ More on this in the [API Responses](/api-design/responses) guide.
 ### 2. Do not use request bodies for DELETE requests
 
 Some API designers use a request body for a DELETE request to capture more
-information about the deletion of a resource. 
+information about the deletion of a resource.
 
 Doing so is recommended against in both [RFC9110: HTTP
 Semantics](https://www.rfc-editor.org/rfc/rfc9110.html#name-delete) which states
 the semantics are undefined, and is warned against further in the OpenAPI
-specification. Some tooling will support it some wont. 
-
+specification. Some tooling will support it some wont.
 
 ```http
 DELETE /drinks/1 HTTP/1.1
@@ -267,4 +274,4 @@ This way, the user always knows what to expect in the request body, and you can
 validate the request body more easily. If the user doesn't send a renewal date,
 you can just use the current date as the default value. This is a lot easier to
 understand and work with than having to check if the request body is present or
-not, and then check if the renewal date is present or not. 
+not, and then check if the renewal date is present or not.

docs/create-client-sdks.mdx

@@ -30,30 +30,35 @@ For a more UI-based experience, use the Speakeasy app:
 
 After signing up, install the Speakeasy CLI using one of the following methods:
 
-<CodeWithTabs>
-
-```bash !!tabs Homebrew
-# Homebrew (macOS)
-brew install speakeasy-api/tap/speakeasy
-```
-
-```bash !!tabs Script
-# Script Installation (macOS and Linux)
-curl -fsSL https://go.speakeasy.com/cli-install.sh | sh
-```
-
-```bash !!tabs Winget
-# Windows Installation
+<CodeWithTabs
+  tabs={[
+    {
+      label: "Homebrew",
+      language: "bash",
+      code: `# Homebrew (macOS)
+brew install speakeasy-api/tap/speakeasy`,
+    },
+    {
+      label: "Script",
+      language: "bash",
+      code: `# Script Installation (macOS and Linux)
+curl -fsSL https://go.speakeasy.com/cli-install.sh | sh`,
+    },
+    {
+      label: "Winget",
+      language: "bash",
+      code: `# Windows Installation
 # Using winget:
-winget install speakeasy
-```
-
-```bash !!tabs Chocolatey
-# Using Chocolatey:
-choco install speakeasy
-```
-
-</CodeWithTabs>
+winget install speakeasy`,
+    },
+    {
+      label: "Chocolatey",
+      language: "bash",
+      code: `# Using Chocolatey:
+choco install speakeasy`,
+    },
+  ]}
+/>
 
 For manual installation, download the latest release from the [releases page](https://github.com/speakeasy-api/speakeasy/releases), extract the binary, and add it to the system path.
 
@@ -75,7 +80,7 @@ If you've not previously signed up for an account, you will be prompted to creat
 
 New accounts start with a 14 day free trial of Speakeasy's business tier, to enable users to try out every SDK generation feature. At the end of the trial, accounts will revert to the free tier. No credit card is required.
 
-Free accounts can continue to generate one SDK with up to 50 API methods free of charge. Please refer to the pricing page for update information on each [pricing tier](https://www.speakeasy.com/pricing). 
+Free accounts can continue to generate one SDK with up to 50 API methods free of charge. Please refer to the pricing page for update information on each [pricing tier](https://www.speakeasy.com/pricing).
 
 ### Upload an OpenAPI document
 
@@ -114,7 +119,8 @@ Provide either a link to a remote hosted OpenAPI document, or a relative path to
 ### Select artifact type
 
 After configuring the OpenAPI document, the next step prompt is to choose the type of artifact being generated: SDK or MCP. Select SDK, and a prompt will appear to choose the target language:
-Choosing Terraform will default you back to the CLI native onboarding. [Editor support for Terraform  previews](https://roadmap.speakeasy.com/roadmap?id=a8164ebf-55e1-4376-b42e-4e040c085586) coming soon.
+Choosing Terraform will default you back to the CLI native onboarding. [Editor support for Terraform previews](https://roadmap.speakeasy.com/roadmap?id=a8164ebf-55e1-4376-b42e-4e040c085586) coming soon.
+
 <Screenshot
   variant="cli"
   image={{