docs: Document Wave features

README.md

@@ -74,7 +74,7 @@ You shouldn't experience any issues but if you do, share them in the #team-docum
    - Language review from a `docs-codeowners` member.
    - Technical review from the backend engineer or other SME closest to the feature.
 6. Check and review the changes using the Netlify preview.
-7. If you created the PR, the onus is on you to merge the PR once approved. This is the Edu team's policy, to ensure that PRs are never merged inadvertently. If you'd like one of us to merge it for you, please let us know.
+7. If you created the PR, the onus is on you to merge the PR once approved. This is the Edu team's policy, to ensure that PRs are never merged inadvertently. If you'd like one of us to merge it for you, let us know.
 
 Once merged to the master branch, the changes will be live immediately.
 

docusaurus.config.js

@@ -227,6 +227,12 @@ export default async function createConfigAsync() {
     //   },
     // },
 
+    markdown: {
+      mermaid: true,
+    },
+
+    themes: ['@docusaurus/theme-mermaid'],
+
     customFields: {
       // Put your custom environment here
     },

internal/fetch-docs-oss.mjs

@@ -18,7 +18,7 @@ const repositories = [
     name: "wave",
     url: "https://github.com/seqeralabs/wave.git",
     path: path.join(__dirname, "..", "wave_docs", "wave_repo"),
-    branch: "master",
+    branch: "chris-wave-features",
   },
 ];
 

netlify.toml

@@ -24,7 +24,7 @@
   EXCLUDE_PLATFORM_API="false"
   EXCLUDE_PLATFORM_OPENAPI="false"
   EXCLUDE_MULTIQC="true"
-  EXCLUDE_WAVE="true"
+  EXCLUDE_FUSION="true"
 
 # Seqera API docs are too large to host / build on netlify on their own.
 # The appropriate ENVVAR is set to disable the API Builds on Netlify for the main docs site.