add llm plugin

.github/workflows/build.yaml

@@ -20,7 +20,7 @@ jobs:
 
       - uses: actions/setup-node@v1
         with:
-          node-version: '18'
+          node-version: '20'
 
       - name: Build
         run: |

.github/workflows/gh-pages.yaml

@@ -17,7 +17,7 @@ jobs:
 
       - uses: actions/setup-node@v1
         with:
-          node-version: '18'
+          node-version: '20'
 
       - name: Build for gh-pages
         run: |

.nvmrc

@@ -1 +1 @@
-18
+20

docs/develop/dynamic-content.md

@@ -5,7 +5,7 @@ sidebar_label: Dynamic Content
 ---
 
 :::warning
-Under construction, set for major revisions to incorporate content from manifests, rout, and host your website pages
+Under construction, set for major revisions.
 :::
 
 

docs/develop/manifests.md

@@ -7,6 +7,11 @@ sidebar_label: Manifests ("Virtual Filesystem")
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
+:::warning
+Under construction, set for major revisions.
+:::
+
+
 Bee nodes — and tools like `bee-js` and `swarm-cli` — let you upload entire folders of files to Swarm.
 
 Swarm doesn’t have a traditional file system like your computer does. Instead, when uploading a collection of files, it uses something called a **manifest**, which acts like a map between relative file paths (like `/images/cat.jpg`) and the actual content stored on Swarm.

docs/develop/routing.md

@@ -8,6 +8,10 @@ import TabItem from '@theme/TabItem';
 
 ## Routing on Swarm 
 
+:::warning
+Under construction, set for major revisions.
+:::
+
 Swarm does not behave like a traditional web server — there is **no server-side routing**, and every route must correspond to a real file inside the site [manifest](/docs/develop/manifests).
 
 If you try to use typical "clean URLs" like: