@eventcatalog/core 4.10.13 → 4.10.15

package/dist/analytics/analytics.cjs

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(analytics_exports);
 var import_os = __toESM(require("os"), 1);
 
 // package.json
-var version = "4.10.13";
+var version = "4.10.15";
 
 // src/constants.ts
 var VERSION = version;

package/dist/analytics/analytics.js

@@ -1,7 +1,7 @@
 import {
   raiseEvent
-} from "../chunk-IIECZFXN.js";
-import "../chunk-PADMH2RJ.js";
+} from "../chunk-A4JRWRCV.js";
+import "../chunk-I6HUOX4R.js";
 export {
   raiseEvent
 };

package/dist/analytics/log-build.cjs

@@ -140,7 +140,7 @@ var verifyRequiredFieldsAreInCatalogConfigFile = async (projectDirectory) => {
 var import_os = __toESM(require("os"), 1);
 
 // package.json
-var version = "4.10.13";
+var version = "4.10.15";
 
 // src/constants.ts
 var VERSION = version;

package/dist/analytics/log-build.js

@@ -1,9 +1,9 @@
 import {
   log_build_default
-} from "../chunk-34RMFKFB.js";
-import "../chunk-IIECZFXN.js";
+} from "../chunk-Q2ATWE7N.js";
+import "../chunk-A4JRWRCV.js";
 import "../chunk-ZAZHAVKB.js";
-import "../chunk-PADMH2RJ.js";
+import "../chunk-I6HUOX4R.js";
 import "../chunk-6QENHZZP.js";
 export {
   log_build_default as default

package/dist/{chunk-SSSN5FXC.js → chunk-7LWOCX4R.js}

@@ -1,6 +1,6 @@
 import {
   logger
-} from "./chunk-JHUICVBT.js";
+} from "./chunk-HBVTU6ZP.js";
 import {
   cleanup,
   getEventCatalogConfigFile

package/dist/{chunk-IIECZFXN.js → chunk-A4JRWRCV.js}

@@ -1,6 +1,6 @@
 import {
   VERSION
-} from "./chunk-PADMH2RJ.js";
+} from "./chunk-I6HUOX4R.js";
 
 // src/analytics/analytics.js
 import os from "os";

package/dist/{chunk-JHUICVBT.js → chunk-HBVTU6ZP.js}

@@ -1,6 +1,6 @@
 import {
   VERSION
-} from "./chunk-PADMH2RJ.js";
+} from "./chunk-I6HUOX4R.js";
 
 // src/utils/cli-logger.ts
 import pc from "picocolors";

package/dist/{chunk-PADMH2RJ.js → chunk-I6HUOX4R.js}

@@ -1,5 +1,5 @@
 // package.json
-var version = "4.10.13";
+var version = "4.10.15";
 
 // src/constants.ts
 var VERSION = version;

package/dist/{chunk-34RMFKFB.js → chunk-Q2ATWE7N.js}

@@ -1,6 +1,6 @@
 import {
   raiseEvent
-} from "./chunk-IIECZFXN.js";
+} from "./chunk-A4JRWRCV.js";
 import {
   countResources,
   hashCatalogContent,

package/dist/constants.cjs

@@ -25,7 +25,7 @@ __export(constants_exports, {
 module.exports = __toCommonJS(constants_exports);
 
 // package.json
-var version = "4.10.13";
+var version = "4.10.15";
 
 // src/constants.ts
 var VERSION = version;

package/dist/constants.js

@@ -1,6 +1,6 @@
 import {
   VERSION
-} from "./chunk-PADMH2RJ.js";
+} from "./chunk-I6HUOX4R.js";
 export {
   VERSION
 };

package/dist/docs/api/02-config.md

@@ -78,7 +78,7 @@ The output type for your EventCatalog, choose from `static` or `server`.
 :::info "What is the difference between static and server?"
 
 - `static` - The default output type for EventCatalog. This will output a static website that you can host anywhere.
-- `server` - This will output a Node.js server that you can host anywhere. This is required for certain features like the [EventCatalog Chat](/features/ai-assistant) (bring your own keys). The easiest way to host this is with our [Docker image](/docs/development/deployment/hosting-options#hosting-a-server).
+- `server` - This will output a Node.js server that you can host anywhere. This is required for certain features like the [EventCatalog Assistant](/docs/development/ask-your-architecture/eventcatalog-assistant/what-is-eventcatalog-assistant) (bring your own keys). The easiest way to host this is with our [Docker image](/docs/development/deployment/hosting-options#hosting-as-a-server).
 
 :::
 
@@ -123,6 +123,54 @@ module.exports = {
 };
 ```
 
+### `linkValidation` {#linkValidation}
+
+- Type: `object` | `false`
+- Default: `{ onBrokenLinks: 'warn', onBrokenAnchors: 'warn' }`
+
+Checks internal links and anchors after a static build and reports any that are broken. Validation is skipped in SSR mode. Set to `false` to turn off the check entirely.
+
+```js title="eventcatalog.config.js"
+module.exports = {
+  linkValidation: {
+    onBrokenLinks: 'warn',
+    onBrokenAnchors: 'warn',
+    ignore: ['/api/**'],
+  },
+};
+```
+
+#### `linkValidation.onBrokenLinks`
+
+- Type: `'warn' | 'error' | 'ignore'`
+- Default: `'warn'`
+
+What to do when a link points to a page that does not exist. `error` fails the build, `warn` logs the problem but still builds, `ignore` skips the check.
+
+#### `linkValidation.onBrokenAnchors`
+
+- Type: `'warn' | 'error' | 'ignore'`
+- Default: `'warn'`
+
+What to do when a link points to a valid page but an anchor (`#section`) that does not exist on it.
+
+#### `linkValidation.ignore`
+
+- Type: `string[]`
+- Default: `[]`
+
+Glob patterns for destination URL paths to skip, relative to your catalog's [`base`](#base), starting with `/`. Patterns exclude the base prefix, query string, and anchor. For example, with `base: '/catalog'`, use `/docs/legacy/**` to ignore `/catalog/docs/legacy/example#section`. Use this for links you know are valid but EventCatalog cannot verify, such as pages rendered outside the build.
+
+```js title="eventcatalog.config.js"
+module.exports = {
+  linkValidation: {
+    ignore: ['/api/**', '/docs/legacy/*'],
+  },
+};
+```
+
+See the [link validation guide](/docs/development/deployment/link-validation) for what gets checked and how to use this in CI.
+
 ### `port` {#port}
 
 - Type: `number`
@@ -449,6 +497,11 @@ module.exports = {
       // The render mode for channels in the visualiser
       // Flat or single
       renderMode: 'flat'
+    },
+
+    // Opt-in, catalog-wide force-directed graph at /visualiser/graph
+    architectureGraph: {
+      enabled: true
     }
   }
 };
@@ -459,6 +512,7 @@ module.exports = {
 | ------------- | ----------- | ----------- | ----------- |
 | `visualiser.enabled` | `true` or `false` | `true` | **Enabled or disables the visualiser**. Setting this to false will not render any visualiser pages in your catalog and also remove references to the visualiser features in your catalog. _(Added in 2.65.1)_ |
 | `visualiser.channels.renderMode` | `flat` or `single` | `flat` | The render mode for the visualiser. `flat` means the channel node is duplicated for each message. `single` means the channel node is a single node for all messages. Depending on your use case/preferences you may want to use one or the other. |
+| `visualiser.architectureGraph.enabled` | `true` or `false` | `false` | Enables the [architecture graph](/docs/development/guides/architecture-graph) at `/visualiser/graph`. Opt-in while in beta. _(Added in 4.5.0)_ |
 
 
 
@@ -530,17 +584,17 @@ docs: {
 
 - Type: `object`
 
-Configuration for the EventCatalog AI chat feature.
+Configuration for [EventCatalog Assistant](/docs/development/ask-your-architecture/eventcatalog-assistant/what-is-eventcatalog-assistant).
 
 :::info
-The `chat` property requires a Starter or Scale plan and `output: 'server'` to take effect.
+The `chat` property requires a Scale plan and `output: 'server'` to take effect.
 :::
 
 ```js title="eventcatalog.config.js"
 module.exports = {
   output: 'server',
   chat: {
-    // Set to false to disable the AI chat feature entirely
+    // Set to false to disable EventCatalog Assistant entirely
     enabled: false,
   },
 };
@@ -548,7 +602,7 @@ module.exports = {
 
 | Option | Type | Default | Description |
 | ------ | ---- | ------- | ----------- |
-| `chat.enabled` | `boolean` | `true` | Enables or disables the AI chat feature. Set to `false` to hide the chat UI and prevent chat requests even when all other prerequisites are met. |
+| `chat.enabled` | `boolean` | `true` | Enables or disables EventCatalog Assistant. Set to `false` to hide the assistant UI and prevent chat requests even when all other prerequisites are met. |
 
 ### `mcp` {#mcp}
 
@@ -634,7 +688,7 @@ module.exports = {
 - Type: `string`
 
 :::tip
-For Stater or Scale plans. This gives you the ability to show your own GitHub repository in EventCatalog (in the header bar).
+For Scale plans. This gives you the ability to show your own GitHub repository in EventCatalog (in the header bar).
 :::
 
 URL to your repository for EventCatalog.

package/dist/docs/development/ask-your-architecture/02-eventcatalog-assistant/02-configuration.md

@@ -12,25 +12,32 @@ import PlanBanner from '@site/src/components/MDX/PlanBanner';
 
 <PlanBanner plan="Scale" />
 
-**EventCatalog Assistant is turned off by default.**
+**EventCatalog Assistant is shown by default.**
 
-To enable the assistant feature, you need to set the following:
+To use the assistant, you need to:
 
-1. Turn on the `chat` feature in your `eventcatalog.config.js` file and add 
-2. Add a `eventcatalog.chat.js` file to your catalog.
+1. Run EventCatalog with `output: 'server'` in your `eventcatalog.config.js` file
+2. Add an `eventcatalog.chat.js` file to your catalog
 
-### Enabling the feature
+```js title="eventcatalog.config.js"
+module.exports = {
+  // AI integrations require you to run EventCatalog as a server
+  output: 'server'
+};
+```
+
+You can hide the assistant by setting `chat.enabled` to `false`.
 
-To turn on the assistant feature, you need to set the following:
+### Disabling the feature
+
+EventCatalog Assistant is enabled by default. Set `chat.enabled` to `false` to hide the assistant UI and prevent chat requests:
 
 ```js title="eventcatalog.config.js"
 module.exports = {
-  // Enable the chat feature in your catalog
+  output: 'server',
   chat: {
-    enabled: true,
+    enabled: false,
   },
-  // AI integrations require you to run eventcatalog as as server
-  output: 'server'
 };
 ```
 
@@ -70,4 +77,4 @@ export const configuration = {
 }
 ```
 
-Once you have enabled the feature and configured your model, restart EventCatalog and you can start asking questions about your architecture.
+Once you have configured your model, restart EventCatalog and you can start asking questions about your architecture.

package/dist/docs/development/authentication/providers/03-setting-up-github.md

@@ -97,6 +97,35 @@ export default {
 
 The host must match the **Authorization callback URL** on your GitHub OAuth app (`https://catalog.example.com/api/auth/callback/github`). Not needed on Vercel, Cloudflare Pages, or local dev. See the [Auth.js reference](https://authjs.dev/reference/core#redirectproxyurl) for more.
 
+## Issuer validation
+
+<AddedIn version="4.10.3" />
+
+GitHub OAuth callbacks include an `iss` parameter, and EventCatalog now sets the correct `issuer` on the GitHub provider automatically, using `https://github.com/login/oauth` for github.com or `{enterprise.baseUrl}/login/oauth` when you configure `providers.github.enterprise.baseUrl` for GitHub Enterprise Server. You can still override it by setting `issuer` explicitly in your provider config.
+
+```js title="eventcatalog.auth.js"
+export default {
+  providers: {
+    github: {
+      clientId: process.env.AUTH_GITHUB_CLIENT_ID,
+      clientSecret: process.env.AUTH_GITHUB_CLIENT_SECRET,
+      issuer: 'https://github.com/login/oauth',
+    },
+  },
+};
+```
+
+### Fix "unexpected iss" errors on older versions
+
+If you're running an EventCatalog version before `4.10.3`, sign-in can fail with users redirected to `/auth/error?error=Configuration` and logs showing:
+
+```
+[auth][cause] OperationProcessingError: unexpected "iss" (issuer) response parameter value
+[auth][details] { "expected": "https://authjs.dev", "provider": "github" }
+```
+
+This happens because GitHub now sends an `iss` parameter on OAuth callbacks, but the GitHub provider had no `issuer` configured, so validation fell back to a placeholder value. Upgrading to `4.10.3` or later fixes this by default. If you can't upgrade yet, set `issuer` explicitly on the GitHub provider as shown above.
+
 ## Found an issue?
 
 Remember to setup the prerequisites for this guide:

package/dist/docs/development/bring-your-own-documentation/custom-pages/02-adding-custom-docs.md

@@ -22,8 +22,8 @@ High level documentation requires an EventCatalog Scale license key. You can get
 
 High level documentation is split into two parts:
 
-1. [Creating your documentation (markdown files)](#creating-your-documentation)
-2. [Configuring your sidebar (eventcatalog.config.js)](#configuring-your-sidebar)
+1. [Creating your documentation (markdown files)](#creating-documentation)
+2. [Configuring your sidebar (eventcatalog.config.js)](#sidebar-configuration)
 
 ### Creating documentation
 

package/dist/docs/development/bring-your-own-documentation/custom-pages/03-components.md

@@ -54,3 +54,20 @@ In custom documentation pages, `id`, `version`, and `type` are all required. A `
 | `search` | boolean | No | Show or hide the search bar. Accepts `true`/`false` or `"true"`/`"false"`. Defaults to `true`. |
 | `legend` | boolean | No | Show or hide the legend. Accepts `true`/`false` or `"true"`/`"false"`. Defaults to `true`. |
 | `mode` | string | No | `"simple"` or `"full"`. Defaults to `"simple"`. |
+
+### Embed the Architecture Graph (ArchitectureGraph)
+
+You can also embed the catalog-wide [architecture graph](/docs/development/guides/architecture-graph) into your custom documentation pages using the `ArchitectureGraph` component.
+
+```md
+This is my custom documentation page, here is the whole catalog graph:
+
+<ArchitectureGraph />
+
+<!-- Or focus the graph on a specific resource -->
+<ArchitectureGraph id="Orders" type="domain" />
+```
+
+Unlike `NodeGraph`, no props are required — without `id` and `type` the whole catalog is rendered. No `version` is needed; the graph always shows the latest version of each resource.
+
+[See the ArchitectureGraph component reference for the full list of props](/docs/development/components/components/architecture-graph).

package/dist/docs/development/components/07-resource-references.md

@@ -108,6 +108,8 @@ Without a version, the reference uses the latest version. Pin versions when docu
 Our legacy [[service|PaymentService@0.9.0]] is being replaced by [[service|PaymentGatewayService]].
 ```
 
+Users, teams, and custom docs are not versioned, so references like `[[user|dboyne]]` and `[[team|backend-team]]` always link straight to the resource.
+
 ## Interactive tooltips
 
 Hover over any reference to see detailed information without leaving the page.
@@ -119,6 +121,10 @@ Hover over any reference to see detailed information without leaving the page.
 
 Tooltips show different information based on resource type.
 
+Owner links open the matching user or team profile. If an owner is not defined in your catalog, its ID appears as plain text.
+
+In service and agent tooltips, sent and received messages link to their matching event, command, or query documentation, including when a message version is specified.
+
 ### Combine with other components
 
 Mix references with other EventCatalog components.
@@ -133,4 +139,4 @@ The [[service|OrdersService]] coordinates between inventory and payment:
 
 ### Review references regularly
 
-Regularly audit references to ensure they point to current resources and remove outdated links.
+Regularly audit references to ensure they point to current resources and remove outdated links. [Link validation](/docs/development/deployment/link-validation) reports broken internal links and anchors after a static build.

package/dist/docs/development/components/components/05-architecture-graph.md

@@ -0,0 +1,65 @@
+---
+sidebar_position: 5
+keywords:
+- components
+- architecture graph
+- force-directed graph
+sidebar_label: ArchitectureGraph
+title: ArchitectureGraph
+description: Component for embedding the catalog-wide architecture graph into your documentation
+---
+
+import AddedIn from '@site/src/components/MDX/AddedIn';
+
+<AddedIn version="4.10.1" />
+
+A component that renders the [architecture graph](/docs/development/guides/architecture-graph) (the force-directed graph of your whole catalog from `/visualiser/graph`) inside your documentation pages, focused on the resource you are documenting.
+
+The `<ArchitectureGraph/>` component is supported in domains, services, systems, all messages, and custom documentation pages.
+
+Unlike [`<NodeGraph/>`](/docs/development/components/components/nodegraph) (which renders one resource's diagram), `<ArchitectureGraph/>` shows where the resource sits in your whole architecture — its neighbourhood inside the catalog graph, with clustering, focus rings, and search.
+
+### Example
+
+```md /domains/Orders/index.mdx
+<!-- Without any properties, this renders the architecture graph focused on the current resource -->
+<ArchitectureGraph />
+
+<!-- Focus another resource -->
+<ArchitectureGraph id="InventoryService" type="service" />
+
+<!-- Show more of the architecture around the resource (1–3 relationship hops) -->
+<ArchitectureGraph depth="3" />
+
+<!-- Render a specific lens of the whole catalog -->
+<ArchitectureGraph lens="messages" />
+```
+
+#### Output
+
+![Example output](./img/architecture-graph.png)
+
+Readers can click any node to focus it, double-click to open its documentation, and use the search to jump to any resource — the same interactions as the full-page architecture graph. Scrolling over the graph scrolls the page; hold `ctrl`/`cmd` while scrolling to zoom.
+
+#### Props
+
+| Name                    | Type      | Default           | Description                                                       |
+| ----------------------- | --------- | ----------------- | ----------------------------------------------------------------- |
+| `id` (optional)         | `string`  | Current page's resource | The id of the resource to focus. Use together with `type`. |
+| `type` (optional)       | `string`  | Current page's type | The type of the resource to focus (e.g. `domain`, `service`, `event`). |
+| `depth` (optional)      | `string`  | `"2"`             | How many relationship hops to render around the focused resource (1–3). |
+| `lens` (optional)       | `string`  | `"all"`           | The lens to render: `all`, `domains`, `systems`, `services`, `teams` or `messages`. |
+| `search` (optional)     | `boolean` | `true`            | Show or hide the search bar. Accepts `true`/`false` or `"true"`/`"false"`. |
+| `legend` (optional)     | `boolean` | `true`            | Show or hide the resources legend. Accepts `true`/`false` or `"true"`/`"false"`. |
+| `lensPicker` (optional) | `boolean` | `false`           | Show the lens picker so readers can switch between views (domains, systems, services, teams, message flow). Accepts `true`/`false` or `"true"`/`"false"`. |
+| `maxHeight` (optional)  | `string`  | `30`              | Max height (em) of the graph in your document. |
+
+The graph always shows the latest version of each resource, so no `version` prop is needed.
+
+:::info Custom documentation pages
+On custom documentation pages there is no "current resource", so `<ArchitectureGraph/>` without `id` and `type` renders the whole catalog graph.
+:::
+
+:::tip Open full screen
+When the [full-page architecture graph is enabled](/docs/development/guides/architecture-graph#turn-on-the-graph) (`visualiser.architectureGraph.enabled` in your `eventcatalog.config.js`), the embedded graph shows an **Open full screen** link to `/visualiser/graph` that carries the current view state — the focused resource, selected depth, and lens — so the full page opens on exactly what the reader is looking at. The embedded component itself works without that flag.
+:::

package/dist/docs/development/components/components/{05-attachments.md → 06-attachments.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 5
+sidebar_position: 6
 keywords:
 - attachments
 - documentation

package/dist/docs/development/components/components/{06-channel-information.md → 07-channel-information.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 6
+sidebar_position: 7
 keywords:
   - components
 sidebar_label: ChannelInformation

package/dist/docs/development/components/components/{07-custom-properties.md → 08-custom-properties.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 7
+sidebar_position: 8
 keywords:
 - components
 - custom properties

package/dist/docs/development/components/components/{08-design.md → 09-design.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 8
+sidebar_position: 9
 keywords:
 - components
 - remote schema

package/dist/docs/development/components/components/{09-entitymap.md → 10-entitymap.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 9
+sidebar_position: 10
 keywords:
 - components
 sidebar_label: EntityMap

package/dist/docs/development/components/components/{10-flow.md → 11-flow.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 10
+sidebar_position: 11
 keywords:
 - components
 sidebar_label: Flow

package/dist/docs/development/components/components/{11-link.md → 12-link.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 11
+sidebar_position: 12
 keywords:
 - components
 sidebar_label: Link

package/dist/docs/development/components/components/{12-mermaid-file-loader.md → 13-mermaid-file-loader.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 12
+sidebar_position: 13
 keywords:
 - components
 - remote schema
@@ -52,11 +52,23 @@ When you use the `<MermaidFileLoader />` component, it will render the diagram i
 
 ![Example output](./img/mermaid.png)
 
+**Control options**
+
+<AddedIn version="4.10.6" />
+
+Use `placement` and `actions` to configure the [interactive controls](/docs/development/components/diagram-syntax/mermaid#control-options) on the diagram.
+
+```jsx /events/MyEvent/index.mdx
+<MermaidFileLoader file="mermaid.mmd" placement="top-left" actions={false} />
+```
+
 ### Props
 
 | Name                    | Type      | Default           | Description                                                       |
 | ----------------------- | --------- | ----------------- | ----------------------------------------------------------------- |
 | `file` (required)        | `string`  | (empty)           | The `.mmd` or `.mermaid` file to load into the diagram block. Path is resolved by EventCatalog. |
+| `placement` (optional)   | `'top-left' \| 'top-right' \| 'bottom-left' \| 'bottom-right'` | `'top-right'` | Corner for the interactive controls. |
+| `actions` (optional)     | `boolean` | shown when the diagram is taller than 120px | `true` always shows the controls. `false` hides them. |
 
 ### Support
 

package/dist/docs/development/components/components/{13-message-table.md → 14-message-table.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 13
+sidebar_position: 14
 keywords:
 - components
 sidebar_label: MessageTable

package/dist/docs/development/components/components/{14-nodegraph.md → 15-nodegraph.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 14
+sidebar_position: 15
 keywords:
 - components
 sidebar_label: NodeGraph

package/dist/docs/development/components/components/{15-openapi.md → 16-openapi.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 15
+sidebar_position: 16
 keywords:
 - components
 sidebar_label: OpenAPI

package/dist/docs/development/components/components/{16-prompt.md → 17-prompt.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 16
+sidebar_position: 17
 keywords:
   - components
   - prompt

package/dist/docs/development/components/components/{17-remote-schema.md → 18-remote-schema.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 17
+sidebar_position: 18
 keywords:
 - components
 - remote schema

package/dist/docs/development/components/components/{18-resource-group-table.md → 19-resource-group-table.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 18
+sidebar_position: 19
 keywords:
 - components
 sidebar_label: ResourceGroupTable

package/dist/docs/development/components/components/{19-resource-link.md → 20-resource-link.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 19
+sidebar_position: 20
 keywords:
 - components
 sidebar_label: ResourceLink

package/dist/docs/development/components/components/{20-schema.md → 21-schema.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 20
+sidebar_position: 21
 keywords:
 - components
 sidebar_label: Schema

package/dist/docs/development/components/components/{21-schema-viewer.md → 22-schema-viewer.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 21
+sidebar_position: 22
 keywords:
 - components
 sidebar_label: SchemaViewer

package/dist/docs/development/components/components/{22-steps.md → 23-steps.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 22
+sidebar_position: 23
 keywords:
   - components
 sidebar_label: Steps

package/dist/docs/development/components/components/{23-tabs.md → 24-tabs.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 23
+sidebar_position: 24
 keywords:
   - components
 sidebar_label: Tabs

package/dist/docs/development/components/components/{24-tiles.md → 25-tiles.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 24
+sidebar_position: 25
 keywords:
   - components
 sidebar_label: Tiles

package/dist/docs/development/components/components/{25-visibility.md → 26-visibility.md}

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 25
+sidebar_position: 26
 keywords:
   - components
   - visibility