[docs] platform core concept revamp and overview update (#3664)

2025-10-26 15:15:13 +05:30
parent 61faf71064
commit 2c18355dd2
19 changed files with 595 additions and 318 deletions
@@ -15,6 +15,7 @@ Operation guides focus on a single action (add, search, update, delete). Show th
 - Lead with a two-sentence promise (problem → outcome), followed by an `<Info>` prerequisites block and optional `<Warning>` for hazards (overwrites, rate limits).
 - Include a “When to pick this” bullet list (≤3 items) so readers confirm they’re in the right doc.
 - Use Tabs with Python and TypeScript examples. If only one SDK exists, add a `<Note>` stating that explicitly.
+- When migrating legacy guides, keep existing code paths and notes—slot them into these sections instead of replacing them unless behavior changed.
 - Provide `<Info icon="check">` verification after each critical step; call out the most common error with a `<Warning>` close to where it can occur.
 - End with exactly two CTA cards: left = conceptual depth, right = applied example/cookbook.