Document deep anchor support for View component

components/view.mdx

@@ -11,7 +11,7 @@
 </Tip>
 
 <View title="JavaScript" icon="js">
   This content is only visible when JavaScript is selected.
 
   ```javascript
   console.log("Hello from JavaScript!");
@@ -19,7 +19,7 @@
 </View>
 
 <View title="Python" icon="python">
   This content is only visible when Python is selected.
 
   ```python
   print("Hello from Python!")
@@ -38,7 +38,7 @@
 </View>
 
 <View title="Python" icon="python">
   This content is only visible when Python is selected.
 
   ```python
   print("Hello from Python!")
@@ -52,6 +52,22 @@
 
 If you have different heading structures in each view, users only see the headings that are relevant to their selected language or framework.
 
+## Deep anchor links
+
+Each `View` automatically generates an anchor ID from its title, so you can link directly to a specific view. When a user visits a URL with a view's anchor hash, that view activates automatically.
+
+```text
+https://your-docs.com/page-with-views#python
+```
+
+You can also link to headings, accordions, or other anchored elements inside a view. The correct view activates and scrolls to the target element.
+
+```text
+https://your-docs.com/page-with-views#install-the-sdk
+```
+
+When a user switches views using the dropdown, the URL hash updates to match the selected view, preserving any existing query parameters. This makes view selections shareable.
+
 ## Properties
 
 <ResponseField name="title" type="string" required>

guides/linking.mdx

@@ -84,6 +84,18 @@
 
 This accordion is reachable at `#install` instead of the auto-generated `#installation-steps`. See [Accordions](/components/accordions) for more.
 
+### View deep links
+
+Pages that use the [View component](/components/view) support deep linking to a specific view or to elements inside a view. Each view generates an anchor ID from its title, so `#python` activates the view titled "Python".
+
+You can also link to a heading or accordion inside a view. The correct view activates and the page scrolls to the target element:
+
+```text
+https://your-docs.com/page-with-views#install-the-sdk
+```
+
+When users switch views using the dropdown, the URL hash updates automatically, making view selections shareable. See [View](/components/view#deep-anchor-links) for more details.
+
 ### API playground deep links
 
 To open the API playground in a link, append `?playground=open` to any endpoint page URL:
@@ -125,7 +137,7 @@
 
 ### Link prerequisites explicitly
 
 When a page assumes prior steps, link to them at the top rather than assuming users will find them:
 
 ```mdx
 ## Prerequisites
@@ -139,7 +151,7 @@
 
 ### Build topic clusters
 
 Link related content together to help users—and search engines—understand how your documentation is organized:
 
 ```mdx
 ## Related topics
@@ -196,7 +208,7 @@
 </Accordion>
 
 <Accordion title="What happens to bookmarked links when I reorganize my documentation?">
 Without redirects, bookmarked and shared links become 404 errors. Set up redirects in your `docs.json` whenever you move or rename a page. Redirects are cheap to add and prevent a poor user experience for anyone who linked to your documentation from an external source—blog posts, Stack Overflow answers, internal wikis.
 </Accordion>
 
 <Accordion title="How many internal links should a page have?">