Included truncation comments for improved readability in markdown files.

docs/my-website/blog/anthropic_opus_4_5_and_advanced_features/index.md

@@ -16,6 +16,8 @@ import TabItem from '@theme/TabItem';
 
 This guide covers Anthropic's latest model (Claude Opus 4.5) and its advanced features now available in LiteLLM: Tool Search, Programmatic Tool Calling, Tool Input Examples, and the Effort Parameter.
 
+{/* truncate */}
+
 ---
 
 | Feature | Supported Models |

docs/my-website/blog/claude_opus_4_6/index.md

@@ -16,6 +16,8 @@ import TabItem from '@theme/TabItem';
 
 LiteLLM now supports Claude Opus 4.6 on Day 0. Use it across Anthropic, Azure, Vertex AI, and Bedrock through the LiteLLM AI Gateway.
 
+{/* truncate */}
+
 ## Docker Image
 
 ```bash

docs/my-website/blog/claude_sonnet_4_6/index.md

@@ -15,6 +15,8 @@ import TabItem from '@theme/TabItem';
 
 LiteLLM now supports Claude Sonnet 4.6 on Day 0. Use it across Anthropic, Azure, Vertex AI, and Bedrock through the LiteLLM AI Gateway.
 
+{/* truncate */}
+
 ## Docker Image
 
 ```bash

docs/my-website/blog/gemin_3.1/index.md

@@ -19,6 +19,8 @@ import TabItem from '@theme/TabItem';
 
 LiteLLM now supports `gemini-3.1-pro-preview` and all the new API changes along with it.
 
+{/* truncate */}
+
 ## Deploy this version
 
 <Tabs>

docs/my-website/blog/gemini_3/index.md

@@ -20,6 +20,8 @@ This guide covers common questions and best practices for using `gemini-3-pro-pr
 
 :::
 
+{/* truncate */}
+
 ## Quick Start
 
 <Tabs>

docs/my-website/blog/gemini_3_1_flash_lite/index.md

@@ -23,6 +23,8 @@ LiteLLM now supports `gemini-3.1-flash-lite-preview` with full day 0 support!
 If you only want cost tracking, you need no change in your current Litellm version. But if you want the support for new features introduced along with it like thinking levels, you will need to use v1.80.8-stable.1 or above.
 :::
 
+{/* truncate */}
+
 ## Deploy this version
 
 <Tabs>

docs/my-website/blog/gemini_3_flash/index.md

@@ -23,6 +23,8 @@ LiteLLM now supports `gemini-3-flash-preview` and all the new API changes along
 If you only want cost tracking, you need no change in your current Litellm version. But if you want the support for new features introduced along with it like thinking levels, you will need to use v1.80.8-stable.1 or above.
 :::
 
+{/* truncate */}
+
 ## Deploy this version
 
 <Tabs>

docs/my-website/blog/gemini_embedding_2_multimodal/index.md

@@ -16,6 +16,8 @@ import TabItem from '@theme/TabItem';
 
 LiteLLM now supports **multimodal embeddings** with `gemini-embedding-2-preview`—generating a single embedding from a mix of text, images, audio, video, and PDF content. Available via both the **Gemini API** (API key) and **Vertex AI** (GCP credentials).
 
+{/* truncate */}
+
 ## Supported Input Types
 
 | Modality | Supported Formats | 

docs/my-website/blog/gpt_5_3_codex/index.md

@@ -16,6 +16,8 @@ import TabItem from '@theme/TabItem';
 
 LiteLLM now supports GPT-5.3-Codex on Day 0, including support for the new assistant `phase` metadata on Responses API output items.
 
+{/* truncate */}
+
 ## Why `phase` matters for GPT-5.3-Codex
 
 `phase` appears on assistant output items and helps distinguish preamble/commentary turns from final closeout responses.

docs/my-website/blog/gpt_5_4/index.md

@@ -16,6 +16,8 @@ import TabItem from '@theme/TabItem';
 
 LiteLLM now supports fully GPT-5.4!
 
+{/* truncate */}
+
 ## Docker Image
 
 ```bash

docs/my-website/blog/httpx_cache_eviction_incident/index.md

@@ -23,6 +23,8 @@ A change to improve Redis connection pool cleanup introduced a regression that c
 
 **Impact:** Any proxy instance that hit the cache TTL (default 10 minutes) or capacity limit (200 entries) would have its httpx clients closed out from under it, causing requests to LLM providers to fail with connection errors.
 
+{/* truncate */}
+
 ---
 
 ## Background

docs/my-website/blog/litellm_observatory/index.md

@@ -19,6 +19,8 @@ As LiteLLM adoption has grown, so have expectations around reliability, performa
 
 This post introduces **LiteLLM Observatory**, a long-running release-validation system we built to catch regressions before they reach users.
 
+{/* truncate */}
+
 ---
 
 ## Why We Built the Observatory
@@ -124,4 +126,3 @@ Reliability is an ongoing investment.
 LiteLLM Observatory is one of several systems we’re building to continuously raise the bar on release quality and operational safety. As LiteLLM evolves, so will our validation tooling, informed by real-world usage and lessons learned.
 
 We’ll continue to share those improvements openly as we go.
-

docs/my-website/blog/minimax_m2_5/index.md

@@ -16,6 +16,8 @@ import TabItem from '@theme/TabItem';
 
 LiteLLM now supports MiniMax-M2.5 on Day 0. Use it across OpenAI-compatible and Anthropic-compatible APIs through the LiteLLM AI Gateway.
 
+{/* truncate */}
+
 ## Supported Models
 
 LiteLLM supports the following MiniMax models:

docs/my-website/blog/realtime_webrtc_http_endpoints/index.md

@@ -15,6 +15,8 @@ import WebRTCTester from '@site/src/components/WebRTCTester';
 
 Connect to the Realtime API via WebRTC from browser/mobile clients. LiteLLM handles auth and key management.
 
+{/* truncate */}
+
 ## How it works
 
 ![WebRTC flow: Browser, LiteLLM Proxy, and OpenAI/Azure](../../img/webrtc_flow.png)
@@ -107,4 +109,3 @@ A: Set the correct `api_version` in `litellm_params` (or via the `AZURE_API_VERS
 
 **Q: What if I get no audio?**  
 A: Make sure you grant microphone permission, ensure `pc.ontrack` assigns the audio element with `autoplay` enabled, check your network/firewall for WebRTC traffic, and inspect the browser console for ICE or SDP errors.
-

docs/my-website/blog/sub_millisecond_proxy_overhead/index.md

@@ -23,6 +23,8 @@ Proxy overhead refers to the latency introduced by LiteLLM itself, independent o
 
 To measure it, we run the same workload directly against the provider and through LiteLLM at identical QPS (for example, 1,000 QPS) and compare the latency delta. To reduce noise, the load generator, LiteLLM, and a mock LLM endpoint all run on the same machine, ensuring the difference reflects proxy overhead rather than network latency.
 
+{/* truncate */}
+
 ---
 
 ## Where We're Coming From

docs/my-website/blog/video_characters_litellm/index.md

@@ -13,6 +13,8 @@ hide_table_of_contents: false
 
 LiteLLM now supoports videos character, edit and extension apis.
 
+{/* truncate */}
+
 ## What's New
 
 Four new endpoints for video character operations:
@@ -116,4 +118,4 @@ Router knows exactly which deployment to use
 **Behind the scenes:**
 - Character ID format: `character_<base64_encoded_metadata>`
 - Metadata includes: provider, model_id, original_character_id
-- Transparent to you - just use the ID, LiteLLM handles routing
+- Transparent to you - just use the ID, LiteLLM handles routing