@eventcatalog/core 4.1.3 → 4.1.4

package/dist/docs/development/upgrading/v3.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 2
+sidebar_position: 3
 keywords:
 - Upgrade EventCatalog
 sidebar_label: v3
@@ -221,7 +221,7 @@ To solve this we have introduced a new navigation system that introduces new ben
 - **Fully customizable navigation system** - define your own navigation system for your catalog.
 - **Favorited resources** - add your favorite resources to your navigation system.
 
-You can read more about the new context aware navigation in the [documentation sidebar documentation](/docs/development/customization/customize-sidebars/documentation-sidebar).
+You can read more about the new context aware navigation in the [documentation sidebar documentation](/docs/development/customization/documentation-sidebar).
 
 ### New caching and performance improvements
 
@@ -274,4 +274,3 @@ module.exports = {
 ## Known issues
 
 Please check [EventCatalog issues on GitHub](https://github.com/event-catalog/eventcatalog/issues) for any reported issues, or to file an issue yourself.
-

package/dist/docs/development/upgrading/v4.md

@@ -0,0 +1,377 @@
+---
+sidebar_position: 2
+keywords:
+- Upgrade EventCatalog
+sidebar_label: v4
+title: Upgrade to EventCatalog v4
+description: How to upgrade to EventCatalog v4.
+---
+
+import ProjectTree from '@site/src/components/MDX/ProjectTree';
+
+This guide will help you upgrade from v3 to v4 of EventCatalog.
+
+EventCatalog v4 introduces systems as a first-class resource, adds system context maps, updates the Discover and Application sidebar experience, moves EventCatalog onto Astro 7 internally, and removes the PDF export feature.
+
+:::info v4 beta
+
+The v4 branch is currently published as a beta. If v4 has not been promoted to `latest` yet, install the beta package instead of `latest`.
+
+:::
+
+## Upgrade EventCatalog
+
+Update your project's version of EventCatalog using your package manager:
+
+```bash
+npm install @eventcatalog/core@latest
+```
+
+If you are testing the v4 beta, use the beta tag:
+
+```bash
+npm install @eventcatalog/core@beta
+```
+
+_Problems upgrading? [Try resetting your project](/docs/development/upgrading#having-problems)._
+
+## Before you upgrade
+
+Most v3 catalogs should continue to build without changing their existing resources. You do not need to move your services, messages, flows, entities, or data stores into systems to upgrade to v4.
+
+Before upgrading, we recommend:
+
+1. Create a branch for the upgrade.
+1. Upgrade `@eventcatalog/core`.
+1. Remove `.eventcatalog-core`, `node_modules`, and your lock file if the catalog does not pick up the new version.
+1. Run your catalog locally and check custom pages, custom navigation, and visualiser links.
+
+## Removed
+
+The following features have now been entirely removed from the code base and can no longer be used.
+
+### Removed: Export to PDF
+
+The Export to PDF / print feature has been removed from EventCatalog v4.
+
+#### What do I need to do?
+
+Remove any user guidance, screenshots, or internal runbooks that tell people to export resource pages to PDF from EventCatalog.
+
+Diagram version comparison is still available, and is no longer gated behind the Scale plan.
+
+### Removed: `/visualiser/context-map`
+
+The old global context map route has been removed.
+
+#### What do I need to do?
+
+If you have custom navigation, docs, or bookmarks that link to `/visualiser/context-map`, update them to the new system context map route:
+
+```diff title="eventcatalog.config.js"
+export default {
+  navigation: {
+    pages: [
+      {
+        type: 'item',
+        title: 'System Context Map',
+-       href: '/visualiser/context-map',
++       href: '/visualiser/system-context-map',
+      },
+    ],
+  },
+};
+```
+
+## Breaking changes
+
+The following changes are considered breaking changes in EventCatalog v4. Breaking changes may or may not affect your catalog depending on how much you customize EventCatalog.
+
+### Changed: EventCatalog now uses Astro 7 internally
+
+EventCatalog v4 upgrades the internal application from Astro 6 to Astro 7.
+
+Most catalogs do not need to change anything. If you have custom Astro pages, custom integrations, or custom MDX/Markdown processing that depends on Astro internals, review those customizations during the upgrade.
+
+#### What do I need to do?
+
+If your catalog only uses EventCatalog resources and MDX content, upgrade EventCatalog and test the catalog.
+
+If you maintain custom Astro pages or custom integrations, check them against Astro 7 behavior and run the catalog locally after upgrading.
+
+### Changed: Application sidebar configuration has moved to `navigation.groups`
+
+EventCatalog v4 removes the top-level `sidebar` configuration that only let you show or hide items in the Application sidebar.
+
+You can now configure the whole Application sidebar using `navigation.groups`. This lets you define groups, labels, item order, icons, custom links, bottom-positioned groups, active route matching, and visibility.
+
+:::info
+
+`navigation.pages` still controls the context-aware documentation sidebar. Use `navigation.groups` for the Application sidebar.
+
+:::
+
+#### What do I need to do?
+
+If you are not using the top-level `sidebar` property in `eventcatalog.config.js`, there is nothing to change.
+
+If you are using `sidebar`, move that configuration to `navigation.groups`.
+
+```diff title="eventcatalog.config.js"
+export default {
+-  sidebar: [
+-    { id: '/directory/teams', visible: false },
+-    { id: '/schemas/fields', visible: false },
+-  ],
++  navigation: {
++    groups: [
++      {
++        id: 'main',
++        items: [{ id: 'home' }, { id: 'docs' }],
++      },
++      {
++        id: 'browse',
++        label: 'Browse',
++        items: [
++          { id: 'catalog' },
++          { id: 'schemas' },
++          { id: 'schema-insights', visible: false },
++        ],
++      },
++      {
++        id: 'organization',
++        label: 'Organization',
++        items: [{ id: 'teams', visible: false }, { id: 'users' }],
++      },
++      {
++        id: 'settings',
++        position: 'bottom',
++        items: [{ id: 'settings' }],
++      },
++    ],
++  },
+};
+```
+
+Built-in Application sidebar item IDs include:
+
+- `home`
+- `docs`
+- `catalog`
+- `schemas`
+- `schema-insights`
+- `teams`
+- `users`
+- `settings`
+You can also use route IDs such as `/schemas/explorer` or add custom items:
+
+```js title="eventcatalog.config.js"
+export default {
+  navigation: {
+    groups: [
+      {
+        id: 'platform',
+        label: 'Platform',
+        items: [
+          {
+            id: 'platform-docs',
+            label: 'Platform Docs',
+            icon: 'BookOpen',
+            href: '/docs/custom/platform/overview',
+            match: ['/docs/custom/platform'],
+          },
+          {
+            id: 'support',
+            label: 'Support',
+            icon: 'LifeBuoy',
+            href: 'https://support.example.com',
+          },
+        ],
+      },
+    ],
+  },
+};
+```
+
+When `navigation.groups` is provided, it replaces the default Application sidebar groups. Add every item you want users to see.
+
+If you import `SideBarConfig` from EventCatalog types, remove that import. It is no longer exported.
+
+### Changed: Discover navigation has been simplified
+
+EventCatalog v4 replaces the resource-specific Browse sidebar links with a single Discover experience and a Kind filter. Users can switch between domains, systems, services, messages, flows, entities, data stores, and other resource collections from the Discover page.
+
+![Discover domains page showing the new Kind filter](./img/discover-domains.png)
+
+#### What do I need to do?
+
+If you use the default Application sidebar, there is nothing to change.
+
+If you have custom screenshots, onboarding docs, or training material that mentions the old resource-specific Browse links, update them to reference Discover and the Kind filter.
+
+### Changed: System context maps are now the high-level architecture view
+
+EventCatalog v4 adds dedicated system context map routes:
+
+- `/visualiser/system-context-map` for the global system context map.
+- `/visualiser/systems/:id/:version/context` for a single system in context.
+- `/visualiser/domains/:id/:version/systems-context` for systems inside a domain.
+
+The existing resource visualiser routes still work for resources such as services and domains.
+
+#### What do I need to do?
+
+Update any custom links that should point users to the new high-level system context map.
+
+## New features
+
+The following new features and improvements have been added to EventCatalog v4.
+
+### Systems are now a first-class resource
+
+Systems are collections of resources that work together to perform a function, such as checkout, payment processing, customer identity, or product search.
+
+A system can group the resources that cooperate to deliver one capability, including [services](/docs/development/guides/resources/services/introduction), [flows](/docs/development/guides/resources/flows/introduction), [entities](/docs/development/guides/resources/entities/introduction), [data stores](/docs/development/guides/resources/data/introduction), [diagrams](/docs/development/bring-your-own-documentation/diagrams/introduction), and documentation.
+
+![Catalog domain system context map showing systems and actors](./img/catalog-systems-context.png)
+
+Systems are versioned resources. You can define them at the top level of your catalog, or inside a domain when that system clearly belongs to a business boundary.
+
+<ProjectTree
+  items={[
+    {
+      name: 'domains',
+      type: 'folder',
+      defaultOpen: true,
+      children: [
+        {
+          name: 'Payments',
+          type: 'folder',
+          defaultOpen: true,
+          children: [
+            { name: 'index.mdx' },
+            {
+              name: 'systems',
+              type: 'folder',
+              defaultOpen: true,
+              children: [
+                {
+                  name: 'payment-processing-system',
+                  type: 'folder',
+                  defaultOpen: true,
+                  children: [
+                    { name: 'index.mdx', highlight: true },
+                    {
+                      name: 'services',
+                      type: 'folder',
+                      defaultOpen: true,
+                      children: [
+                        {
+                          name: 'PaymentAPI',
+                          type: 'folder',
+                          defaultOpen: true,
+                          children: [{ name: 'index.mdx' }],
+                        },
+                      ],
+                    },
+                  ],
+                },
+              ],
+            },
+          ],
+        },
+      ],
+    },
+  ]}
+/>
+
+Example system frontmatter:
+
+```md title="domains/Payments/systems/payment-processing-system/index.mdx"
+---
+id: payment-processing-system
+name: Payment Processing System
+version: 1.0.0
+summary: Handles payment authorization, capture, and refund processing.
+owners:
+  - payments-platform
+services:
+  - id: PaymentAPI
+flows:
+  - id: CheckoutSaga
+relationships:
+  - id: fraud-detection
+    version: 1.0.0
+    label: requests fraud checks from
+---
+```
+
+You can also reference systems from a domain:
+
+```md title="domains/Payments/index.mdx"
+---
+id: payments
+name: Payments
+version: 1.0.0
+systems:
+  - id: payment-processing-system
+    version: 1.0.0
+---
+```
+
+Read more in the [systems documentation](/docs/development/guides/systems/introduction).
+
+### System context maps
+
+Systems can declare relationships to other systems. EventCatalog uses those relationships to render context maps that show how systems relate to each other.
+
+System context maps help users move from a high-level architecture view into a detailed system view. From the global map, users can click into a system, then explore the [services](/docs/development/guides/resources/services/introduction), [APIs](/docs/development/guides/resources/schemas/add-specifications-to-services/add-openapi-specifications), [messages](/docs/development/guides/resources/messages/what-are-messages), [flows](/docs/development/guides/resources/flows/introduction), [entities](/docs/development/guides/resources/entities/introduction), and [data stores](/docs/development/guides/resources/data/introduction) that make up that system.
+
+Read more in the [system context maps documentation](/docs/development/guides/systems/system-context-maps).
+
+### Systems in the SDK
+
+The EventCatalog SDK now supports systems. You can read and write systems, add resources to a system, write resources directly into a system, and add systems to domains.
+
+This is useful for generators and integrations that sync architecture information from source code, specifications, schema registries, or internal platforms.
+
+### Systems in AI, MCP, and catalog tools
+
+EventCatalog Assistant, MCP tools, and catalog tools now understand systems. AI workflows can retrieve systems, inspect system resources, and generate architecture diagrams for systems.
+
+### Systems in Discover, sidebars, teams, and ADRs
+
+Systems are now available across the catalog experience:
+
+- Systems can be discovered on `/discover/systems`.
+- Systems appear in sidebars with their own icon and color.
+- Teams and users can own systems.
+- ADRs can target systems with `appliesTo: [{ type: 'system' }]`.
+- Resource-level documentation can be attached to systems.
+
+### Top-level diagrams sidebar group
+
+EventCatalog v4 adds a Top level diagrams navigation group when systems exist. This surfaces the System Context Map from the sidebar so users can start from the highest-level architecture view.
+
+### Custom homepages are available in Community Edition
+
+Custom homepages are now available in Community Edition. You no longer need a paid feature flag to customize the catalog homepage.
+
+Create your custom homepage at `pages/homepage.astro`.
+
+<ProjectTree
+  items={[
+    {
+      name: 'pages',
+      type: 'folder',
+      defaultOpen: true,
+      children: [{ name: 'homepage.astro', highlight: true }],
+    },
+  ]}
+/>
+
+Custom homepages can also embed the new System Context Map using the `SystemContextMap` component.
+
+## Known issues
+
+Please check [EventCatalog issues on GitHub](https://github.com/event-catalog/eventcatalog/issues) for any reported issues, or to file an issue yourself.

package/dist/docs/editor/00-overview.md

@@ -15,7 +15,7 @@ It runs on your machine, opens your catalog from disk, lets you edit architectur
 
 The editor is for people who maintain an EventCatalog:
 
-- Architects documenting [domains](/docs/development/guides/domains/introduction), [services](/docs/development/guides/services/introduction), [messages](/docs/development/guides/messages/overview), and [ownership](/docs/owners)
+- Architects documenting [domains](/docs/development/guides/domains/introduction), [services](/docs/development/guides/resources/services/introduction), [messages](/docs/development/guides/resources/messages/what-are-messages), and [ownership](/docs/owners)
 - Developers keeping resource documentation, schemas, and specifications up to date
 - Analysts, product owners, or domain experts who can improve catalog content but do not want to edit MDX files directly
 
@@ -32,10 +32,10 @@ These docs assume you already have an EventCatalog project. If you are just gett
 Use EventCatalog Editor to:
 
 - Open a local EventCatalog project
-- Browse [domains](/docs/development/guides/domains/introduction), [services](/docs/development/guides/services/introduction), [messages](/docs/development/guides/messages/overview), [channels](/docs/development/guides/channels/introduction), [entities](/docs/development/guides/domains/entities/introduction), [data stores](/docs/development/guides/data/introduction), [flows](/docs/development/guides/flows/introduction), [users](/docs/development/guides/owners/users/introduction), and [teams](/docs/development/guides/owners/teams/introduction)
+- Browse [domains](/docs/development/guides/domains/introduction), [services](/docs/development/guides/resources/services/introduction), [messages](/docs/development/guides/resources/messages/what-are-messages), [channels](/docs/development/guides/resources/messages/message-channels/introduction), [entities](/docs/development/guides/resources/entities/introduction), [data stores](/docs/development/guides/resources/data/introduction), [flows](/docs/development/guides/resources/flows/introduction), [users](/docs/development/guides/owners/what-are-teams-and-users), and [teams](/docs/development/guides/owners/what-are-teams-and-users)
 - Edit documentation in a rich editor or source editor
 - Update common frontmatter fields through forms
-- Add schemas to [events](/docs/development/guides/messages/events/introduction), [commands](/docs/development/guides/messages/commands/introduction), and [queries](/docs/development/guides/messages/queries/introduction)
+- Add schemas to [events](/docs/development/guides/resources/messages/message-types/events), [commands](/docs/development/guides/resources/messages/message-types/commands), and [queries](/docs/development/guides/resources/messages/message-types/queries)
 - Add OpenAPI, AsyncAPI, and GraphQL specifications to domains and services
 - Preview resources in a running EventCatalog site
 - Inspect local Git changes, view diffs, revert files, and commit work

package/dist/docs/editor/01-first-edit.md

@@ -69,7 +69,7 @@ If the editor asks you to sign in, sign in with [EventCatalog Cloud](https://eve
 
 ## Open a resource
 
-Choose a resource from the left navigation. A good first edit is a [service](/docs/development/guides/services/introduction), [domain](/docs/development/guides/domains/introduction), [event](/docs/development/guides/messages/events/introduction), [command](/docs/development/guides/messages/commands/introduction), or [query](/docs/development/guides/messages/queries/introduction) that already exists in your catalog.
+Choose a resource from the left navigation. A good first edit is a [service](/docs/development/guides/resources/services/introduction), [domain](/docs/development/guides/domains/introduction), [event](/docs/development/guides/resources/messages/message-types/events), [command](/docs/development/guides/resources/messages/message-types/commands), or [query](/docs/development/guides/resources/messages/message-types/queries) that already exists in your catalog.
 
 The editor shows:
 

package/dist/docs/editor/explanation/markdown-mdx-git.md

@@ -13,7 +13,7 @@ Instead of asking every contributor to edit Markdown, MDX, YAML frontmatter, sch
 
 Each EventCatalog resource is still represented by files in your catalog.
 
-For example, a [service](/docs/development/guides/services/introduction) might live at:
+For example, a [service](/docs/development/guides/resources/services/introduction) might live at:
 
 ```txt
 domains/Orders/services/OrderService/index.mdx

package/dist/docs/editor/how-to/add-schemas-and-specifications.md

@@ -11,9 +11,9 @@ Use schemas and specifications to keep implementation contracts close to the arc
 
 Schemas are supported on:
 
-- [Events](/docs/development/guides/messages/events/introduction)
-- [Commands](/docs/development/guides/messages/commands/introduction)
-- [Queries](/docs/development/guides/messages/queries/introduction)
+- [Events](/docs/development/guides/resources/messages/message-types/events)
+- [Commands](/docs/development/guides/resources/messages/message-types/commands)
+- [Queries](/docs/development/guides/resources/messages/message-types/queries)
 
 Open the message resource, then use the **Schema** section to add or edit the schema file.
 
@@ -33,7 +33,7 @@ If the schema editor does not expose the exact change you need yet, use source m
 Specifications are supported on:
 
 - [Domains](/docs/development/guides/domains/introduction)
-- [Services](/docs/development/guides/services/introduction)
+- [Services](/docs/development/guides/resources/services/introduction)
 
 Open the domain or service, then use the specifications area to add:
 
@@ -63,4 +63,4 @@ Use source mode when you need to:
 - Add custom MDX around a schema
 - Edit specification metadata the visual form does not expose yet
 
-For more on schema documentation in EventCatalog, see the [schema documentation guides](/docs/development/guides/schemas/introduction).
+For more on schema documentation in EventCatalog, see the [schema documentation guides](/docs/development/guides/resources/schemas/what-are-schemas-and-specifications).

package/dist/docs/editor/how-to/edit-resource.md

@@ -11,7 +11,7 @@ Use this guide when you want to update a resource that already exists in your ca
 
 Start the editor and choose a resource from the resource list.
 
-The editor supports common EventCatalog resource types, including [domains](/docs/development/guides/domains/introduction), [services](/docs/development/guides/services/introduction), [events](/docs/development/guides/messages/events/introduction), [commands](/docs/development/guides/messages/commands/introduction), [queries](/docs/development/guides/messages/queries/introduction), [channels](/docs/development/guides/channels/introduction), [entities](/docs/development/guides/domains/entities/introduction), [data stores](/docs/development/guides/data/introduction), [flows](/docs/development/guides/flows/introduction), [users](/docs/development/guides/owners/users/introduction), and [teams](/docs/development/guides/owners/teams/introduction).
+The editor supports common EventCatalog resource types, including [domains](/docs/development/guides/domains/introduction), [services](/docs/development/guides/resources/services/introduction), [events](/docs/development/guides/resources/messages/message-types/events), [commands](/docs/development/guides/resources/messages/message-types/commands), [queries](/docs/development/guides/resources/messages/message-types/queries), [channels](/docs/development/guides/resources/messages/message-channels/introduction), [entities](/docs/development/guides/resources/entities/introduction), [data stores](/docs/development/guides/resources/data/introduction), [flows](/docs/development/guides/resources/flows/introduction), [users](/docs/development/guides/owners/what-are-teams-and-users), and [teams](/docs/development/guides/owners/what-are-teams-and-users).
 
 ![Resource list with a service selected](../images/editor.png)
 

package/dist/docs/editor/how-to/use-flow-editor.md

@@ -5,7 +5,7 @@ title: Use the Flow Editor
 description: Create and update EventCatalog flows visually with EventCatalog Editor.
 ---
 
-Use the Flow Editor when you want to document a business process, user journey, or architecture workflow without editing the [flow](/docs/development/guides/flows/introduction) files by hand.
+Use the Flow Editor when you want to document a business process, user journey, or architecture workflow without editing the [flow](/docs/development/guides/resources/flows/introduction) files by hand.
 
 Flow resources are still stored in your local EventCatalog project. The editor gives you a visual way to create and arrange the steps, then writes the change back to your catalog files.
 
@@ -33,10 +33,10 @@ Use the node picker to add the resource that best represents the next step.
 
 For example:
 
-- Add a [service](/docs/development/guides/services/introduction) when a system performs work
-- Add an [event](/docs/development/guides/messages/events/introduction) when something has happened
-- Add a [command](/docs/development/guides/messages/commands/introduction) when one system asks another system to do something
-- Add a [query](/docs/development/guides/messages/queries/introduction) when the flow reads information
+- Add a [service](/docs/development/guides/resources/services/introduction) when a system performs work
+- Add an [event](/docs/development/guides/resources/messages/message-types/events) when something has happened
+- Add a [command](/docs/development/guides/resources/messages/message-types/commands) when one system asks another system to do something
+- Add a [query](/docs/development/guides/resources/messages/message-types/queries) when the flow reads information
 
 Use existing catalog resources when they already exist. Create new resources when the flow reveals something that is missing from the catalog.
 

package/dist/docs/editor/how-to/use-slash-commands.md

@@ -32,7 +32,7 @@ You can insert components such as:
 - Draw.io diagram
 - Lucid diagram
 - IcePanel diagram
-- [Flow](/docs/development/guides/flows/introduction)
+- [Flow](/docs/development/guides/resources/flows/introduction)
 - Mermaid diagram
 - Entity Map
 - Schema Viewer
@@ -43,7 +43,7 @@ You can insert components such as:
 - Visibility
 - Admonitions such as note, tip, warning, danger, and info
 
-Some commands are available only when they make sense for the current resource. For example, **Schema Viewer** is available for [events](/docs/development/guides/messages/events/introduction), [commands](/docs/development/guides/messages/commands/introduction), and [queries](/docs/development/guides/messages/queries/introduction), while **Entity Map** is available for [domains](/docs/development/guides/domains/introduction).
+Some commands are available only when they make sense for the current resource. For example, **Schema Viewer** is available for [events](/docs/development/guides/resources/messages/message-types/events), [commands](/docs/development/guides/resources/messages/message-types/commands), and [queries](/docs/development/guides/resources/messages/message-types/queries), while **Entity Map** is available for [domains](/docs/development/guides/domains/introduction).
 
 ## Use visual previews
 

package/dist/docs/editor/reference/supported-content.md

@@ -36,11 +36,11 @@ Common command groups include:
 - Lists: bullet and ordered lists
 - Advanced: code blocks, dividers, and tables
 - Admonitions: note, tip, warning, danger, and info callouts
-- Diagrams: Node Graph, [Flow](/docs/development/guides/flows/introduction), Mermaid, Miro, Draw.io, Lucid, IcePanel, Entity Map, and Schema Viewer
+- Diagrams: Node Graph, [Flow](/docs/development/guides/resources/flows/introduction), Mermaid, Miro, Draw.io, Lucid, IcePanel, Entity Map, and Schema Viewer
 - Layout: Steps, Tiles, and Accordion group
 - AI: Prompt and Visibility blocks
 
-Some commands are resource-aware. For example, Schema Viewer appears for [events](/docs/development/guides/messages/events/introduction), [commands](/docs/development/guides/messages/commands/introduction), and [queries](/docs/development/guides/messages/queries/introduction), and Entity Map appears for [domains](/docs/development/guides/domains/introduction).
+Some commands are resource-aware. For example, Schema Viewer appears for [events](/docs/development/guides/resources/messages/message-types/events), [commands](/docs/development/guides/resources/messages/message-types/commands), and [queries](/docs/development/guides/resources/messages/message-types/queries), and Entity Map appears for [domains](/docs/development/guides/domains/introduction).
 
 ## Source mode
 

package/dist/docs/editor/reference/supported-resources.md

@@ -10,31 +10,31 @@ EventCatalog Editor can browse and edit the main EventCatalog resource types.
 | Resource type | Browse | Edit docs | Edit metadata | Create | Delete | Notes |
 | --- | --- | --- | --- | --- | --- | --- |
 | [Domain](/docs/development/guides/domains/introduction) | Yes | Yes | Yes | Yes | Yes | Supports services, messages, entities, specifications, and ubiquitous language |
-| [Service](/docs/development/guides/services/introduction) | Yes | Yes | Yes | Yes | Yes | Supports message relationships, data store relationships, and specifications |
-| [Event](/docs/development/guides/messages/events/introduction) | Yes | Yes | Yes | Yes | Yes | Supports schemas and producer/consumer relationships |
-| [Command](/docs/development/guides/messages/commands/introduction) | Yes | Yes | Yes | Yes | Yes | Supports schemas, operations, and producer/consumer relationships |
-| [Query](/docs/development/guides/messages/queries/introduction) | Yes | Yes | Yes | Yes | Yes | Supports schemas, operations, and producer/consumer relationships |
-| [Channel](/docs/development/guides/channels/introduction) | Yes | Yes | Yes | Yes | Yes | Supports common metadata |
-| [Entity](/docs/development/guides/domains/entities/introduction) | Yes | Yes | Yes | Yes | Yes | Supports common metadata |
-| [Data store](/docs/development/guides/data/introduction) | Yes | Yes | Yes | Yes | Yes | Represented as EventCatalog container resources |
-| [Flow](/docs/development/guides/flows/introduction) | Yes | Yes | Yes | Yes | Yes | Supports flow step editing |
-| [User](/docs/development/guides/owners/users/introduction) | Yes | Yes | Yes | Yes | Yes | Versionless |
-| [Team](/docs/development/guides/owners/teams/introduction) | Yes | Yes | Yes | Yes | Yes | Versionless |
+| [Service](/docs/development/guides/resources/services/introduction) | Yes | Yes | Yes | Yes | Yes | Supports message relationships, data store relationships, and specifications |
+| [Event](/docs/development/guides/resources/messages/message-types/events) | Yes | Yes | Yes | Yes | Yes | Supports schemas and producer/consumer relationships |
+| [Command](/docs/development/guides/resources/messages/message-types/commands) | Yes | Yes | Yes | Yes | Yes | Supports schemas, operations, and producer/consumer relationships |
+| [Query](/docs/development/guides/resources/messages/message-types/queries) | Yes | Yes | Yes | Yes | Yes | Supports schemas, operations, and producer/consumer relationships |
+| [Channel](/docs/development/guides/resources/messages/message-channels/introduction) | Yes | Yes | Yes | Yes | Yes | Supports common metadata |
+| [Entity](/docs/development/guides/resources/entities/introduction) | Yes | Yes | Yes | Yes | Yes | Supports common metadata |
+| [Data store](/docs/development/guides/resources/data/introduction) | Yes | Yes | Yes | Yes | Yes | Represented as EventCatalog container resources |
+| [Flow](/docs/development/guides/resources/flows/introduction) | Yes | Yes | Yes | Yes | Yes | Supports flow step editing |
+| [User](/docs/development/guides/owners/what-are-teams-and-users) | Yes | Yes | Yes | Yes | Yes | Versionless |
+| [Team](/docs/development/guides/owners/what-are-teams-and-users) | Yes | Yes | Yes | Yes | Yes | Versionless |
 
 ## Schemas
 
 Schemas are supported on:
 
-- [Events](/docs/development/guides/messages/events/introduction)
-- [Commands](/docs/development/guides/messages/commands/introduction)
-- [Queries](/docs/development/guides/messages/queries/introduction)
+- [Events](/docs/development/guides/resources/messages/message-types/events)
+- [Commands](/docs/development/guides/resources/messages/message-types/commands)
+- [Queries](/docs/development/guides/resources/messages/message-types/queries)
 
 ## Specifications
 
 Specifications are supported on:
 
 - [Domains](/docs/development/guides/domains/introduction)
-- [Services](/docs/development/guides/services/introduction)
+- [Services](/docs/development/guides/resources/services/introduction)
 
 Supported specification types:
 

package/dist/docs/plugins/amazon-apigateway/00-intro.md

@@ -46,11 +46,11 @@ This will map your routes into commands, events and queries in your catalog and
 
 ## 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.
 
@@ -59,16 +59,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 Amazon API Gateway 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 Amazon API Gateway 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). Your organization can have a 14 day trial license key to try the plugin out.
+### How do I get an EventCatalog Scale license key?
+You can obtain an EventCatalog Scale license key by visiting [EventCatalog Cloud](https://eventcatalog.cloud). Your organization can start with a 30-day 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