@eventcatalog/core 4.1.3 → 4.1.5

package/dist/docs/plugins/amazon-apigateway/01-installation.md

@@ -127,36 +127,35 @@ export default {
 
 The API Gateway and OpenAPI plugin both require a license key to work with EventCatalog.
 
-You can get a trial license key from [EventCatalog Cloud](https://eventcatalog.cloud).
+You can get a trial Scale license key from [EventCatalog Cloud](https://eventcatalog.cloud).
 
 You have a few options for setting the license key:
 
 1. [Setting license key in `.env` file (recommended)](#setting-license-key-in-env-file-recommended)
 2. [Setting license key in eventcatalog.config.js](#setting-license-key-in-eventcatalogconfigjs)
 
-#### 1. Setting license key in `.env` file (recommended)
+#### 1. Setting license key in `.env` file (recommended) {#setting-license-key-in-env-file-recommended}
 
 <AddedIn version="2.35.4" />
 
 Create a `.env` file in the root of your project and add the following:
 
 ```bash title=".env"
-EVENTCATALOG_LICENSE_KEY_AMAZON_APIGATEWAY=your-license-key
-EVENTCATALOG_LICENSE_KEY_OPENAPI=your-license-key
+EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
 ```
 
-:::tip Using an older version of EventCatalog?
+:::tip Using an Older API Key?
 
-If you are using an older version of EventCatalog that does not support the `.env` file, you can just export the license key as an environment variable.
+If you already have older Amazon API Gateway and OpenAPI plugin keys, you can still use them with the plugin-specific environment variables.
 
-```bash title="Setting license key in environment variables"
-export EVENTCATALOG_LICENSE_KEY_AMAZON_APIGATEWAY=your-license-key
-export EVENTCATALOG_LICENSE_KEY_OPENAPI=your-license-key
+```bash title=".env"
+EVENTCATALOG_LICENSE_KEY_AMAZON_APIGATEWAY=your-license-key
+EVENTCATALOG_LICENSE_KEY_OPENAPI=your-license-key
 ```
 
 :::
 
-#### 2. Setting license key in eventcatalog.config.js
+#### 2. Setting license key in eventcatalog.config.js {#setting-license-key-in-eventcatalogconfigjs}
 
 If you prefer, you can set the license key in the `eventcatalog.config.js` file
 using the `licenseKey` property in both the API Gateway and OpenAPI plugin.
@@ -167,7 +166,7 @@ export default {
     [
       '@eventcatalog/generator-eventbridge',
       {
-        licenseKey: '[INSERT_YOUR_LICENSE_KEY]', // or process.env.EVENTCATALOG_LICENSE_KEY_AMAZON_APIGATEWAY
+        licenseKey: '[INSERT_YOUR_LICENSE_KEY]', // or process.env.EVENTCATALOG_SCALE_LICENSE_KEY
       },
     ],
   ],
@@ -195,4 +194,3 @@ npm run dev
 ```
 
 
-

package/dist/docs/plugins/amazon-apigateway/02-plugin-configuration.md

@@ -7,9 +7,11 @@ title: Plugin Configuration
 description: Configuration of the Amazon API Gateway plugin
 ---
 
-This plugin requires a license key. You can get a 14 day free trial license key by signing up to [EventCatalog Cloud](https://eventcatalog.dev/cloud).
+This plugin requires an EventCatalog Scale license key.
 
-Once you have your license key you can set the `EVENTCATALOG_LICENSE_KEY_AMAZON_APIGATEWAY` environment variable.
+You can get a 30-day free trial license key by signing up to [EventCatalog Cloud](https://eventcatalog.dev/cloud).
+
+Once you have your license key you can set the `EVENTCATALOG_SCALE_LICENSE_KEY` environment variable.
 
 ## Overview
 
@@ -21,7 +23,7 @@ The Amazon API Gateway plugin is configured in the `eventcatalog.config.js` file
 |--------|------|----------|---------|-------------|
 | `output` | string | No | `amazon-apigateway-specs` | The output directory for the OpenAPI specifications (used by the OpenAPI Generator plugin) |
 | `credentials` | [AwsCredentialIdentity](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/Package/-smithy-types/Interface/AwsCredentialIdentity/) | No | - | AWS credentials to use for the import on AWS. If this is not provided it will default to the credentials on the machine. |
-| `licenseKey` | string | No | - | You can either pass the license key directly or set the `EVENTCATALOG_LICENSE_KEY_AMAZON_APIGATEWAY` environment variable. |
+| `licenseKey` | string | No | - | You can either pass the license key directly or set the `EVENTCATALOG_SCALE_LICENSE_KEY` environment variable. |
 | `apis` | API[] | Yes | - | Array of API configurations |
 
 ## API Configuration
@@ -133,4 +135,3 @@ You can view an example configuration in the  [EventCatalog Amazon API Gateway p
 
 
 
-

package/dist/docs/plugins/apicurio/00-intro.md

@@ -69,11 +69,11 @@ The EventCatalog Apicurio Registry plugin is a generator. It will import your sc
 
 ## Commercial and License
 
-This plugin requires a license key to be used.
+This plugin requires an EventCatalog Scale license key to be used.
 
-You can get a 14 day trial license key to try the plugin out by going to [EventCatalog Cloud](https://eventcatalog.cloud).
+You can get a 30-day trial Scale license key by going to [EventCatalog Cloud](https://eventcatalog.cloud).
 
-After the trial you can purchase a license to continue using this plugin, we have different plans to suit your organization based on where you are in your governance and documentation journey.
+After the trial, you can continue using this plugin with EventCatalog Scale.
 
 See [pricing](/pricing) for more information.
 
@@ -86,16 +86,16 @@ If you would like a demo of the plugin, please feel free to reach out to us and
 ## License FAQ
 
 ### What is the license key for?
-The license key is required to use the Apicurio Registry plugin with EventCatalog. It helps support ongoing development and maintenance of the plugin and project.
+The EventCatalog Scale license key is required to use the Apicurio Registry plugin with EventCatalog. It helps support ongoing development and maintenance of the plugin and project.
 
-### How do I get a license key?
-You can obtain a license key by visiting [EventCatalog Cloud](https://eventcatalog.cloud). New users can start with a 14-day free trial.
+### How do I get an EventCatalog Scale license key?
+You can obtain an EventCatalog Scale license key by visiting [EventCatalog Cloud](https://eventcatalog.cloud). New users can start with a 30-day free trial.
 
 ### Terms
-- **Trial Period**: 14 days free trial no credit card required
+- **Trial Period**: 30-day free trial no credit card required
 - **Support**: Discord community support (extra for priority support)
 
-After your trial period ends, you can purchase a full license through [EventCatalog Cloud](https://eventcatalog.cloud) to continue using the plugin.
+After your trial period ends, you can continue with EventCatalog Scale through [EventCatalog Cloud](https://eventcatalog.cloud).
 
 ## Any questions or need help?
 

package/dist/docs/plugins/apicurio/01-installation.md

@@ -117,19 +117,29 @@ We create an `orders` domain and an `Orders Service` that sends and receives mes
 
 The EventCatalog Apicurio Registry plugin requires API keys in your environment variables.
 
-1. A license key for the Apicurio Registry plugin (14 days trial, at [EventCatalog Cloud](https://eventcatalog.cloud))
+1. An EventCatalog Scale license key for the Apicurio Registry plugin (30-day trial, at [EventCatalog Cloud](https://eventcatalog.cloud))
 2. Apicurio Registry access token (optional - only if your registry requires authentication)
 
 Create a `.env` file in the root, and add your keys to the project.
 
 ```bash title=".env"
 # EventCatalog license key
-EVENTCATALOG_LICENSE_KEY_APICURIO_SCHEMA_REGISTRY=your-license-key
+EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
 
 # Apicurio Registry Bearer Token (optional - only if your registry requires authentication)
 APICURIO_ACCESS_TOKEN=your-access-token-here
 ```
 
+:::tip Using an Older API Key?
+
+If you already have an older Apicurio Registry plugin key, you can still use it with the plugin-specific environment variable.
+
+```bash title=".env"
+EVENTCATALOG_LICENSE_KEY_APICURIO_SCHEMA_REGISTRY=your-license-key
+```
+
+:::
+
 #### White listing EventCatalog domains
 
 If you are behind a firewall you will need to white list the domain `https://api.eventcatalog.cloud` in your firewall. This is because the plugin needs to verify your license key.

package/dist/docs/plugins/apicurio/02-plugin-configuration.md

@@ -74,12 +74,11 @@ You can attach OpenAPI or AsyncAPI specifications stored in your Apicurio Regist
 You can attach OpenAPI or AsyncAPI specifications from your Apicurio Registry to services. These specifications can optionally be processed by their respective EventCatalog plugins to generate additional documentation.
 
 :::info Plugin Licenses Required
-The OpenAPI and AsyncAPI generators are separate licensed plugins. To use them with the Apicurio plugin, you'll need to:
+The OpenAPI and AsyncAPI generators require an EventCatalog Scale license key. To use them with the Apicurio plugin, you'll need to:
 - Install the respective plugins: `npm install @eventcatalog/generator-openapi @eventcatalog/generator-asyncapi`
-- Obtain license keys from [EventCatalog Cloud](https://eventcatalog.cloud) (14-day free trial available)
-- Configure the license keys in your `.env` file:
-  - `EVENTCATALOG_LICENSE_KEY_OPENAPI=your-openapi-license-key`
-  - `EVENTCATALOG_LICENSE_KEY_ASYNCAPI=your-asyncapi-license-key`
+- Obtain an EventCatalog Scale license key from [EventCatalog Cloud](https://eventcatalog.cloud) (30-day free trial available)
+- Configure the license key in your `.env` file:
+  - `EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key`
 
 Learn more: [OpenAPI Plugin Docs](/docs/plugins/openapi/intro) | [AsyncAPI Plugin Docs](/docs/plugins/asyncapi/intro)
 :::
@@ -534,11 +533,10 @@ When using nested generators, make sure to:
 ```bash
 npm install @eventcatalog/generator-openapi @eventcatalog/generator-asyncapi
 ```
-2. Obtain license keys from [EventCatalog Cloud](https://eventcatalog.cloud) (14-day free trial available)
-3. Add the license keys to your `.env` file:
+2. Obtain an EventCatalog Scale license key from [EventCatalog Cloud](https://eventcatalog.cloud) (30-day free trial available)
+3. Add the license key to your `.env` file:
 ```bash
-EVENTCATALOG_LICENSE_KEY_OPENAPI=your-openapi-license-key
-EVENTCATALOG_LICENSE_KEY_ASYNCAPI=your-asyncapi-license-key
+EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
 ```
 
 See [OpenAPI Plugin Docs](/docs/plugins/openapi/intro) | [AsyncAPI Plugin Docs](/docs/plugins/asyncapi/intro) for more information.

package/dist/docs/plugins/apicurio/03-features.md

@@ -65,8 +65,8 @@ One of the powerful features of the Apicurio Registry plugin is its ability to w
 
 You can store OpenAPI and AsyncAPI specifications in your Apicurio Registry and use them to generate comprehensive service documentation automatically.
 
-:::info Plugin Licenses Required
-The OpenAPI and AsyncAPI generators are separate licensed plugins. You'll need to obtain license keys for each plugin you want to use from [EventCatalog Cloud](https://eventcatalog.cloud). A 14-day free trial is available for both plugins.
+:::info EventCatalog Scale License Required
+The OpenAPI and AsyncAPI generators require an EventCatalog Scale license key. You can get a 30-day free trial from [EventCatalog Cloud](https://eventcatalog.cloud).
 
 See the [OpenAPI Plugin](/docs/plugins/openapi/intro) and [AsyncAPI Plugin](/docs/plugins/asyncapi/intro) documentation for more details on installation and configuration.
 :::

package/dist/docs/plugins/asyncapi/00-intro.md

@@ -56,11 +56,11 @@ The EventCatalog AsyncAPI plugin let's you define 1 or many AsyncAPI files. When
 
 ## Commercial and License
 
-This plugin requires a license key to be used. 
+This plugin requires an EventCatalog Scale license key to be used.
 
-You can get a 14 day trial license key to try the plugin out by going to [EventCatalog Cloud](https://eventcatalog.cloud).
+You can get a 30-day trial Scale license key by going to [EventCatalog Cloud](https://eventcatalog.cloud).
 
-After the trial you can purchase a license to continue using this plugin, we have different plans to suit your organization. 
+After the trial, you can continue using this plugin with EventCatalog Scale. 
 
 See [pricing](/pricing) for more information.
 
@@ -69,13 +69,13 @@ _Have any questions? You can email us at `hello@eventcatalog.dev`._
 ## License FAQ
 
 ### What is the license key for?
-The license key is required to use the OpenAPI plugin with EventCatalog. It helps support ongoing development and maintenance of the plugin and project.
+The EventCatalog Scale license key is required to use the OpenAPI plugin with EventCatalog. It helps support ongoing development and maintenance of the plugin and project.
 
-### How do I get a license key?
-You can obtain a license key by visiting [EventCatalog Cloud](https://eventcatalog.cloud). New users can start with a 14-day free trial.
+### How do I get an EventCatalog Scale license key?
+You can obtain an EventCatalog Scale license key by visiting [EventCatalog Cloud](https://eventcatalog.cloud). New users can start with a 30-day free trial.
 
 ### Terms
-- **Trial Period**: 14 days free trial no credit card required
+- **Trial Period**: 30-day free trial no credit card required
 - **Support**: Discord community support (extra for priority support)
 
-After your trial period ends, you can purchase a full license through [EventCatalog Cloud](https://eventcatalog.cloud) to continue using the plugin.
+After your trial period ends, you can continue with EventCatalog Scale through [EventCatalog Cloud](https://eventcatalog.cloud).

package/dist/docs/plugins/asyncapi/01-installation.md

@@ -80,36 +80,36 @@ generators: [
 
 ### Configure license key
 
-The EventCatalog AsyncAPI plugin requires a license key to work with EventCatalog.
+The EventCatalog AsyncAPI plugin requires an EventCatalog Scale license key to work with EventCatalog.
 
-You can get a trial license key from [EventCatalog Cloud](https://eventcatalog.cloud).
+You can get a trial Scale license key from [EventCatalog Cloud](https://eventcatalog.cloud).
 
 You have a few options for setting the license key:
 
 1. [Setting license key in `.env` file (recommended)](#setting-license-key-in-env-file-recommended)
 2. [Setting license key in eventcatalog.config.js](#setting-license-key-in-eventcatalogconfigjs)
 
-#### 1. Setting license key in `.env` file (recommended)
+#### 1. Setting license key in `.env` file (recommended) {#setting-license-key-in-env-file-recommended}
 
 <AddedIn version="2.35.4" />
 
 Create a `.env` file in the root of your project and add the following:
 
 ```bash title=".env"
-EVENTCATALOG_LICENSE_KEY_ASYNCAPI=your-license-key
+EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
 ```
 
-:::tip Using an older version of EventCatalog?
+:::tip Using an Older API Key?
 
-If you are using an older version of EventCatalog that does not support the `.env` file, you can just export the license key as an environment variable.
+If you already have an older AsyncAPI plugin key, you can still use it with the AsyncAPI-specific environment variable.
 
-```bash title="Setting license key in environment variables"
-export EVENTCATALOG_LICENSE_KEY_ASYNCAPI=your-license-key
+```bash title=".env"
+EVENTCATALOG_LICENSE_KEY_ASYNCAPI=your-license-key
 ```
 
 :::
 
-#### 2. Setting license key in eventcatalog.config.js
+#### 2. Setting license key in eventcatalog.config.js {#setting-license-key-in-eventcatalogconfigjs}
 
 If you prefer, you can set the license key in the `eventcatalog.config.js` file
 using the `licenseKey` property in the EventCatalog AsyncAPI plugin.
@@ -120,7 +120,7 @@ export default {
     [
       '@eventcatalog/generator-asyncapi',
       {
-        licenseKey: '[INSERT_YOUR_LICENSE_KEY]', // or process.env.EVENTCATALOG_LICENSE_KEY_ASYNCAPI
+        licenseKey: '[INSERT_YOUR_LICENSE_KEY]', // or process.env.EVENTCATALOG_SCALE_LICENSE_KEY
       },
     ],
   ],
@@ -152,4 +152,3 @@ npm run dev
 If you get stuck, find an issue or need help, please raise an issue on [GitHub](https://github.com/event-catalog/eventcatalog/issues) or join our [Discord community](https://eventcatalog.dev/discord).
 
 
-

package/dist/docs/plugins/asyncapi/02-plugin-configuration.md

@@ -22,7 +22,7 @@ The EventCatalog AsyncAPI plugin is configured in the `eventcatalog.config.js` f
 | Option | Type | Required | Description |
 |--------|------|----------|-------------|
 | `services` | `Service[]` | Yes | List of AsyncAPI files to add to your catalog |
-| `licenseKey` | string | Yes* | License key for the plugin. Get a 14-day trial at [EventCatalog Cloud](https://eventcatalog.cloud). Can also be set via `EVENTCATALOG_LICENSE_KEY_ASYNCAPI` environment variable. |
+| `licenseKey` | string | Yes* | EventCatalog Scale license key. Get a 30-day trial at [EventCatalog Cloud](https://eventcatalog.cloud). Can also be set via the `EVENTCATALOG_SCALE_LICENSE_KEY` environment variable. |
 
 ### Service Configuration
 
@@ -32,12 +32,13 @@ Each service in the `services` array requires the following properties:
 |----------|------|----------|-------------|
 | `id` | string | Yes | EventCatalog ID for the service. |
 | `path` | string | Yes | Path to your AsyncAPI file or remote URL to the AsyncAPI file |
+| `version` | string | No | Version for the generated EventCatalog service. If not provided, the version from the AsyncAPI `info.version` field is used. Messages and channels default to this version unless overridden by `x-eventcatalog-message-version` or `x-eventcatalog-channel-version`. |
 | `name` | string | No | Display name for the service. If not provided, the specification will be used. _Added in v4.5.3_|
 | `summary` | string | No | Short summary of the service. If not provided, the specification will be used. _Added in v4.5.3_|
 | `owners` | string[] | No | Owners of the service. You can assign EventCatalog users or teams to services. Setting owners on the service will also set the owners of the messages in the AsyncAPI file. If owners are already set on any resource, those owners are persisted. |
 | `generateMarkdown` | function | - | Function to override the default markdown generation for the service. See [Markdown templates](#markdown-templates) for more information. |
-| `writesTo` | array[\{id: string, version?: string\}] | No | Array of [data stores](/docs/development/guides/data/introduction) id and version (optional) that the service writes to. (Added in v4.5.4) |
-| `readsFrom` | array[\{id: string, version?: string\}] | No | Array of [data stores](/docs/development/guides/data/introduction) id and version (optional) that the service reads from. (Added in v4.5.4) |
+| `writesTo` | array[\{id: string, version?: string\}] | No | Array of [data stores](/docs/development/guides/resources/data/introduction) id and version (optional) that the service writes to. (Added in v4.5.4) |
+| `readsFrom` | array[\{id: string, version?: string\}] | No | Array of [data stores](/docs/development/guides/resources/data/introduction) id and version (optional) that the service reads from. (Added in v4.5.4) |
 | `headers` | `Record<string, string>` | No | HTTP headers for authenticated remote URLs (e.g., `{ Authorization: 'Bearer token' }`). Used when fetching AsyncAPI files from URLs that require authentication. |
 
 ## Optional Configuration Options
@@ -103,7 +104,7 @@ export default {
       '@eventcatalog/generator-asyncapi',
       {
         services: [
-          { path: path.join(__dirname, 'asyncapi-files', 'orders-service.yml'), id: 'Orders Service' },
+          { path: path.join(__dirname, 'asyncapi-files', 'orders-service.yml'), id: 'Orders Service', version: '1.0.0' },
           { path: path.join(__dirname, 'asyncapi-files', 'order-fulfillment-service.yml'), id: 'Order Fulfillment' },
           { path: path.join(__dirname, 'asyncapi-files', 'inventory-service.yml'), id: 'Inventory Service' },
         ],
@@ -309,4 +310,3 @@ or refer to the [AsyncAPI examples on GitHub](https://github.com/event-catalog/g
 
 
 
-

package/dist/docs/plugins/asyncapi/03-features.md

@@ -17,9 +17,9 @@ import TabItem from '@theme/TabItem';
 | [Mapping messages events, commands or queries](#mapping-messages-events-commands-or-queries) | AsyncAPI does not distinguish between commands, events and queries, everything is a message. Using the EventCatalog custom AsyncAPI [extension](https://www.asyncapi.com/docs/concepts/asyncapi-document/extending-specification) `x-eventcatalog-message-type` you can specify if your messages are events, command or queries. |
 | [Defining message ownership roles](#defining-message-ownership-roles) | AsyncAPI specification files do not define who owns the message and it's contract. Your AsyncAPI file my define messages your service consumes and produces but that service may not be the service that owns it's contract. (e.g An order service that consumes a Payment event. The order service (AsyncAPI file) would specify it consumes the payment event, but it is not the owner of the contract or event). |
 | [Defining message versions](#defining-message-versions) | In EventCatalog you can version your domains, services and all your messages. This can be useful as you can specify which version of a message your service produces or consumes. |
-| [Mapping channels into EventCatalog](#mapping-channels-into-eventcatalog) | EventCatalog supports [Channels](/docs/development/guides/channels/introduction) ([see demo](https://demo.eventcatalog.dev/docs/channels/inventory.%7Benv%7D.events/1.0.0)). This let's you document how messages or organized and transported in your event-driven architecture. |
+| [Mapping channels into EventCatalog](#mapping-channels-into-eventcatalog) | EventCatalog supports [Channels](/docs/development/guides/resources/messages/message-channels/introduction) ([see demo](https://demo.eventcatalog.dev/docs/channels/inventory.%7Benv%7D.events/1.0.0)). This let's you document how messages or organized and transported in your event-driven architecture. |
 | [Creating draft domains, services and messages](#creating-draft-domains-services-and-messages) | You can create draft domains, services and messages in EventCatalog from your AsyncAPI files. This will be used to mark the resources as draft in EventCatalog. |
-| [Persist markdown](#persist-markdown) | When you generate your AsyncAPI files your markdown on your domains,services, and messages in EventCatalog is persisted between versions. This allows you to add [custom components](/docs/custom-components), our [MDX components](/docs/components) and customize your EventCatalog pages without losing changes when you version your AsyncAPI files. |
+| [Persist markdown](#persist-markdown) | When you generate your AsyncAPI files your markdown on your domains,services, and messages in EventCatalog is persisted between versions. This allows you to add [custom components](/docs/components/custom-components), our [MDX components](/docs/components) and customize your EventCatalog pages without losing changes when you version your AsyncAPI files. |
 | [Fetch AsyncAPI files by URL](#fetch-asyncapi-files-by-url) | You can use the `path` property of the generator to specify a path to your local file system or an external URL, or you can mix both of them. |
 | [Authenticate remote URLs](#authenticate-remote-urls) | Use HTTP headers to access protected AsyncAPI files from authenticated URLs. |
 | [Automatic versioning](#automatic-versioning) | When you change versions in your AsyncAPI file and run generate, your services and messages are automatically versioned. This allows you to keep an audit log of changes between AsyncAPI files, schemas and more. |
@@ -182,7 +182,7 @@ UserSignedUp:
 
 <AddedIn version="2.7.0" pkg="@eventcatalog/generator-asyncapi" url="https://github.com/event-catalog/generators/releases/tag/v"/>
 
-EventCatalog supports [Channels](/docs/development/guides/channels/introduction) ([see demo](https://demo.eventcatalog.dev/docs/channels/inventory.%7Benv%7D.events/1.0.0)). This let's you document how messages or organized and transported in your event-driven architecture.
+EventCatalog supports [Channels](/docs/development/guides/resources/messages/message-channels/introduction) ([see demo](https://demo.eventcatalog.dev/docs/channels/inventory.%7Benv%7D.events/1.0.0)). This let's you document how messages or organized and transported in your event-driven architecture.
 
 ![Example](../../../docs/development/guides/img/channels/channels-example.png)
 
@@ -581,7 +581,7 @@ _Example of a deprecated resource in EventCatalog:_
 
 When you generate your AsyncAPI files your markdown on your domains,services, and messages in EventCatalog is persisted between versions.
 
-This allows you to add [custom components](/docs/custom-components), our [MDX components](/docs/components) and customize your EventCatalog pages without losing changes when you version your AsyncAPI files.
+This allows you to add [custom components](/docs/components/custom-components), our [MDX components](/docs/components) and customize your EventCatalog pages without losing changes when you version your AsyncAPI files.
 
 ### Fetch AsyncAPI files by URL
 
@@ -641,7 +641,7 @@ The headers are passed with every HTTP request when fetching the AsyncAPI file f
 
 When you change versions in your AsyncAPI file and run generate, your services and messages are automatically versioned. This allows you to keep an audit log of changes between AsyncAPI files, schemas and more.
 
-You can also add changelogs between different versions of your services and messages. [Read here for more information](/docs/development/guides/messages/common/changelog).
+You can also add changelogs between different versions of your services and messages. [Read here for more information](/docs/development/guides/resources/messages/versioning-and-lifecycle/add-changelog).
 
 ### Downloading schemas
 
@@ -659,11 +659,11 @@ The generator supports AsyncAPI specification files up to and including version
 
 <AddedIn version="6.4.0" pkg="@eventcatalog/generator-asyncapi" url="https://github.com/event-catalog/generators/releases/tag/v"/>
 
-When a service sends or receives many messages, the [visualiser](/docs/development/guides/messages/common/grouping-messages) can become crowded. The `groupMessagesBy` option lets you automatically group related messages together so they collapse into a single node in the visualiser map, making your architecture easier to understand at a glance.
+When a service sends or receives many messages, the [visualiser](/docs/development/guides/resources/messages/connect-messages/group-messages) can become crowded. The `groupMessagesBy` option lets you automatically group related messages together so they collapse into a single node in the visualiser map, making your architecture easier to understand at a glance.
 
 ![Message group expanded in the visualiser](./img/message-group-expanded.png)
 
-To learn more about how groups work in the visualiser, see [Grouping messages](/docs/development/guides/messages/common/grouping-messages).
+To learn more about how groups work in the visualiser, see [Grouping messages](/docs/development/guides/resources/messages/connect-messages/group-messages).
 
 Set `groupMessagesBy: 'x-extension'` in your generator config, then add `x-eventcatalog-group` to each message in your AsyncAPI components.
 
@@ -690,9 +690,9 @@ components:
 When `parseChannels` is also enabled, group assignments and channel pointers are both preserved on the generated messages.
 
 :::tip
-Once grouped, messages appear as a compact stacked card in the visualiser. Click the group to expand it and see the full downstream graph — channels, consumers, and producers — just as if the messages were ungrouped. See [Grouping messages](/docs/development/guides/messages/common/grouping-messages) for more details.
+Once grouped, messages appear as a compact stacked card in the visualiser. Click the group to expand it and see the full downstream graph — channels, consumers, and producers — just as if the messages were ungrouped. See [Grouping messages](/docs/development/guides/resources/messages/connect-messages/group-messages) for more details.
 :::
 
 ### Example
 
-See the [eventcatalog-asyncapi-example](https://github.com/event-catalog/generators/tree/main/examples/generator-asyncapi) for a working example.
+See the [eventcatalog-asyncapi-example](https://github.com/event-catalog/generators/tree/main/examples/generator-asyncapi) for a working example.

package/dist/docs/plugins/aws-glue-registry/00-intro.md

@@ -75,11 +75,11 @@ If you would like to get started with our example project, [you can find it on G
 
 ## Commercial and License
 
-This plugin requires a license key to be used. 
+This plugin requires an EventCatalog Scale license key to be used.
 
-You can get a 14 day trial license key to try the plugin out by going to [EventCatalog Cloud](https://eventcatalog.cloud).
+You can get a 30-day trial Scale license key by going to [EventCatalog Cloud](https://eventcatalog.cloud).
 
-After the trial you can purchase a license to continue using this plugin, we have different plans to suit your organization. 
+After the trial, you can continue using this plugin with EventCatalog Scale. 
 
 See [pricing](/pricing) for more information.
 
@@ -88,16 +88,16 @@ _Have any questions? You can email us at `hello@eventcatalog.dev`._
 ## License FAQ
 
 ### What is the license key for?
-The license key is required to use the AWS Glue Schema Registry plugin with EventCatalog. It helps support ongoing development and maintenance of the plugin and project.
+The EventCatalog Scale license key is required to use the AWS Glue Schema Registry plugin with EventCatalog. It helps support ongoing development and maintenance of the plugin and project.
 
-### How do I get a license key?
-You can obtain a license key by visiting [EventCatalog Cloud](https://eventcatalog.cloud). New users can start with a 14-day free trial.
+### How do I get an EventCatalog Scale license key?
+You can obtain an EventCatalog Scale license key by visiting [EventCatalog Cloud](https://eventcatalog.cloud). New users can start with a 30-day free trial.
 
 ### Terms
-- **Trial Period**: 14 days free trial no credit card required
+- **Trial Period**: 30-day free trial no credit card required
 - **Support**: Discord community support (extra for priority support)
 
-After your trial period ends, you can purchase a full license through [EventCatalog Cloud](https://eventcatalog.cloud) to continue using the plugin.
+After your trial period ends, you can continue with EventCatalog Scale through [EventCatalog Cloud](https://eventcatalog.cloud).
 
 ## Issues
 

package/dist/docs/plugins/aws-glue-registry/00a-installation.md

@@ -168,24 +168,34 @@ generators: [
 
 ### Configure license key
 
-The EventCatalog AWS Glue Schema Registry plugin requires a license key to work with EventCatalog.
+The EventCatalog AWS Glue Schema Registry plugin requires an EventCatalog Scale license key to work with EventCatalog.
 
-You can get a trial license key from [EventCatalog Cloud](https://eventcatalog.cloud).
+You can get a trial Scale license key from [EventCatalog Cloud](https://eventcatalog.cloud).
 
 You have a few options for setting the license key:
 
 1. [Setting license key in `.env` file (recommended)](#setting-license-key-in-env-file-recommended)
 2. [Setting license key in eventcatalog.config.js](#setting-license-key-in-eventcatalogconfigjs)
 
-#### 1. Setting license key in `.env` file (recommended)
+#### 1. Setting license key in `.env` file (recommended) {#setting-license-key-in-env-file-recommended}
 
 Create a `.env` file in the root of your project and add the following:
 
+```bash title=".env"
+EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
+```
+
+:::tip Using an Older API Key?
+
+If you already have an older AWS Glue Schema Registry plugin key, you can still use it with the plugin-specific environment variable.
+
 ```bash title=".env"
 EVENTCATALOG_LICENSE_KEY_AWS_GLUE_SCHEMA_REGISTRY=your-license-key
 ```
 
-#### 2. Setting license key in eventcatalog.config.js
+:::
+
+#### 2. Setting license key in eventcatalog.config.js {#setting-license-key-in-eventcatalogconfigjs}
 
 If you prefer, you can set the license key in the `eventcatalog.config.js` file
 using the `licenseKey` property in the EventCatalog AWS Glue Schema Registry plugin.
@@ -196,7 +206,7 @@ export default {
     [
       '@eventcatalog/generator-aws-glue',
       {
-        licenseKey: '[INSERT_YOUR_LICENSE_KEY]', // or process.env.EVENTCATALOG_LICENSE_KEY_AWS_GLUE_SCHEMA_REGISTRY
+        licenseKey: '[INSERT_YOUR_LICENSE_KEY]', // or process.env.EVENTCATALOG_SCALE_LICENSE_KEY
       },
     ],
   ],
@@ -302,4 +312,4 @@ Once configured, generate your catalog:
 npm run generate
 ```
 
-This will connect to your AWS Glue Schema Registry and generate EventCatalog documentation for all your schemas.
+This will connect to your AWS Glue Schema Registry and generate EventCatalog documentation for all your schemas.

package/dist/docs/plugins/aws-glue-registry/01-features.md

@@ -218,7 +218,7 @@ When multiple filter criteria are specified in a single filter object, ALL crite
 
 Your markdown is persisted between generation runs on EventCatalog. Initially the generator will generate markdown for you for your domains, services and events, but any edits to the markdown file will be persisted between versions.
 
-This allows you to add [custom components](/docs/custom-components), our [MDX components](/docs/components) and customize your EventCatalog pages without losing changes when your schemas are versioned.
+This allows you to add [custom components](/docs/components/custom-components), our [MDX components](/docs/components) and customize your EventCatalog pages without losing changes when your schemas are versioned.
 
 This can be useful for adding extra additional context to your events, example payloads, example CLI commands on how to produce/consume them and any other useful information.
 
@@ -284,4 +284,4 @@ generators: [
 ],
 ```
 
-This is useful for organizations that centralize schema management across multiple AWS accounts.
+This is useful for organizations that centralize schema management across multiple AWS accounts.

package/dist/docs/plugins/azure-schema-registry/00-intro.md

@@ -29,11 +29,11 @@ The EventCatalog Azure Schema Registry plugin can provide you with many features
 
 - Keep your schemas in sync with your architecture documentation
 - Automatic versioning; as your schemas change they are versioned in EventCatalog alongside your documentation
-- Understand how your schemas have evolved over time with the Schema diff explorer with the [Schema Explorer](/docs/development/guides/schemas/schema-explorer)
+- Understand how your schemas have evolved over time with the Schema diff explorer with the [Schema Explorer](/docs/development/guides/resources/schemas/explore-schemas/schema-explorer)
 - Add meaning (markdown) to your schemas. Provide business context to your schemas and add value
 - Quickly find who is producing or consuming your schemas
 - Visualize your Azure Event Hubs architecture with the [EventCatalog Visualizer](/features/visualization)
-- Download and view schemas in EventCatalog (Avro, JSON Schema) or through the [Schema API](/docs/development/guides/schemas/schema-api)
+- Download and view schemas in EventCatalog (Avro, JSON Schema) or through the [Schema API](/docs/development/guides/resources/schemas/schema-api)
 - Use [EventCatalog MCP server](/docs/development/ask-your-architecture/mcp-server/introduction) to get schemas for your LLMs
 
 ### How it works
@@ -67,11 +67,11 @@ We use the REST API because it is simpler and more flexible. It doesn't require
 
 ## Commercial and License
 
-This plugin requires a license key to be used.
+This plugin requires an EventCatalog Scale license key to be used.
 
-You can get a 14 day trial license key to try the plugin out by going to [EventCatalog Cloud](https://eventcatalog.cloud).
+You can get a 30-day trial Scale license key by going to [EventCatalog Cloud](https://eventcatalog.cloud).
 
-After the trial you can purchase a license to continue using this plugin, we have different plans to suit your organization based on where you are in your governance and documentation journey.
+After the trial, you can continue using this plugin with EventCatalog Scale.
 
 See [pricing](/pricing) for more information.
 
@@ -80,13 +80,13 @@ _Have any questions? You can email us at `hello@eventcatalog.dev`._
 ## License FAQ
 
 ### What is the license key for?
-The license key is required to use the Azure Schema Registry plugin with EventCatalog. It helps support ongoing development and maintenance of the plugin and project.
+The EventCatalog Scale license key is required to use the Azure Schema Registry plugin with EventCatalog. It helps support ongoing development and maintenance of the plugin and project.
 
-### How do I get a license key?
-You can obtain a license key by visiting [EventCatalog Cloud](https://eventcatalog.cloud). New users can start with a 14-day free trial.
+### How do I get an EventCatalog Scale license key?
+You can obtain an EventCatalog Scale license key by visiting [EventCatalog Cloud](https://eventcatalog.cloud). New users can start with a 30-day free trial.
 
 ### Terms
-- **Trial Period**: 14 days free trial no credit card required
+- **Trial Period**: 30-day free trial no credit card required
 - **Support**: Discord community support (extra for priority support)
 
-After your trial period ends, you can purchase a full license through [EventCatalog Cloud](https://eventcatalog.cloud) to continue using the plugin.
+After your trial period ends, you can continue with EventCatalog Scale through [EventCatalog Cloud](https://eventcatalog.cloud).

package/dist/docs/plugins/azure-schema-registry/01-installation.md

@@ -26,9 +26,9 @@ npm i @eventcatalog/generator-azure-schema-registry
 ```
 
 :::info License Key
-The EventCatalog Azure Schema Registry plugin requires a license key to work with EventCatalog.
+The EventCatalog Azure Schema Registry plugin requires an EventCatalog Scale license key to work with EventCatalog.
 
-You can get a trial license key from [EventCatalog Cloud](https://eventcatalog.cloud).
+You can get a trial Scale license key from [EventCatalog Cloud](https://eventcatalog.cloud).
 :::
 
 ## Configuration
@@ -201,9 +201,9 @@ The EventCatalog Azure Schema Registry plugin uses Azure's REST API with Bearer
 
 ### Configure Azure Schema Registry License Key
 
-The EventCatalog Azure Schema Registry plugin requires a license key to work with EventCatalog.
+The EventCatalog Azure Schema Registry plugin requires an EventCatalog Scale license key to work with EventCatalog.
 
-You can get a trial license key from [EventCatalog Cloud](https://eventcatalog.cloud).
+You can get a trial Scale license key from [EventCatalog Cloud](https://eventcatalog.cloud).
 
 
 ---
@@ -286,12 +286,22 @@ Create or update your `.env` file in your EventCatalog project root:
 
 ```bash title=".env"
 # EventCatalog license key
-EVENTCATALOG_LICENSE_KEY_AZURE_SCHEMA_REGISTRY=your-license-key
+EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
 
 # Azure Schema Registry access token (paste the token from step 1)
 AZURE_SCHEMA_REGISTRY_TOKEN=eyJ0eXAiOiJKV1QiLCJhbGciOi...
 ```
 
+:::tip Using an Older API Key?
+
+If you already have an older Azure Schema Registry plugin key, you can still use it with the plugin-specific environment variable.
+
+```bash title=".env"
+EVENTCATALOG_LICENSE_KEY_AZURE_SCHEMA_REGISTRY=your-license-key
+```
+
+:::
+
 **Step 3: Run the Generator**
 
 ```bash