@eventcatalog/core 4.1.3 → 4.1.5

package/dist/docs/tutorial/06-create-a-service.md

@@ -0,0 +1,99 @@
+---
+sidebar_position: 3
+sidebar_label: Create a service
+title: Create a service
+description: Add the first service to your tutorial catalog.
+---
+
+import ChapterOverview from '@site/src/components/MDX/ChapterOverview';
+
+In this step, you will add your first service to the catalog.
+
+A service is a system, application, or process that owns part of your architecture. Later in the tutorial, this service will send and receive events. For now, you only need a simple service page that gives people a place to start.
+
+<ChapterOverview
+  items={[
+    {
+      icon: 'folder',
+      text: 'Create the folder structure for OrderService.',
+    },
+    {
+      icon: 'file',
+      text: 'Add an index.mdx file with the service metadata.',
+    },
+    {
+      icon: 'eye',
+      text: 'Refresh EventCatalog and find the service in the browser.',
+    },
+  ]}
+/>
+
+### Create the service folder
+
+From the root of your catalog, create a new folder for the service:
+
+```bash
+mkdir -p services/OrderService
+```
+
+EventCatalog looks inside the `services` folder for service pages. Each service has its own folder and an `index.mdx` file.
+
+### Add the service page
+
+Create a new file at `services/OrderService/index.mdx`:
+
+```mdx title="services/OrderService/index.mdx"
+---
+id: OrderService
+name: Order Service
+version: 0.0.1
+summary: |
+  Handles customer orders from checkout through to fulfilment.
+---
+
+## Overview
+
+The Order Service is responsible for creating and managing customer orders.
+
+In this tutorial, you will use this service to learn how EventCatalog connects services, domains, events, schemas, and ownership.
+```
+
+Keep the content small for now. The important part is the frontmatter at the top of the file:
+
+- `id` is the stable identifier EventCatalog uses for links and references.
+- `name` is the label people see in the UI.
+- `version` is the version of this service.
+- `summary` appears in service lists and page headers.
+
+### Check the service in EventCatalog
+
+If your catalog is still running, refresh your browser.
+
+If it is not running, start it again:
+
+```bash
+npm run dev
+```
+
+Open the local EventCatalog URL shown in your terminal. You should now see the Order Service in your catalog at [http://localhost:3000/docs/services/OrderService/0.0.1](http://localhost:3000/docs/services/OrderService/0.0.1).
+
+<figure style={{ textAlign: "center" }}>
+  <img
+    src="/img/tutorial/order-service-page.png"
+    alt="The Order Service page in EventCatalog"
+    style={{ display: "block", margin: "0 auto" }}
+  />
+  <figcaption style={{ fontSize: "0.875rem", fontStyle: "italic" }}>The Order Service page after adding the service file.</figcaption>
+</figure>
+
+### What you have now
+
+Your catalog now has one documented service:
+
+- `services/OrderService/index.mdx`
+
+This is the first building block. Next, you will group your architecture around a domain.
+
+### Next
+
+Continue to [Create an event](/docs/tutorial/create-event).

package/dist/docs/tutorial/11-visualize-your-catalog.md

@@ -0,0 +1,105 @@
+---
+sidebar_position: 9
+sidebar_label: Visualize your catalog
+title: Visualize your catalog
+description: Use EventCatalog visualizations to inspect the tutorial architecture.
+---
+
+import ChapterOverview from '@site/src/components/MDX/ChapterOverview';
+
+In this step, you will use EventCatalog visualizations to understand the model you created.
+
+Visualizations help people see how systems connect. They grow as your catalog grows, so the same view can start with one event relationship and later include domains, commands, queries, flows, channels, data stores, agents, and other architecture primitives.
+
+<ChapterOverview
+  items={[
+    {
+      icon: 'network',
+      text: 'Use NodeGraph inside documentation pages.',
+    },
+    {
+      icon: 'eye',
+      text: 'Use the Visualizer to explore the catalog map.',
+    },
+    {
+      icon: 'code',
+      text: 'Export visualizations to Mermaid when you need to share or edit them elsewhere.',
+    },
+  ]}
+/>
+
+### Use NodeGraph on a page
+
+The [`NodeGraph`](/docs/development/components/components/nodegraph) component can be added to domain, service, message, changelog, and custom documentation pages.
+
+Add it to a resource page like this:
+
+```mdx
+<NodeGraph />
+```
+
+When used without props, `NodeGraph` renders a visualization for the current page. For example, on the `OrderPlaced` page it can show the event, the service that publishes it, and the service that consumes it.
+
+You can also render a graph for a specific resource:
+
+```mdx
+<NodeGraph id="E-Commerce" version="0.0.1" type="domain" />
+```
+
+This is useful when you want the visualization to appear directly next to the documentation people are reading.
+
+### Use the Visualizer
+
+The Visualizer is the full map view in EventCatalog. It gives you more room to explore how resources connect across your catalog.
+
+Open the `OrderPlaced` map from the event page. You should see:
+
+- `OrderService` publishes `OrderPlaced`.
+- `InventoryService` consumes `OrderPlaced`.
+- the relationship between the producer, event, and consumer.
+
+<figure style={{ textAlign: "center" }}>
+  <img
+    src="/img/tutorial/order-placed-producer-consumer-map.png"
+    alt="The OrderPlaced visualizer map showing OrderService as producer and InventoryService as consumer"
+    style={{ display: "block", margin: "0 auto" }}
+  />
+  <figcaption style={{ fontSize: "0.875rem", fontStyle: "italic" }}>
+    The OrderPlaced map shows the producer, event, and consumer relationship.
+  </figcaption>
+</figure>
+
+Now open the `E-Commerce` domain map. The domain only references the services, but the map can still show the event relationship between them.
+
+<figure style={{ textAlign: "center" }}>
+  <img
+    src="/img/tutorial/e-commerce-domain-map.png"
+    alt="The E-Commerce domain visualizer map showing services and their event relationship"
+    style={{ display: "block", margin: "0 auto" }}
+  />
+  <figcaption style={{ fontSize: "0.875rem", fontStyle: "italic" }}>
+    The E-Commerce domain map gives a focused view of the services in that part of the architecture.
+  </figcaption>
+</figure>
+
+### Export to Mermaid
+
+NodeGraph visualizations can be switched to Mermaid view or copied as Mermaid diagram code. This is useful when you want to share the architecture with another tool, paste it into documentation, or give it to an AI assistant for review.
+
+You can learn more in the [NodeGraph docs](/docs/development/components/components/nodegraph#export-as-mermaid) and the [Mermaid docs](/docs/development/components/diagram-syntax/mermaid#export-nodegraphs-as-mermaid).
+
+### What you have now
+
+You can use EventCatalog to:
+
+- embed visualizations directly inside documentation pages
+- explore the wider catalog with the Visualizer
+- see events between systems
+- understand how services, domains, ownership, and messages connect
+- export visualizations as Mermaid when you need to use them elsewhere
+
+As you add more resources, these visualizations become more useful. Commands, queries, domains, flows, channels, data stores, agents, and extra services can all add more context to the map.
+
+### Next
+
+Continue to [Build and deploy your catalog](/docs/tutorial/build-your-catalog).

package/dist/docs/tutorial/12-build-your-catalog.md

@@ -0,0 +1,79 @@
+---
+sidebar_position: 10
+sidebar_label: Build and deploy
+title: Build and deploy your catalog
+description: Build your EventCatalog site and choose a deployment path.
+---
+
+import ChapterOverview from '@site/src/components/MDX/ChapterOverview';
+
+In this step, you will build your catalog and decide how you want to deploy it.
+
+Most new EventCatalog projects build as a static site. That means EventCatalog creates HTML files that you can host on most static hosting platforms.
+
+<ChapterOverview
+  items={[
+    {
+      icon: 'code',
+      text: 'Run a production build.',
+    },
+    {
+      icon: 'eye',
+      text: 'Preview the built catalog locally.',
+    },
+    {
+      icon: 'server',
+      text: 'Choose a deployment path for your team.',
+    },
+  ]}
+/>
+
+### Build the catalog
+
+Run:
+
+```bash
+npm run build
+```
+
+EventCatalog creates a production-ready build in the `dist` folder.
+
+You can learn more in the [develop and build guide](/docs/development/getting-started/develop-and-build) and the [static build guide](/docs/development/deployment/build-and-deploy).
+
+### Preview the build
+
+After the build finishes, preview the built catalog locally:
+
+```bash
+npm run preview
+```
+
+This lets you check the production build before you publish it.
+
+If the build fails, check the error in your terminal first. Common issues are broken links, invalid frontmatter, schema path mistakes, or missing files.
+
+### Choose a deployment path
+
+For most first catalogs, static hosting is the simplest path. You can deploy the `dist` folder to the hosting platform your team already uses.
+
+EventCatalog also supports server-side rendering for larger catalogs or features that need a server.
+
+Useful deployment docs:
+
+- [Build and deploy](/docs/development/deployment/build-and-deploy)
+- [Hosting options](/docs/development/deployment/hosting-options)
+- [Deployment workflows](/docs/development/deployment/deployment-workflows)
+- [SSR mode](/docs/development/deployment/build-ssr-mode)
+
+### What you have now
+
+You now know how to:
+
+- build the catalog for production
+- preview the production build locally
+- choose between static hosting and server-side rendering
+
+
+### Next
+
+Continue to [Next steps](/docs/tutorial/next-steps).

package/dist/docs/tutorial/14-next-steps.md

@@ -0,0 +1,108 @@
+---
+sidebar_position: 11
+sidebar_label: Next steps
+title: Next steps
+description: Grow your catalog beyond the tutorial.
+---
+
+import ChapterOverview from '@site/src/components/MDX/ChapterOverview';
+
+Congratulations, you have created your first EventCatalog.
+
+This is a real catalog now. It models architecture primitives, links them together, and gives people a place to understand how part of your system works.
+
+<ChapterOverview
+  title="Your catalog now has..."
+  description="The first pieces of a useful architecture catalog"
+  items={[
+    {
+      icon: 'server',
+      text: 'Services that describe the systems in your architecture.',
+    },
+    {
+      icon: 'network',
+      text: 'An event with producer and consumer relationships.',
+    },
+    {
+      icon: 'code',
+      text: 'A schema that explains the event payload.',
+    },
+    {
+      icon: 'folder',
+      text: 'Ownership and a domain to group the work.',
+    },
+    {
+      icon: 'eye',
+      text: 'Visualizations and a production build path.',
+    },
+  ]}
+/>
+
+This is enough to give people a useful first view of your architecture. From here, you can keep adding detail in the way that fits your team.
+
+### See a fuller catalog
+
+The tutorial catalog is small on purpose. EventCatalog can model many more architecture primitives, including [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), [data stores](/docs/development/guides/resources/data/introduction), [data products](/docs/development/guides/resources/data-products/introduction), [agents](/docs/development/guides/resources/agents/introduction), [owners](/docs/development/guides/owners/what-are-teams-and-users), [domains](/docs/development/guides/domains/introduction), [flows](/docs/development/guides/resources/flows/introduction), and the relationships between them.
+
+You can explore the public [EventCatalog demo catalog](https://demo.eventcatalog.dev/) to see a larger example.
+
+<figure style={{ textAlign: "center" }}>
+  <img
+    src="/img/tutorial/demo-catalog-orders-service-visualizer.png"
+    alt="The EventCatalog demo visualizer showing a larger Orders Service architecture"
+    style={{ display: "block", margin: "0 auto" }}
+  />
+  <figcaption style={{ fontSize: "0.875rem", fontStyle: "italic" }}>
+    The demo catalog visualizer shows services, events, channels, data stores, agents, and workflows connected together.
+  </figcaption>
+</figure>
+
+[Open this view in the demo catalog](https://demo.eventcatalog.dev/visualiser/services/OrdersService/0.0.3).
+
+### Add more documentation
+
+Every resource page is Markdown and MDX. You can add more explanation, diagrams, links, runbooks, examples, or any other content that helps people understand the system.
+
+Useful docs:
+
+- [Using components](/docs/development/components/using-components)
+- [Custom components](/docs/development/components/custom-components/introduction)
+- [Resource references](/docs/development/components/resource-references)
+- [Bring your own documentation](/docs/development/bring-your-own-documentation/custom-pages/adding-custom-docs)
+
+### Edit visually with EventCatalog Editor
+
+If you prefer a visual local editor, try [EventCatalog Editor](/docs/editor/overview). It runs locally and gives you a UI for editing the catalog files in your project.
+
+### Automate from existing specifications
+
+You do not have to maintain everything by hand. EventCatalog can generate catalog resources from specifications and registries.
+
+Useful plugin docs:
+
+- [OpenAPI plugin](/docs/plugins/openapi/intro)
+- [AsyncAPI plugin](/docs/plugins/asyncapi/intro)
+- [Confluent Schema Registry plugin](/docs/plugins/confluent-schema-registry/intro)
+- [GitHub plugin](/docs/plugins/github/intro)
+
+### Model more architecture primitives
+
+The tutorial focused on services, events, schemas, owners, and domains. EventCatalog can model more of your architecture as your catalog grows.
+
+Use these docs when you are ready to add more primitives to your catalog:
+
+- [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)
+- [Data stores](/docs/development/guides/resources/data/introduction)
+- [Data products](/docs/development/guides/resources/data-products/introduction)
+- [Agents](/docs/development/guides/resources/agents/introduction)
+- [Flows](/docs/development/guides/resources/flows/add-flows-to-resources)
+- [Owners](/docs/development/guides/owners/what-are-teams-and-users)
+
+### Keep improving the catalog
+
+Start small, keep the content close to the systems it describes, and add more detail when people ask questions the catalog cannot answer yet.

package/dist/docs/tutorial/_category_.json

@@ -0,0 +1,12 @@
+{
+  "label": "Tutorial",
+  "position": 1,
+  "collapsible": false,
+  "collapsed": false,
+  "link": {
+    "type": "generated-index",
+    "slug": "tutorial",
+    "title": "EventCatalog Tutorial",
+    "description": "Build your first EventCatalog from a small commerce architecture and learn how domains, services, messages, schemas, owners, and visualizations fit together."
+  }
+}

package/dist/eventcatalog.cjs

@@ -144,7 +144,7 @@ var verifyRequiredFieldsAreInCatalogConfigFile = async (projectDirectory) => {
 var import_picocolors = __toESM(require("picocolors"), 1);
 
 // package.json
-var version = "4.1.3";
+var version = "4.1.5";
 
 // src/constants.ts
 var VERSION = version;

package/dist/eventcatalog.js

@@ -1,16 +1,16 @@
 import {
   log_build_default
-} from "./chunk-DDGOJV25.js";
+} from "./chunk-DIUAURE2.js";
 import {
   runMigrations
 } from "./chunk-XUAF2H54.js";
 import "./chunk-CA4U2JP7.js";
 import {
   generate
-} from "./chunk-WEDJTUSQ.js";
+} from "./chunk-E6IUV4GX.js";
 import {
   logger
-} from "./chunk-TUKKXNQR.js";
+} from "./chunk-G74MXXTG.js";
 import {
   resolve_catalog_dependencies_default
 } from "./chunk-LHR4G2UO.js";
@@ -20,7 +20,7 @@ import {
 import {
   watch
 } from "./chunk-CAJUIMDJ.js";
-import "./chunk-PDQER3NQ.js";
+import "./chunk-GIU3S4CI.js";
 import "./chunk-K2XIENVT.js";
 import {
   catalogToAstro
@@ -28,7 +28,7 @@ import {
 import "./chunk-W5JQON7Z.js";
 import {
   VERSION
-} from "./chunk-G3D7IZ67.js";
+} from "./chunk-X77TET65.js";
 import {
   linkCoreNodeModules,
   resolveInstalledCoreNodeModules

package/dist/generate.cjs

@@ -108,7 +108,7 @@ var getEventCatalogConfigFile = async (projectDirectory) => {
 var import_picocolors = __toESM(require("picocolors"), 1);
 
 // package.json
-var version = "4.1.3";
+var version = "4.1.5";
 
 // src/constants.ts
 var VERSION = version;

package/dist/generate.js

@@ -1,8 +1,8 @@
 import {
   generate
-} from "./chunk-WEDJTUSQ.js";
-import "./chunk-TUKKXNQR.js";
-import "./chunk-G3D7IZ67.js";
+} from "./chunk-E6IUV4GX.js";
+import "./chunk-G74MXXTG.js";
+import "./chunk-X77TET65.js";
 import "./chunk-6QENHZZP.js";
 export {
   generate

package/dist/utils/cli-logger.cjs

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(cli_logger_exports);
 var import_picocolors = __toESM(require("picocolors"), 1);
 
 // package.json
-var version = "4.1.3";
+var version = "4.1.5";
 
 // src/constants.ts
 var VERSION = version;

package/dist/utils/cli-logger.js

@@ -1,7 +1,7 @@
 import {
   logger
-} from "../chunk-TUKKXNQR.js";
-import "../chunk-G3D7IZ67.js";
+} from "../chunk-G74MXXTG.js";
+import "../chunk-X77TET65.js";
 export {
   logger
 };

package/eventcatalog/public/favicon.svg

@@ -0,0 +1,8 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="58 54 1133 1133" role="img" aria-labelledby="t">
+<title id="t">Reading cat logo</title>
+<style>
+  path { fill: #000; }
+  @media (prefers-color-scheme: dark) { path { fill: #fff; } }
+</style>
+<path fill-rule="evenodd" d="M 445 55 c -174.6 0.5 -188.1 0.7 -196.5 2.3 -20.7 4.1 -35.3 8.5 -51 15.3 -66.7 28.8 -114.7 86.9 -130.3 157.9 l -2.6 12 -0.4 371 c -0.2 261 0 373.8 0.8 380.5 4.6 40.7 21.8 79.6 49.8 113 36.8 43.9 89.5 72.4 144.2 77.9 5.9 0.6 148.2 1.1 372.5 1.3 345.2 0.3 363.5 0.2 373 -1.5 32.1 -5.7 58.7 -16.4 85.5 -34.2 53.2 -35.3 89.1 -93.6 96 -156 0.8 -7.2 1 -114.8 0.8 -381.5 l -0.3 -371.5 -2.2 -10.4 c -7.7 -35.9 -18.8 -61.1 -38.9 -88.2 -9.5 -12.8 -30.7 -34.1 -43.4 -43.5 -34.4 -25.6 -73.7 -40.9 -113.5 -44.3 -12.5 -1.1 -182.7 -1.1 -543.5 -0.1 z m -26.3 152.5 c 30.7 11.6 86.7 67 122.9 121.6 l 8.4 12.6 9.7 -2.3 c 13.3 -3.3 30.3 -6.1 44.8 -7.5 15.1 -1.5 51.8 -0.6 67.5 1.6 10.1 1.4 37.1 6.8 40.5 8.1 0.7 0.3 3.6 -3.4 7.1 -8.8 18.3 -29.1 37.9 -53.5 64.7 -80.7 31.8 -32.2 53.3 -47 68.5 -47.1 10.5 -0 16.2 4.1 22.3 16.1 11.6 23 17.3 80.8 15 153.1 l -1 33.7 6 14.7 c 3.2 8 7.8 20.4 10 27.5 2.3 7.1 4.5 12.9 4.9 12.9 0.4 -0 5 -1.5 10.1 -3.4 29.8 -10.8 61.4 -20.5 89.6 -27.5 20 -5.1 21.5 -5.1 25.9 -0.7 2.9 2.9 3.4 4.1 3.4 7.9 0 3.4 -0.6 5.3 -2.5 7.5 -2.9 3.5 -4.7 4.3 -18 7.7 -23.9 6.3 -83.7 25.2 -103 32.5 -2 0.8 -2 1.2 -1 10.6 0.5 5.3 1.5 9.9 2 10 0.6 0.2 16.8 2.4 36 4.9 69.6 9.1 85.9 11.5 89.4 13.3 10.1 5.1 7.6 20.4 -3.6 21.9 -3.7 0.5 -26.4 -2.1 -63.3 -7.2 -18.4 -2.6 -56.7 -7.5 -58 -7.5 -0.4 -0 -1 0.8 -1.2 1.8 -0.4 1.4 -2.9 2.3 -11.4 4.1 -50.2 10.3 -130.1 33.1 -167.9 47.8 -35.1 13.6 -69.4 33.4 -96.1 55.6 -6.6 5.4 -10.1 7.7 -10.9 7.1 -0.7 -0.5 -5.8 -4.6 -11.5 -9.2 -25 -20.2 -55.1 -37.5 -88.5 -50.7 -39.3 -15.6 -111.9 -36.5 -170.7 -49.1 -15.1 -3.2 -17.8 -4.1 -17.8 -5.6 0 -2.4 0.4 -2.4 -35 2.2 -16.8 2.2 -42.6 5.7 -57.5 7.6 -14.8 2 -28.8 3.3 -31 3 -5.9 -0.7 -9.5 -5.1 -9.5 -11.5 0 -5.7 2.4 -9.4 7.3 -11 3.2 -1.1 62.2 -9.4 103.2 -14.6 11.6 -1.5 21.3 -3 21.7 -3.3 0.3 -0.4 0.9 -5 1.3 -10.3 l 0.7 -9.6 -30.3 -10.1 c -24.9 -8.3 -73.2 -22.8 -85.2 -25.6 -1.5 -0.4 -4.1 -1.9 -5.8 -3.4 -2.6 -2.3 -3.3 -3.8 -3.7 -8 -0.4 -4.7 -0.2 -5.4 2.5 -8.1 1.7 -1.6 4.3 -3.3 5.8 -3.7 5.8 -1.4 46 9.3 88.5 23.7 16.2 5.5 30.3 10.3 31.2 10.6 1 0.3 2 -0.1 2.2 -0.8 4.6 -14.9 9 -27.2 14 -39.4 l 6.2 -15 -1 -32.5 c -1.5 -48.5 0.9 -93.8 6.4 -122.4 5 -25.8 12 -40.4 21.9 -45.6 5.4 -2.9 15.3 -2.6 23.8 0.5 z m -67.6 364.4 c 81.9 16.7 161.5 40.4 199.3 59.3 11.7 5.9 29.8 16.7 34.1 20.3 l 3 2.6 -9.5 -0.4 c -8.7 -0.4 -15.5 -2.1 -78.5 -19.7 -37.9 -10.6 -76 -21.2 -84.5 -23.5 -56.6 -15.7 -123.4 -34.6 -123.8 -35 -0.6 -0.6 13.5 -2.8 37.3 -5.8 6.4 -0.8 8.6 -0.6 22.6 2.2 z m 589.5 -0.4 c 10.4 1.4 20.4 2.8 22.3 3.2 3.4 0.6 -40.5 13.5 -170.9 50.2 -20.1 5.7 -42.6 12 -50 14.1 -50.1 14.2 -53.5 15 -60.8 15 -4 -0 -7.2 -0.3 -7.2 -0.8 0 -2.1 28.9 -19.2 45.8 -27.1 36.1 -16.7 110.6 -38.3 193.2 -55.9 6.6 -1.4 7.1 -1.4 27.6 1.3 z m -672.2 33.1 c 13.2 3.6 31.1 8.5 39.6 10.9 8.5 2.4 35.3 9.8 59.5 16.4 52.5 14.3 120.5 33 167.5 46.1 22.9 6.3 23.5 6.6 24.9 9.6 0.8 1.8 1.1 45.6 1.1 162.2 0 175.7 0.4 164.2 -5.9 164.2 -1.5 -0 -12.4 -2.7 -24.2 -6.1 -20.6 -5.8 -66.3 -18.6 -188.9 -52.7 -31.6 -8.8 -63.1 -17.5 -70 -19.2 -13 -3.3 -16.3 -4.8 -17.9 -7.8 -1.1 -2.1 -7.2 -104.7 -15.6 -262.7 -1.3 -25.9 -2.7 -50.5 -3.1 -54.7 -0.6 -7.3 -0.5 -7.8 2 -10.2 1.4 -1.5 3.5 -2.6 4.7 -2.6 1.2 -0 13 3 26.3 6.6 z m 748.1 -5.6 c 3.9 1.5 4.4 4.2 3.4 19.5 -0.8 12.4 -4.2 70.9 -15 256 -2.6 46 -3.3 53.3 -4.8 55.5 -1.9 2.6 1.3 1.6 -78.6 23.9 -9.9 2.8 -34.2 9.6 -54 15.1 -19.8 5.6 -50.4 14.1 -68 19 -17.6 4.9 -45.7 12.8 -62.5 17.5 -16.7 4.7 -31.7 8.5 -33.2 8.5 -6.3 -0 -5.9 11.3 -5.6 -165.1 0.2 -88.2 0.7 -161.2 1.2 -162.1 0.9 -1.9 4.6 -3.1 32.6 -10.7 10.2 -2.8 25.9 -7.1 35 -9.6 9.1 -2.5 32 -8.9 51 -14.1 47.4 -13.1 124.2 -34.5 168.5 -46.9 14.3 -4 26.3 -7.4 26.7 -7.4 0.4 -0.1 1.8 0.3 3.3 0.9 z m -351.7 95.3 c 0.9 0.7 1.2 35.1 1.2 166.7 l 0 165.9 -2.2 1.3 c -1.8 1 -10.2 1.3 -35.1 1.3 -31.4 -0 -32.9 -0.1 -34.3 -1.9 -2.1 -2.9 -2.1 -330.7 0 -332.8 1.1 -1.2 7.6 -1.4 35.2 -1.4 18.7 0.1 34.5 0.5 35.2 0.9 z"/>
+</svg>

package/eventcatalog/src/components/Seo.astro

@@ -25,7 +25,11 @@ if (typeof _image === 'string') {
 <meta charset="UTF-8" />
 <meta name="viewport" content="width=device-width, initial-scale=1.0" />
 <meta name="viewport" content="width=device-width" />
-<link rel="icon" type="image/png" href={buildUrl('/logo.png', true)} />
+<link rel="icon" href={buildUrl('/favicon.ico', true)} sizes="any" />
+<link rel="icon" type="image/svg+xml" href={buildUrl('/favicon.svg', true)} />
+<link rel="icon" type="image/png" sizes="32x32" href={buildUrl('/favicon-32x32.png', true)} />
+<link rel="icon" type="image/png" sizes="16x16" href={buildUrl('/favicon-16x16.png', true)} />
+<link rel="apple-touch-icon" href={buildUrl('/apple-touch-icon.png', true)} />
 
 <SEO
   title={title}

package/eventcatalog/src/enterprise/auth/error.astro

@@ -21,7 +21,9 @@ const errorMessage = errorMessages[error] || errorMessages.Default;
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width" />
-    <link rel="icon" type="image/png" href="/logo.png" />
+    <link rel="icon" href="/favicon.ico" sizes="any" />
+    <link rel="icon" type="image/svg+xml" href="/favicon.svg" />
+    <link rel="apple-touch-icon" href="/apple-touch-icon.png" />
     <meta name="generator" content={Astro.generator} />
     <title>Authentication Error - EventCatalog</title>
   </head>

package/eventcatalog/src/enterprise/auth/login.astro

@@ -102,7 +102,9 @@ const providerConfig = {
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width" />
-    <link rel="icon" type="image/png" href="/logo.png" />
+    <link rel="icon" href="/favicon.ico" sizes="any" />
+    <link rel="icon" type="image/svg+xml" href="/favicon.svg" />
+    <link rel="apple-touch-icon" href="/apple-touch-icon.png" />
     <meta name="generator" content={Astro.generator} />
     <title>Sign In | {title}</title>
     <link rel="preconnect" href="https://fonts.googleapis.com" />

package/eventcatalog/src/layouts/VerticalSideBarLayout.astro

@@ -5,6 +5,8 @@ interface Props {
   description?: string;
   showNestedSideBar?: boolean;
   showHeader?: boolean;
+  /** Wrap the page content in EventCatalog's default app content container. Defaults to true. */
+  wrapContent?: boolean;
   // When true, the main content uses a reduced horizontal padding instead of the
   // default 5rem. Used by wide pages such as the custom landing page.
   reducedContentPadding?: boolean;
@@ -89,6 +91,7 @@ if (isCustomStylesEnabled()) {
 }
 
 const currentPath = Astro.url.pathname;
+const wrapContent = Astro.props.wrapContent ?? true;
 
 const getDefaultUrl = (route: string, defaultValue: string) => {
   if (route === 'docs/custom') {
@@ -762,7 +765,7 @@ const verticalNavAutoCollapsePaths = [buildUrl('/discover', true), buildUrl('/do
       }
       <main class="content-panel sidebar-transition w-full bg-[rgb(var(--ec-page-bg))]" id="content">
         {
-          Astro.slots.has('sidebar-content') ? (
+          Astro.slots.has('sidebar-content') || !wrapContent ? (
             <slot />
           ) : (
             <div class={`app-content-wrapper ${reducedContentPadding ? 'app-content-wrapper--reduced-padding' : ''}`}>

package/eventcatalog/src/pages/studio.astro

@@ -42,7 +42,9 @@ const hasResources = resourcesToShow.length > 0;
   <head>
     <meta charset="UTF-8" />
     <meta name="viewport" content="width=device-width" />
-    <link rel="icon" type="image/png" href="/logo.png" />
+    <link rel="icon" href="/favicon.ico" sizes="any" />
+    <link rel="icon" type="image/svg+xml" href="/favicon.svg" />
+    <link rel="apple-touch-icon" href="/apple-touch-icon.png" />
     <meta name="generator" content={Astro.generator} />
     <title>EventCatalog Studio</title>
   </head>

package/eventcatalog/src/toolkit/layouts/Layout.astro

@@ -20,6 +20,12 @@ import VerticalSideBarLayout from '@layouts/VerticalSideBarLayout.astro';
 const { title, description, sidebar = true, showHeader = true } = Astro.props;
 ---
 
-<VerticalSideBarLayout title={title} description={description} showHeader={showHeader} showNestedSideBar={sidebar}>
+<VerticalSideBarLayout
+  title={title}
+  description={description}
+  showHeader={showHeader}
+  showNestedSideBar={sidebar}
+  wrapContent={false}
+>
   <slot />
 </VerticalSideBarLayout>

package/package.json

@@ -7,7 +7,7 @@
   },
   "license": "SEE LICENSE IN LICENSE",
   "type": "module",
-  "version": "4.1.3",
+  "version": "4.1.5",
   "publishConfig": {
     "access": "public"
   },
@@ -117,8 +117,8 @@
     "uuid": "^10.0.0",
     "zod": "^4.3.6",
     "@eventcatalog/linter": "1.1.4",
-    "@eventcatalog/visualiser": "^4.0.1",
-    "@eventcatalog/sdk": "2.25.0"
+    "@eventcatalog/sdk": "2.25.0",
+    "@eventcatalog/visualiser": "^4.0.1"
   },
   "devDependencies": {
     "@astrojs/check": "^0.9.9",