@eventcatalog/create-eventcatalog 4.3.2 → 4.3.3

package/dist/index.js

@@ -29808,7 +29808,7 @@ var import_os2 = __toESM(require("os"));
 var package_default = {
   name: "@eventcatalog/create-eventcatalog",
   description: "Create EventCatalog with one command",
-  version: "4.3.2",
+  version: "4.3.3",
   license: "MIT",
   bin: {
     "create-catalog": "./dist/index.js"
@@ -29915,6 +29915,7 @@ var installTemplate = async ({
     private: true,
     scripts: {
       dev: "eventcatalog dev",
+      editor: "npx @eventcatalog/editor@latest",
       build: "eventcatalog build",
       start: "eventcatalog start",
       preview: "eventcatalog preview",
@@ -30051,14 +30052,17 @@ async function createApp({
     console.log(`    ${import_chalk3.default.dim("\u25A0")} Git initialized`);
   }
   console.log();
-  console.log(`  ${import_chalk3.default.cyan.bold("next")}  You're all set! Explore your project!`);
+  console.log(`  You're all set! Explore your catalog!`);
   console.log();
-  console.log(`  Enter your project directory using ${import_chalk3.default.cyan("cd " + cdpath)}`);
-  console.log(`  Run ${import_chalk3.default.cyan(`${packageManager2} run dev`)} to start the dev server. ${import_chalk3.default.dim("CTRL+C to stop.")}`);
+  console.log(`    ${import_chalk3.default.dim("\u25A0")} ${import_chalk3.default.cyan("cd " + cdpath)}`);
+  console.log(`    ${import_chalk3.default.dim("\u25A0")} Run ${import_chalk3.default.cyan(`${packageManager2} run dev`)} to start the dev server.`);
   console.log();
   console.log(`  ${import_chalk3.default.dim("Star us on GitHub:")} ${import_chalk3.default.underline("https://github.com/event-catalog/eventcatalog")}`);
   console.log(`  ${import_chalk3.default.dim("Join our Discord:")}  ${import_chalk3.default.underline("https://eventcatalog.dev/discord")}`);
   console.log();
+  console.log(`  ${import_chalk3.default.dim("Want a better editing experience?")}`);
+  console.log(`  Run ${import_chalk3.default.cyan(`${packageManager2} run editor`)} to open EventCatalog Editor.`);
+  console.log();
 }
 
 // helpers/get-pkg-manager.ts

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@eventcatalog/create-eventcatalog",
   "description": "Create EventCatalog with one command",
-  "version": "4.3.2",
+  "version": "4.3.3",
   "license": "MIT",
   "bin": {
     "create-catalog": "./dist/index.js"

package/templates/amazon-api-gateway/README-template.md

@@ -1,27 +1,54 @@
-# My Amazon API Gateway Event Catalog
+# Welcome to EventCatalog
 
-Welcome to your new Amazon API Gateway EventCatalog!
+[EventCatalog](https://www.eventcatalog.dev/) is your architecture catalog for distributed systems. This template adds the Amazon API Gateway generator so you can import OpenAPI specs from API Gateway 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 apis in the `eventcatalog.config.js` file
-1. Run `npm run generate` to import your OpenAPI specs from apigateway and document them.
-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 your APIs in `eventcatalog.config.js`.
+3. Import your OpenAPI specs:
 
-### What else can you do?
+```sh
+npm run generate
+```
 
-With the ApiGateway integration you can :
+4. Start the catalog:
 
-- Document your apis
-- Assign your apis to producers and consumers
-- Assign resources to users and teams in your organization
-- Visualize your APIGateway architecture
-- And much more!
+```sh
+npm run dev
+```
 
-The easiest way to get started and dive deeper is to read the [EventCatalog documentation](https://www.eventcatalog.dev/docs/plugins/amazon-apigateway/intro).
+Open [http://localhost:3000](http://localhost:3000) to view your catalog.
 
-### Found a problem?
+## Edit Your Catalog
 
-If you found a problem or have a feature request, please open an issue on [GitHub](https://github.com/event-catalog/generators).
+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 API Gateway.
+
+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 API Gateway APIs change. You can also run the generator in CI so your catalog stays aligned with AWS.
+
+With this integration you can:
+
+- Document APIs and OpenAPI specs
+- Assign APIs to producers and consumers
+- Connect resources to users and teams
+- Visualize your API Gateway architecture
+
+## 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
+
+- [Amazon API Gateway integration docs](https://www.eventcatalog.dev/docs/plugins/amazon-apigateway/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?
+
+Open an issue on [GitHub](https://github.com/event-catalog/generators).

package/templates/asyncapi/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/confluent/README-template.md

@@ -1,28 +1,55 @@
-# My Confluent Event Catalog
+# Welcome to EventCatalog
 
-Welcome to your new Confluent Event Catalog!
+[EventCatalog](https://www.eventcatalog.dev/) is your architecture catalog for distributed systems. This template adds the Confluent Schema Registry generator so you can import schemas and topics, then 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. Run Confluent Cloud locally, or configure your `schemaRegistryUrl` 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 Confluent settings.
+2. Run Confluent locally, or configure `schemaRegistryUrl` in `eventcatalog.config.js`.
+3. Import your schemas:
 
-### What else can you do?
+```sh
+npm run generate
+```
 
-With the Confluent Schema Registry integration you can :
+4. Start the catalog:
 
-- Document your schemas, topics
-- 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 schema registry.
+
+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 schemas or topics change. You can also run the generator in CI so your catalog stays aligned with Confluent.
+
+With this integration you can:
+
+- Document schemas and topics
+- Assign schemas to producers and consumers
+- Connect resources to users and teams
 - Visualize your Kafka architecture
-- Add semantic meaning to your schemas and topics
-- And much more!
+- Add semantic meaning to schemas and topics
+
+## 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
 
-The easiest way to get started and dive deeper is to read the [Event Catalog documentation](https://eventcatalog.dev/docs/plugins/confluent-schema-registry/intro).
+- [Confluent Schema Registry integration docs](https://eventcatalog.dev/docs/plugins/confluent-schema-registry/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/default/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/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).