@eventcatalog/create-eventcatalog 4.3.2 → 4.3.4-beta.0

package/templates/default/users/dboyne.mdx

@@ -1,11 +1,11 @@
 ---
 id: dboyne
 name: David Boyne
-summary: Tech Lead of the Full Stackers team
 avatarUrl: 'https://pbs.twimg.com/profile_images/1262283153563140096/DYRDqKg6_400x400.png'
 role: Lead developer
 email: test@test.com
 slackDirectMessageUrl: https://yourteam.slack.com/channels/boyney123
+msTeamsDirectMessageUrl: https://teams.microsoft.com/l/chat/0/0?users=test@test.com
 ---
 
 Hello! I'm David Boyne, the Tech Lead of an amazing team called Full Stackers. With a passion for building robust and scalable systems, I specialize in designing and implementing event-driven architectures that power modern, responsive applications.

package/templates/empty/README-template.md

@@ -1,55 +1,63 @@
-# My Event Catalog
+# Welcome to EventCatalog
 
-Welcome to your new catalog, powered by [EventCatalog](https://www.eventcatalog.dev) — the open-source documentation tool for event-driven architectures.
+[EventCatalog](https://www.eventcatalog.dev/) is your architecture catalog for distributed systems. Use it to document, govern, and discover your services, domains, APIs, events, commands, queries, schemas, teams, and flows in one place.
 
-## Getting Started
+## Start the Catalog
 
 ```sh
 npm run dev
 ```
 
-Open [http://localhost:3000](http://localhost:3000) to see your catalog.
+Open [http://localhost:3000](http://localhost:3000) to view your catalog.
 
-You can start editing your catalog by adding **domains**, **services**, and **messages** to this project. Each resource is a folder with an `index.md` file containing frontmatter metadata and markdown content.
+Using `pnpm` or `yarn`? Run the same scripts with the package manager you chose when creating this project.
 
-## What Can You Do?
+## Edit Your Catalog
 
-- **Document services** — define producers and consumers with their schemas
-- **Map events, commands & queries** — capture every message flowing through your system
-- **Organize with domains** — group resources into bounded contexts
-- **Visualize your architecture** — auto-generated diagrams of your services and message flows
-- **Version everything** — track how your architecture evolves over time
-- **Use AI to explore & document** — connect AI tools directly to your catalog
+Your catalog is docs-as-code. Resources live in folders with an `index.mdx` file for frontmatter metadata and Markdown content.
 
-## Use AI with Your Catalog
+Good places to start:
 
-### Skills
+- `domains/` - bounded contexts, business capabilities, and ownership
+- `domains/<domain>/services/` - services, APIs, and message producers or consumers
+- `events/`, `commands/`, and `queries/` - the messages flowing through your system
+- `teams/` and `users/` - who owns each part of the architecture
 
-Let AI agents document your architecture for you. Install [EventCatalog Skills](https://github.com/event-catalog/skills):
+Prefer a visual workflow? Run `npm run editor` to open the [EventCatalog Editor](https://www.eventcatalog.dev/docs/editor/overview) and browse, create, or update catalog resources through a GitHub-backed UI.
 
-```sh
-npx skills add event-catalog/skills
-```
+## Make Your First Change
+
+1. Add or edit a domain, service, or message.
+2. Run `npm run dev` and check the generated pages and diagrams.
+3. Commit the MDX and schema files to Git.
+
+## Keep It in Sync
 
-Skills can generate service documentation, create domain models, and map business flows — all through natural language.
+Use `npm run generate` with [EventCatalog integrations](https://www.eventcatalog.dev/integrations) to import architecture data from OpenAPI, AsyncAPI, schema registries, EventBridge, GitHub, internal systems, and more.
 
-### MCP Server
+Run generators locally while you work, or in CI so your catalog stays aligned with the systems it describes.
 
-Connect your catalog to Claude, Cursor, Windsurf, or any MCP-compatible AI tool using the [EventCatalog MCP Server](https://www.eventcatalog.dev/docs/development/guides/ai/using-mcp-server). Ask questions about your architecture and get instant answers.
+## Use AI with Architecture Context
 
-## Automate Your Catalog
+EventCatalog gives AI tools structured context about your domains, services, messages, schemas, owners, and flows.
 
-Keep your catalog in sync with your architecture using [EventCatalog integrations](https://www.eventcatalog.dev/integrations). Import services, messages, and schemas from sources like AsyncAPI, OpenAPI, Schema Registries, and more — so your documentation is always up to date.
+- Connect Claude, Cursor, VS Code, Windsurf, or another MCP-compatible tool with the [EventCatalog MCP Server](https://www.eventcatalog.dev/docs/development/guides/ai/using-mcp-server).
+- Install [EventCatalog Skills](https://github.com/event-catalog/skills) to help agents document services, create domain models, and map business flows:
+
+```sh
+npx skills add event-catalog/skills
+```
 
-## Learn More
+## Learn by Task
 
-- [Documentation](https://www.eventcatalog.dev/docs/development/getting-started/introduction) — understand how EventCatalog works
-- [Adding Services](https://www.eventcatalog.dev/docs/development/guides/services) — document your first service
-- [Adding Messages](https://www.eventcatalog.dev/docs/development/guides/messages/adding-messages) — create events, commands, and queries
-- [Adding Domains](https://www.eventcatalog.dev/docs/development/guides/domains) — organize into bounded contexts
-- [SDK](https://www.eventcatalog.dev/docs/development/sdk) — manage your catalog programmatically
-- [Discord](https://discord.gg/3rjaZMmrAm) — join the community
+- [Create a domain](https://www.eventcatalog.dev/docs/development/guides/domains)
+- [Document a service](https://www.eventcatalog.dev/docs/development/guides/services)
+- [Add events, commands, and queries](https://www.eventcatalog.dev/docs/development/guides/messages/adding-messages)
+- [Use the EventCatalog Editor](https://www.eventcatalog.dev/docs/editor/overview)
+- [Generate from integrations](https://www.eventcatalog.dev/integrations)
+- [Manage your catalog with the SDK](https://www.eventcatalog.dev/docs/development/sdk)
+- [Join the community](https://discord.gg/3rjaZMmrAm)
 
-## Found a problem?
+## Found a Problem?
 
 Open an issue on [GitHub](https://github.com/event-catalog/eventcatalog/issues).

package/templates/eventbridge/README-template.md

@@ -1,27 +1,54 @@
-# My EventBridge Event Catalog
+# Welcome to EventCatalog
 
-Welcome to your new EventBridge EventCatalog!
+[EventCatalog](https://www.eventcatalog.dev/) is your architecture catalog for distributed systems. This template adds the EventBridge generator so you can import schemas from Amazon EventBridge and document how they connect to your domains, services, and teams.
 
-Getting started:
+## Generate Your Catalog
 
-1. Edit the `.env` file to configure your environment variables.
-1. Configure the region and schema registry name in the `eventcatalog.config.js` file
-1. Run `npm run generate` to import your schemas from confluent schema registry.
-1. Run `npm run dev` to start the development server.
-1. Go to localhost:3000 to view your catalog.
+1. Edit `.env` with your AWS settings.
+2. Configure the region and schema registry name in `eventcatalog.config.js`.
+3. Import your EventBridge schemas:
 
-### What else can you do?
+```sh
+npm run generate
+```
 
-With the EventBridge integration you can :
+4. Start the catalog:
 
-- Document your schemas
-- Assign your schemas to producers and consumers
-- Assign resources to users and teams in your organization
+```sh
+npm run dev
+```
+
+Open [http://localhost:3000](http://localhost:3000) to view your catalog.
+
+## Edit Your Catalog
+
+Your generated resources are docs-as-code. You can enrich them with ownership, domain context, Markdown, examples, and relationships that are not always available in the source schema.
+
+Prefer a visual workflow? Run `npm run editor` to open the [EventCatalog Editor](https://www.eventcatalog.dev/docs/editor/overview) and browse, create, or update catalog resources through a GitHub-backed UI.
+
+## Keep It in Sync
+
+Run `npm run generate` whenever your EventBridge schemas change. You can also run the generator in CI so your catalog stays aligned with your registry.
+
+With this integration you can:
+
+- Document EventBridge schemas and events
+- Assign schemas to producers and consumers
+- Connect resources to users and teams
 - Visualize your EventBridge architecture
-- And much more!
 
-The easiest way to get started and dive deeper is to read the [EventCatalog documentation](https://www.eventcatalog.dev/docs/plugins/eventbridge/intro).
+## Use AI with Architecture Context
+
+EventCatalog gives AI tools structured context about your domains, services, messages, schemas, owners, and flows. Connect an MCP-compatible tool with the [EventCatalog MCP Server](https://www.eventcatalog.dev/docs/development/guides/ai/using-mcp-server).
+
+## Learn by Task
+
+- [EventBridge integration docs](https://www.eventcatalog.dev/docs/plugins/eventbridge/intro)
+- [Use the EventCatalog Editor](https://www.eventcatalog.dev/docs/editor/overview)
+- [Document a service](https://www.eventcatalog.dev/docs/development/guides/services)
+- [Add events, commands, and queries](https://www.eventcatalog.dev/docs/development/guides/messages/adding-messages)
+- [Join the community](https://discord.gg/3rjaZMmrAm)
 
-### Found a problem?
+## Found a Problem?
 
-If you found a problem or have a feature request, please open an issue on [GitHub](https://github.com/event-catalog/generators).
+Open an issue on [GitHub](https://github.com/event-catalog/generators).

package/templates/graphql/README-template.md

@@ -1,55 +1,63 @@
-# My Event Catalog
+# Welcome to EventCatalog
 
-Welcome to your new catalog, powered by [EventCatalog](https://www.eventcatalog.dev) — the open-source documentation tool for event-driven architectures.
+[EventCatalog](https://www.eventcatalog.dev/) is your architecture catalog for distributed systems. Use it to document, govern, and discover your services, domains, APIs, events, commands, queries, schemas, teams, and flows in one place.
 
-## Getting Started
+## Start the Catalog
 
 ```sh
 npm run dev
 ```
 
-Open [http://localhost:3000](http://localhost:3000) to see your catalog.
+Open [http://localhost:3000](http://localhost:3000) to view your catalog.
 
-You can start editing your catalog by adding **domains**, **services**, and **messages** to this project. Each resource is a folder with an `index.md` file containing frontmatter metadata and markdown content.
+Using `pnpm` or `yarn`? Run the same scripts with the package manager you chose when creating this project.
 
-## What Can You Do?
+## Edit Your Catalog
 
-- **Document services** — define producers and consumers with their schemas
-- **Map events, commands & queries** — capture every message flowing through your system
-- **Organize with domains** — group resources into bounded contexts
-- **Visualize your architecture** — auto-generated diagrams of your services and message flows
-- **Version everything** — track how your architecture evolves over time
-- **Use AI to explore & document** — connect AI tools directly to your catalog
+Your catalog is docs-as-code. Resources live in folders with an `index.mdx` file for frontmatter metadata and Markdown content.
 
-## Use AI with Your Catalog
+Good places to start:
 
-### Skills
+- `domains/` - bounded contexts, business capabilities, and ownership
+- `domains/<domain>/services/` - services, APIs, and message producers or consumers
+- `events/`, `commands/`, and `queries/` - the messages flowing through your system
+- `teams/` and `users/` - who owns each part of the architecture
 
-Let AI agents document your architecture for you. Install [EventCatalog Skills](https://github.com/event-catalog/skills):
+Prefer a visual workflow? Run `npm run editor` to open the [EventCatalog Editor](https://www.eventcatalog.dev/docs/editor/overview) and browse, create, or update catalog resources through a GitHub-backed UI.
 
-```sh
-npx skills add event-catalog/skills
-```
+## Make Your First Change
+
+1. Add or edit a domain, service, or message.
+2. Run `npm run dev` and check the generated pages and diagrams.
+3. Commit the MDX and schema files to Git.
+
+## Keep It in Sync
 
-Skills can generate service documentation, create domain models, and map business flows — all through natural language.
+Use `npm run generate` with [EventCatalog integrations](https://www.eventcatalog.dev/integrations) to import architecture data from OpenAPI, AsyncAPI, schema registries, EventBridge, GitHub, internal systems, and more.
 
-### MCP Server
+Run generators locally while you work, or in CI so your catalog stays aligned with the systems it describes.
 
-Connect your catalog to Claude, Cursor, Windsurf, or any MCP-compatible AI tool using the [EventCatalog MCP Server](https://www.eventcatalog.dev/docs/development/guides/ai/using-mcp-server). Ask questions about your architecture and get instant answers.
+## Use AI with Architecture Context
 
-## Automate Your Catalog
+EventCatalog gives AI tools structured context about your domains, services, messages, schemas, owners, and flows.
 
-Keep your catalog in sync with your architecture using [EventCatalog integrations](https://www.eventcatalog.dev/integrations). Import services, messages, and schemas from sources like AsyncAPI, OpenAPI, Schema Registries, and more — so your documentation is always up to date.
+- Connect Claude, Cursor, VS Code, Windsurf, or another MCP-compatible tool with the [EventCatalog MCP Server](https://www.eventcatalog.dev/docs/development/guides/ai/using-mcp-server).
+- Install [EventCatalog Skills](https://github.com/event-catalog/skills) to help agents document services, create domain models, and map business flows:
+
+```sh
+npx skills add event-catalog/skills
+```
 
-## Learn More
+## Learn by Task
 
-- [Documentation](https://www.eventcatalog.dev/docs/development/getting-started/introduction) — understand how EventCatalog works
-- [Adding Services](https://www.eventcatalog.dev/docs/development/guides/services) — document your first service
-- [Adding Messages](https://www.eventcatalog.dev/docs/development/guides/messages/adding-messages) — create events, commands, and queries
-- [Adding Domains](https://www.eventcatalog.dev/docs/development/guides/domains) — organize into bounded contexts
-- [SDK](https://www.eventcatalog.dev/docs/development/sdk) — manage your catalog programmatically
-- [Discord](https://discord.gg/3rjaZMmrAm) — join the community
+- [Create a domain](https://www.eventcatalog.dev/docs/development/guides/domains)
+- [Document a service](https://www.eventcatalog.dev/docs/development/guides/services)
+- [Add events, commands, and queries](https://www.eventcatalog.dev/docs/development/guides/messages/adding-messages)
+- [Use the EventCatalog Editor](https://www.eventcatalog.dev/docs/editor/overview)
+- [Generate from integrations](https://www.eventcatalog.dev/integrations)
+- [Manage your catalog with the SDK](https://www.eventcatalog.dev/docs/development/sdk)
+- [Join the community](https://discord.gg/3rjaZMmrAm)
 
-## Found a problem?
+## Found a Problem?
 
 Open an issue on [GitHub](https://github.com/event-catalog/eventcatalog/issues).

package/templates/index.ts

@@ -48,6 +48,7 @@ export const installTemplate = async ({
     private: true,
     scripts: {
       dev: 'eventcatalog dev',
+      editor: 'npx @eventcatalog/editor@latest',
       build: 'eventcatalog build',
       start: 'eventcatalog start',
       preview: 'eventcatalog preview',

package/templates/openapi/README-template.md

@@ -1,59 +1,63 @@
-# My Event Catalog
+# Welcome to EventCatalog
 
-Welcome to your new catalog, powered by [EventCatalog](https://www.eventcatalog.dev) — the open-source documentation tool for event-driven architectures.
+[EventCatalog](https://www.eventcatalog.dev/) is your architecture catalog for distributed systems. Use it to document, govern, and discover your services, domains, APIs, events, commands, queries, schemas, teams, and flows in one place.
 
-## Getting Started
+## Start the Catalog
 
 ```sh
 npm run dev
 ```
 
-Open [http://localhost:3000](http://localhost:3000) to see your catalog.
+Open [http://localhost:3000](http://localhost:3000) to view your catalog.
 
-You can start editing your catalog by adding **domains**, **services**, and **messages** to this project. Each resource is a folder with an `index.md` file containing frontmatter metadata and markdown content.
+Using `pnpm` or `yarn`? Run the same scripts with the package manager you chose when creating this project.
 
-## What Can You Do?
+## Edit Your Catalog
 
-- **Document services** — define producers and consumers with their schemas
-- **Map events, commands & queries** — capture every message flowing through your system
-- **Organize with domains** — group resources into bounded contexts
-- **Visualize your architecture** — auto-generated diagrams of your services and message flows
-- **Version everything** — track how your architecture evolves over time
-- **Use AI to explore & document** — connect AI tools directly to your catalog
+Your catalog is docs-as-code. Resources live in folders with an `index.mdx` file for frontmatter metadata and Markdown content.
 
-## Use AI with Your Catalog
+Good places to start:
 
-### Skills
+- `domains/` - bounded contexts, business capabilities, and ownership
+- `domains/<domain>/services/` - services, APIs, and message producers or consumers
+- `events/`, `commands/`, and `queries/` - the messages flowing through your system
+- `teams/` and `users/` - who owns each part of the architecture
 
-Let AI agents document your architecture for you. Install [EventCatalog Skills](https://github.com/event-catalog/skills):
+Prefer a visual workflow? Run `npm run editor` to open the [EventCatalog Editor](https://www.eventcatalog.dev/docs/editor/overview) and browse, create, or update catalog resources through a GitHub-backed UI.
 
-```sh
-npx skills add event-catalog/skills
-```
+## Make Your First Change
+
+1. Add or edit a domain, service, or message.
+2. Run `npm run dev` and check the generated pages and diagrams.
+3. Commit the MDX and schema files to Git.
 
-Skills can generate service documentation, create domain models, and map business flows — all through natural language.
+## Keep It in Sync
 
-### MCP Server
+Use `npm run generate` with [EventCatalog integrations](https://www.eventcatalog.dev/integrations) to import architecture data from OpenAPI, AsyncAPI, schema registries, EventBridge, GitHub, internal systems, and more.
 
-Connect your catalog to Claude, Cursor, Windsurf, or any MCP-compatible AI tool using the [EventCatalog MCP Server](https://www.eventcatalog.dev/docs/development/guides/ai/using-mcp-server). Ask questions about your architecture and get instant answers.
+Run generators locally while you work, or in CI so your catalog stays aligned with the systems it describes.
 
-## Automate Your Catalog
+## Use AI with Architecture Context
 
-Keep your catalog in sync with your architecture using [EventCatalog integrations](https://www.eventcatalog.dev/integrations). Import services, messages, and schemas from sources like AsyncAPI, OpenAPI, Confluent Schema Registry, AWS EventBridge, and more — so your documentation is always up to date.
+EventCatalog gives AI tools structured context about your domains, services, messages, schemas, owners, and flows.
 
-## Automate Your Catalog
+- Connect Claude, Cursor, VS Code, Windsurf, or another MCP-compatible tool with the [EventCatalog MCP Server](https://www.eventcatalog.dev/docs/development/guides/ai/using-mcp-server).
+- Install [EventCatalog Skills](https://github.com/event-catalog/skills) to help agents document services, create domain models, and map business flows:
 
-Keep your catalog in sync with your architecture using [EventCatalog integrations](https://www.eventcatalog.dev/integrations). Import services, messages, and schemas from sources like AsyncAPI, OpenAPI, Schema Registries, and more — so your documentation is always up to date.
+```sh
+npx skills add event-catalog/skills
+```
 
-## Learn More
+## Learn by Task
 
-- [Documentation](https://www.eventcatalog.dev/docs/development/getting-started/introduction) — understand how EventCatalog works
-- [Adding Services](https://www.eventcatalog.dev/docs/development/guides/services) — document your first service
-- [Adding Messages](https://www.eventcatalog.dev/docs/development/guides/messages/adding-messages) — create events, commands, and queries
-- [Adding Domains](https://www.eventcatalog.dev/docs/development/guides/domains) — organize into bounded contexts
-- [SDK](https://www.eventcatalog.dev/docs/development/sdk) — manage your catalog programmatically
-- [Discord](https://discord.gg/3rjaZMmrAm) — join the community
+- [Create a domain](https://www.eventcatalog.dev/docs/development/guides/domains)
+- [Document a service](https://www.eventcatalog.dev/docs/development/guides/services)
+- [Add events, commands, and queries](https://www.eventcatalog.dev/docs/development/guides/messages/adding-messages)
+- [Use the EventCatalog Editor](https://www.eventcatalog.dev/docs/editor/overview)
+- [Generate from integrations](https://www.eventcatalog.dev/integrations)
+- [Manage your catalog with the SDK](https://www.eventcatalog.dev/docs/development/sdk)
+- [Join the community](https://discord.gg/3rjaZMmrAm)
 
-## Found a problem?
+## Found a Problem?
 
 Open an issue on [GitHub](https://github.com/event-catalog/eventcatalog/issues).

package/templates/default/channels/inventory.{env}.events/index.mdx

@@ -1,159 +0,0 @@
----
-id: inventory.{env}.events
-name: Inventory Events Channel
-version: 1.0.0
-summary: |
-  Central event stream for all inventory-related events including stock updates, allocations, and adjustments
-owners:
-  - dboyne
-address: inventory.{env}.events
-protocols:
-  - kafka
-
-parameters:
-  env:
-    enum:
-      - dev
-      - sit
-      - prod
-    description: 'Environment to use'
----
-
-### Overview
-
-The Inventory Events channel is the central stream for all inventory-related events across the system. This includes stock level changes, inventory allocations, adjustments, and stocktake events. Events for a specific SKU are guaranteed to be processed in sequence when using productId as the partition key.
-
-<ChannelInformation />
-
-### Publishing and Subscribing to Events
-
-#### Publishing Example
-
-```python
-from kafka import KafkaProducer
-import json
-from datetime import datetime
-
-# Kafka configuration
-bootstrap_servers = ['localhost:9092']
-topic = f'inventory.{env}.events'
-
-# Create a Kafka producer
-producer = KafkaProducer(
-    bootstrap_servers=bootstrap_servers,
-    value_serializer=lambda v: json.dumps(v).encode('utf-8')
-)
-
-# Example inventory update event
-inventory_event = {
-    "eventType": "STOCK_LEVEL_CHANGED",
-    "timestamp": datetime.utcnow().isoformat(),
-    "version": "1.0",
-    "payload": {
-        "productId": "PROD-456",
-        "locationId": "WH-123",
-        "previousQuantity": 100,
-        "newQuantity": 95,
-        "changeReason": "ORDER_FULFILLED",
-        "unitOfMeasure": "EACH",
-        "batchInfo": {
-            "batchId": "BATCH-789",
-            "expiryDate": "2025-12-31"
-        }
-    },
-    "metadata": {
-        "source": "warehouse_system",
-        "correlationId": "inv-xyz-123",
-        "userId": "john.doe"
-    }
-}
-
-# Send the message - using productId as key for partitioning
-producer.send(
-    topic,
-    key=inventory_event['payload']['productId'].encode('utf-8'),
-    value=inventory_event
-)
-producer.flush()
-
-print(f"Inventory event sent to topic {topic}")
-
-```
-
-### Subscription example
-
-```python
-from kafka import KafkaConsumer
-import json
-from datetime import datetime
-
-class InventoryEventConsumer:
-    def __init__(self):
-        # Kafka configuration
-        self.topic = f'inventory.{env}.events'
-        self.consumer = KafkaConsumer(
-            self.topic,
-            bootstrap_servers=['localhost:9092'],
-            group_id='inventory-processor-group',
-            auto_offset_reset='earliest',
-            enable_auto_commit=False,
-            value_deserializer=lambda x: json.loads(x.decode('utf-8')),
-            key_deserializer=lambda x: x.decode('utf-8') if x else None
-        )
-
-    def process_event(self, event):
-        """Process individual inventory events based on type"""
-        event_type = event.get('eventType')
-
-        if event_type == 'STOCK_LEVEL_CHANGED':
-            self.handle_stock_level_change(event)
-        elif event_type == 'LOW_STOCK_ALERT':
-            self.handle_low_stock_alert(event)
-        # Add more event type handlers as needed
-
-    def handle_stock_level_change(self, event):
-        """Handle stock level change events"""
-        payload = event['payload']
-        print(f"Stock level change detected for product {payload['productId']}")
-        print(f"New quantity: {payload['newQuantity']}")
-        # Add your business logic here
-
-    def handle_low_stock_alert(self, event):
-        """Handle low stock alert events"""
-        payload = event['payload']
-        print(f"Low stock alert for product {payload['productId']}")
-        print(f"Current quantity: {payload['currentQuantity']}")
-        # Add your business logic here
-
-    def start_consuming(self):
-        """Start consuming messages from the topic"""
-        try:
-            print(f"Starting consumption from topic: {self.topic}")
-            for message in self.consumer:
-                try:
-                    # Process the message
-                    event = message.value
-                    print(f"Received event: {event['eventType']} for product: {event['payload']['productId']}")
-
-                    # Process the event
-                    self.process_event(event)
-
-                    # Commit the offset after successful processing
-                    self.consumer.commit()
-
-                except Exception as e:
-                    print(f"Error processing message: {str(e)}")
-                    # Implement your error handling logic here
-                    # You might want to send to a DLQ (Dead Letter Queue)
-
-        except Exception as e:
-            print(f"Consumer error: {str(e)}")
-        finally:
-            # Clean up
-            self.consumer.close()
-
-if __name__ == "__main__":
-    # Create and start the consumer
-    consumer = InventoryEventConsumer()
-    consumer.start_consuming()
-```

package/templates/default/channels/orders.{env}.events/index.mdx

@@ -1,85 +0,0 @@
----
-id: orders.{env}.events
-name: Order Events Channel
-version: 1.0.1
-summary: |
-  Central event stream for all order-related events in the order processing lifecycle
-owners:
-  - dboyne
-address: orders.{env}.events
-protocols:
-  - kafka
-routes:
-  - id: inventory-queue
-parameters:
-  env:
-    enum:
-      - dev
-      - sit
-      - prod
-    description: 'Environment to use'
----
-
-### Overview
-
-The Orders Events channel is the central stream for all order-related events across the order processing lifecycle. This includes order creation, updates, payment status, fulfillment status, and customer communications. All events related to a specific order are guaranteed to be processed in sequence when using orderId as the partition key.
-
-<ChannelInformation />
-
-### Publishing a message using Kafka
-
-Here is an example of how to publish an order event using Kafka:
-
-```python
-from kafka import KafkaProducer
-import json
-from datetime import datetime
-
-# Kafka configuration
-bootstrap_servers = ['localhost:9092']
-topic = f'orders.{env}.events'
-
-# Create a Kafka producer
-producer = KafkaProducer(
-    bootstrap_servers=bootstrap_servers,
-    value_serializer=lambda v: json.dumps(v).encode('utf-8')
-)
-
-# Example order created event
-order_event = {
-    "eventType": "ORDER_CREATED",
-    "timestamp": datetime.utcnow().isoformat(),
-    "version": "1.0",
-    "payload": {
-        "orderId": "12345",
-        "customerId": "CUST-789",
-        "items": [
-            {
-                "productId": "PROD-456",
-                "quantity": 2,
-                "price": 29.99
-            }
-        ],
-        "totalAmount": 59.98,
-        "shippingAddress": {
-            "street": "123 Main St",
-            "city": "Springfield",
-            "country": "US"
-        }
-    },
-    "metadata": {
-        "source": "web_checkout",
-        "correlationId": "abc-xyz-123"
-    }
-}
-
-# Send the message - using orderId as key for partitioning
-producer.send(
-    topic,
-    key=order_event['payload']['orderId'].encode('utf-8'),
-    value=order_event
-)
-producer.flush()
-
-print(f"Order event sent to topic {topic}")
-```