From 16fd2afb25d7886b7c0a9adf72dc6bf24d53ef2e Mon Sep 17 00:00:00 2001
From: Kris Zyp <kriszyp@gmail.com>
Date: Tue, 16 Sep 2025 07:02:07 -0600
Subject: [PATCH] Update diagram to better reflect Harper architecture

---
 docs/developers/applications/index.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/developers/applications/index.md b/docs/developers/applications/index.md
index f12fadb5..f44b3cbb 100644
--- a/docs/developers/applications/index.md
+++ b/docs/developers/applications/index.md
@@ -33,7 +33,7 @@ flowchart TD
 		CustomResource["Custom Resource"]
 	end
 
-	subgraph Extensions
+	subgraph Plugins
 		direction TB
 		subgraph Custom
 			NextjsExt["@harperdb/nextjs"]
@@ -49,22 +49,22 @@ flowchart TD
 	subgraph Core
 		direction TB
 		Database["database"]
-		FileSystem["file-system"]
-		Networking["networking"]
+		HTTP["http"]
+		WebSockets["ws"]
 	end
 
 	NextJSApp --> NextjsExt
 	ApolloApp --> ApolloExt
 	CustomResource --> JsResource & GraphqlSchema & Rest
 
-	NextjsExt --> Networking
-	NextjsExt --> FileSystem
+	NextjsExt --> HTTP
+	NextjsExt --> WebSockets
 	ApolloExt --> GraphqlSchema
 	ApolloExt --> Networking
 
 	GraphqlSchema --> Database
 	JsResource --> Database
-	Rest --> Networking
+	Rest --> HTTP
 ```
 
 > As of Harper v4.6, a new, **experimental** component system has been introduced called **plugins**. Plugins are a **new iteration of the existing extension system**. They are simultaneously a simplification and an extensibility upgrade. Instead of defining multiple methods (`start` vs `startOnMainThread`, `handleFile` vs `setupFile`, `handleDirectory` vs `setupDirectory`), plugins only have to define a single `handleApplication` method. Plugins are **experimental**, and complete documentation is available on the [plugin API](../../reference/components/plugins) page. In time we plan to deprecate the concept of extensions in favor of plugins, but for now, both are supported.