Guide pages should not use APIRef sidebar (#35327)

* Guide pages should not use APIRef sidebar * Update files/en-us/web/api/media_capabilities_api/using_the_media_capabilities_api/index.md
mdn · Sep 23, 2024 · b07efa1 · b07efa1
1 parent a66fcac
commit b07efa1
Show file tree

Hide file tree

Showing 10 changed files with 10 additions and 10 deletions.
diff --git a/files/en-us/web/api/css_object_model/css_declaration/index.md b/files/en-us/web/api/css_object_model/css_declaration/index.md
@@ -5,7 +5,7 @@ page-type: guide
 spec-urls: https://drafts.csswg.org/cssom/#css-declarations
 ---
 
-{{ APIRef("CSSOM") }}
+{{DefaultAPISidebar("CSSOM")}}
 
 A **CSS declaration** is an abstract concept not exposed as an object in the DOM. It represents a CSS property and value pairing.
 

diff --git a/files/en-us/web/api/css_object_model/css_declaration_block/index.md b/files/en-us/web/api/css_object_model/css_declaration_block/index.md
@@ -5,7 +5,7 @@ page-type: guide
 spec-urls: https://drafts.csswg.org/cssom/#css-declaration-blocks
 ---
 
-{{ APIRef("CSSOM") }}
+{{DefaultAPISidebar("CSSOM")}}
 
 A **CSS declaration block** is an ordered collection of CSS properties and values. It is represented in the DOM as a {{domxref("CSSStyleDeclaration")}}.
 

diff --git a/files/en-us/web/api/html_dom_api/microtask_guide/in_depth/index.md b/files/en-us/web/api/html_dom_api/microtask_guide/in_depth/index.md
@@ -4,7 +4,7 @@ slug: Web/API/HTML_DOM_API/Microtask_guide/In_depth
 page-type: guide
 ---
 
-{{APIRef("HTML DOM")}}
+{{DefaultAPISidebar("HTML DOM")}}
 
 When debugging or, possibly, when trying to decide upon the best approach to solving a problem around timing and scheduling of tasks and microtasks, there are things about how the JavaScript runtime operates under the hood that may be useful to understand.
 

diff --git a/files/en-us/web/api/html_dom_api/microtask_guide/index.md b/files/en-us/web/api/html_dom_api/microtask_guide/index.md
@@ -4,7 +4,7 @@ slug: Web/API/HTML_DOM_API/Microtask_guide
 page-type: guide
 ---
 
-{{APIRef("HTML DOM")}}
+{{DefaultAPISidebar("HTML DOM")}}
 
 A **microtask** is a short function which is executed after the function or program which created it exits _and_ only if the [JavaScript execution stack](/en-US/docs/Web/JavaScript/Event_loop#stack) is empty, but before returning control to the event loop being used by the {{Glossary("user agent")}} to drive the script's execution environment.
 

diff --git a/.../en-us/web/api/media_capabilities_api/using_the_media_capabilities_api/index.md b/.../en-us/web/api/media_capabilities_api/using_the_media_capabilities_api/index.md
@@ -5,7 +5,7 @@ page-type: guide
 browser-compat: api.MediaCapabilities
 ---
 
-{{APIRef("Media Capabilities API")}}
+{{DefaultAPISidebar("Media Capabilities API")}}
 
 The [Media Capabilities API](/en-US/docs/Web/API/Media_Capabilities_API) provides several key features to help you better decide how to handle media, but also to determine how well media is being handled, in real time.
 

diff --git a/files/en-us/web/api/media_capture_and_streams_api/constraints/index.md b/files/en-us/web/api/media_capture_and_streams_api/constraints/index.md
@@ -5,7 +5,7 @@ page-type: guide
 browser-compat: api.MediaDevices.getSupportedConstraints
 ---
 
-{{APIRef("Media Capture and Streams")}}
+{{DefaultAPISidebar("Media Capture and Streams")}}
 
 This article discusses the twin concepts of **constraints** and **capabilities**, as well as media settings, and includes an example we call the [Constraint Exerciser](#example_constraint_exerciser). The Constraint Exerciser lets you experiment with the results of different constraint sets being applied to the audio and video tracks coming from the computer's A/V input devices (such as its webcam and microphone).
 

diff --git a/files/en-us/web/api/webvr_api/concepts/index.md b/files/en-us/web/api/webvr_api/concepts/index.md
@@ -4,7 +4,7 @@ slug: Web/API/WebVR_API/Concepts
 page-type: guide
 ---
 
-{{APIRef("WebVR API")}}{{deprecated_header}}
+{{DefaultAPISidebar("WebVR API")}}{{deprecated_header}}
 
 > [!NOTE]
 > WebVR API is replaced by [WebXR API](/en-US/docs/Web/API/WebXR_Device_API). WebVR was never ratified as a standard, was implemented and enabled by default in very few browsers and supported a small number of devices.

diff --git a/files/en-us/web/api/webvr_api/using_the_webvr_api/index.md b/files/en-us/web/api/webvr_api/using_the_webvr_api/index.md
@@ -4,7 +4,7 @@ slug: Web/API/WebVR_API/Using_the_WebVR_API
 page-type: guide
 ---
 
-{{APIRef("WebVR API")}}{{deprecated_header}}
+{{DefaultAPISidebar("WebVR API")}}{{deprecated_header}}
 
 > [!NOTE]
 > WebVR API is replaced by [WebXR API](/en-US/docs/Web/API/WebXR_Device_API). WebVR was never ratified as a standard, was implemented and enabled by default in very few browsers and supported a small number of devices.

diff --git a/files/en-us/web/api/webvr_api/using_vr_controllers_with_webvr/index.md b/files/en-us/web/api/webvr_api/using_vr_controllers_with_webvr/index.md
@@ -6,7 +6,7 @@ status:
   - experimental
 ---
 
-{{APIRef("WebVR API")}}{{Deprecated_Header}}
+{{DefaultAPISidebar("WebVR API")}}{{Deprecated_Header}}
 
 Many WebVR hardware setups feature controllers that go along with the headset. These can be used in WebVR apps via the [Gamepad API](/en-US/docs/Web/API/Gamepad_API), and specifically the [Gamepad Extensions API](/en-US/docs/Web/API/Gamepad_API#experimental_gamepad_extensions) that adds API features for accessing [controller pose](/en-US/docs/Web/API/GamepadPose), [haptic actuators](/en-US/docs/Web/API/GamepadHapticActuator), and more. This article explains the basics.
 

diff --git a/files/en-us/web/api/webxr_device_api/inputs/index.md b/files/en-us/web/api/webxr_device_api/inputs/index.md
@@ -4,7 +4,7 @@ slug: Web/API/WebXR_Device_API/Inputs
 page-type: guide
 ---
 
-{{APIRef("WebXR Device API")}}{{SecureContext_Header}}
+{{DefaultAPISidebar("WebXR Device API")}}{{SecureContext_Header}}
 
 A full WebXR experience isn't just about showing the user a wholly virtual scene or augmenting reality by adding to or altering the world around them. In order to make an experience that's fulfilling and engaging, the user needs to be able to interact with it. To that end, WebXR provides support for a variety of kinds of input devices.