Docusaurus v3

website/docs/reference/network-view.mdx

@@ -77,14 +77,7 @@ The `PROMETHEUS_API` environment variable should point to the base path of the P
 
 This setup means that there is a mutual dependency between Unleash and Prometheus, where Prometheus regularly fetches data from Unleash's backstage API and Unleash fetches and displays this data when you use the network view. This diagram provides a visual representation of that.
 
-```mermaid
-sequenceDiagram
-    participant Unleash
-    loop Scrape data
-    Prometheus-->>Unleash: fetch internal-backstage/prometheus
-    end
-    Unleash->>+Prometheus: Query data for network view
-```
+![](./network-view.png)
 
 
 [^1]: For instance: when using Unleash in an API setting, a common mistake is to instantiate a new SDK for every request instead of sharing a single instance across requests. This would be visible in the network overview graph as a large number of requests from the same app.

website/docusaurus.config.ts

@@ -53,7 +53,6 @@ const config: Config = {
     organizationName: 'Unleash', // Usually your GitHub org/user name.
     projectName: 'unleash.github.io', // Usually your repo name.
     trailingSlash: false,
-    markdown: { mermaid: true },
     customFields: {
         // expose env vars etc here
         environment: process.env.NODE_ENV,
@@ -901,7 +900,6 @@ const config: Config = {
     ],
     themes: [
         'docusaurus-theme-openapi-docs', // Allows use of @theme/ApiItem and other components
-        '@docusaurus/theme-mermaid',
     ],
     scripts: [
         {

website/package.json

@@ -25,10 +25,7 @@
     "@docusaurus/plugin-google-analytics": "^3.5.2",
     "@docusaurus/preset-classic": "^3.5.2",
     "@docusaurus/remark-plugin-npm2yarn": "3.5.2",
-    "@docusaurus/theme-mermaid": "^3.5.2",
     "@mdx-js/react": "^3.1.0",
-    "@svgr/webpack": "8.1.0",
-    "browserslist": "^4.24.2",
     "docusaurus-plugin-openapi-docs": "^4.1.0",
     "docusaurus-plugin-remote-content": "^4.0.0",
     "docusaurus-theme-openapi-docs": "^4.1.0",