@eventcatalog/core 4.1.3 → 4.1.5

package/dist/docs/plugins/azure-schema-registry/02-plugin-configuration.md

@@ -21,7 +21,7 @@ The plugin uses Azure's REST API with Bearer token authentication. You must set
 
 ```bash
 # EventCatalog license key
-export EVENTCATALOG_LICENSE_KEY_AZURE_SCHEMA_REGISTRY=your-license-key
+export EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
 
 # Azure Schema Registry access token
 export AZURE_SCHEMA_REGISTRY_TOKEN=your-azure-access-token
@@ -57,8 +57,8 @@ You can assign schemas to services (producers/consumers) in your architecture.
 | `services[].version` | `string` | - | Version of the service (e.g., `1.0.0`). |
 | `services[].sends` | `array` | - | Array of schema filters for messages this service sends. |
 | `services[].receives` | `array` | - | Array of schema filters for messages this service receives. |
-| `services[].writesTo` | `array[{id: string, version?: string}]` | - | Array of [data stores](/docs/development/guides/data/introduction) id and version (optional) that the service writes to. |
-| `services[].readsFrom` | `array[{id: string, version?: string}]` | - | Array of [data stores](/docs/development/guides/data/introduction) id and version (optional) that the service reads from. |
+| `services[].writesTo` | `array[{id: string, version?: string}]` | - | Array of [data stores](/docs/development/guides/resources/data/introduction) id and version (optional) that the service writes to. |
+| `services[].readsFrom` | `array[{id: string, version?: string}]` | - | Array of [data stores](/docs/development/guides/resources/data/introduction) id and version (optional) that the service reads from. |
 
 ### Schema Filters (sends/receives)
 
@@ -87,7 +87,7 @@ You can define and assign domains to organize your services.
 
 | Option | Type | Default | Description |
 |--------|------|---------|-------------|
-| `licenseKey` | `string` | From env var | EventCatalog license key. Can also be set via `EVENTCATALOG_LICENSE_KEY_AZURE_SCHEMA_REGISTRY` environment variable. |
+| `licenseKey` | `string` | From env var | EventCatalog Scale license key. Can also be set via the `EVENTCATALOG_SCALE_LICENSE_KEY` environment variable. |
 
 ## Example Configurations
 

package/dist/docs/plugins/azure-schema-registry/04-examples.md

@@ -106,7 +106,7 @@ Each example includes:
 - Azure CLI installed ([Install guide](https://docs.microsoft.com/en-us/cli/azure/install-azure-cli))
 - Azure account with Event Hubs namespace
 - Azure Schema Registry with sample schemas
-- EventCatalog license key ([14-day trial available](https://eventcatalog.cloud))
+- EventCatalog license key ([30-day trial available](https://eventcatalog.cloud))
 - Appropriate Azure permissions (`Azure Event Hubs Data Receiver` role)
 
 ### Quick Start

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

@@ -53,13 +53,13 @@ _Note: If you want to embed private EventCatalog instances, raise an issue on Gi
 
 ## Commercial Use
 
-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).
 
 You can try the Backstage plugin, or use EventCatalog Scale (as it's already included).
 
-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.
 

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

@@ -24,11 +24,11 @@ We recommend using the latest version of the plugin. You can read the [migration
 
 ## Configuring EventCatalog for Backstage
 
-You will need a license key to use the backstage integration, this is either the SCALE license key or the Backstage license key.
+You will need an EventCatalog Scale license key to use the Backstage integration.
 
-You can get a 14 day trial license key from [EventCatalog Cloud](https://eventcatalog.cloud).
+You can get a 30-day trial Scale license key from [EventCatalog Cloud](https://eventcatalog.cloud).
 
-Once you have a license key for Backstage, you will need to build and deploy your EventCatalog with the license key set.
+Once you have an EventCatalog Scale license key, you will need to build and deploy your EventCatalog with the license key set.
 
 #### 1. Setting license key in `.env` file (recommended)
 
@@ -37,23 +37,15 @@ Once you have a license key for Backstage, you will need to build and deploy you
 Create a `.env` file in the root of your project and add the following:
 
 ```bash title=".env"
-# If you have a Backstage license key
-EVENTCATALOG_LICENSE_KEY_BACKSTAGE=your-license-key
-
-# If you have a SCALE license key
 EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
 ```
 
-:::tip Using an older version of EventCatalog?
-
-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.
+:::tip Using an Older API Key?
 
-```bash title="Setting license key in environment variables"
-# If you have a Backstage license key
-export EVENTCATALOG_LICENSE_KEY_BACKSTAGE=your-license-key
+If you already have an older Backstage plugin key, you can still use it with the Backstage-specific environment variable.
 
-# If you have a SCALE license key
-export EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
+```bash title=".env"
+EVENTCATALOG_LICENSE_KEY_BACKSTAGE=your-license-key
 ```
 
 :::

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

@@ -61,11 +61,11 @@ The EventCatalog Confluent Schema Registry plugin is a generator. It will import
 
 ## 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.
 
@@ -78,13 +78,13 @@ 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 Confluent 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 Confluent 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/confluent-schema-registry/01-installation.md

@@ -169,20 +169,30 @@ In this example we configure the plugin twice, the first time we import and crea
 
 The EventCatalog Confluent Schema Registry plugin requires API keys in your environment variables.
 
-1. A license key for the Confluent Schema Registry plugin (14 days trial, at [EventCatalog Cloud](https://eventcatalog.cloud))
+1. An EventCatalog Scale license key for the Confluent Schema Registry plugin (30-day trial, at [EventCatalog Cloud](https://eventcatalog.cloud))
 2. Confluent Schema Registry API keys (found in the [Confluent Cloud](https://confluent.cloud) console)
 
 Create a `.env` file in the root, and add your keys to the project.
 
 ```bash title=".env"
 # EventCatalog license key
-EVENTCATALOG_LICENSE_KEY_CONFLUENT_SCHEMA_REGISTRY=your-license-key
+EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
 
 # Confluent Schema Registry API Keys
 CONFLUENT_SCHEMA_REGISTRY_KEY=your-confluent-schema-registry-key
 CONFLUENT_SCHEMA_REGISTRY_SECRET=your-confluent-schema-registry-key-secret
 ```
 
+:::tip Using an Older API Key?
+
+If you already have an older Confluent Schema Registry plugin key, you can still use it with the plugin-specific environment variable.
+
+```bash title=".env"
+EVENTCATALOG_LICENSE_KEY_CONFLUENT_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.
@@ -219,5 +229,3 @@ If you get stuck, find an issue or need help, please raise an issue on [GitHub](
 
 You can also find some examples of the plugin in action in our examples repository: [eventcatalog/examples](https://github.com/event-catalog/generators/tree/main/examples/generator-confluent-schema-registry).
 
-
-

package/dist/docs/plugins/confluent-schema-registry/02-plugin-configuration.md

@@ -49,8 +49,8 @@ You can assign the schemas to a producer or consumer (service).
 | `services.id` | string | - | EventCatalog ID for the service. |
 | `services.sends` | Filter | - | Configuration to assign schemas to a producer. The schemas and topic defined here will be assigned to the producer. |
 | `services.receives` | Filter | - | Configuration to assign schemas to a consumer. The schemas and topic defined here will be assigned to the consumer. |
-| `services.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 v0.2.1) |
-| `services.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 v0.2.1) |
+| `services.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 v0.2.1) |
+| `services.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 v0.2.1) |
 
 ### Topics
 
@@ -60,7 +60,7 @@ Schemas are mapped to their topics.
 
 | Option | Type | Default | Description |
 |--------|------|---------|-------------|
-| `topics` | object | - | Optional list of topics to assign the schemas to. (optional). [These are documented as channels](/docs/development/guides/channels/introduction) in EventCatalog. |
+| `topics` | object | - | Optional list of topics to assign the schemas to. (optional). [These are documented as channels](/docs/development/guides/resources/messages/message-channels/introduction) in EventCatalog. |
 | `topics.id` | string | - | EventCatalog ID for the topic (e.g `orders-topic`). |
 | `topics.name` | string | - | Name of the topic (e.g `Orders Topic`). |
 | `topics.address` | string | - | Address of the topic (e.g `kafka-cluster-1.us-east-1.confluent.cloud:9092`). |

package/dist/docs/plugins/eventbridge/00a-installation.md

@@ -186,37 +186,37 @@ generators: [
 
 ### Configure license key
 
-The EventBridge plugin requires a license key to work with EventCatalog.
+The EventBridge plugin requires an EventCatalog Scale license key to work with EventCatalog.
 
-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).
 
 You have a few options for setting the license key:
 
-1. [Setting license key in `.env` file (recommended)](#1-setting-license-key-in-env-file-recommended)
-2. [Setting license key in eventcatalog.config.js](#2-setting-license-key-in-eventcatalogconfigjs)
+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_EVENTBRIDGE=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 EventBridge plugin key, you can still use it with the EventBridge-specific environment variable.
 
-```bash title="Setting license key in environment variables"
-export EVENTCATALOG_LICENSE_KEY_EVENTBRIDGE=your-license-key
+```bash title=".env"
+EVENTCATALOG_LICENSE_KEY_EVENTBRIDGE=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 EventBridge plugin.
@@ -227,7 +227,7 @@ export default {
     [
       '@eventcatalog/generator-eventbridge',
       {
-        licenseKey: '[INSERT_YOUR_LICENSE_KEY]', // or process.env.EVENTCATALOG_LICENSE_KEY_EVENTBRIDGE
+        licenseKey: '[INSERT_YOUR_LICENSE_KEY]', // or process.env.EVENTCATALOG_SCALE_LICENSE_KEY
         region: 'us-east-1',
         registryName: 'discovered-schemas'
       },
@@ -288,11 +288,11 @@ It's recommended you create a new IAM user with the following policy.
 
 ## 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.
 
@@ -301,17 +301,17 @@ _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).
 
 ## Issues
 
-If you have any problems or feature requests please feel free to raise them on GitHub. https://github.com/event-catalog/generators
+If you have any problems or feature requests please feel free to raise them on GitHub. https://github.com/event-catalog/generators

package/dist/docs/plugins/eventbridge/01-features.md

@@ -154,7 +154,7 @@ generators: [
 
 <AddedIn version="1.2.0" pkg="@eventcatalog/generator-eventbridge" url="https://github.com/event-catalog/generator-eventbridge/releases/tag/v"/>
 
-EventCatalog [supports channels as resources](/docs/development/guides/channels/introduction). This let's you document your event buses in EventCatalog.
+EventCatalog [supports channels as resources](/docs/development/guides/resources/messages/message-channels/introduction). This let's you document your event buses in EventCatalog.
 
 EventCatalog will use your Event Bus as a channel, the protocol for the channel is set to `eventbridge`.
 
@@ -196,7 +196,7 @@ generators: [
 
 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 events 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 events are versioned.
 
 This can be useful for adding extra additional context to your events, example payloads, example CLI commands on how to raise them and any other useful information.
 
@@ -222,4 +222,4 @@ Any version changes here will get copied over into EventCatalog.
 
 ### Downloading schemas
 
-The generator will try and download the JSONDraft4 and OpenAPI specifications for your events from EventBridge. These files will be attached to each even in EventCatalog. Users will be able to see and download these files.
+The generator will try and download the JSONDraft4 and OpenAPI specifications for your events from EventBridge. These files will be attached to each even in EventCatalog. Users will be able to see and download these files.

package/dist/docs/plugins/eventbridge/03-api.md

@@ -142,7 +142,7 @@ The EventBridge registry name for your schemas.
 
 - Type: `String`
 
-The license key for the EventBridge generator. You can get a 14 day trial license key to try the plugin out by going to [EventCatalog Cloud](https://eventcatalog.cloud).
+The license key for the EventBridge generator. You can get a 30-day trial Scale license key by going to [EventCatalog Cloud](https://eventcatalog.cloud).
 
 ```js title="eventcatalog.config.js"
 [
@@ -158,7 +158,7 @@ The license key for the EventBridge generator. You can get a 14 day trial licens
 You can also set the license key as an environment variable. If this is set on the machine the `licenseKey` is not required in the generator configuration.
 
 ```bash
-EVENTCATALOG_LICENSE_KEY_EVENTBRIDGE=YOUR_LICENSE_KEY
+EVENTCATALOG_SCALE_LICENSE_KEY=YOUR_SCALE_LICENSE_KEY
 ```
 :::
 
@@ -202,8 +202,8 @@ List of services to add and what events they publish (sends) and consume (receiv
 | sends.eventBusName            | optional | The name of the EventBus for the matched events. This will be displayed as an EventCatalog Channel. |
 | receives            | optional | The events the service receives (consumes). You can use [EventCatalog filters](/docs/plugins/eventbridge/intro#using-filters-to-map-events-to-your-services) to match your events. |
 | receives.eventBusName            | optional | The name of the EventBus for the matched events. This will be displayed as an EventCatalog Channel. |
-| writesTo            | optional | Array of [data stores](/docs/development/guides/data/introduction) ids that the service writes to. (Added in v3.2.2) |
-| readsFrom            | optional | Array of [data stores](/docs/development/guides/data/introduction) ids that the service reads from. (Added in v3.2.2) |
+| writesTo            | optional | Array of [data stores](/docs/development/guides/resources/data/introduction) ids that the service writes to. (Added in v3.2.2) |
+| readsFrom            | optional | Array of [data stores](/docs/development/guides/resources/data/introduction) ids that the service reads from. (Added in v3.2.2) |
 | writeToRoot            | optional | Write the service to the root of your catalog, ignoring the domain structure. [Useful if you have shared services between domains](/docs/plugins/eventbridge/03a-workflows#shared-services-between-domains) (Added in v3.3.0) |
 
 ### `domain` {#domain}
@@ -438,4 +438,4 @@ If you are using an older version of EventCatalog that does not support mdx file
 
 | Property name | Required | Options | Description                                                                   |
 | ------------- | -------- | -----------| ----------------------------------------------------------------------------- |
-| format            | optional (default 'mdx') | `md`, `mdx` | Specify the format of the markdown files that are generated. |
+| format            | optional (default 'mdx') | `md`, `mdx` | Specify the format of the markdown files that are generated. |

package/dist/docs/plugins/eventcatalog-federation/00-introduction.md

@@ -43,8 +43,8 @@ EventCatalog Federation is powered by the [EventCatalog Federation Generator](ht
 5. You use the federation generator to merge your teams catalogs into the main catalog
 6. You setup CI/CD to keep your main catalog up to date with your teams catalogs (or just rebuild every X time)
 
-To use the federation generator you will need a License Key from [EventCatalog Cloud](https://eventcatalog.cloud).
-You can get a free 14 day trial license key for the plugin.
+To use the federation generator you will need an EventCatalog Scale license key from [EventCatalog Cloud](https://eventcatalog.cloud).
+You can get a free 30-day trial Scale license key for the plugin.
 
 You can read more documentation:
 
@@ -55,15 +55,15 @@ You can read more documentation:
 
 ## Commercial Use
 
-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.
 
 _Have any questions? You can email us at `hello@eventcatalog.dev`._
 
 
-<a href="https://eventcatalog.cloud" target="_blank" className="bg-purple-500 hover:bg-purple-100 cursor-pointer hover:text-white !hover:underline px-2 py-1 rounded-md text-white ">Login to EventCatalog Dashboard</a>
+<a href="https://eventcatalog.cloud" target="_blank" className="bg-purple-500 hover:bg-purple-100 cursor-pointer hover:text-white !hover:underline px-2 py-1 rounded-md text-white ">Login to EventCatalog Dashboard</a>

package/dist/docs/plugins/eventcatalog-federation/01-installation.md

@@ -107,36 +107,36 @@ generators: [
 
 ### Configure license key
 
-The EventCatalog Federation plugin requires a license key to work with EventCatalog.
+The EventCatalog Federation 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_FEDERATION=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 Federation plugin key, you can still use it with the Federation-specific environment variable.
 
-```bash title="Setting license key in environment variables"
-export EVENTCATALOG_LICENSE_KEY_FEDERATION=your-license-key
+```bash title=".env"
+EVENTCATALOG_LICENSE_KEY_FEDERATION=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 Federation plugin.
@@ -147,7 +147,7 @@ export default {
     [
       '@eventcatalog/generator-federation',
       {
-        licenseKey: '[INSERT_YOUR_LICENSE_KEY]', // or process.env.EVENTCATALOG_LICENSE_KEY_FEDERATION
+        licenseKey: '[INSERT_YOUR_LICENSE_KEY]', // or process.env.EVENTCATALOG_SCALE_LICENSE_KEY
       },
     ],
   ],
@@ -179,4 +179,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/eventcatalog-federation/04-configuration.md

@@ -12,7 +12,7 @@ import Beta from '@site/src/components/MDX/Beta';
 
 <!-- <Beta /> -->
 <AddedIn version="2.18.0" />
-<PluginLicense url="/docs/development/guides/custom-components%20copy/introduction#commercial-use" />
+<PluginLicense url="/docs/plugins/eventcatalog-federation/intro#commercial-use" />
 
 EventCatalog Federation is powered by the [EventCatalog Federation Generator](https://github.com/event-catalog/generators), this let's you define the repositories you want to merge into your main catalog.
 
@@ -162,7 +162,7 @@ If you want to learn more about the federation generator you can read the [Event
 
 ### Running the generator
 
-You will need a license key to run the generator, you can get a free 14 day trial license key from [EventCatalog Cloud](https://eventcatalog.cloud).
+You will need an EventCatalog Scale license key to run the generator. You can get a free 30-day trial Scale license key from [EventCatalog Cloud](https://eventcatalog.cloud).
 
 Once you have configured the federation generator you can run the generator.
 

package/dist/docs/plugins/eventcatalog-federation/05-setup-team-catalog.md

@@ -12,7 +12,7 @@ import Beta from '@site/src/components/MDX/Beta';
 
 <!-- <Beta /> -->
 <AddedIn version="2.18.0" />
-<PluginLicense url="/docs/development/guides/custom-components%20copy/introduction#commercial-use" />
+<PluginLicense url="/docs/plugins/eventcatalog-federation/intro#commercial-use" />
 
 Multiple teams can own their own EventCatalog, this is useful if you have multiple teams that want to own their own EventCatalog / Documentation.
 
@@ -39,10 +39,10 @@ Your team can document their own services, messages and domains in this catalog,
 To help you get started:
 
 - [Creating domains in EventCatalog](/docs/development/guides/domains/introduction)
-- [Creating services in EventCatalog](/docs/development/guides/services/introduction)
-- [Creating events in EventCatalog](/docs/development/guides/messages/events/introduction)
-- [Creating commands in EventCatalog](/docs/development/guides/messages/commands/introduction)
-- [Creating queries in EventCatalog](/docs/development/guides/messages/queries/introduction)
+- [Creating services in EventCatalog](/docs/development/guides/resources/services/introduction)
+- [Creating events in EventCatalog](/docs/development/guides/resources/messages/message-types/events)
+- [Creating commands in EventCatalog](/docs/development/guides/resources/messages/message-types/commands)
+- [Creating queries in EventCatalog](/docs/development/guides/resources/messages/message-types/queries)
 
 Once your teams have created their own documentation you can [merge them into the main catalog using the federation generator](https://github.com/event-catalog/generators).
 
@@ -94,4 +94,3 @@ dependencies: {
 // rest of your config
 ```
 
-

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

@@ -64,11 +64,11 @@ Any documentation you add to your schemas in EventCatalog will persist between b
 
 ## 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.
 
@@ -81,13 +81,13 @@ 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 GitHub 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 GitHub 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/github/01-installation.md

@@ -198,15 +198,25 @@ In this example we:
 
 The EventCatalog GitHub plugin requires API keys in your environment variables.
 
-1. A license key for the GitHub plugin (14 days trial, at [EventCatalog Cloud](https://eventcatalog.cloud))
+1. An EventCatalog Scale license key for the GitHub plugin (30-day trial, at [EventCatalog Cloud](https://eventcatalog.cloud))
 
 Create a `.env` file in the root, and add your keys to the project.
 
 ```bash title=".env"
 # EventCatalog license key
+EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
+```
+
+:::tip Using an Older API Key?
+
+If you already have an older GitHub plugin key, you can still use it with the plugin-specific environment variable.
+
+```bash title=".env"
 EVENTCATALOG_LICENSE_KEY_GITHUB=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.
@@ -225,7 +235,7 @@ Set the `EVENTCATALOG_GITHUB_TOKEN` environment variable in your `.env` file.
 
 ```bash title=".env"
 # EventCatalog license key
-EVENTCATALOG_LICENSE_KEY_GITHUB=your-license-key
+EVENTCATALOG_SCALE_LICENSE_KEY=your-scale-license-key
 
 # GitHub token for private repository access
 EVENTCATALOG_GITHUB_TOKEN=ghp_your_token_here
@@ -288,6 +298,3 @@ npm run build
 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).
 
 You can also find some examples of the plugin in action in our examples repository: [eventcatalog/examples](https://github.com/event-catalog/generators/tree/main/examples/generator-github).
-
-
-

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

@@ -49,11 +49,11 @@ This let's you visualize your architecture, assign owners to your services and m
 
 ## 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.
 
@@ -62,13 +62,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 GraphQL 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 GraphQL 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).