@eventcatalog/create-eventcatalog 4.3.8 → 4.3.9

package/dist/index.js

@@ -29831,7 +29831,7 @@ var import_os2 = __toESM(require("os"));
 var package_default = {
   name: "@eventcatalog/create-eventcatalog",
   description: "Create EventCatalog with one command",
-  version: "4.3.8",
+  version: "4.3.9",
   license: "MIT",
   bin: {
     "create-catalog": "./dist/index.js"

package/package.json

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

package/templates/default/domains/Catalog/index.mdx

@@ -54,6 +54,12 @@ The **Catalog** domain is responsible for the lifecycle of every product Acme In
 
 The **Product Catalog System** is the authoritative source of product data. Whenever a product is created, updated or deleted it publishes a domain event. The **Search System** subscribes to those events, keeps its search index in sync, and exposes a search API so other teams never have to query the catalog database directly.
 
+## Architecture Graph
+
+Where Catalog sits in the wider architecture — its systems and messages, and the neighbouring domains it talks to.
+
+<ArchitectureGraph />
+
 The diagram below shows the domain's systems, how they relate, and the people who interact with them.
 
 <ContextDiagram />

package/templates/default/domains/Ordering/index.mdx

@@ -68,3 +68,9 @@ The systems in this domain, how they relate, and the people who interact with th
 The components that make up this domain.
 
 <NodeGraph />
+
+## Architecture Graph
+
+Where Ordering sits in the wider architecture — its systems and messages, and the neighbouring domains it talks to.
+
+<ArchitectureGraph />

package/templates/default/domains/Ordering/systems/checkout-system/index.mdx

@@ -55,3 +55,9 @@ The services and messages that make up this system.
 - [[command\|reserve-inventory]] — reserve stock for the items in the cart.
 - [[command\|authorize-payment]] — authorize payment for the order total.
 - [[command\|create-order]] — create the order in the Order Management System.
+
+## Architecture Graph
+
+The checkout system's neighbourhood in the wider architecture.
+
+<ArchitectureGraph />

package/templates/default/domains/Payments/index.mdx

@@ -67,3 +67,9 @@ The **Payment Processing System** is the internal orchestrator. When the Orderin
 The systems in this domain, how they relate, and the people who interact with them.
 
 <ContextDiagram />
+
+## Architecture Graph
+
+Where Payments sits in the wider architecture — its systems and messages, and the neighbouring domains it talks to.
+
+<ArchitectureGraph />

package/templates/default/domains/Payments/systems/payment-processing-system/services/PaymentAPI/index.mdx

@@ -46,6 +46,12 @@ The **Payment API** is the entry point to the Payment Processing System. It rece
 
 <NodeGraph />
 
+## Architecture Graph
+
+How PaymentAPI connects to the rest of the catalog — the messages it exchanges and the systems around it.
+
+<ArchitectureGraph />
+
 <MessageTable format="all" limit={8} />
 
 <Footer />

package/templates/default/pages/homepage.astro

@@ -2,8 +2,8 @@
 import { getCollection } from 'astro:content';
 
 // EventCatalog injects its components via Astro.props.components. Destructure the ones
-// this landing page uses (including the SystemContextMap embed).
-const { Tile, Tiles, SystemContextMap } = Astro.props.components;
+// this landing page uses (including the ArchitectureGraph and SystemContextMap embeds).
+const { Tile, Tiles, SystemContextMap, ArchitectureGraph } = Astro.props.components;
 
 // Count the catalog's top-level resources. We filter out versioned/ entries so each
 // resource is counted once (by its latest version).
@@ -49,6 +49,16 @@ const stats = [
     }
   </div>
 
+  {/* Architecture graph */}
+  <h2 class="text-2xl font-semibold text-[rgb(var(--ec-page-text))] mt-12 mb-2">Architecture</h2>
+  <p class="text-[rgb(var(--ec-page-text-muted))] font-light mb-2">
+    Every resource in the catalog and the relationships between them.
+  </p>
+</div>
+
+<ArchitectureGraph lens="domains" lensPicker="true" />
+
+<div class="not-prose">
   {/* System context map */}
   <h2 class="text-2xl font-semibold text-[rgb(var(--ec-page-text))] mt-12 mb-2">System context map</h2>
   <p class="text-[rgb(var(--ec-page-text-muted))] font-light mb-2">