(docs) Document schema component

fern/products/docs/docs.yml

@@ -111,6 +111,9 @@ navigation:
           - page: Runnable endpoint
             path: ./pages/component-library/default-components/runnable-endpoint.mdx
             icon: fa-duotone fa-play-circle
+          - page: Schema
+            path: ./pages/component-library/default-components/schema.mdx
+            icon: fa-duotone fa-brackets-curly
           - page: Step
             path: ./pages/component-library/default-components/steps.mdx
             icon: fa-duotone fa-list-ol
@@ -325,4 +328,7 @@ navigation:
     paginated: false
     api-name: mcp-tools
     slug: fern-api-reference
+    # must be included to use the schema component
+  - api: API reference
+    api-name: docs-yml
 

fern/products/docs/pages/changelog/2025-11-26.mdx

@@ -0,0 +1,17 @@
+## Schema component
+
+The new `<Schema>` component displays type definitions from your API Reference anywhere in your documentation. Use it to reference data models, request objects, or response types outside of your API Reference pages.
+
+This example displays the `AIChatConfig` type from the `docs-yml` API:
+
+<div className="highlight-frame">
+  <div className="highlight-frame-content">
+  <Schema type="AIChatConfig" />
+  </div>
+</div>
+
+```jsx Markdown
+<Schema type="AIChatConfig" />
+```
+
+[Learn more](/docs/writing-content/components/schema) about the Schema component.

fern/products/docs/pages/component-library/default-components/endpoint-schema-snippet.mdx

@@ -5,6 +5,8 @@ description: 'Reference an endpoint schema from your API Reference'
 
 The `<EndpointSchemaSnippet>` component displays endpoint schemas from your API Reference. By default, it renders the complete schema, or you can use the `selector` prop to display specific parts like request body, response, path parameters, or query parameters.
 
+To display any type definition by name (not limited to endpoint schemas), use the [`<Schema>`](/docs/writing-content/components/schema) component.
+
 <Note>
   Markdown-rich field descriptions aren't yet supported and will display as plain text. See the [Request path](#request-path) example below.
 </Note>

fern/products/docs/pages/component-library/default-components/overview.mdx

@@ -3,7 +3,7 @@ title: 'Components overview'
 description: 'Built-in components for creating interactive documentation'
 ---
 
-Fern includes 23 built-in components for creating interactive documentation. Select a component below to view usage examples and configuration options.
+Fern includes 24 built-in components for creating interactive documentation. Select a component below to view usage examples and configuration options.
 
 <CardGroup cols={3}>
   <Card
@@ -139,6 +139,13 @@ Fern includes 23 built-in components for creating interactive documentation. Sel
   >
     Interactive request builder for testing API endpoints
   </Card>
+  <Card
+    title="Schema"
+    icon="fa-duotone fa-brackets-curly"
+    href="/docs/writing-content/components/schema"
+  >
+    Display type definitions from your API Reference
+  </Card>
   <Card
     title="Step"
     icon="fa-duotone fa-list-ol"

fern/products/docs/pages/component-library/default-components/schema.mdx

@@ -0,0 +1,36 @@
+---
+title: Schema
+description: Display any type definition from your API Reference
+---
+
+The `<Schema>` component displays type definitions from your API Reference anywhere in your documentation. Use it to reference data models, request objects, or response types outside of your API Reference pages. Field descriptions support markdown formatting.
+
+Similar to [`<EndpointSchemaSnippet>`](/docs/writing-content/components/endpoint-schema-snippet), but accepts any type name rather than being limited to endpoint-specific schemas.
+
+<Note>
+  The component only discovers types referenced by endpoints. Types exclusively used by websockets or webhooks won't be available. If multiple APIs have the same type name, the component returns the first match.
+</Note>
+
+## Usage
+
+The component works with [API references already configured in your `docs.yml`](/learn/docs/api-references/generate-api-ref). This example displays the `AIChatConfig` type from the `docs-yml` API:
+
+<div className="highlight-frame">
+  <div className="highlight-frame-content">
+  <Schema type="AIChatConfig" />
+  </div>
+</div>
+
+```jsx Markdown
+<Schema type="AIChatConfig" />
+```
+
+## Properties
+
+<ParamField path="type" type="string" required={true}>
+  The name of the type to display. The component will search for this type across all endpoints in your API definition.
+</ParamField>
+
+<ParamField path="className" type="string" required={false}>
+  Optional CSS class name for custom styling.
+</ParamField>

fern/products/sdks/overview/php/changelog/2025-11-25.mdx

@@ -3,7 +3,7 @@
 
 
 ## 1.22.2
-**`(fix):`** Add missing <?php opening tag to generated wire test files for proper syntax highlighting.
+**`(fix):`** Add missing `<?php` opening tag to generated wire test files for proper syntax highlighting.
 
 
 ## 1.22.1