@eventcatalog/core 5.0.0-beta.9 → 5.0.0

package/dist/docs/development/ask-your-architecture/{05-skills/01-introduction.md → 03-install-skills.md}

@@ -1,18 +1,21 @@
 ---
-sidebar_position: 1
+sidebar_position: 3
 keywords:
 - AI Skills
 - Claude Code
 - documentation generation
-sidebar_label: Introduction
-title: AI Skills
-description: Pre-built AI skills to help you document your architecture with EventCatalog
+- installation
+sidebar_label: Install Skills
+title: Install Skills
+description: Install EventCatalog Skills so your AI agent can document your architecture with EventCatalog.
 ---
 
 EventCatalog Skills are pre-built instructions that teach AI agents how to work with your EventCatalog project. Install a skill and your AI agent gains the ability to generate correct documentation, following EventCatalog conventions and best practices.
 
 Skills work with any AI coding agent that supports the skills format (e.g. [Claude Code](https://claude.ai/code)).
 
+**Source code:** [github.com/event-catalog/skills](https://github.com/event-catalog/skills)
+
 ## Why use skills?
 
 When you ask an AI agent to generate EventCatalog documentation, it doesn't know about EventCatalog's frontmatter format, folder structure, or component conventions. Skills solve this by providing the agent with structured instructions and reference material.
@@ -33,8 +36,55 @@ The agent will generate properly formatted `index.mdx` files with correct frontm
 | [Catalog Documentation Creator](https://github.com/event-catalog/skills) | Generates EventCatalog documentation files (services, events, commands, queries, domains, flows, channels, containers) with correct frontmatter, folder structure, and best practices. |
 | [Flow Wizard](https://github.com/event-catalog/skills) | Guides you through documenting a business flow step by step in a conversational session, cross-referencing your existing catalog resources to link services, events, and commands automatically. |
 
-## Getting started
+## Install skills
 
-Head to the [installation guide](/docs/development/ask-your-architecture/skills/installation) to add skills to your project.
+### CLI install (recommended)
 
-**Source code:** [github.com/event-catalog/skills](https://github.com/event-catalog/skills)
+Use [npx skills](https://github.com/vercel-labs/skills) to install skills directly into your project:
+
+```bash
+# Install all EventCatalog skills
+npx skills add event-catalog/skills
+
+# Install a specific skill
+npx skills add event-catalog/skills --skill catalog-documentation-creator
+```
+
+This copies the skill files into your project's `.claude/skills/` directory where your AI agent can access them.
+
+### Clone and copy
+
+Clone the repository and copy the skills you need:
+
+```bash
+git clone https://github.com/event-catalog/skills.git
+cp -r skills/skills/catalog-documentation-creator .claude/skills/
+```
+
+### Git submodule
+
+Add as a submodule for easy updates:
+
+```bash
+git submodule add https://github.com/event-catalog/skills.git .claude/skills/eventcatalog
+```
+
+When new skills are released, pull updates with:
+
+```bash
+git submodule update --remote
+```
+
+### Fork and customize
+
+Fork the repository and tailor skills to your team's conventions:
+
+1. Fork [event-catalog/skills](https://github.com/event-catalog/skills) on GitHub
+2. Modify skills to match your naming conventions, ownership patterns, and schema formats
+3. Install from your fork:
+
+```bash
+npx add-skill https://github.com/YOUR_ORG/eventcatalog-skills
+```
+
+This is useful when your team has specific conventions for IDs, owners, or folder structures that differ from the defaults.

package/dist/docs/development/ask-your-architecture/03-mcp-server/_category_.json

@@ -1,6 +1,6 @@
 {
   "label": "EventCatalog MCP Server",
-  "position": 5,
+  "position": 2,
   "collapsible": true,
   "collapsed": true,
   "link": {

package/dist/docs/development/ask-your-architecture/03-mcp-server/getting-started.md

@@ -8,14 +8,10 @@ description: Connect MCP clients to your EventCatalog
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
-
-<PlanBanner plan="Scale" />
 
 ### Prerequisites
 
 1. **SSR mode** - EventCatalog must run in [server mode](/docs/development/deployment/build-ssr-mode#building-your-eventcatalog-ssr) (not static)
-2. **Scale license** - You can get a 30-day free trial at [eventcatalog.cloud](https://eventcatalog.cloud)
 
 ### Quick start
 
@@ -31,6 +27,11 @@ For local development:
 http://localhost:3000/docs/mcp/
 ```
 
+The server accepts URLs with or without a trailing slash (`/docs/mcp` and `/docs/mcp/`).
+
+To find your server URLs in EventCatalog, open **Settings > MCP**. It lists the **Catalog MCP Server** and, under **Domain
+MCP Servers**, the MCP server of each domain, each with its full URL to copy.
+
 ### Connect to a domain or system
 
 Domain and system pages include a **Connect to MCP server** action when the built-in MCP server is available. Select it to see
@@ -57,14 +58,17 @@ connection action uses the versioned URL instead.
 
 You can use a scoped URL anywhere the client examples below use the whole-catalog `/docs/mcp/` URL.
 
+On a scoped server, tools only return resources in that scope, and an omitted version means the latest version in that domain
+or system.
+
 :::note Scoped tool availability
-Scoped servers omit C4, team and user directory, custom documentation, and user-defined extended tools. System-scoped servers
-also omit the domain-specific ubiquitous-language tool.
+Scoped servers omit C4, team and user directory, data product, custom documentation, and user-defined extended tools.
+System-scoped servers also omit the domain-specific ubiquitous-language tool. See [Available tools](#available-tools).
 :::
 
 ### Disable the MCP server
 
-The built-in MCP server is enabled by default when EventCatalog is running in server mode with a Scale license. To disable the
+The built-in MCP server is enabled by default when EventCatalog is running in server mode. To disable the
 whole-catalog endpoint, scoped endpoints, and MCP connection actions, set `mcp.enabled` to `false`:
 
 ```js title="eventcatalog.config.js"
@@ -83,7 +87,7 @@ Visit the endpoint in your browser to verify. It returns available tools and res
 ```json
 {
   "name": "EventCatalog MCP Server",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "status": "running",
   "tools": ["getResources", "getResource", ...],
   "resources": ["eventcatalog://all", "eventcatalog://events", ...]
@@ -228,27 +232,78 @@ claude mcp add --transport http <name> <url>
 
 ## Available tools
 
-### 19 built-in tools
-
-- `getResources` - Get events, services, commands, queries, flows, domains
-- `getResource` - Get a specific resource by id and version
-- `getMessagesProducedOrConsumedByResource` - Messages a resource sends/receives
-- `getSchemaForResource` - Get OpenAPI, AsyncAPI, or other schemas
-- `findResourcesByOwner` - Resources owned by a team or user
-- `getProducersOfMessage` - Services that produce a message
-- `getConsumersOfMessage` - Services that consume a message
-- `getC4Diagram` - Get the source for a C4 diagram
-- `analyzeChangeImpact` - Impact of changing a message
-- `explainBusinessFlow` - Detailed flow information
-- `getTeams` / `getTeam` - Query teams
-- `getUsers` / `getUser` - Query users
-- `findMessageBySchemaId` - Find messages by schema identifiers
-- `explainUbiquitousLanguageTerms` - DDD ubiquitous language from domains
-- `getCustomDocs` - List and search custom documentation pages
-- `searchCustomDocs` - Full-text search custom documentation
-- `getCustomDoc` - Get a custom documentation page or section
-
-[See full API documentation →](/docs/development/ask-your-architecture/mcp-server/getting-started)
+### 22 built-in tools
+
+Every built-in tool is read-only (`readOnlyHint: true`) and has a title, so MCP clients can show readable names and
+auto-approve the tools. Version parameters are optional on every tool: omit them (or pass `latest`) to use the latest
+version. Hidden resources (`hidden: true`) are not listed.
+
+The server also sends instructions to clients on how to navigate the catalog, for example to use `showResource` when the user
+wants to see a diagram or schema.
+
+| Tool | Title | What it does | Scoped servers |
+|---|---|---|---|
+| `getResources` | List catalog resources | Lists resources in a collection, with pagination (`cursor`) and an optional `search` term | Yes |
+| `getResource` | Get a catalog resource | Returns a resource's frontmatter and markdown as `{ id, version, collection, data, body }` | Yes |
+| `getMessagesProducedOrConsumedByResource` | Get messages a resource sends and receives | Returns the messages a service, agent or domain sends and receives, resolved to their catalog entries. `resourceCollection` defaults to `services` | Yes |
+| `getSchemaForResource` | Get schemas and specifications | Returns the schemas or OpenAPI/AsyncAPI/GraphQL specifications of a resource, for the model to read. `resourceCollection` defaults to `services` | Yes |
+| `showResource` | Show a resource | Shows the user a resource's architecture diagram or schema. See [Interactive diagrams and schemas](#interactive-diagrams-and-schemas) | Yes |
+| `findResourcesByOwner` | Find resources by owner | Finds resources owned by a team or user | Yes |
+| `getProducersOfMessage` | Find producers of a message | Finds the services and agents that send a message. `messageCollection` defaults to `events` | Yes |
+| `getConsumersOfMessage` | Find consumers of a message | Finds the services and agents that receive a message. `messageCollection` defaults to `events` | Yes |
+| `analyzeChangeImpact` | Analyze the impact of changing a message | Returns the affected producers and consumers, their owning teams and the blast radius of a change | Yes |
+| `explainBusinessFlow` | Explain a business flow | Returns a flow's definition, steps and related services and agents | Yes |
+| `findMessageBySchemaId` | Find a message from a schema | Finds a message from the `x-eventcatalog-id` (and optional `x-eventcatalog-version`) in a schema | Yes |
+| `explainUbiquitousLanguageTerms` | Explain ubiquitous language terms | Returns the ubiquitous language terms of a domain and its subdomains | Domain servers only |
+| `getC4Diagram` | Get C4 (LikeC4) diagrams | Returns the source of your C4 (LikeC4) diagrams | No |
+| `getTeams` / `getTeam` | List teams / Get a team | Lists teams, or gets a team with its members | No |
+| `getUsers` / `getUser` | List users / Get a user | Lists users, or gets a user with their role and contact details | No |
+| `getDataProductInputs` | Get data product inputs | Returns the resources a data product consumes | No |
+| `getDataProductOutputs` | Get data product outputs and contracts | Returns the resources a data product produces, with their data contracts | No |
+| `getCustomDocs` | List custom documentation | Lists custom documentation pages, with pagination and an optional `search` term | No |
+| `searchCustomDocs` | Search custom documentation | Full-text search across custom documentation pages | No |
+| `getCustomDoc` | Get a custom documentation page | Returns a custom documentation page, or one `section` of it | No |
+
+`showResource`, `getDataProductInputs` and `getDataProductOutputs` were added in EventCatalog 5.0.0.
+
+In clients that support MCP Apps, the server also registers `getResourceView`. The viewer uses this app-only tool to load
+diagrams and schemas. The model doesn't call it.
+
+### Interactive diagrams and schemas
+
+<AddedIn version="5.0.0" />
+
+The `showResource` tool shows the user a resource in EventCatalog's viewer. Ask your agent things like "show me how the Order
+Service works" or "show me the schema for OrderCreated".
+
+| Parameter | Required | Description |
+|---|---|---|
+| `view` | Yes | `"architecture"` for an architecture diagram, or `"schema"` for the schema of a message or other resource |
+| `resourceId` | Yes | The id of the resource to show |
+| `resourceVersion` | No | The version to show. Defaults to the latest version |
+| `resourceCollection` | No | The collection of the resource, for example `services`, `domains` or `events`. Defaults to `events` |
+| `detail` | No | For `view: "architecture"` of domains and systems: `"overview"` shows only the domains, systems and their relationships (level 1). `"full"` (default) also shows services, messages and channels |
+
+With `view: "architecture"`, the diagram is built the same way as the resource's **Diagram** page in EventCatalog. You can
+show diagrams of domains, systems, services, agents, events, commands, queries, flows, data stores and data products.
+
+In MCP clients that support MCP Apps (for example Claude, ChatGPT and VS Code):
+
+- **Architecture diagrams** open in the interactive visualiser. You can switch levels, search, open other resources'
+  diagrams, and click a node to ask the conversation a question about it.
+- **Schemas** open in the same viewer as the [Schema Explorer](/docs/development/guides/resources/schemas/explore-schemas/schema-explorer):
+  a **Schema** tab with the highlighted source, and a **Properties** tab for JSON Schema, Avro and Protobuf that you can
+  search and expand. Messages with several schemas can switch between them.
+
+Diagrams and schemas share one viewer. Clients such as ChatGPT keep that viewer open and switch it to each diagram or schema
+you ask for. The viewer asks the client to open it full screen.
+
+Other MCP clients get the diagram as Mermaid code and the schema as code, which the agent can show you.
+
+:::tip Showing schemas vs reading schemas
+Use `showResource` with `view: "schema"` when a person wants to see a schema. `getSchemaForResource` returns the raw schemas
+and specifications for the agent to read, for example to generate code.
+:::
 
 ### 17 resources
 
@@ -303,7 +358,7 @@ For local development and testing, you can use the MCP Server on stdio. This is
 
 **Prerequisites:**
 - EventCatalog configured with the [`LLMS.txt` feature](/docs/development/ask-your-architecture/llms.txt)
-- EventCatalog Scale license
+- EventCatalog license key
 - MCP client installed
 
 **Command:**
@@ -321,7 +376,7 @@ Run the MCP Server over HTTP for production deployments.
 
 **Prerequisites:**
 - EventCatalog instance running
-- EventCatalog Scale license
+- EventCatalog license key
 - MCP client installed
 
 **Run using npx:**
@@ -344,5 +399,3 @@ See [instructions on the GitHub repository](https://github.com/event-catalog/mcp
 
 </details>
 
-
-

package/dist/docs/development/ask-your-architecture/03-mcp-server/introduction.md

@@ -9,10 +9,6 @@ description: Connect AI tools to your architecture catalog
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
 
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
-
-<PlanBanner plan="Scale" />
-
 EventCatalog exposes a built-in MCP server that lets AI agents and other MCP clients query your architecture catalog. Its
 built-in tools can find resources, inspect schemas and ownership, follow message producers and consumers, and analyze change
 impact.
@@ -23,7 +19,21 @@ unrelated parts of the catalog.
 
 On a domain or system page, select **Connect to MCP server** to copy the appropriate scoped server URL. EventCatalog uses the
 unversioned URL for the latest resource version and includes the version when you are viewing historical documentation.
+**Settings > MCP** lists the catalog MCP server and the MCP server of each domain, with full URLs to copy.
+
+Every built-in tool is read-only and has a title, so MCP clients can auto-approve them. Versions are optional on every tool
+and default to the latest version.
+
+<AddedIn version="5.0.0" />
 
+The `showResource` tool shows your users architecture diagrams and schemas. In MCP clients that support
+[MCP Apps](/docs/development/ask-your-architecture/mcp-server/getting-started#interactive-diagrams-and-schemas) (for example
+Claude, ChatGPT and VS Code), diagrams open in the interactive visualiser and schemas open in the same viewer as the Schema
+Explorer. Other clients get the diagram as Mermaid and the schema as code.
 
+## Canvas tools
 
+When [EventCatalog Studio](/docs/development/studio/introduction) is on, the MCP server also has tools to create, read and
+edit Studio canvases, so agents can design on a canvas with your team. These tools change your canvases, so they are not
+read-only. See the [MCP tools reference](/docs/development/studio/reference#mcp-tools) for the full list.
 

package/dist/docs/development/ask-your-architecture/03-schemas.txt.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 3
+sidebar_position: 7
 keywords:
 - mermaid
 sidebar_label: schemas.txt

package/dist/docs/development/ask-your-architecture/04-agents/_category_.json

@@ -1,6 +1,6 @@
 {
   "label": "Agents",
-  "position": 6,
+  "position": 4,
   "collapsible": true,
   "collapsed": true,
   "link": {

package/dist/docs/development/authentication/01-introduction.md

@@ -8,21 +8,15 @@ description: Introduction to EventCatalog Authentication
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 
 # Authentication Guide
 
-<PlanBanner plan="Scale" />
 <AddedIn version="2.43.0" />
 
-
 EventCatalog provides secure authentication to control access to your event-driven architecture documentation. Whether you're a small team getting started or a large enterprise with complex identity requirements, EventCatalog's flexible authentication system grows with your needs.
 
 <iframe width="100%" height="455" src="https://www.youtube.com/embed/OVbXNP0Ns_U?si=TagMKL49ZD_G_HYE" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
 
-
-
-
 ## How it works
 
 EventCatalog uses industry-standard **OpenID Connect (OIDC)** and **OAuth 2.0** protocols to integrate with your identity provider. Here's the authentication flow:
@@ -37,19 +31,10 @@ EventCatalog uses industry-standard **OpenID Connect (OIDC)** and **OAuth 2.0**
 
 EventCatalog runs in **SSR mode** to handle authentication sessions and uses [Auth.js](https://authjs.dev/) to manage the authentication flow securely.
 
-## Authentication by Plan
-
-EventCatalog Authentication is a **paid feature** available in Scale and Enterprise plans.
-
-#### Scale Plan
-Perfect for growing teams that need secure collaboration with popular business providers:
+## Supported providers
 
 - **GitHub** - Ideal for development teams already using GitHub
 <!-- - **Google** - For teams using Gmail and Google Workspace -->
-
-#### Enterprise Plan
-Designed for large organizations with dedicated identity management systems:
-
 - **Microsoft Azure AD (Entra ID)** - For organizations using Office 365 and Azure
 - **Auth0** - Developer-friendly identity platform with advanced features
 - **Okta** - Popular enterprise identity platform with custom claims
@@ -63,16 +48,10 @@ Designed for large organizations with dedicated identity management systems:
 - ✅ **Centralized management** - Control access through your existing identity systems
 - ✅ **Team collaboration** - Secure access for distributed teams
 
-## Getting Started
-
-Ready to secure your EventCatalog with authentication?
-
-**New to EventCatalog?** Start your **30-day free trial** at [EventCatalog.cloud](https://eventcatalog.cloud) to explore all authentication features.
-
 ## Next steps
 
 Ready to get started? Let's enable authentication in your EventCatalog project:
 
 → [Enabling Authentication](/docs/development/authentication/enabling-authentication)
 
-**Questions?** Join our [Discord community](https://discord.gg/eventcatalog) for support and guidance.
+**Questions?** Join our [Discord community](https://eventcatalog.dev/discord) for support and guidance.

package/dist/docs/development/authentication/02-enabling-authentication.md

@@ -8,11 +8,9 @@ description: Enabling authentication for EventCatalog
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 import { Card, CardGrid, GitHubIcon, OktaIcon, AzureIcon, GoogleIcon, Auth0Icon, GitLabIcon } from '@site/src/components/MDX/Card';
 
 <AddedIn version="2.43.0" />
-<PlanBanner plan="Scale" />
 
 To enable authentication for your site, you will need to do three things:
 
@@ -20,18 +18,6 @@ To enable authentication for your site, you will need to do three things:
 1. [Enable EventCatalog Server Side Rendering (SSR)](#enable-eventcatalog-server-side-rendering-ssr)
 1. [Create your `eventcatalog.auth.js` file](#create-your-eventcatalogauthjs-file)
 
-:::info Authentication is a paid feature
-Authentication is a paid feature, and is available on EventCatalog Scale and Enterprise plans.
-
-You can get a 30-day free trial of EventCatalog Scale and Enterprise [here](https://www.eventcatalog.dev/pricing).
-
-You will need to set your license key in your `.env` file.
-
-```env title=".env"
-EVENTCATALOG_LICENSE_KEY=your-license-key
-```
-:::
-
 ### Setup Environment
 
 EventCatalog uses [Auth.js](https://authjs.dev/) to handle the authentication flow.
@@ -60,7 +46,6 @@ You do not need to set `AUTH_TRUST_HOST` when deploying to Vercel or Cloudflare
 
 To learn more, refer to the [Auth.js deployment documentation](https://authjs.dev/getting-started/deployment#auth_trust_host).
 
-
 ### Enable EventCatalog Server Side Rendering (SSR)
 
 Authentication requires EventCatalog to be SSR enabled. This is because EventCatalog needs to be able to access the user's session to determine if they are authenticated.
@@ -113,19 +98,16 @@ EventCatalog supports a range of authentication providers, and you can find the
   <Card
     title="Setting up GitHub"
     icon={<GitHubIcon />}
-    badge="Scale"
     href="/docs/development/authentication/providers/setting-up-github"
   />
   <Card
     title="Setting up Google"
     icon={<GoogleIcon />}
-    badge="Scale"
     href="/docs/development/authentication/providers/setting-up-google"
   />
   <Card
     title="Setting up Azure AD"
     icon={<AzureIcon />}
-    badge="Enterprise"
     href="/docs/development/authentication/providers/setting-up-azure-ad"
   />
   <!-- <Card
@@ -138,13 +120,11 @@ EventCatalog supports a range of authentication providers, and you can find the
     title="Setting up Okta"
     icon={<OktaIcon />}
     href="/docs/development/authentication/providers/setting-up-okta"
-    badge="Enterprise"
   />
   <Card
     title="Setting up Auth0"
     icon={<Auth0Icon />}
     href="/docs/development/authentication/providers/setting-up-auth0"
-    badge="Enterprise"
   />
 </CardGrid>
 

package/dist/docs/development/authentication/07-rbac-middleware.md

@@ -12,10 +12,8 @@ description: Implementing role-based access control with custom middleware in Ev
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 
 <AddedIn version="2.44.0" />
-<PlanBanner plan="Enterprise" />
 
 # Role-Based Access Control (RBAC) Middleware
 

package/dist/docs/development/authentication/providers/03-setting-up-github.md

@@ -8,10 +8,8 @@ description: Setting up GitHub authentication for EventCatalog
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 
 <AddedIn version="2.43.0" />
-<PlanBanner plan="Scale" />
 
 :::info
 This guide takes your through setting up a protected sign-in screen for your docs. Before going through this guide, make sure you’ve first gone through [Enabling authentication](/docs/development/authentication/enabling-authentication).

package/dist/docs/development/authentication/providers/03a-setting-up-google.md

@@ -9,10 +9,8 @@ id: setting-up-google
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 
 <AddedIn version="2.43.3" />
-<PlanBanner plan="Scale" />
 
 :::info
 This guide takes your through setting up a protected sign-in screen for your docs. Before going through this guide, make sure you've first gone through [Enabling authentication](/docs/development/authentication/enabling-authentication).

package/dist/docs/development/authentication/providers/04-setting-up-azure-ad.md

@@ -8,10 +8,8 @@ description: Setting up Microsoft Entra ID authentication for EventCatalog
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 
 <AddedIn version="2.43.1" />
-<PlanBanner plan="Enterprise" />
 
 :::info
 This guide takes your through setting up a protected sign-in screen for your docs. Before going through this guide, make sure you've first gone through [Enabling authentication](/docs/development/authentication/enabling-authentication).

package/dist/docs/development/authentication/providers/05-setting-up-okta.md

@@ -8,10 +8,8 @@ description: Setting up Okta authentication for EventCatalog
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 
 <AddedIn version="2.43.0" />
-<PlanBanner plan="Enterprise" />
 
 :::info
 This guide takes your through setting up a protected sign-in screen for your docs. Before going through this guide, make sure you've first gone through [Enabling authentication](/docs/development/authentication/enabling-authentication).
@@ -94,7 +92,6 @@ All pages should now be protected and require an Okta account to access.
 1. Enter your Okta credentials
 1. After successful authentication, you'll be redirected back to EventCatalog
 
-
 ## Found an issue?
 
 Remember to setup the prerequisites for this guide:

package/dist/docs/development/authentication/providers/06-setting-up-auth0.md

@@ -8,10 +8,8 @@ description: Setting up Auth0 authentication for EventCatalog
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 
 <AddedIn version="2.43.1" />
-<PlanBanner plan="Enterprise" />
 
 :::info
 This guide takes your through setting up a protected sign-in screen for your docs. Before going through this guide, make sure you've first gone through [Enabling authentication](/docs/development/authentication/enabling-authentication).

package/dist/docs/development/bring-your-own-documentation/01-introduction.md

@@ -7,10 +7,6 @@ title: Bring your own documentation
 description: Bring your own documentation to EventCatalog
 ---
 
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
-
-<PlanBanner plan="Scale" />
-
 EventCatalog lets you bring your own documentation and diagrams into your catalog.
 
 This is useful when your documentation is spread across multiple repositories, project folders, wikis, or internal tools. You can bring that context into EventCatalog and make it part of the same experience people already use to explore your architecture.

package/dist/docs/development/bring-your-own-documentation/custom-pages/01-introduction.md

@@ -8,10 +8,8 @@ description: Customize documentation in EventCatalog
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 
 <AddedIn version="2.33.0" />
-<PlanBanner plan="Scale" />
 
 <iframe width="100%" height="415" src="https://www.youtube.com/embed/auzmEf0AdJg?si=wHe-3X6b6uLN39sB" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
 
@@ -21,7 +19,6 @@ High level documentation is a way to add catalog-wide custom documentation pages
 
 This can be a great way to extend your catalog beyond what is provided, and bring your own documentation to EventCatalog, rather than having documentation spread across multiple tools.
 
-
 ![Example](./img/custom-docs.png)
 <a class="block" href="https://demo.eventcatalog.dev/docs/custom/technical-architecture-design/architecture-decision-records/published/01-api-gateway-pattern">View demo</a>
 

package/dist/docs/development/bring-your-own-documentation/custom-pages/02-adding-custom-docs.md

@@ -8,15 +8,9 @@ description: Adding high level documentation to your EventCatalog
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 import ProjectTree from '@site/src/components/MDX/ProjectTree';
 
 <AddedIn version="2.33.0" />
-<PlanBanner plan="Scale" />
-
-## Getting started
-
-High level documentation requires an EventCatalog Scale license key. You can get a 30-day free trial from [EventCatalog Cloud](https://eventcatalog.cloud).
 
 ## Adding high level documentation
 
@@ -97,7 +91,6 @@ In this example we have high level documentation for:
 We added numbers (01, 02, 03) to the files to help with maintenance, you can configure the order of the files in your configuration.
 :::
 
-
 #### Structure of markdown files for high level documentation
 
 Each markdown file is split into two parts:
@@ -194,7 +187,6 @@ export default {
 };
  ```
 
-
 #### Rendered output
 
 The rendered output will be the content of the markdown file, with the frontmatter properties.
@@ -234,12 +226,3 @@ export default {
 
 ![Example](./img/custom-attrs.png)
 
-
-
-
-
-
-
-
-
-

package/dist/docs/development/bring-your-own-documentation/custom-pages/03-components.md

@@ -8,10 +8,6 @@ title: Components
 description: Component list for custom pages 
 ---
 
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
-
-<PlanBanner plan="Scale" />
-
 You can add custom EventCatalog components to your custom pages.
 
 [See the list of components and how to use them](/docs/development/components/using-components).

package/dist/docs/development/bring-your-own-documentation/custom-pages/04-owners.md

@@ -10,10 +10,8 @@ description: Adding owners to custom pages with EventCatalog.
 ---
 
 import AddedIn from '@site/src/components/MDX/AddedIn';
-import PlanBanner from '@site/src/components/MDX/PlanBanner';
 
 <AddedIn version="2.33.0" />
-<PlanBanner plan="Scale" />
 
 Owners in EventCatalog are either **users** or **teams** and are **optional**.