From 2e619e5512d7a8c330d74b85527bb28d9c818159 Mon Sep 17 00:00:00 2001
From: LadyBluenotes <gerrardsarah@gmail.com>
Date: Sat, 23 Aug 2025 21:46:01 -0700
Subject: [PATCH 01/37] start of v2 structure

---
 .../advanced-concepts/data.json               |  0
 .../fine-grained-reactivity.mdx               |  0
 .../concepts/components/basics.mdx            |  0
 .../concepts/components/class-style.mdx       |  0
 .../concepts/components/data.json             |  0
 .../concepts/components/event-handlers.mdx    |  0
 .../concepts/components/props.mdx             |  0
 .../routes => old pages}/concepts/context.mdx |  0
 .../control-flow/conditional-rendering.mdx    |  0
 .../concepts/control-flow/data.json           |  0
 .../concepts/control-flow/dynamic.mdx         |  0
 .../concepts/control-flow/error-boundary.mdx  |  0
 .../concepts/control-flow/list-rendering.mdx  |  0
 .../concepts/control-flow/portal.mdx          |  0
 {src/routes => old pages}/concepts/data.json  |  0
 .../concepts/derived-values/data.json         |  0
 .../derived-values/derived-signals.mdx        |  0
 .../concepts/derived-values/memos.mdx         |  0
 .../routes => old pages}/concepts/effects.mdx |  0
 .../concepts/intro-to-reactivity.mdx          |  0
 {src/routes => old pages}/concepts/refs.mdx   |  0
 .../routes => old pages}/concepts/signals.mdx |  0
 {src/routes => old pages}/concepts/stores.mdx |  0
 .../concepts/understanding-jsx.mdx            |  0
 .../configuration/data.json                   |  0
 .../configuration/environment-variables.mdx   |  0
 .../configuration/typescript.mdx              |  0
 .../guides/complex-state-management.mdx       |  0
 old pages/guides/data.json                    | 14 ++++
 .../guides/deploying-your-app.mdx             |  0
 .../aws-via-flightcontrol.mdx                 |  0
 .../guides/deployment-options/aws-via-sst.mdx |  0
 .../guides/deployment-options/cloudflare.mdx  |  0
 .../guides/deployment-options/data.json       |  0
 .../guides/deployment-options/firebase.mdx    |  0
 .../guides/deployment-options/netlify.mdx     |  0
 .../guides/deployment-options/railway.mdx     |  0
 .../guides/deployment-options/stormkit.mdx    |  0
 .../guides/deployment-options/vercel.mdx      |  0
 .../guides/deployment-options/zerops.mdx      |  0
 .../guides/fetching-data.mdx                  |  0
 .../guides/routing-and-navigation.mdx         |  0
 .../guides/state-management.mdx               |  0
 .../guides/styling-components/css-modules.mdx |  0
 .../guides/styling-components/data.json       |  0
 .../guides/styling-components/less.mdx        |  0
 .../guides/styling-components/macaron.mdx     |  0
 .../guides/styling-components/sass.mdx        |  0
 .../guides/styling-components/tailwind-v3.mdx |  0
 .../guides/styling-components/tailwind.mdx    |  0
 .../guides/styling-components/uno.mdx         |  0
 .../guides/styling-your-components.mdx        |  0
 {src/routes => old pages}/guides/testing.mdx  |  0
 {src/routes => old pages}/quick-start.mdx     |  0
 package.json                                  |  2 +-
 src/routes/advanced/data.json                 |  4 +
 src/routes/components/data.json               |  4 +
 src/routes/control-flow/data.json             |  4 +
 src/routes/data.json                          | 13 ++--
 src/routes/getting-started/counter.mdx        | 12 +++
 src/routes/getting-started/data.json          |  4 +
 src/routes/getting-started/quick-start.mdx    | 26 +++++++
 src/routes/getting-started/todo.mdx           | 15 ++++
 src/routes/guides/data.json                   | 12 +--
 src/routes/index.mdx                          |  2 +
 src/routes/intro.mdx                          | 35 +++++++++
 src/routes/reactivity/data.json               | 12 +++
 src/routes/reactivity/effects.mdx             | 12 +++
 src/routes/reactivity/how-to/async-data.mdx   |  8 ++
 src/routes/reactivity/how-to/data.json        |  4 +
 .../reactivity/how-to/debug-reactivity.mdx    |  4 +
 .../reactivity/how-to/derived-signals.mdx     | 11 +++
 src/routes/reactivity/memos.mdx               | 11 +++
 src/routes/reactivity/overview.mdx            | 74 +++++++++++++++++++
 src/routes/reactivity/resources.mdx           |  8 ++
 src/routes/reactivity/signals.mdx             | 10 +++
 src/routes/reactivity/stores.mdx              |  4 +
 src/routes/rendering/data.json                |  4 +
 78 files changed, 292 insertions(+), 17 deletions(-)
 rename {src/routes => old pages}/advanced-concepts/data.json (100%)
 rename {src/routes => old pages}/advanced-concepts/fine-grained-reactivity.mdx (100%)
 rename {src/routes => old pages}/concepts/components/basics.mdx (100%)
 rename {src/routes => old pages}/concepts/components/class-style.mdx (100%)
 rename {src/routes => old pages}/concepts/components/data.json (100%)
 rename {src/routes => old pages}/concepts/components/event-handlers.mdx (100%)
 rename {src/routes => old pages}/concepts/components/props.mdx (100%)
 rename {src/routes => old pages}/concepts/context.mdx (100%)
 rename {src/routes => old pages}/concepts/control-flow/conditional-rendering.mdx (100%)
 rename {src/routes => old pages}/concepts/control-flow/data.json (100%)
 rename {src/routes => old pages}/concepts/control-flow/dynamic.mdx (100%)
 rename {src/routes => old pages}/concepts/control-flow/error-boundary.mdx (100%)
 rename {src/routes => old pages}/concepts/control-flow/list-rendering.mdx (100%)
 rename {src/routes => old pages}/concepts/control-flow/portal.mdx (100%)
 rename {src/routes => old pages}/concepts/data.json (100%)
 rename {src/routes => old pages}/concepts/derived-values/data.json (100%)
 rename {src/routes => old pages}/concepts/derived-values/derived-signals.mdx (100%)
 rename {src/routes => old pages}/concepts/derived-values/memos.mdx (100%)
 rename {src/routes => old pages}/concepts/effects.mdx (100%)
 rename {src/routes => old pages}/concepts/intro-to-reactivity.mdx (100%)
 rename {src/routes => old pages}/concepts/refs.mdx (100%)
 rename {src/routes => old pages}/concepts/signals.mdx (100%)
 rename {src/routes => old pages}/concepts/stores.mdx (100%)
 rename {src/routes => old pages}/concepts/understanding-jsx.mdx (100%)
 rename {src/routes => old pages}/configuration/data.json (100%)
 rename {src/routes => old pages}/configuration/environment-variables.mdx (100%)
 rename {src/routes => old pages}/configuration/typescript.mdx (100%)
 rename {src/routes => old pages}/guides/complex-state-management.mdx (100%)
 create mode 100644 old pages/guides/data.json
 rename {src/routes => old pages}/guides/deploying-your-app.mdx (100%)
 rename {src/routes => old pages}/guides/deployment-options/aws-via-flightcontrol.mdx (100%)
 rename {src/routes => old pages}/guides/deployment-options/aws-via-sst.mdx (100%)
 rename {src/routes => old pages}/guides/deployment-options/cloudflare.mdx (100%)
 rename {src/routes => old pages}/guides/deployment-options/data.json (100%)
 rename {src/routes => old pages}/guides/deployment-options/firebase.mdx (100%)
 rename {src/routes => old pages}/guides/deployment-options/netlify.mdx (100%)
 rename {src/routes => old pages}/guides/deployment-options/railway.mdx (100%)
 rename {src/routes => old pages}/guides/deployment-options/stormkit.mdx (100%)
 rename {src/routes => old pages}/guides/deployment-options/vercel.mdx (100%)
 rename {src/routes => old pages}/guides/deployment-options/zerops.mdx (100%)
 rename {src/routes => old pages}/guides/fetching-data.mdx (100%)
 rename {src/routes => old pages}/guides/routing-and-navigation.mdx (100%)
 rename {src/routes => old pages}/guides/state-management.mdx (100%)
 rename {src/routes => old pages}/guides/styling-components/css-modules.mdx (100%)
 rename {src/routes => old pages}/guides/styling-components/data.json (100%)
 rename {src/routes => old pages}/guides/styling-components/less.mdx (100%)
 rename {src/routes => old pages}/guides/styling-components/macaron.mdx (100%)
 rename {src/routes => old pages}/guides/styling-components/sass.mdx (100%)
 rename {src/routes => old pages}/guides/styling-components/tailwind-v3.mdx (100%)
 rename {src/routes => old pages}/guides/styling-components/tailwind.mdx (100%)
 rename {src/routes => old pages}/guides/styling-components/uno.mdx (100%)
 rename {src/routes => old pages}/guides/styling-your-components.mdx (100%)
 rename {src/routes => old pages}/guides/testing.mdx (100%)
 rename {src/routes => old pages}/quick-start.mdx (100%)
 create mode 100644 src/routes/advanced/data.json
 create mode 100644 src/routes/components/data.json
 create mode 100644 src/routes/control-flow/data.json
 create mode 100644 src/routes/getting-started/counter.mdx
 create mode 100644 src/routes/getting-started/data.json
 create mode 100644 src/routes/getting-started/quick-start.mdx
 create mode 100644 src/routes/getting-started/todo.mdx
 create mode 100644 src/routes/intro.mdx
 create mode 100644 src/routes/reactivity/data.json
 create mode 100644 src/routes/reactivity/effects.mdx
 create mode 100644 src/routes/reactivity/how-to/async-data.mdx
 create mode 100644 src/routes/reactivity/how-to/data.json
 create mode 100644 src/routes/reactivity/how-to/debug-reactivity.mdx
 create mode 100644 src/routes/reactivity/how-to/derived-signals.mdx
 create mode 100644 src/routes/reactivity/memos.mdx
 create mode 100644 src/routes/reactivity/overview.mdx
 create mode 100644 src/routes/reactivity/resources.mdx
 create mode 100644 src/routes/reactivity/signals.mdx
 create mode 100644 src/routes/reactivity/stores.mdx
 create mode 100644 src/routes/rendering/data.json

diff --git a/src/routes/advanced-concepts/data.json b/old pages/advanced-concepts/data.json
similarity index 100%
rename from src/routes/advanced-concepts/data.json
rename to old pages/advanced-concepts/data.json
diff --git a/src/routes/advanced-concepts/fine-grained-reactivity.mdx b/old pages/advanced-concepts/fine-grained-reactivity.mdx
similarity index 100%
rename from src/routes/advanced-concepts/fine-grained-reactivity.mdx
rename to old pages/advanced-concepts/fine-grained-reactivity.mdx
diff --git a/src/routes/concepts/components/basics.mdx b/old pages/concepts/components/basics.mdx
similarity index 100%
rename from src/routes/concepts/components/basics.mdx
rename to old pages/concepts/components/basics.mdx
diff --git a/src/routes/concepts/components/class-style.mdx b/old pages/concepts/components/class-style.mdx
similarity index 100%
rename from src/routes/concepts/components/class-style.mdx
rename to old pages/concepts/components/class-style.mdx
diff --git a/src/routes/concepts/components/data.json b/old pages/concepts/components/data.json
similarity index 100%
rename from src/routes/concepts/components/data.json
rename to old pages/concepts/components/data.json
diff --git a/src/routes/concepts/components/event-handlers.mdx b/old pages/concepts/components/event-handlers.mdx
similarity index 100%
rename from src/routes/concepts/components/event-handlers.mdx
rename to old pages/concepts/components/event-handlers.mdx
diff --git a/src/routes/concepts/components/props.mdx b/old pages/concepts/components/props.mdx
similarity index 100%
rename from src/routes/concepts/components/props.mdx
rename to old pages/concepts/components/props.mdx
diff --git a/src/routes/concepts/context.mdx b/old pages/concepts/context.mdx
similarity index 100%
rename from src/routes/concepts/context.mdx
rename to old pages/concepts/context.mdx
diff --git a/src/routes/concepts/control-flow/conditional-rendering.mdx b/old pages/concepts/control-flow/conditional-rendering.mdx
similarity index 100%
rename from src/routes/concepts/control-flow/conditional-rendering.mdx
rename to old pages/concepts/control-flow/conditional-rendering.mdx
diff --git a/src/routes/concepts/control-flow/data.json b/old pages/concepts/control-flow/data.json
similarity index 100%
rename from src/routes/concepts/control-flow/data.json
rename to old pages/concepts/control-flow/data.json
diff --git a/src/routes/concepts/control-flow/dynamic.mdx b/old pages/concepts/control-flow/dynamic.mdx
similarity index 100%
rename from src/routes/concepts/control-flow/dynamic.mdx
rename to old pages/concepts/control-flow/dynamic.mdx
diff --git a/src/routes/concepts/control-flow/error-boundary.mdx b/old pages/concepts/control-flow/error-boundary.mdx
similarity index 100%
rename from src/routes/concepts/control-flow/error-boundary.mdx
rename to old pages/concepts/control-flow/error-boundary.mdx
diff --git a/src/routes/concepts/control-flow/list-rendering.mdx b/old pages/concepts/control-flow/list-rendering.mdx
similarity index 100%
rename from src/routes/concepts/control-flow/list-rendering.mdx
rename to old pages/concepts/control-flow/list-rendering.mdx
diff --git a/src/routes/concepts/control-flow/portal.mdx b/old pages/concepts/control-flow/portal.mdx
similarity index 100%
rename from src/routes/concepts/control-flow/portal.mdx
rename to old pages/concepts/control-flow/portal.mdx
diff --git a/src/routes/concepts/data.json b/old pages/concepts/data.json
similarity index 100%
rename from src/routes/concepts/data.json
rename to old pages/concepts/data.json
diff --git a/src/routes/concepts/derived-values/data.json b/old pages/concepts/derived-values/data.json
similarity index 100%
rename from src/routes/concepts/derived-values/data.json
rename to old pages/concepts/derived-values/data.json
diff --git a/src/routes/concepts/derived-values/derived-signals.mdx b/old pages/concepts/derived-values/derived-signals.mdx
similarity index 100%
rename from src/routes/concepts/derived-values/derived-signals.mdx
rename to old pages/concepts/derived-values/derived-signals.mdx
diff --git a/src/routes/concepts/derived-values/memos.mdx b/old pages/concepts/derived-values/memos.mdx
similarity index 100%
rename from src/routes/concepts/derived-values/memos.mdx
rename to old pages/concepts/derived-values/memos.mdx
diff --git a/src/routes/concepts/effects.mdx b/old pages/concepts/effects.mdx
similarity index 100%
rename from src/routes/concepts/effects.mdx
rename to old pages/concepts/effects.mdx
diff --git a/src/routes/concepts/intro-to-reactivity.mdx b/old pages/concepts/intro-to-reactivity.mdx
similarity index 100%
rename from src/routes/concepts/intro-to-reactivity.mdx
rename to old pages/concepts/intro-to-reactivity.mdx
diff --git a/src/routes/concepts/refs.mdx b/old pages/concepts/refs.mdx
similarity index 100%
rename from src/routes/concepts/refs.mdx
rename to old pages/concepts/refs.mdx
diff --git a/src/routes/concepts/signals.mdx b/old pages/concepts/signals.mdx
similarity index 100%
rename from src/routes/concepts/signals.mdx
rename to old pages/concepts/signals.mdx
diff --git a/src/routes/concepts/stores.mdx b/old pages/concepts/stores.mdx
similarity index 100%
rename from src/routes/concepts/stores.mdx
rename to old pages/concepts/stores.mdx
diff --git a/src/routes/concepts/understanding-jsx.mdx b/old pages/concepts/understanding-jsx.mdx
similarity index 100%
rename from src/routes/concepts/understanding-jsx.mdx
rename to old pages/concepts/understanding-jsx.mdx
diff --git a/src/routes/configuration/data.json b/old pages/configuration/data.json
similarity index 100%
rename from src/routes/configuration/data.json
rename to old pages/configuration/data.json
diff --git a/src/routes/configuration/environment-variables.mdx b/old pages/configuration/environment-variables.mdx
similarity index 100%
rename from src/routes/configuration/environment-variables.mdx
rename to old pages/configuration/environment-variables.mdx
diff --git a/src/routes/configuration/typescript.mdx b/old pages/configuration/typescript.mdx
similarity index 100%
rename from src/routes/configuration/typescript.mdx
rename to old pages/configuration/typescript.mdx
diff --git a/src/routes/guides/complex-state-management.mdx b/old pages/guides/complex-state-management.mdx
similarity index 100%
rename from src/routes/guides/complex-state-management.mdx
rename to old pages/guides/complex-state-management.mdx
diff --git a/old pages/guides/data.json b/old pages/guides/data.json
new file mode 100644
index 000000000..364f3f925
--- /dev/null
+++ b/old pages/guides/data.json	
@@ -0,0 +1,14 @@
+{
+	"title": "Guides",
+	"pages": [
+		"styling-your-components.mdx",
+		"styling-components",
+		"state-management.mdx",
+		"routing-and-navigation.mdx",
+		"complex-state-management.mdx",
+		"fetching-data.mdx",
+    "testing.mdx",
+		"deploying-your-app.mdx",
+		"deployment-options"
+	]
+}
diff --git a/src/routes/guides/deploying-your-app.mdx b/old pages/guides/deploying-your-app.mdx
similarity index 100%
rename from src/routes/guides/deploying-your-app.mdx
rename to old pages/guides/deploying-your-app.mdx
diff --git a/src/routes/guides/deployment-options/aws-via-flightcontrol.mdx b/old pages/guides/deployment-options/aws-via-flightcontrol.mdx
similarity index 100%
rename from src/routes/guides/deployment-options/aws-via-flightcontrol.mdx
rename to old pages/guides/deployment-options/aws-via-flightcontrol.mdx
diff --git a/src/routes/guides/deployment-options/aws-via-sst.mdx b/old pages/guides/deployment-options/aws-via-sst.mdx
similarity index 100%
rename from src/routes/guides/deployment-options/aws-via-sst.mdx
rename to old pages/guides/deployment-options/aws-via-sst.mdx
diff --git a/src/routes/guides/deployment-options/cloudflare.mdx b/old pages/guides/deployment-options/cloudflare.mdx
similarity index 100%
rename from src/routes/guides/deployment-options/cloudflare.mdx
rename to old pages/guides/deployment-options/cloudflare.mdx
diff --git a/src/routes/guides/deployment-options/data.json b/old pages/guides/deployment-options/data.json
similarity index 100%
rename from src/routes/guides/deployment-options/data.json
rename to old pages/guides/deployment-options/data.json
diff --git a/src/routes/guides/deployment-options/firebase.mdx b/old pages/guides/deployment-options/firebase.mdx
similarity index 100%
rename from src/routes/guides/deployment-options/firebase.mdx
rename to old pages/guides/deployment-options/firebase.mdx
diff --git a/src/routes/guides/deployment-options/netlify.mdx b/old pages/guides/deployment-options/netlify.mdx
similarity index 100%
rename from src/routes/guides/deployment-options/netlify.mdx
rename to old pages/guides/deployment-options/netlify.mdx
diff --git a/src/routes/guides/deployment-options/railway.mdx b/old pages/guides/deployment-options/railway.mdx
similarity index 100%
rename from src/routes/guides/deployment-options/railway.mdx
rename to old pages/guides/deployment-options/railway.mdx
diff --git a/src/routes/guides/deployment-options/stormkit.mdx b/old pages/guides/deployment-options/stormkit.mdx
similarity index 100%
rename from src/routes/guides/deployment-options/stormkit.mdx
rename to old pages/guides/deployment-options/stormkit.mdx
diff --git a/src/routes/guides/deployment-options/vercel.mdx b/old pages/guides/deployment-options/vercel.mdx
similarity index 100%
rename from src/routes/guides/deployment-options/vercel.mdx
rename to old pages/guides/deployment-options/vercel.mdx
diff --git a/src/routes/guides/deployment-options/zerops.mdx b/old pages/guides/deployment-options/zerops.mdx
similarity index 100%
rename from src/routes/guides/deployment-options/zerops.mdx
rename to old pages/guides/deployment-options/zerops.mdx
diff --git a/src/routes/guides/fetching-data.mdx b/old pages/guides/fetching-data.mdx
similarity index 100%
rename from src/routes/guides/fetching-data.mdx
rename to old pages/guides/fetching-data.mdx
diff --git a/src/routes/guides/routing-and-navigation.mdx b/old pages/guides/routing-and-navigation.mdx
similarity index 100%
rename from src/routes/guides/routing-and-navigation.mdx
rename to old pages/guides/routing-and-navigation.mdx
diff --git a/src/routes/guides/state-management.mdx b/old pages/guides/state-management.mdx
similarity index 100%
rename from src/routes/guides/state-management.mdx
rename to old pages/guides/state-management.mdx
diff --git a/src/routes/guides/styling-components/css-modules.mdx b/old pages/guides/styling-components/css-modules.mdx
similarity index 100%
rename from src/routes/guides/styling-components/css-modules.mdx
rename to old pages/guides/styling-components/css-modules.mdx
diff --git a/src/routes/guides/styling-components/data.json b/old pages/guides/styling-components/data.json
similarity index 100%
rename from src/routes/guides/styling-components/data.json
rename to old pages/guides/styling-components/data.json
diff --git a/src/routes/guides/styling-components/less.mdx b/old pages/guides/styling-components/less.mdx
similarity index 100%
rename from src/routes/guides/styling-components/less.mdx
rename to old pages/guides/styling-components/less.mdx
diff --git a/src/routes/guides/styling-components/macaron.mdx b/old pages/guides/styling-components/macaron.mdx
similarity index 100%
rename from src/routes/guides/styling-components/macaron.mdx
rename to old pages/guides/styling-components/macaron.mdx
diff --git a/src/routes/guides/styling-components/sass.mdx b/old pages/guides/styling-components/sass.mdx
similarity index 100%
rename from src/routes/guides/styling-components/sass.mdx
rename to old pages/guides/styling-components/sass.mdx
diff --git a/src/routes/guides/styling-components/tailwind-v3.mdx b/old pages/guides/styling-components/tailwind-v3.mdx
similarity index 100%
rename from src/routes/guides/styling-components/tailwind-v3.mdx
rename to old pages/guides/styling-components/tailwind-v3.mdx
diff --git a/src/routes/guides/styling-components/tailwind.mdx b/old pages/guides/styling-components/tailwind.mdx
similarity index 100%
rename from src/routes/guides/styling-components/tailwind.mdx
rename to old pages/guides/styling-components/tailwind.mdx
diff --git a/src/routes/guides/styling-components/uno.mdx b/old pages/guides/styling-components/uno.mdx
similarity index 100%
rename from src/routes/guides/styling-components/uno.mdx
rename to old pages/guides/styling-components/uno.mdx
diff --git a/src/routes/guides/styling-your-components.mdx b/old pages/guides/styling-your-components.mdx
similarity index 100%
rename from src/routes/guides/styling-your-components.mdx
rename to old pages/guides/styling-your-components.mdx
diff --git a/src/routes/guides/testing.mdx b/old pages/guides/testing.mdx
similarity index 100%
rename from src/routes/guides/testing.mdx
rename to old pages/guides/testing.mdx
diff --git a/src/routes/quick-start.mdx b/old pages/quick-start.mdx
similarity index 100%
rename from src/routes/quick-start.mdx
rename to old pages/quick-start.mdx
diff --git a/package.json b/package.json
index 238a4b94d..00e10cf87 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
 	"name": "solid-docs-next",
-	"version": "1.0.0",
+	"version": "2.0.0",
 	"private": true,
 	"description": "Docs for Solid",
 	"type": "module",
diff --git a/src/routes/advanced/data.json b/src/routes/advanced/data.json
new file mode 100644
index 000000000..89c57710b
--- /dev/null
+++ b/src/routes/advanced/data.json
@@ -0,0 +1,4 @@
+{
+	"title": "Advanced Concepts",
+	"pages": []
+}
diff --git a/src/routes/components/data.json b/src/routes/components/data.json
new file mode 100644
index 000000000..f675b706b
--- /dev/null
+++ b/src/routes/components/data.json
@@ -0,0 +1,4 @@
+{
+	"title": "Components",
+	"pages": []
+}
diff --git a/src/routes/control-flow/data.json b/src/routes/control-flow/data.json
new file mode 100644
index 000000000..91d5713a5
--- /dev/null
+++ b/src/routes/control-flow/data.json
@@ -0,0 +1,4 @@
+{
+	"title": "Control Flow",
+	"pages": []
+}
diff --git a/src/routes/data.json b/src/routes/data.json
index 5c04652ac..5091d9eaa 100644
--- a/src/routes/data.json
+++ b/src/routes/data.json
@@ -2,10 +2,13 @@
 	"title": "root",
 	"pages": [
 		"index.mdx",
-		"quick-start.mdx",
-		"concepts",
-		"advanced-concepts",
-		"guides",
-		"configuration"
+		"intro.mdx",
+		"getting-started",
+		"reactivity",
+		"components",
+		"control-flow",
+		"rendering",
+		"advanced",
+		"guides"
 	]
 }
diff --git a/src/routes/getting-started/counter.mdx b/src/routes/getting-started/counter.mdx
new file mode 100644
index 000000000..ee8d28182
--- /dev/null
+++ b/src/routes/getting-started/counter.mdx
@@ -0,0 +1,12 @@
+---
+title: "Counter Tutorial"
+order: 2
+---
+
+[TODO]
+
+1. Open your newly scaffolded project in your code editor of choice.
+2. Create a new file called `Counter.jsx` in the `src/components` directory.
+3. In `Counter.tsx`, use Solid's `createSignal` to create a reactive counter state.
+4. Export the `Counter` component and import it into your main application file (e.g., `src/App.jsx`).
+5. Use the `Counter` component in your application and test its functionality.
\ No newline at end of file
diff --git a/src/routes/getting-started/data.json b/src/routes/getting-started/data.json
new file mode 100644
index 000000000..4b2a8a548
--- /dev/null
+++ b/src/routes/getting-started/data.json
@@ -0,0 +1,4 @@
+{
+	"title": "Getting Started",
+	"pages": ["quick-start.mdx", "counter.mdx", "todo.mdx"]
+}
diff --git a/src/routes/getting-started/quick-start.mdx b/src/routes/getting-started/quick-start.mdx
new file mode 100644
index 000000000..4e5a93110
--- /dev/null
+++ b/src/routes/getting-started/quick-start.mdx
@@ -0,0 +1,26 @@
+---
+title: Quick Start Guide
+order: 1
+---
+
+The fastest way to try Solid is to create a new project and run it locally.
+In just a few minutes, you’ll have a working Solid app running in your browser.
+
+## Solid in your Browser
+
+If you're looking to experiment with Solid without setting up a local environment, open the [Solid Playground](https://playground.solidjs.com/) in your browser.
+
+If you prefer a more complete development setup, you can use the StackBlitz [Javascript](https://stackblitz.com/github/solidjs/templates/tree/master/js) or [TypeScript](https://stackblitz.com/github/solidjs/templates/tree/master/ts) templates.
+
+## Create a New Project
+
+:::note[Before You Begin]
+Make sure you have a recent version of your prefer JavaScript runtime installed, such as [Node.js](https://nodejs.org/en), [Bun](https://bun.sh/), or [Deno](https://deno.com/).
+:::
+
+[TODO]
+
+- Navigate to directory and run command
+- CLI will take you through options
+- Once you've selected your options, the CLI will prompt you to install the dependencies and start the development server
+- Open browser and navigate to the provided local URL to see your new Solid app in action!
\ No newline at end of file
diff --git a/src/routes/getting-started/todo.mdx b/src/routes/getting-started/todo.mdx
new file mode 100644
index 000000000..4e031d3d1
--- /dev/null
+++ b/src/routes/getting-started/todo.mdx
@@ -0,0 +1,15 @@
+---
+title: Todo Tutorial
+order: 3
+---
+
+[TODO]
+
+1. Open your newly scaffolded project in your code editor of choice.
+
+- Signal to track all tasks
+- Function to add a new task
+- Function to remove a task
+- Function to toggle task completion
+- Show number of completed tasks
+- Show number of tasks
\ No newline at end of file
diff --git a/src/routes/guides/data.json b/src/routes/guides/data.json
index 364f3f925..88ddc06cb 100644
--- a/src/routes/guides/data.json
+++ b/src/routes/guides/data.json
@@ -1,14 +1,4 @@
 {
 	"title": "Guides",
-	"pages": [
-		"styling-your-components.mdx",
-		"styling-components",
-		"state-management.mdx",
-		"routing-and-navigation.mdx",
-		"complex-state-management.mdx",
-		"fetching-data.mdx",
-    "testing.mdx",
-		"deploying-your-app.mdx",
-		"deployment-options"
-	]
+	"pages": []
 }
diff --git a/src/routes/index.mdx b/src/routes/index.mdx
index bc137a50e..2be7028b9 100644
--- a/src/routes/index.mdx
+++ b/src/routes/index.mdx
@@ -3,6 +3,8 @@ title: Overview
 mainNavExclude: true
 ---
 
+[TODO: Convert to landing page. Move any relevant info into Solid Info]
+
 # Overview
 
 Solid is a modern JavaScript framework designed to build responsive and high-performing user interfaces (UI).
diff --git a/src/routes/intro.mdx b/src/routes/intro.mdx
new file mode 100644
index 000000000..1809b9ecf
--- /dev/null
+++ b/src/routes/intro.mdx
@@ -0,0 +1,35 @@
+---
+title: Intro to Solid
+order: 1
+---
+
+[TODO: 
+- Input on what should be included in a Solid intro
+- Answer questions such as: (maybe)
+    - What are the key features of Solid?
+    - Why use
+    - What are the benefits of using Solid?
+    - Ecosystem
+]
+
+Solid is a modern JavaScript framework designed to build responsive and high-performing user interfaces.
+It prioritizes a simple, yet predictable, developer experience, making it a great choice for developers of all skill levels.
+
+## What is Solid?
+
+As a JavaScript framework, Solid embraces reactivity and fine-grained updates.
+What this means is that Solid can efficiently update the user interface by only re-rendering the parts of the UI that have changed, rather than the entire page. 
+
+Traditionally, when a change occurs, the entire page would need to reload to display the updated information.
+With Solid's fine-grained reactive system, updates are only applied to the parts of the page that need to be updated.
+This decreases work and can result in faster load times as well as a smoother user experience overall.
+
+## The Mental Model
+
+[TODO: Simple explanation of the mental model behind Solid]
+
+## Where to Go Next
+
+- [Quick Start Guide](https://solidjs.com/docs/getting-started)
+- [Reactivity Overview](/concepts/reactivity/)
+- [Component Overview](/concepts/components/)
\ No newline at end of file
diff --git a/src/routes/reactivity/data.json b/src/routes/reactivity/data.json
new file mode 100644
index 000000000..cf237240a
--- /dev/null
+++ b/src/routes/reactivity/data.json
@@ -0,0 +1,12 @@
+{
+	"title": "Reactivity",
+	"pages": [
+		"overview.mdx",
+		"signals.mdx",
+		"memos.mdx",
+		"effects.mdx",
+		"stores.mdx",
+		"resources.mdx",
+		"how-to"
+	]
+}
diff --git a/src/routes/reactivity/effects.mdx b/src/routes/reactivity/effects.mdx
new file mode 100644
index 000000000..64f626609
--- /dev/null
+++ b/src/routes/reactivity/effects.mdx
@@ -0,0 +1,12 @@
+---
+title: "Effects"
+order: 4
+---
+
+[TODO:
+Concept page for Effects
+- What are Effects
+- How to use them
+- When to use Effects
+- Move relevant sections to ref and vice versa
+]
\ No newline at end of file
diff --git a/src/routes/reactivity/how-to/async-data.mdx b/src/routes/reactivity/how-to/async-data.mdx
new file mode 100644
index 000000000..f8ba4a246
--- /dev/null
+++ b/src/routes/reactivity/how-to/async-data.mdx
@@ -0,0 +1,8 @@
+---
+title: "Async Data"
+order: 2
+---
+
+[TODO:
+How to work with async Data
+]
\ No newline at end of file
diff --git a/src/routes/reactivity/how-to/data.json b/src/routes/reactivity/how-to/data.json
new file mode 100644
index 000000000..53d08c540
--- /dev/null
+++ b/src/routes/reactivity/how-to/data.json
@@ -0,0 +1,4 @@
+{
+	"title": "How To",
+	"pages": ["derived-signals.mdx", "async-data.mdx", "debug-reactivity.mdx"]
+}
diff --git a/src/routes/reactivity/how-to/debug-reactivity.mdx b/src/routes/reactivity/how-to/debug-reactivity.mdx
new file mode 100644
index 000000000..28ad0f70b
--- /dev/null
+++ b/src/routes/reactivity/how-to/debug-reactivity.mdx
@@ -0,0 +1,4 @@
+---
+title: "Debugging Reactivity"
+order: 3
+---
diff --git a/src/routes/reactivity/how-to/derived-signals.mdx b/src/routes/reactivity/how-to/derived-signals.mdx
new file mode 100644
index 000000000..59dd72745
--- /dev/null
+++ b/src/routes/reactivity/how-to/derived-signals.mdx
@@ -0,0 +1,11 @@
+---
+title: "Derived Signals"
+order: 1
+---
+
+[TODO:
+How to create derived signals
+- when to use
+- how to use
+- examples
+]
\ No newline at end of file
diff --git a/src/routes/reactivity/memos.mdx b/src/routes/reactivity/memos.mdx
new file mode 100644
index 000000000..bdaf190ab
--- /dev/null
+++ b/src/routes/reactivity/memos.mdx
@@ -0,0 +1,11 @@
+---
+title: "Memos"
+order: 3
+---
+
+[TODO:
+Concept page on Memos
+- Improve on existing page
+- Move relevant sections to reference and vice versa
+- Link out to how-to for derived signals where appropriate
+]
\ No newline at end of file
diff --git a/src/routes/reactivity/overview.mdx b/src/routes/reactivity/overview.mdx
new file mode 100644
index 000000000..725a2186c
--- /dev/null
+++ b/src/routes/reactivity/overview.mdx
@@ -0,0 +1,74 @@
+---
+title: "Overview"
+order: 1
+---
+
+[TODO: Review]
+
+:::note
+While this guide can be helpful for understanding reactive systems, it does use some Solid-specific terminology and concepts.
+:::
+
+Reactivity is what powers the interactivity of Solid apps.
+This programming paradigm refers to a system's ability to respond to changes in data, or state, automatically and efficiently.
+Solid is built with reactivity at the core of its design, assisting applications with staying up-to-date with its underlying data.
+
+## The Importance of Reactivity
+
+Reactivity is what keeps the user interface (UI) in sync with the underlying application state. 
+When the state changes, the UI is automatically updated, reducing the need for manual updates.
+
+In addition, reactivity enables real-time updates, allowing applications to reflect changes instantly without requiring a full page refresh. 
+This helps with creating more responsive and interactive user experiences. 
+
+As an example, when building a Counter, you can use the reactive primitives provided by Solid to create a counter. 
+Once the counter is set up, whenever the count changes, the UI will automatically update to reflect the new count:
+
+```tsx
+function Counter() {
+  const [count, setCount] = createSignal<number>(0);
+  const increment = () => setCount((prev) => prev + 1);
+
+  return (
+    <div>
+      <span>Count: {count()}</span>{" "}
+      {/* Only `count()` is updated when the button is clicked. */}
+      <button type="button" onClick={increment}>
+        Increment
+      </button>
+    </div>
+  );
+}
+```
+
+## Reactive Principles
+
+### Signals
+
+Signals serve as the core elements within a reactive system.
+They play a crucial role in tracking and managing state changes, allowing the UI to respond automatically when the underlying data changes.
+They are responsible for storing and managing data, as well as triggering updates across the system.
+
+Signals are able to achieve this reactivity through the use of:
+
+- **Getters**: A function responsible for retrieving the current value of a signal.
+When called within a reactive context, it will give access to the current value of the signal.
+- **Setters**: This function is responsible for updating the value of a signal.
+To trigger reactivity, setters notify the system that the signal's value has changed, prompting anything that depends on the signal to re-evaluate and update accordingly.
+
+<EraserLink
+	href="https://app.eraser.io/workspace/maDvFw5OryuPJOwSLyK9?elements=lseAEjGlKLslaVsTlfej_g"
+	preview="https://app.eraser.io/workspace/maDvFw5OryuPJOwSLyK9/preview?elements=lseAEjGlKLslaVsTlfej_g&type=embed"
+/>
+
+### Subscribers
+
+Subscribers refer to other reactive contexts or components that depend on the value of a signal.
+These automated responders keep the system up-to-date by re-evaluating and updating whenever the signal's value changes.
+
+Subscribers work based on two main actions:
+- **Observation**: The core function of a subscriber is to observe signals.
+This keeps the subscriber informed about any changes to the signal(s) they're tracking.
+- **Respond**: Once the signal has updated and the subscriber is notified, it triggers a re-evaluation of the dependent computations or UI updates.
+
+[TODO: Some kind of image / code block??]
\ No newline at end of file
diff --git a/src/routes/reactivity/resources.mdx b/src/routes/reactivity/resources.mdx
new file mode 100644
index 000000000..143db8236
--- /dev/null
+++ b/src/routes/reactivity/resources.mdx
@@ -0,0 +1,8 @@
+---
+title: "Resources"
+order: 6
+---
+
+[TODO:
+Concept page on Resource
+]
\ No newline at end of file
diff --git a/src/routes/reactivity/signals.mdx b/src/routes/reactivity/signals.mdx
new file mode 100644
index 000000000..701839712
--- /dev/null
+++ b/src/routes/reactivity/signals.mdx
@@ -0,0 +1,10 @@
+---
+title: "Signals"
+order: 2
+---
+
+[TODO: 
+Concept page on signals
+- Any complex parts should be moved to reference section
+- Move any concept bits from reference section into here
+]
\ No newline at end of file
diff --git a/src/routes/reactivity/stores.mdx b/src/routes/reactivity/stores.mdx
new file mode 100644
index 000000000..eb8a33bb3
--- /dev/null
+++ b/src/routes/reactivity/stores.mdx
@@ -0,0 +1,4 @@
+---
+title: "Stores"
+order: 5
+---
diff --git a/src/routes/rendering/data.json b/src/routes/rendering/data.json
new file mode 100644
index 000000000..1fbb9d7ea
--- /dev/null
+++ b/src/routes/rendering/data.json
@@ -0,0 +1,4 @@
+{
+	"title": "Rendering",
+	"pages": []
+}

From 780750c92b01bdc91aa0b6c16822f2826df46ef8 Mon Sep 17 00:00:00 2001
From: Amir Hossein Hashemi <87268103+amirhhashemi@users.noreply.github.com>
Date: Tue, 26 Aug 2025 19:48:39 +0330
Subject: [PATCH 02/37] Improve data fetching docs (#1179)

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
Co-authored-by: Sarah <gerrardsarah@gmail.com>
---
 src/middleware/legacy-routes-redirect.ts      |   2 +
 src/routes/solid-router/concepts/actions.mdx  | 470 ++++++++++++++----
 src/routes/solid-router/concepts/data.json    |   3 +-
 .../solid-router/data-fetching/data.json      |   4 +
 .../data-fetching/how-to/data.json            |   4 +
 .../handle-error-and-loading-states.mdx       |  29 ++
 .../data-fetching/how-to/preload-data.mdx     |  54 ++
 .../solid-router/data-fetching/queries.mdx    |  81 +++
 .../data-fetching/revalidation.mdx            |  60 +++
 .../solid-router/data-fetching/streaming.mdx  |  90 ++++
 src/routes/solid-router/data.json             |   1 +
 .../reference/data-apis/action.mdx            | 243 ++++-----
 .../data-apis/create-async-store.mdx          | 126 ++++-
 .../reference/data-apis/create-async.mdx      | 139 ++++--
 .../reference/data-apis/query.mdx             | 153 +++---
 .../reference/data-apis/use-action.mdx        |  48 +-
 .../reference/data-apis/use-submission.mdx    | 231 ++++-----
 .../reference/data-apis/use-submissions.mdx   | 281 +++++------
 .../reference/preload-functions/preload.mdx   | 108 ++--
 .../data-fetching.mdx                         |  43 ++
 .../data-loading.mdx                          | 157 ------
 .../data-mutation.mdx                         | 104 ++++
 .../building-your-application/data.json       |   3 +-
 .../solid-start/guides/data-fetching.mdx      |  27 +-
 .../solid-start/guides/data-mutation.mdx      |   8 +-
 .../reference/server/use-server.mdx           |   8 +-
 26 files changed, 1593 insertions(+), 884 deletions(-)
 create mode 100644 src/routes/solid-router/data-fetching/data.json
 create mode 100644 src/routes/solid-router/data-fetching/how-to/data.json
 create mode 100644 src/routes/solid-router/data-fetching/how-to/handle-error-and-loading-states.mdx
 create mode 100644 src/routes/solid-router/data-fetching/how-to/preload-data.mdx
 create mode 100644 src/routes/solid-router/data-fetching/queries.mdx
 create mode 100644 src/routes/solid-router/data-fetching/revalidation.mdx
 create mode 100644 src/routes/solid-router/data-fetching/streaming.mdx
 create mode 100644 src/routes/solid-start/building-your-application/data-fetching.mdx
 delete mode 100644 src/routes/solid-start/building-your-application/data-loading.mdx
 create mode 100644 src/routes/solid-start/building-your-application/data-mutation.mdx

diff --git a/src/middleware/legacy-routes-redirect.ts b/src/middleware/legacy-routes-redirect.ts
index fdf371f9b..647d1b38b 100644
--- a/src/middleware/legacy-routes-redirect.ts
+++ b/src/middleware/legacy-routes-redirect.ts
@@ -180,6 +180,8 @@ const LEGACY_ROUTES = {
 
 	"/solid-router/reference/response-helpers/revalidate":
 		"/solid-router/reference/data-apis/revalidate",
+
+	"/solid-start/guides/data-loading": "/solid-start/guides/data-fetching",
 } as const;
 
 function isLegacyRoute(path: string): path is keyof typeof LEGACY_ROUTES {
diff --git a/src/routes/solid-router/concepts/actions.mdx b/src/routes/solid-router/concepts/actions.mdx
index 53a96da9c..3d59eb63b 100644
--- a/src/routes/solid-router/concepts/actions.mdx
+++ b/src/routes/solid-router/concepts/actions.mdx
@@ -2,151 +2,445 @@
 title: "Actions"
 ---
 
-When developing applications, it is common to need to communicate new information to the server based on user interactions.
-Actions are Solid Router’s solution to this problem.
+Many user interactions in an application involve changing data on the server.
+These **mutations** can be challenging to manage, as they require updates to the application's state and proper error handling.
+Actions simplify managing data mutations.
 
-## What are actions?
+Actions provide several benefits:
 
-Actions are asynchronous processing functions that allow you to submit data to your server and receive a response.
-They are isomorphic, meaning they can run either on the server or the client, depending on what is needed.
-This flexibility makes actions a powerful tool for managing and tracking data submissions.
+- **Integrated state management:**
+  Solid Router automatically tracks the execution state of an action, simplifying reactive UI feedback.
+- **Automatic data revalidation:**
+  After an action successfully completes, Solid Router revalidates relevant [`queries`](/solid-router/concepts/queries), ensuring the UI reflects the latest data.
+- **Progressive enhancement:**
+  When used with HTML forms, actions enable functionality even if JavaScript is not yet loaded.
 
-### How actions work
+## Defining actions
 
-Actions represent the server-side part of an [HTML form](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/form).
-They handle submissions through POST requests, allowing you to easily use HTML forms to send data.
+Actions are defined by wrapping the data-mutation logic with the [`action` function](/solid-router/reference/data-apis/action).
 
-When a user performs an action, such as submitting a form, the data is sent to the server for processing via an action.
+```tsx
+import { action } from "@solidjs/router";
+
+const createTicketAction = action(async (subject: string) => {
+	const response = await fetch("https://my-api.com/support/tickets", {
+		method: "POST",
+		headers: { "Content-Type": "application/json" },
+		body: JSON.stringify({ subject }),
+	});
+
+	if (!response.ok) {
+		const errorData = await response.json();
+		return { ok: false, message: errorData.message };
+	}
+
+	return { ok: true };
+}, "createTicket");
+```
+
+In this example, an action is defined that creates a support ticket using a remote API.
+
+## Using actions
+
+Actions can be triggered in two ways: using a HTML [`<form>` element](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/form) or programmatically using the [`useAction` primitive](/solid-router/reference/data-apis/use-action).
 
-### Benefits of using actions
+The recommended approach is to use a `<form>` element.
+This ensures a robust user experience with progressive enhancement, since the form works even without JavaScript.
 
-1. **Isomorphic**: Since actions can run on both the server and client, you can optimize performance by choosing the best execution environment for your needs.
-2. **Asynchronous processing**: Actions handle data submissions asynchronously, ensuring that your application remains responsive.
-3. **Simplified data handling**: By using actions, the process of managing and tracking data submissions can be streamlined, reducing the complexity of your application.
+For cases where a form is not suitable, the [`useAction` primitive](/solid-router/reference/data-apis/use-action) can be used to trigger the action programmatically.
 
-## Creating actions
+### With the `<form>` element
 
-To create an action, use the `action` function from the `@solidjs/router` package. 
-This function takes an asynchronous function as an argument and returns a new function that can be used to submit data.
+Solid Router extends the standard HTML `<form>` element to work with actions.
+Form submissions can be handled using action by passing an action to the `action` prop.
+
+Consider these points when using actions with `<form>`:
+
+1. The `<form>` element **must** have `method="post"`.
+2. The action function will automatically receive the form's data as a [`FormData`](https://developer.mozilla.org/en-US/docs/Web/API/FormData) object as its first parameter.
+3. For SSR environments, a unique name **must** be provided as the second parameter to the `action` function.
+   This name is used by Solid Router to identify and serialize the action across the client and server.
 
 ```tsx
 import { action } from "@solidjs/router";
 
-const echo = action(async (message: string) => {
-  // Simulates an asynchronous operation, such as an API call
-  await new Promise((resolve, reject) => setTimeout(resolve, 1000));
-  console.log(message);
-});
+const submitFeedbackAction = action(async (formData: FormData) => {
+	const message = formData.get("message")?.toString();
+	// ... Sends the feedback to the server.
+}, "submitFeedback");
+
+function FeedbackForm() {
+	return (
+		<form action={submitFeedbackAction} method="post">
+			<textarea name="message" placeholder="Message" />
+			<button type="submit">Send feedback</button>
+		</form>
+	);
+}
 ```
 
-In this example, the `echo` action simulates a fetch call with a 1 second delay before logging the message to the console.
-The `echo` action will act as a backend, however, it can be substituted for any API provided it can be run on the client.
-Typically, route actions are used with some sort of solution like fetch or GraphQL.
+In this example, when the form is submitted, `submitFeedbackAction` will be triggered with the `FormData` containing the form values.
+
+:::tip[Uploading files]
+If a form that includes file inputs, the `<form>` element must have `enctype="multipart/form-data"` to correctly send the file data.
+
+```tsx
+<form action={uploadFileAction} method="post" enctype="multipart/form-data">
+	<input type="file" name="myFile" />
+	<button type="submit">Upload</button>
+</form>
+```
 
-:::tip
-In [SolidStart](/solid-start) apps, it's recommended to use the [`"use server"`](/solid-start/reference/server/use-server) directive to leverage server-side functionality.
 :::
 
-### Using actions
+#### Passing additional arguments
 
-To use the action, you can call it from within a component using [`useAction`](/solid-router/reference/data-apis/use-action).
-This returns a function that can be called with the necessary arguments to trigger the action.
+Sometimes, an action needs data that isn't part of the form's inputs.
+These additional arguments can be passed using the `with` method.
 
-```tsx del={1} ins={2,9-13}
+The `with` method creates a new action that wraps around the original action.
+When this new action is triggered, it forwards the arguments specified in the `with` method to the original action, followed by the `FormData` object.
+
+```tsx
 import { action } from "@solidjs/router";
+
+const updateProductAction = action(
+	async (productId: string, formData: FormData) => {
+		// ... Sends the updated fields to the server.
+
+		return { ok: true };
+	},
+	"updateProduct"
+);
+
+function EditProductForm(props: { productId: string }) {
+	return (
+		<form action={updateProductAction.with(props.productId)} method="post">
+			<input name="name" placeholder="Product name" />
+			<button type="submit">Save</button>
+		</form>
+	);
+}
+```
+
+In this example, `updateProductAction` receives `productId` (passed via `with`), and then the `formData` from the form.
+
+### With the `useAction` primitive
+
+For scenarios where a `<form>` element is not suitable, the `useAction` primitive provides a way to trigger an action programmatically.
+The `useAction` primitive takes an action as its parameter and returns a function that, when called, triggers the action with the provided arguments.
+
+This approach requires client-side JavaScript and is not progressively enhanceable.
+
+```tsx
 import { action, useAction } from "@solidjs/router";
 
-const echo = action(async (message: string) => {
-  await new Promise((resolve, reject) => setTimeout(resolve, 1000));
-  console.log(message);
+const markNotificationReadAction = action(async (notificationId: string) => {
+	// ... Marks a notification as read on the server.
 });
 
-export function MyComponent() {
-  const myEcho = useAction(echo);
+function NotificationItem(props: { id: string }) {
+	const markRead = useAction(markNotificationReadAction);
 
-  myEcho("Hello from Solid!");
+	return <button onClick={() => markRead(props.id)}>Mark as read</button>;
 }
 ```
 
-In this component, `useAction` is used to get a reference to the `echo` action.
-The action is then called with the message `"Hello from Solid!"`, which will be logged to the console after a 1 second delay.
+In this example, `markRead` is a function that can be called with arguments matching `markNotificationReadAction`.
+When the button is clicked, the action is triggered with the provided arguments.
 
-### Returning data from actions
+## Tracking submission state
 
-In many cases, after submitting data, the server sends some data back as well.
-This may be in the form of an error message if something has failed or the results of a successful operation.
-Anything returned from an action can be accessed using the reactive `action.result` property, where the value can change each time you submit your action.
+When an action is triggered, it creates a **submission** object.
+This object is a snapshot of the action's execution, containing its input, current status (pending or complete), and its final result or error.
+To access this state, Solid Router provides the [`useSubmission`](/solid-router/reference/data-apis/use-submission) and [`useSubmissions`](/solid-router/reference/data-apis/use-submissions) primitives.
 
-To access the action's result, you must pass the action to `useSubmission`:
+The `useSubmission` primitive tracks the state of the _most recent_ submission for a specific action.
+This is ideal for most use cases, such as disabling a form's submit button while the action is pending or displaying a confirmation message upon success.
 
-```tsx del={1} ins={2,11,15-17}
-import { action, useAction } from "@solidjs/router";
-import { action, useAction, useSubmission } from "@solidjs/router";
+```tsx
+import { Show } from "solid-js";
+import { action, useSubmission } from "@solidjs/router";
 
-const echo = action(async (message: string) => {
-  await new Promise((resolve, reject) => setTimeout(resolve, 1000));
-  return message;
-});
+const updateSettingsAction = action(async (formData: FormData) => {
+	// ... Sends the settings data to the server.
+}, "updateSettings");
 
-export function MyComponent() {
-  const myEcho = useAction(echo);
-  const echoing = useSubmission(echo);
+function UserSettingsForm() {
+	const submission = useSubmission(updateSettingsAction);
 
-  myEcho("Hello from solid!");
+	return (
+		<form action={updateSettingsAction} method="post">
+			<input name="email" type="email" placeholder="Enter your email" />
 
-  setTimeout(() => myEcho("This is a second submission!"), 1500);
+			<button disabled={submission.pending}>
+				{submission.pending ? "Saving..." : "Save settings"}
+			</button>
+		</form>
+	);
+}
+```
 
-  return <p>{echoing.result}</p>;
+In this example, the form's submit button is disabled while `submission.pending` is `true`.
+
+:::tip
+To track multiple submissions for a single action, such as in a multi-file uploader interface, the [`useSubmissions` primitive](/solid-router/reference/data-apis/use-submissions) can be used.
+:::
+
+## Handling errors
+
+An action can fail for various reasons.
+A robust application must handle these failures gracefully.
+Solid Router provides two mechanisms for an action to signal failure: throwing an `Error` or returning a value.
+
+Throwing an `Error` is a valid way to signal failure.
+Solid Router will catch the thrown error and make it available in the `submission.error` property.
+However, this approach has some drawbacks.
+The `submission.error` property is typed as `any`, which undermines type safety in the consuming component.
+It is also difficult to convey structured error information, such as validation messages for multiple form fields, using a simple `Error` instance.
+
+For these reasons, the recommended practice is to always `return` a descriptive object from an action to represent its outcome.
+The returned object is available in the `submission.result` property, which will be fully typed.
+This makes handling different outcomes in the UI simple and safe.
+
+```tsx
+import { Show } from "solid-js";
+import { action, useSubmission } from "@solidjs/router";
+
+const verifyTwoFactorAction = action(async (formData: FormData) => {
+	const code = formData.get("code")?.toString();
+
+	if (!code || code.length !== 6) {
+		return {
+			ok: false,
+			errors: { code: "Enter the 6-digit code from the authenticator app." },
+		};
+	}
+
+	// ... Verifies the code with the server and handles potential errors.
+
+	return { ok: true };
+}, "verifyTwoFactor");
+
+function TwoFactorForm() {
+	const submission = useSubmission(verifyTwoFactorAction);
+
+	const errors = () => {
+		const result = submission.result;
+		if (result && !result.ok) {
+			return result.errors;
+		}
+	};
+
+	return (
+		<form action={verifyTwoFactorAction} method="post">
+			<div>
+				<input name="code" placeholder="6-digit code" inputMode="numeric" />
+				<Show when={errors()?.code}>
+					<p>{errors().code}</p>
+				</Show>
+			</div>
+
+			<button type="submit" disabled={submission.pending}>
+				{submission.pending ? "Verifying..." : "Verify"}
+			</button>
+		</form>
+	);
+}
+```
+
+In this example, the `errors` derived signal inspects `submission.result` to check for failures.
+If an `errors` object is found, its properties are used to conditionally render error messages next to the relevant form fields.
+
+:::caution[Always return a value]
+It is important that an action consistently returns a value from all of its possible code paths.
+Because, if an action returns `undefined` or `null`, Solid Router removes that submission from its internal list upon completion.
+This can lead to unexpected behavior.
+
+For example, consider an action that returns an error object on failure but returns nothing on success.
+If the action fails once, `useSubmission` will correctly report the error.
+However, if a subsequent submission succeeds, it will be removed from the list, and `useSubmission` will continue to report the previous stale error state.
+To prevent this, ensure every code path in an action returns a value, such as `{ ok: true }` to indicate a successful outcome.
+:::
+
+## Automatic data revalidation
+
+After server data changes, the application's can become stale.
+To solve this, Solid Router automatically revalidates all [queries](/solid-router/concepts/queries) used in the same page after a successful action.
+This ensures any component using that data is automatically updated with the freshest information.
+
+For example, if a page displays a list of registered devices and includes a form to register a new one, the list will automatically update after the form is submitted.
+
+```tsx
+import { For } from "solid-js";
+import { query, action, createAsync } from "@solidjs/router";
+
+const getDevicesQuery = query(async () => {
+	// ... Fetches the list of registered devices.
+}, "devices");
+
+const registerDeviceAction = action(async (formData: FormData) => {
+	// ... Registers a new device on the server.
+}, "registerDevice");
+
+function DevicesPage() {
+	// This query will automatically revalidate after registerDeviceAction completes.
+	const devices = createAsync(() => getDevicesQuery());
+
+	return (
+		<div>
+			<h2>Registered devices</h2>
+			<For each={devices()}>{(device) => <p>{device.name}</p>}</For>
+
+			<h3>Register new device</h3>
+			<form action={registerDeviceAction} method="post">
+				<input name="name" placeholder="Device name" />
+				<button type="submit">Register device</button>
+			</form>
+		</div>
+	);
 }
 ```
 
-Using `useSubmission` leaves the implementation details of how you trigger `echo` up to you.
-When handling user inputs, for example, it is better to use a `form` for a multitude of reasons.
+While this automatic behavior is convenient for most cases, more fine-grained control may be needed.
+The next section explains how to customize or even disable this behavior for specific actions.
 
-## Using forms to submit data
+## Managing navigation and revalidation
 
-When submitting data with actions, it is recommended to use HTML forms.
-These forms can be used prior to JavaScript loading, which creates instantly interactive applications.
-This also inherently provides accessibility benefits, saving the time of designing a custom UI library that may not have these benefits.
+While automatic revalidation is powerful, more control is often needed.
+It may be desirable to redirect the user to a different page, prevent revalidation entirely, or revalidate a specific set of queries.
+This is where response helpers come in.
 
-When using forms to submit actions, the first argument passed to your action function is an instance of [`FormData`](https://developer.mozilla.org/en-US/docs/Web/API/FormData).
-To use actions with forms, pass the action to the `action` property of your form.
-This creates progressively enhanced forms that work even when JavaScript is disabled.
+Response helpers are functions that create special [`Response`](https://developer.mozilla.org/en-US/docs/Web/API/Response) objects.
+When an action returns or throws one of these responses, Solid Router intercepts it and performs a specific task.
 
-If you do not return a `Response` from your action, the user will stay on the same page and responses will be re-triggered.
-Using a `redirect` can tell the browser to navigate to a new page.
+### Redirecting
 
+To navigate the user to a new page after an action completes, the [`redirect` helper](/solid-router/reference/response-helpers/redirect) can be used.
+It can also be used to revalidate specific queries upon redirection, which is useful for updating data that is displayed on the new page.
 
 ```tsx
 import { action, redirect } from "@solidjs/router";
+import { useSession } from "vinxi/http";
+
+const logoutAction = action(async () => {
+	"use server";
+	const session = await useSession({
+		password: process.env.SESSION_SECRET as string,
+		name: "session",
+	});
+
+	if (session.data.sessionId) {
+		await session.clear();
+		await db.session.delete({ id: sessionId });
+	}
+
+	throw redirect("/");
+}, "logout");
+```
+
+In this example, after a successful login, the `redirect` helper is used to navigate to the dashboard.
+It also revalidates the "session" query to ensure the UI reflects the user's authenticated state.
+
+### Customizing revalidation
 
-const isAdmin = action(async (formData: FormData) => {
-  await new Promise((resolve, reject) => setTimeout(resolve, 1000));
+To override the default revalidation behavior, the [`reload`](/solid-router/reference/response-helpers/reload) and [`json`](/solid-router/reference/response-helpers/json) helpers can be used.
 
-  const username = formData.get("username");
+- `reload` is used when only revalidation needs to be customized.
+- `json` is used when revalidation needs to be controlled _and_ data needs to be returned from the action.
 
-  if (username === "admin") throw redirect("/admin");
-  return new Error("Invalid username");
+Both helpers accept a `revalidate` option, which takes an array of query keys to revalidate.
+If an empty array (`[]`) is provided, revalidation is prevented altogether.
+
+```tsx
+import { action, reload, json } from "@solidjs/router";
+
+// Example 1: Revalidating a specific query
+const savePreferencesAction = action(async () => {
+	// ... Saves the user preferences.
+
+	// Only revalidate the 'userPreferences' query
+	throw reload({ revalidate: ["userPreferences"] });
 });
 
-export function MyComponent() {
+// Example 2: Disabling revalidation and returning data
+const logActivityAction = action(async () => {
+	// ... Logs the activity to the server.
 
-  return (
-    <form action={isAdmin} method="post">
-      <label for="username">Username:</label>
-      <input type="text" name="username" />
-      <input type="submit" value="submit" />
-    </form>
-  );
-}
+	// Return without revalidating any queries
+	return json({ ok: true }, { revalidate: [] });
+});
 ```
 
-**Note:** If you are uploading files make sure you include `enctype="multipart/form-data"` to your `<form>` element.
+:::tip[Throwing vs. Returning]
+A response helper can be either `return`ed or `throw`n.
+In TypeScript, `throw` can be more convenient, as it avoids potential type conflicts with an action's expected return value.
+:::
+
+## Optimistic UI
+
+Optimistic UI is a pattern where the user interface is updated immediately after a user performs an operation.
+This is done without waiting for the server to confirm the operation's success.
+This approach makes an application feel faster and more responsive.
+
+Actions can be combined with local state management to implement optimistic UI.
+The `useSubmission` primitive can be used to access the input of an action as it's being submitted.
+This input can be used to temporarily update the UI.
 
-## Error handling
+```tsx
+import { For, Show } from "solid-js";
+import { query, action, createAsync, useSubmission } from "@solidjs/router";
+
+const getCartQuery = query(async () => {
+	// ... Fetches the current shopping cart items.
+}, "cart");
+
+const addToCartAction = action(async (formData: FormData) => {
+	// ... Adds a product to the cart.
+}, "addToCart");
+
+function CartPage() {
+	const cart = createAsync(() => getCartQuery());
+	const submission = useSubmission(addToCartAction);
+
+	const optimisticCart = () => {
+		const originalItems = cart() ?? [];
+		if (submission.pending) {
+			const formData = submission.input[0] as FormData;
+			const productId = formData.get("productId")?.toString();
+			const name = formData.get("name")?.toString();
+			if (productId && name) {
+				// Add the optimistic line item with a temporary identifier.
+				return [...originalItems, { id: "temp", productId, name, quantity: 1 }];
+			}
+		}
+		return originalItems;
+	};
+
+	return (
+		<div>
+			<h2>Your cart</h2>
+			<For each={optimisticCart()}>{(item) => <p>{item.name}</p>}</For>
+
+			<h3>Add item</h3>
+			<form action={addToCartAction} method="post">
+				<input name="productId" placeholder="Product ID" />
+				<input name="name" placeholder="Product name" />
+				<button type="submit" disabled={submission.pending}>
+					{submission.pending ? "Adding..." : "Add to cart"}
+				</button>
+			</form>
+		</div>
+	);
+}
+```
 
-Rather than throwing errors, it is recommended to return them from actions.
-This helps with the typing of submissions that would be used with `useSubmission`.
-This is important when handling progressive enhancement where no JavaScript is present in the client, so that errors can be used declaratively to render the updated page on the server.
+In this example, a derived signal `optimisticCart` is created.
+When an action is pending, it checks the `submission.input` and adds the new cart item to the list with a temporary ID.
+If the action fails, `submission.pending` becomes false, and `optimisticCart` will revert to showing the original list from `cart`.
+When the action succeeds, Solid Router automatically revalidates `getCartQuery` and updates the UI with the confirmed cart state.
 
-Additionally, when using server actions, it is good practice to handle errors on the server to sanitize error messages.
+:::note
+For more advanced patterns, consider using [TanStack Query](https://tanstack.com/query/latest/docs/framework/solid/guides/optimistic-updates).
+It provides robust tools for managing server state, including cache-based optimistic updates.
+:::
diff --git a/src/routes/solid-router/concepts/data.json b/src/routes/solid-router/concepts/data.json
index 9d91d50dd..835a9fb96 100644
--- a/src/routes/solid-router/concepts/data.json
+++ b/src/routes/solid-router/concepts/data.json
@@ -8,6 +8,7 @@
 		"nesting.mdx",
 		"layouts.mdx",
 		"alternative-routers.mdx",
+		"queries.mdx",
 		"actions.mdx"
 	]
-}
\ No newline at end of file
+}
diff --git a/src/routes/solid-router/data-fetching/data.json b/src/routes/solid-router/data-fetching/data.json
new file mode 100644
index 000000000..e67f9ab6e
--- /dev/null
+++ b/src/routes/solid-router/data-fetching/data.json
@@ -0,0 +1,4 @@
+{
+	"title": "Data fetching",
+	"pages": ["queries.mdx", "streaming.mdx", "revalidation.mdx", "how-to"]
+}
diff --git a/src/routes/solid-router/data-fetching/how-to/data.json b/src/routes/solid-router/data-fetching/how-to/data.json
new file mode 100644
index 000000000..d96966227
--- /dev/null
+++ b/src/routes/solid-router/data-fetching/how-to/data.json
@@ -0,0 +1,4 @@
+{
+	"title": "How to",
+	"pages": ["preload-data.mdx", "handle-error-and-loading-states.mdx"]
+}
diff --git a/src/routes/solid-router/data-fetching/how-to/handle-error-and-loading-states.mdx b/src/routes/solid-router/data-fetching/how-to/handle-error-and-loading-states.mdx
new file mode 100644
index 000000000..2f559a617
--- /dev/null
+++ b/src/routes/solid-router/data-fetching/how-to/handle-error-and-loading-states.mdx
@@ -0,0 +1,29 @@
+---
+title: "Handle pending and error states"
+---
+
+The `createAsync` primitive is designed to work with Solid's native components for managing asynchronous states.
+It reports its pending state to the nearest [`<Suspense>` boundary](/reference/components/suspense) to display loading fallbacks, and propagate errors to an [`<ErrorBoundary>`](/reference/components/error-boundary) for handling and displaying error messages.
+
+```tsx
+import { Suspense, ErrorBoundary, For } from "solid-js";
+import { query, createAsync } from "@solidjs/router";
+
+const getNewsQuery = query(async () => {
+	// ... Fetches the latest news from an API.
+}, "news");
+
+function NewsFeed() {
+	const news = createAsync(() => getNewsQuery());
+
+	return (
+		<ErrorBoundary fallback={<p>Could not fetch news.</p>}>
+			<Suspense fallback={<p>Loading news...</p>}>
+				<ul>
+					<For each={news()}>{(item) => <li>{item.headline}</li>}</For>
+				</ul>
+			</Suspense>
+		</ErrorBoundary>
+	);
+}
+```
diff --git a/src/routes/solid-router/data-fetching/how-to/preload-data.mdx b/src/routes/solid-router/data-fetching/how-to/preload-data.mdx
new file mode 100644
index 000000000..39215abe6
--- /dev/null
+++ b/src/routes/solid-router/data-fetching/how-to/preload-data.mdx
@@ -0,0 +1,54 @@
+---
+title: "Preload data"
+---
+
+Preloading data improves perceived performance by fetching the data for an upcoming page before the user navigates to it.
+
+Solid Router initiates preloading in two scenarios:
+
+- When a user indicates intent to navigate to the page (e.g., by hovering over a link).
+- When the route's component is rendering.
+
+This ensures data fetching starts as early as possible, often making data ready once the component renders.
+
+Preloading is configured using the [`preload`](/solid-router/reference/preload-functions/preload) prop on a [`Route`](/solid-router/reference/components/route).
+This prop accepts a function that calls one or more queries.
+When triggered, the queries execute and their results are stored in a short-lived internal cache.
+Once the user navigates and the destination route’s component renders, any `createAsync` calls within the page will consume the preloaded data.
+Thanks to the [deduplication mechanism](#deduplication), no redundant network requests are made.
+
+```tsx {18-20,27}
+import { Show } from "solid-js";
+import { Route, query, createAsync } from "@solidjs/router";
+
+const getProductQuery = query(async (id: string) => {
+	// ... Fetches product details for the given ID.
+}, "product");
+
+function ProductDetails(props) {
+	const product = createAsync(() => getProductQuery(props.params.id));
+
+	return (
+		<Show when={product()}>
+			<h1>{product().name}</h1>
+		</Show>
+	);
+}
+
+function preloadProduct({ params }: { params: { id: string } }) {
+	getProductQuery(params.id);
+}
+
+function Routes() {
+	return (
+		<Route
+			path="/products/:id"
+			component={ProductDetails}
+			preload={preloadProduct}
+		/>
+	);
+}
+```
+
+In this example, hovering a link to `/products/:id` triggers `preloadProduct`.
+When the `ProductDetails` component renders, its `createAsync` call will instantly resolve with the preloaded data.
diff --git a/src/routes/solid-router/data-fetching/queries.mdx b/src/routes/solid-router/data-fetching/queries.mdx
new file mode 100644
index 000000000..0f43335a6
--- /dev/null
+++ b/src/routes/solid-router/data-fetching/queries.mdx
@@ -0,0 +1,81 @@
+---
+title: "Queries"
+---
+
+Queries are the core building blocks for data fetching in Solid Router.
+They provide an elegant solution for managing data fetching.
+
+## Defining queries
+
+They are defined using the [`query` function](/solid-router/reference/data-apis/query).
+It wraps the data-fetching logic and extends it with powerful capabilities like [request deduplication](#deduplication) and [automatic revalidation](#revalidation).
+
+The `query` function takes two parameters: a **fetcher** and a **name**.
+
+- The **fetcher** is an asynchronous function that fetches data from any source, such as a remote API.
+- The **name** is a unique string used to identify the query.
+  When a query is called, Solid Router uses this name and the arguments passed to the query to create a unique key, which is used for the internal deduplication mechanism.
+
+```tsx
+import { query } from "@solidjs/router";
+
+const getUserProfileQuery = query(async (userId: string) => {
+	const response = await fetch(
+		`https://api.example.com/users/${encodeURIComponent(userId)}`
+	);
+	const json = await response.json();
+
+	if (!response.ok) {
+		throw new Error(json?.message ?? "Failed to load user profile.");
+	}
+
+	return json;
+}, "userProfile");
+```
+
+In this example, the defined query fetches a user's profile from an API.
+If the request fails, the fetcher will throw an error that will be caught by the nearest [`<ErrorBoundary>`](/reference/components/error-boundary) in the component tree.
+
+## Using queries in components
+
+Defining a query does not by itself fetch any data.
+To access its data, the query can be used with the [`createAsync` primitive](/solid-router/reference/data-apis/create-async).
+`createAsync` takes an asynchronous function, such as a query, and returns a signal that tracks its result.
+
+```tsx
+import { For, Show } from "solid-js";
+import { query, createAsync } from "@solidjs/router";
+
+const getArticlesQuery = query(async () => {
+	// ... Fetches a list of articles from an API.
+}, "articles");
+
+function Articles() {
+	const articles = createAsync(() => getArticlesQuery());
+
+	return (
+		<Show when={articles()}>
+			<For each={articles()}>{(article) => <p>{article.title}</p>}</For>
+		</Show>
+	);
+}
+```
+
+In this example, `createAsync` is used to call the query.
+Once the query completes, `articles` holds the result, which is then rendered.
+
+:::tip
+When working with complex data types, such as arrays or deeply nested objects, the [`createAsyncStore` primitive](/solid-router/reference/data-apis/create-async-store) offers a more ergonomic and performant solution.
+It works like `createAsync`, but returns a [store](/concepts/stores) for easier state management..
+:::
+
+## Deduplication
+
+A key feature of queries is their ability to deduplicate requests, preventing redundant data fetching in quick succession.
+
+One common use case is preloading: when a user hovers over a link, the application can begin preloading the data for the destination page.
+If the user then clicks the link, the query has already been completed, and the data is available instantly without triggering another network request.
+This mechanism is fundamental to the performance of Solid Router applications.
+
+Deduplication also applies when multiple components on the same page use the same query.
+As long as at least one component is actively using the query, Solid Router will reuse the cached result instead of refetching the data.
diff --git a/src/routes/solid-router/data-fetching/revalidation.mdx b/src/routes/solid-router/data-fetching/revalidation.mdx
new file mode 100644
index 000000000..3ee773fdf
--- /dev/null
+++ b/src/routes/solid-router/data-fetching/revalidation.mdx
@@ -0,0 +1,60 @@
+---
+title: "Revalidation"
+---
+
+Since server data can change, Solid Router provides mechanisms to revalidate queries and keep the UI up to date.
+
+The most common case is **automatic revalidation**.
+After an [action](/solid-router/concepts/actions) completes successfully, Solid Router automatically revalidates all active queries on the page.
+For more details, see the [actions documentation](/solid-router/concepts/actions#automatic-data-revalidation).
+
+For more fine-grained control, you can trigger revalidation manually with the [`revalidate` function](/solid-router/reference/data-apis/revalidate).
+It accepts a query key (or an array of keys) to target specific queries.
+Each query exposes two properties for this: `key` and `keyFor`.
+
+- `query.key` is the base key for a query and targets all of its instances.
+  Using this key will revalidate all data fetched by that query, regardless of the arguments provided.
+- `query.keyFor(arguments)` generates a key for a specific set of arguments, allowing you to target and revalidate only that particular query.
+
+```tsx
+import { For } from "solid-js";
+import { query, createAsync, revalidate } from "@solidjs/router";
+
+const getProjectsQuery = query(async () => {
+	// ... Fetches a list of projects.
+}, "projects");
+
+const getProjectTasksQuery = query(async (projectId: string) => {
+	// ... Fetches a list of tasks for a project.
+}, "projectTasks");
+
+function Projects() {
+	const projects = createAsync(() => getProjectsQuery());
+
+	function refetchAllTasks() {
+		revalidate(getProjectTasksQuery.key);
+	}
+
+	return (
+		<div>
+			<button onClick={refetchAllTasks}>Refetch all tasks</button>
+			<For each={projects()}>{(project) => <Project id={project.id} />}</For>
+		</div>
+	);
+}
+
+function Project(props: { id: string }) {
+	const tasks = createAsync(() => getProjectTasksQuery(props.id));
+
+	function refetchTasks() {
+		revalidate(getProjectTasksQuery.keyFor(props.id));
+	}
+
+	return (
+		<div>
+			<button onClick={refetchTasks}>Refetch tasks for this project</button>
+			<For each={project.tasks}>{(task) => <div>{task.title}</div>}</For>
+		</div>
+	);
+}
+```
diff --git a/src/routes/solid-router/data-fetching/streaming.mdx b/src/routes/solid-router/data-fetching/streaming.mdx
new file mode 100644
index 000000000..42fa45f41
--- /dev/null
+++ b/src/routes/solid-router/data-fetching/streaming.mdx
@@ -0,0 +1,90 @@
+---
+title: "Streaming"
+---
+
+In traditional server-rendered applications, the server must fetch all data before rendering and sending the page to the browser.
+If some queries are slow, this delays the initial load.
+**Streaming** solves this by sending the page’s HTML shell immediately and progressively streaming data-dependent sections as they become ready.
+
+When a query is accessed during a server-side render, Solid suspends the UI until the data resolves.
+By default, this suspension affects the entire page.
+
+To control this behavior, you can use suspense boundaries - regions of the component tree defined by a [`<Suspense>` component](/reference/components/suspense).
+It isolates asynchronous behavior to a specific section of the page.
+
+Content inside the boundary is managed by Solid’s concurrency system: if it isn’t ready, the boundary’s fallback UI is shown while the rest of the page renders and streams immediately.
+Once the data resolves, the server streams the final HTML for that section, replacing the fallback and letting users see and interact with most of the page much sooner.
+
+```tsx
+import { Suspense, For } from "solid-js";
+import { query, createAsync } from "@solidjs/router";
+
+const getAccountStatsQuery = query(async () => {
+	// ... Fetches account statistics.
+}, "accountStats");
+
+const getRecentTransactionsQuery = query(async () => {
+	// ... Fetches a list of recent transactions.
+}, "recentTransactions");
+
+function Dashboard() {
+	const stats = createAsync(() => getAccountStatsQuery());
+	const transactions = createAsync(() => getRecentTransactionsQuery());
+
+	return (
+		<div>
+			<h1>Dashboard</h1>
+			<Suspense fallback={<p>Loading account stats...</p>}>
+				<For each={stats()}>
+					{(stat) => (
+						<p>
+							{stat.label}: {stat.value}
+						</p>
+					)}
+				</For>
+			</Suspense>
+
+			<Suspense fallback={<p>Loading recent transactions...</p>}>
+				<For each={transactions()}>
+					{(transaction) => (
+						<h2>
+							{transaction.description} - {transaction.amount}
+						</h2>
+					)}
+				</For>
+			</Suspense>
+		</div>
+	);
+}
+```
+
+For example, each `<Suspense>` component creates its own independent boundary.
+The server can stream the heading `<h1>Dashboard</h1>` immediately, while the `stats` and `transactions` are handled separately.
+If the `transactions` query is slow, only its boundary will display a fallback, while `stats` will render as soon as its data is ready.
+
+## When to disable streaming
+
+While streaming is powerful, there are cases where it is better to wait for the data to load on the server.
+In these situations, you can use the `deferStream` option in `createAsync`.
+
+When `deferStream` is set to `true`, the server waits for the query to resolve before sending the initial HTML.
+
+A common reason to disable streaming is for Search Engine Optimization (SEO).
+Some search engine crawlers may not wait for streamed content to load.
+If critical data, such as a page title or meta description, affects SEO, it should be included in the initial server response.
+
+```tsx
+import { query, createAsync } from "@solidjs/router";
+
+const getArticleQuery = query(async () => {
+	// ... Fetches an article.
+}, "article");
+
+function ArticleHeader() {
+	const article = createAsync(() => getArticleQuery(), {
+		deferStream: true,
+	});
+
+	return <h1>{article()?.title}</h1>;
+}
+```
diff --git a/src/routes/solid-router/data.json b/src/routes/solid-router/data.json
index a141ae4d4..e60a784f2 100644
--- a/src/routes/solid-router/data.json
+++ b/src/routes/solid-router/data.json
@@ -5,6 +5,7 @@
 		"getting-started",
 		"concepts",
 		"rendering-modes",
+		"data-fetching",
 		"advanced-concepts",
 		"guides"
 	]
diff --git a/src/routes/solid-router/reference/data-apis/action.mdx b/src/routes/solid-router/reference/data-apis/action.mdx
index 8f3a5e666..7847080fc 100644
--- a/src/routes/solid-router/reference/data-apis/action.mdx
+++ b/src/routes/solid-router/reference/data-apis/action.mdx
@@ -2,196 +2,139 @@
 title: action
 ---
 
-Actions are data mutations that can trigger invalidations and further routing.
-A list of prebuilt response helpers can be found below.
+The `action` function wraps an asynchronous function and returns an [action](/solid-router/concepts/actions).
 
-```jsx
-import { action, revalidate, redirect } from "@solidjs/router"
+When an action is triggered, it creates a submission object that tracks its execution status.
+This state can be accessed with the [`useSubmission`](/solid-router/reference/data-apis/use-submission) and [`useSubmissions`](/solid-router/reference/data-apis/use-submissions) primitives.
 
-// anywhere
-const myAction = action(async (data) => {
-  await doMutation(data);
-  throw redirect("/", { revalidate: getUser.keyFor(data.id) }); // throw a response to do a redirect
-});
-
-// in component
-<form action={myAction} method="post" />
+After an action completed successfully, all queries active in the same page are revalidated, unless revalidation is configured using [response helpers](/solid-router/concepts/actions#managing-navigation-and-revalidation).
 
-//or
-<button type="submit" formaction={myAction}></button>
+## Import
 
+```tsx
+import { action } from "@solidjs/router";
 ```
 
-Actions only work with **post** requests.
-This means forms require `method="post"`.
-
-A `with` method can be used when typed data is required.
-This removes the need to use `FormData` or other additional hidden fields.
-The `with` method works similar to [`bind`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_objects/Function/bind), which applies the arguments in order.
-
-Without `with`:
-
-```jsx
-const deleteTodo = action(async (formData: FormData) => {
-  const id = Number(formData.get("id"))
-  await api.deleteTodo(id)
-})
-
-<form action={deleteTodo} method="post">
-  <input type="hidden" name="id" value={todo.id} />
-  <button type="submit">Delete</button>
-</form>
-
+## Type
+
+```tsx
+function action<T extends Array<any>, U = void>(
+	fn: (...args: T) => Promise<U>,
+	name?: string
+): Action<T, U>;
+
+function action<T extends Array<any>, U = void>(
+	fn: (...args: T) => Promise<U>,
+	options?: { name?: string; onComplete?: (s: Submission<T, U>) => void }
+): Action<T, U>;
+
+function action<T extends Array<any>, U = void>(
+	fn: (...args: T) => Promise<U>,
+	options:
+		| string
+		| { name?: string; onComplete?: (s: Submission<T, U>) => void } = {}
+): Action<T, U>;
 ```
 
-Using `with`:
+## Parameters
 
-```jsx del={5,6} ins={7}
-const deleteTodo = action(async (id: number) => {
-  await api.deleteTodo(id)
-})
+### `handler`
 
-<form action={deleteTodo} method="post">
-  <input type="hidden" name="id" value={todo.id} />
-<form action={deleteTodo.with(todo.id)} method="post">
-  <button type="submit">Delete</button>
-</form>
+- **Type:** `(...args: T) => Promise<U>`
+- **Required:** Yes
 
-```
+An asynchronous function that performs the action's logic.
+When the action is used with a [`<form>` element](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/form), the function receives a [`FormData` object](https://developer.mozilla.org/en-US/docs/Web/API/FormData) as its first parameter.
 
-:::tip
-In [SolidStart](/solid-start) apps, it's recommended to use the [`"use server"`](/solid-start/reference/server/use-server) directive to leverage server-side caching.
-:::
+### `options`
 
-## Notes of `<form>` implementation and SSR
+- **Type:** `string | { name?: string; onComplete?: (s: Submission<T, U>) => void }`
+- **Required**: No
 
-This requires stable references because a string can only be serialized as an attribute, and it is crucial for consistency across SSR. where these references must align.
-The solution is to provide a unique name.
+A unique string used to identify the action in Server-Side Rendering (SSR) environments.
+This is required when using the action with a `<form>` element.
 
-```jsx
-const myAction = action(async (args) => {}, "my-action");
-```
+Alternatively, a configuration object can be passed with the following properties.
 
-## `useAction`
+#### `name`
 
-Instead of forms, actions can directly be wrapped in a `useAction` primitive.
-This is how router context is created.
+- **Type:** `string`
+- **Required:** No
 
-```jsx
-// in component
-const submit = useAction(myAction);
-submit(...args);
+The unique string to identify the action in SSR environments.
+Required for `<form>` usage.
 
-```
+#### `onComplete` (optional):
 
-The outside of a form context can use custom data instead of `formData`.
-These helpers preserve types.
+- **Type:** `(s: Submission<T, U>) => void`
+- **Required:** No
 
-However, even when used with server functions, such as with [SolidStart](https://start.solidjs.com/getting-started/what-is-solidstart), this requires client-side JavaScript and is not progressively enhanceable like forms are.
+A function that runs after the action completes.
+It receives a submission object as its parameter.
 
-## `useSubmission`/`useSubmissions`
+## Return value
 
-These functions are used when incorporating optimistic updates during ongoing actions.
-They provide either a singular Submission (the latest one), or a collection of Submissions that match, with an optional filtering function.
+`action` returns an action with the following properties.
 
-```jsx
-type Submission<T, U> = {
-  input: T;
-  result: U;
-  error: any;
-  pending: boolean
-  clear: () => {}
-  retry: () => {}
-}
+### `with`
 
-const submissions = useSubmissions(action, (input) => filter(input));
-const submission = useSubmission(action, (input) => filter(input));
+A method that wraps the original action and returns a new one.
+When this new action is triggered, the arguments passed to `with` are forwarded to the original action.
+If this new action is used with a `<form>`, the `FormData` object is passed as the last parameter, after any other forwarded parameters.
 
-```
-
-##  Revalidate cached functions
+## Examples
 
-###  Revalidate all (default)
-By default all cached functions will be revalidated wether the action does not return or return a "normal" response.
+### Form submission
 
-```jsx
+```tsx
+import { action } from "@solidjs/router";
 
-const deleteTodo = action(async (formData: FormData) => {
-  const id = Number(formData.get("id"))
-  await api.deleteTodo(id)
-  // ...
-  return new  Response("success",  {  status:  200  });
-})
-```
-
-### Revalidate specific cached keys
-
-By returning a response with solid-router's `json`, `reload` or `redirect` helpers you can pass a key / keys to the revalidate prop as the second argument of the json response helper.
-You can either pass as `string` directly or use the cached functions `key` or `keyFor` props.
-
-```jsx
-import { action, json, reload, redirect } from "@solidjs/router"
-
-const deleteTodo = action(async (formData: FormData) => {
-  const id = Number(formData.get("id"))
-  await api.deleteTodo(id)
-  return json(
-  { deleted: id },
-  { revalidate: ["getAllTodos", getTodos.key, getTodoByID.keyFor(id)]}
-  )
-
-  //or
-  return reload({ revalidate: ["getAllTodos", getTodos.key, getTodoByID.keyFor(id)]})
-
-  //or
-  return redirect("/", { revalidate: ["getAllTodos", getTodos.key, getTodoByID.keyFor(id)]})
-
-})
+const addTodoAction = action(async (formData: FormData) => {
+	// Adds a new todo to the server.
+}, "addTodo");
 
+function TodoForm() {
+	return (
+		<form action={addTodoAction} method="post">
+			<input name="name" />
+			<button>Add todo</button>
+		</form>
+	);
+}
 ```
 
-## Prevent revalidation
-To opt out of any revalidation you can pass any `string` to revalidate which is not a key of any cached function.
-
-```jsx
-const deleteTodo = action(async (formData: FormData) => {
-  const id = Number(formData.get("id"))
-  await api.deleteTodo(id)
-  // returns a `json` without revalidating the action.
-  return json(`deleted ${id}`,{ revalidate: "nothing" })
+### Passing additional arguments
 
-  // or reload the route without revalidating the request.
-  return reload({ revalidate: "nothing" })
+```tsx
+import { action } from "@solidjs/router";
 
- // or redirect without revalidating
- return redirect("/", { revalidate: "nothing" })
-})
+const addTodoAction = action(async (userId: number, formData: FormData) => {
+	// ... Adds a new todo for a specific user.
+}, "addTodo");
 
+function TodoForm() {
+	const userId = 1;
+	return (
+		<form action={addTodoAction.with(userId)} method="post">
+			<input name="name" />
+			<button>Add todo</button>
+		</form>
+	);
+}
 ```
 
-###  Revalidate without action
+### Triggering actions programmatically
 
-Cached functions can also be revalidated by the  `revalidate` helper.
+```tsx
+import { action, useAction } from "@solidjs/router";
 
-```jsx
-revalidate([getTodos.key, getTodoByID.keyFor(id)])
+const markDoneAction = action(async (id: string) => {
+	// ... Marks a todo as done on the server.
+});
 
-```
+function NotificationItem(props: { id: string }) {
+	const markDone = useAction(markDoneAction);
 
-This is also great if you want to set your own "refresh" interval e.g. poll data every 30 seconds.
-
-```jsx
-export default function TodoLayout(){
-	
-	const todos = createAsync(() => getTodos())
-	
-	onMount(() => {
-		//30 second polling
-		const interval = setInterval(() => revalidate(getTodos.key),1000 * 30)
-		onCleanup(() => clearInterval(interval))
-	})
-	
-	// ...
+	return <button onClick={() => markDone(props.id)}>Mark as done</button>;
 }
-
 ```
diff --git a/src/routes/solid-router/reference/data-apis/create-async-store.mdx b/src/routes/solid-router/reference/data-apis/create-async-store.mdx
index a1659422c..caa015890 100644
--- a/src/routes/solid-router/reference/data-apis/create-async-store.mdx
+++ b/src/routes/solid-router/reference/data-apis/create-async-store.mdx
@@ -2,8 +2,128 @@
 title: createAsyncStore
 ---
 
-Similar to [createAsync](/solid-router/reference/data-apis/create-async) except it uses a deeply reactive store. Perfect for applying fine-grained changes to large model data that updates.
+The `createAsyncStore` primitive manages asynchronous data fetching by tracking the result of a promise-returning function in a [store](/concepts/stores).
 
-```jsx
-const todos = createAsyncStore(() => getTodos());
+The main difference from [createAsync](/solid-router/reference/data-apis/create-async) is its use of reconciliation: when new data arrives, it intelligently merges with the existing store, updating only changed fields while preserving unchanged state.
+
+## Import
+
+```tsx
+import { createAsyncStore } from "@solidjs/router";
+```
+
+## Type
+
+```tsx
+function createAsyncStore<T>(
+  fn: (prev: T) => Promise<T>,
+  options: {
+    name?: string;
+    initialValue: T;
+    deferStream?: boolean;
+    reconcile?: ReconcileOptions;
+  }
+): AccessorWithLatest<T>;
+
+function createAsyncStore<T>(
+  fn: (prev: T | undefined) => Promise<T>,
+  options?: {
+    name?: string;
+    initialValue?: T;
+    deferStream?: boolean;
+    reconcile?: ReconcileOptions;
+  }
+): AccessorWithLatest<T | undefined>;
+```
+
+## Parameters
+
+### `fetcher`
+
+- **Type:** `(prev: T | undefined) => Promise<T>`
+- **Required:** Yes
+
+An asynchronous function or a function that returns a `Promise`.
+The resolved value of this `Promise` is what `createAsyncStore` tracks.
+This function is reactive and will automatically re-execute if any of its dependencies change.
+
+### `options`
+
+- **Type:** `{ name?: string; initialValue?: T; deferStream?: boolean; reconcile?: ReconcileOptions; }`
+- **Required:** No
+
+An object for configuring the primitive.
+It has the following properties.
+
+#### `name`
+
+- **Type:** `string`
+- **Required:** No
+
+A name for the resource, used for identification in debugging tools like [Solid Debugger](https://github.com/thetarnav/solid-devtools).
+
+#### `initialValue`
+
+- **Type:** `T`
+- **Required:** No
+
+The initial value of the returned store before the fetcher resolves.
+
+#### `deferStream`
+
+- **Type:** `boolean`
+- **Required:** No
+
+If `true`, [streaming](/solid-router/concepts/queries#streaming) will be deferred until the resource has resolved.
+
+#### `reconcile`
+
+- **Type:** `ReconcileOptions`
+- **Required:** No
+
+[Options](/reference/store-utilities/reconcile#options) passed directly to the `reconcile` function.
+It controls how new data is merged with the existing store.
+
+## Return value
+
+`createAsyncStore` returns a derived signal that contains the resolved value of the fetcher as a store.
+
+While the fetcher is executing for the first time, unless an `initialValue` is specified, the store's value is `undefined`.
+
+## Examples
+
+### Basic usage
+
+```tsx
+import { For, createSignal } from "solid-js";
+import { createAsyncStore, query } from "@solidjs/router";
+
+const getNotificationsQuery = query(async (unreadOnly: boolean) => {
+	// ... Fetches the list of notifications from the server.
+}, "notifications");
+
+function Notifications() {
+	const [unreadOnly, setUnreadOnly] = createSignal(false);
+	const notifications = createAsyncStore(() =>
+		getNotificationsQuery(unreadOnly())
+	);
+
+	return (
+		<div>
+			<button onClick={() => setUnreadOnly(!unreadOnly())}>
+				Toggle unread
+			</button>
+			<ul>
+				<For each={notifications()}>
+					{(notification) => (
+						<li>
+							<div>{notification.message}</div>
+							<div>{notification.user.name}</div>
+						</li>
+					)}
+				</For>
+			</ul>
+		</div>
+	);
+}
 ```
diff --git a/src/routes/solid-router/reference/data-apis/create-async.mdx b/src/routes/solid-router/reference/data-apis/create-async.mdx
index c8b7b833d..59823bdc7 100644
--- a/src/routes/solid-router/reference/data-apis/create-async.mdx
+++ b/src/routes/solid-router/reference/data-apis/create-async.mdx
@@ -2,42 +2,125 @@
 title: createAsync
 ---
 
-An asynchronous primitive with a function that tracks similar to `createMemo`.
-`createAsync` expects a promise back that is then turned into a Signal.
-Reading it before it is ready causes Suspense/Transitions to trigger.
+The `createAsync` primitive manages asynchronous data fetching by tracking the result of a promise-returning function.
 
-:::caution
-	Using `query` in `createResource` directly will not work since the fetcher is
-	not reactive. This means that it will not invalidate properly.
+:::note
+`createAsync` is currently a thin wrapper over `createResource`.
+While `createResource` offers similar functionality, **`createAsync` is the recommended primitive for most asynchronous data fetching**.
+It is intended to be the standard async primitive in a future Solid 2.0 release.
 :::
 
-This is light wrapper over [`createResource`](/reference/basic-reactivity/create-resource) which serves as a stand-in for a future primitive being brought to Solid core in 2.0.
-It is recommended that `createAsync` be used in favor of `createResource` specially when in a **SolidStart** app because `createAsync` works better in conjunction with the [cache](/solid-router/reference/data-apis/cache) helper.
+## Import
 
+```tsx
+import { createAsync } from "@solidjs/router";
+```
 
+## Type
 
-```tsx title="component.tsx" {6,10}
-import { createAsync } from "@solidjs/router";
-import { Suspense } from "solid-js";
-import { getUser } from "./api";
+```tsx
+function createAsync<T>(
+  fn: (prev: T) => Promise<T>,
+  options: {
+    name?: string;
+    initialValue: T;
+    deferStream?: boolean;
+  }
+): AccessorWithLatest<T>;
 
-export function Component () => {
-	const user = createAsync(() => getUser(params.id));
+function createAsync<T>(
+  fn: (prev: T | undefined) => Promise<T>,
+  options?: {
+    name?: string;
+    initialValue?: T;
+    deferStream?: boolean;
+  }
+): AccessorWithLatest<T | undefined>;
+```
 
-	return (
-		<Suspense fallback="loading user...">
-			<p>{user()}</p>
-		</Suspense>
-	);
+## Parameters
+
+### `fetcher`
+
+- **Type:** `(prev: T | undefined) => Promise<T>`
+- **Required:** Yes
+
+An asynchronous function or a function that returns a `Promise`.
+The resolved value of this `Promise` is what `createAsync` tracks.
+This function is reactive and will automatically re-execute if any of its dependencies change.
+
+### `options`
+
+- **Type:** `{ name?: string; initialValue?: T; deferStream?: boolean; }`
+- **Required:** No
+
+An object for configuring the primitive.
+It has the following properties:
+
+#### `name`
+
+- **Type:** `string`
+- **Required:** No
+
+A name for the resource, used for identification in debugging tools like [Solid Debugger](https://github.com/thetarnav/solid-devtools).
+
+#### `initialValue`
+
+- **Type:** `T`
+- **Required:** No
+
+The initial value of the returned signal before the fetcher finishes executing.
+
+#### `deferStream`
+
+- **Type:** `boolean`
+- **Required:** No
+
+If `true`, [streaming](/solid-router/concepts/queries#streaming) will be deferred until the fetcher finishes executing.
+
+## Return value
+
+`createAsync` returns a derived signal that contains the resolved value of the fetcher.
+
+While the fetcher is executing for the first time, unless an `initialValue` is specified, the signal's value is `undefined`.
+
+## Examples
+
+### Basic usage
+
+```tsx
+import { createAsync, query } from "@solidjs/router";
+
+const getUserQuery = query(async (id: string) => {
+	// ... Fetches the user from the server.
+}, "user");
+
+function UserProfile() {
+	const user = createAsync(() => getUserQuery());
+
+	return <p>{user()?.name}</p>;
+}
 ```
 
-## Options
+### Handling loading and errors
+
+```tsx
+import { Suspense, ErrorBoundary, For } from "solid-js";
+import { createAsync, query } from "@solidjs/router";
+
+const getUserQuery = query(async (id: string) => {
+	// ... Fetches the user from the server.
+}, "user");
 
-| Name         | Type                    | Default        | Description                                                                                                                                                   |
-| ------------ | ----------------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| name         | `string`                | `undefined`    | A name for the resource. This is used for debugging purposes.                                                                                                 |
-| deferStream  | `boolean`               | `false`        | If true, Solid will wait for the resource to resolve before flushing the stream.                                                                              |
-| initialValue | `any`                   | `undefined`    | The initial value of the resource.                                                                                                                            |
-| onHydrated   | `function`              | `undefined`    | A callback that is called when the resource is hydrated.                                                                                                      |
-| ssrLoadFrom  | `"server" \| "initial"` | `"server"`     | The source of the initial value for SSR. If set to `"initial"`, the resource will use the `initialValue` option instead of the value returned by the fetcher. |
-| storage      | `function`              | `createSignal` | A function that returns a signal. This can be used to create a custom storage for the resource. This is still experimental
+function UserProfile() {
+	const user = createAsync(() => getUserQuery());
+
+	return (
+		<ErrorBoundary fallback={<p>Could not fetch user data.</p>}>
+			<Suspense fallback={<p>Loading user...</p>}>
+				<p>{user()!.name}</p>
+			</Suspense>
+		</ErrorBoundary>
+	);
+}
+```
diff --git a/src/routes/solid-router/reference/data-apis/query.mdx b/src/routes/solid-router/reference/data-apis/query.mdx
index eab7749ba..09c75eef5 100644
--- a/src/routes/solid-router/reference/data-apis/query.mdx
+++ b/src/routes/solid-router/reference/data-apis/query.mdx
@@ -2,118 +2,87 @@
 title: query
 ---
 
-`query` is a [higher-order function](https://en.wikipedia.org/wiki/Higher-order_function) designed to create a new function with the same signature as the function passed to it.
-When this newly created function is called for the first time with a specific set of arguments, the original function is run, and its return value is stored in a cache and returned to the caller of the created function.
-The next time the created function is called with the same arguments (as long as the cache is still valid), it will return the cached value instead of re-executing the original function.
-
-:::note
-`query` can be defined anywhere and then used inside your components with [`createAsync`](/solid-router/reference/data-apis/create-async).
-
-However, using `query` directly in [`createResource`](/reference/basic-reactivity/create-resource) will not work since the fetcher is not reactive and will not invalidate properly.
-
-:::
-
-## Usage
-
-```js
-const getUser = query(
-	(id, options = {}) =>
-		fetch(`/api/users/${id}?summary=${options.summary || false}`).then((r) =>
-			r.json()
-		),
-	"usersById"
-);
-
-getUser(123); // Causes a GET request to /api/users/123?summary=false
-getUser(123); // Does not cause a GET request
-getUser(123, { summary: true }); // Causes a GET request to /api/users/123?summary=true
-setTimeout(() => getUser(123, { summary: true }), 999000); // Eventually causes another GET request to /api/users/123?summary=true
+The `query` function wraps an asynchronous function (the fetcher) and returns a query.
+
+The primary purpose of a query is to prevent redundant data fetching.
+When a query is called, a key is generated from its name and arguments.
+This key is used to internally cache the result of the fetcher.
+If a query with the same key is called, the cached result is used in these scenarios:
+
+- **For preloading:**
+  After a route's data is preloaded, a subsequent call to the same query within a 5-second window uses the preloaded data.
+- **For active subscriptions:**
+  When a query is actively being used by a component (e.g., via [`createAsync`](/solid-router/reference/data-apis/create-async)), its data is reused without expiration.
+- **On native history navigation:**
+  When navigating with the browser's back or forward buttons, the data is reused instead of being re-fetched.
+- **For server-side deduplication:**
+  Within a single server-side rendering (SSR) request, repeated calls to the same query reuse the same value.
+- **During client hydration:**
+  If SSR has provided data for a key, that data is used immediately on the client without a new network request.
+
+## Import
+
+```tsx
+import { query } from "@solidjs/router";
 ```
 
-### With preload functions
-
-Using it with a [preload function](/solid-router/reference/preload-functions/preload):
-
-```js
-import { lazy } from "solid-js";
-import { Route } from "@solidjs/router";
-import { getUser } from ... // the cache function
+## Type
 
-const User = lazy(() => import("./pages/users/[id].js"));
-
-// preload function
-function preloadUser({params, location}) {
-  void getUser(params.id)
-}
-
-// Pass it in the route definition
-<Route path="/users/:id" component={User} preload={preloadUser} />;
+```tsx
+function query<T extends (...args: any) => any>(
+  fn: T,
+  name: string
+): CachedFunction<T>;
 ```
 
-### Inside a route's component
-
-Using it inside a route's component:
-
-```jsx
-// pages/users/[id].js
-import { getUser } from ... // the cache function
+## Parameters
 
-export default function User(props) {
-  const user = createAsync(() => getUser(props.params.id));
-  return <h1>{user().name}</h1>;
-}
-```
+### `fetcher`
 
-## Query Function Capabilities
+- **Type:** `T extends (...args: any) => any`
+- **Required:** Yes
 
-`query` accomplishes the following:
+An asynchronous function that handles the logic for fetching data.
+All arguments passed to this function must be JSON-serializable.
 
-1. Deduping on the server for the lifetime of the request.
-2. It fills a preload cache in the browser - this lasts 5 seconds.
-   When a route is preloaded on hover or when preload is called when entering a route it will make sure to dedupe calls.
-3. A reactive refetch mechanism based on key.
-   This prevents routes that are not new from retriggering on action revalidation.
-4. Serve as a back/forward cache for browser navigation for up to 5 minutes.
-   Any user based navigation or link click bypasses this cache.
-   Revalidation or new fetch updates the cache.
+### `name`
 
-## Query Keys
+- **Type:** `string`
+- **Required:** Yes
 
-To ensure that the query keys are consistent and unique, arguments are deterministically serialized using `JSON.stringify`.
-Before serialization, key/value pairs in objects are sorted so that the order of properties does not affect the serialization.
-For instance, both `{ name: 'Ryan', awesome: true }` and `{ awesome: true, name: 'Ryan' }` will serialize to the same string so that they produce the same query key.
+A string used as a namespace for the query.
+Solid Router combines this with the query's arguments to generate a unique key for deduplication.
 
 ## Return value
 
-The return value is a `CachedFunction`, a function that has the same signature as the function you passed to `query`.
-This cached function stores the return value using the query key.
-Under most circumstances, this temporarily prevents the passed function from running with the same arguments, even if the created function is called repeatedly.
+`query` returns a new function with the same call signature as the fetcher.
+This returned function has the following properties attached to it:
 
-## Arguments
+### `key`
 
-| argument | type                    | description                                                               |
-| -------- | ----------------------- | ------------------------------------------------------------------------- |
-| `fn`     | `(...args: any) => any` | A function whose return value you'd like to be cached.                    |
-| `name`\* | string                  | Any arbitrary string that you'd like to use as the rest of the query key. |
+The base key for the query, derived from its name.
 
-\*Since the internal cache is shared by all the functions using `query`, the string should be unique for each function passed to `query`.
-If the same key is used with multiple functions, one function might return the cached result of the other.
+### `keyFor`
 
-## Methods
+A function that takes the same arguments as the fetcher and returns a string representing a specific key for that set of arguments.
 
-### `.key` and `.keyFor`
+## Example
 
-Query functions provide `.key` and `.keyFor`, are useful when retrieving the keys used in cases involving invalidation:
+### Basic usage
 
-```ts
-let id = 5;
-getUser.key; // returns "users"
-getUser.keyFor(id); // returns "users[5]"
-```
+```tsx
+import { query } from "@solidjs/router";
 
-### `revalidate`
+const getUserProfileQuery = query(async (userId: string) => {
+	const response = await fetch(
+		`https://api.example.com/users/${encodeURIComponent(userId)}`
+	);
+	const json = await response.json();
 
-The `query` can be revalidated using the `revalidate` method or the `revalidate` keys that are set on the response from the actions.
-If the entire key is passed, it will invalidate all entries for the cache (ie. `users` in the example above).
-If only a single entry needs to be invalidated, `keyFor` is provided.
-To revalidate everything in the cache, pass `undefined` as the key.
+	if (!response.ok) {
+		throw new Error(json?.message ?? "Failed to load user profile.");
+	}
+
+	return json;
+}, "userProfile");
+```
diff --git a/src/routes/solid-router/reference/data-apis/use-action.mdx b/src/routes/solid-router/reference/data-apis/use-action.mdx
index 91d8a5e80..68e117b4b 100644
--- a/src/routes/solid-router/reference/data-apis/use-action.mdx
+++ b/src/routes/solid-router/reference/data-apis/use-action.mdx
@@ -2,26 +2,50 @@
 title: useAction
 ---
 
-`useAction` allows an [`action`](/solid-router/reference/data-apis/action) to be invoked programmatically.
+The `useAction` primitive returns a function that triggers an [action](/solid-router/concepts/actions) when called.
+
+`useAction` requires client-side JavaScript and is not progressively enhanceable.
+
+## Import
 
 ```tsx
 import { useAction } from "@solidjs/router";
-import { updateNameAction } from "./actions";
+```
 
-const updateName = useAction(updateNameAction);
+## Type
 
-const result = updateName("John Wick");
+```tsx
+function useAction<T extends Array<any>, U, V>(
+  action: Action<T, U, V>
+): (...args: Parameters<Action<T, U, V>>) => Promise<NarrowResponse<U>>;
 ```
 
-:::note
-`useAction` requires client-side JavaScript and is not progressively enhanceable.
-:::
-
 ## Parameters
 
-- `action`: The action to be invoked.
+### `action`
+
+- **Type:** `Action<T, U, V>`
+- **Required:** Yes
 
-## Returns
+The action to be triggered.
 
-`useAction` returns a function that invokes the action.
-It shares the same signature as the action itself.
+## Return value
+
+`useAction` returns a function that triggers the action.
+It takes the same parameters as the action handler and returns a [`Promise`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) that resolves with the action's result.
+
+## Example
+
+```tsx
+import { action, useAction } from "@solidjs/router";
+
+const likePostAction = action(async (id: string) => {
+	// ... Likes a post on the server.
+});
+
+function LikeButton(props: { postId: string }) {
+	const likePost = useAction(likePostAction);
+
+	return <button onClick={() => likePost(props.postId)}>Like</button>;
+}
+```
diff --git a/src/routes/solid-router/reference/data-apis/use-submission.mdx b/src/routes/solid-router/reference/data-apis/use-submission.mdx
index 7153e664c..acd2f82e9 100644
--- a/src/routes/solid-router/reference/data-apis/use-submission.mdx
+++ b/src/routes/solid-router/reference/data-apis/use-submission.mdx
@@ -2,160 +2,127 @@
 title: useSubmission
 ---
 
-This helper is used to handle form submissions and can provide optimistic updates while actions are in flight as well as pending state feedback.
-This method will return a single (latest) value while its sibling, [`useSubmissions`](/solid-router/reference/data-apis/use-submissions), will return all values submitted while the component is active. With an optional second parameter for a filter function.
+The `useSubmission` primitive returns the state of the _most recent_ submission for a given [action](/solid-router/concepts/actions).
 
-It's important to note that `useSubmission` requires the form method to be **post** otherwise it will trigger a browser navigation and will not work.
+## Import
 
-```tsx title="component.tsx" {4,8}
+```tsx
 import { useSubmission } from "@solidjs/router";
+```
 
-function Component() {
-  const submission = useSubmission(postNameAction);
-
-    return (
-      <form action={postNameAction} method="post">
-          <input type="text" name="name" />
-          <button type="submit">
-              {submission.pending ? "Adding..." : "Add"}
-          </button>
-      </form>
-    )
-}
+## Type
+
+```tsx
+function useSubmission<T extends Array<any>, U, V>(
+  fn: Action<T, U, V>,
+  filter?: (input: V) => boolean
+): Submission<T, NarrowResponse<U>> | SubmissionStub;
 ```
 
-:::note
-Learn more about actions in the [`action`](/solid-router/reference/data-apis/action) docs.
-:::
+## Parameters
 
-## Filtering Submissions
+### `action`
 
-As an optional second parameter, the `useSubmission` helper can receive a filter function to only return the submission that matches the condition.
-The filter receives the submitted dated as a parameter and should return a boolean value.
-E.g.: action below will only submit if the name is "solid".
+- **Type:** `Action<T, U, V>`
+- **Required:** Yes
 
-```tsx title="component.tsx" {4-8}
-import { useSubmission } from "@solidjs/router";
+The action to track.
 
-function Component() {
-  const submission = useSubmission(postNameAction, ([formData]) => {
-    const name = formData.get("name") ?? "";
-
-    return name === "solid";
-  });
-
-    return (
-      <form action={postNameAction} method="post">
-          <input type="text" name="name" />
-          <button type="submit">
-              {submission.pending ? "Adding..." : "Add"}
-          </button>
-      </form>
-    )
-}
-```
+### `filter`
 
-## Optimistic Updates
+- **Type:** `(input: V) => boolean`
+- **Required:** No
 
-When the form is submitted, the `submission` object will be updated with the new value and the `pending` property will be set to `true`.
-This allows you to provide feedback to the user that the action is in progress.
-Once the action is complete, the `pending` property will be set to `false` and the `result` property will be updated with final value.
+A function that filters submissions.
+It is executed for each submission in the order of creation.
+It receives an array of the action's inputs as a parameter and must return `true` to select the submission or `false` otherwise.
+The first submission that passes the filter is returned by `useSubmission`.
 
-```tsx tab title="TypeScript" {6,10-12}
-// component.tsx
-import { Show } from "solid-js";
-import { useSubmission } from "@solidjs/router";
+## Return value
 
-function Component() {
-  const submission = useSubmission(postNameAction);
-
-    return (
-      <>
-        <Show when={submission.input?.[0].get("name")}>
-          {(name) => <div>Optimistic: {name() as string}</div>}
-        </Show>
-
-        <Show when={submission.result?.name}>
-          {(name) => <div>Result: {name()}</div>}
-        </Show>
-
-        <form method="post" action={sendData}>
-          <input type="text" name="name" required />
-          <button type="submit" disabled={submission.pending}>
-            {submission.pending ? "Submitting" : "Submit"}
-          </button>
-        </form>
-      </>
-    )
-}
-```
+`useSubmission` returns a reactive object with the following properties:
 
-```tsx tab title="JavaScript" {6,10-12}
-// component.jsx
-import { Show } from "solid-js";
-import { useSubmission } from "@solidjs/router";
+### `input`
 
-function Component() {
-  const submission = useSubmission(postNameAction);
-
-    return (
-      <>
-        <Show when={submission.input?.[0].get("name")}>
-          {(name) => <div>Optimistic: {name()}</div>}
-        </Show>
-
-        <Show when={submission.result?.name}>
-          {(name) => <div>Result: {name()}</div>}
-        </Show>
-
-        <form method="post" action={sendData}>
-          <input type="text" name="name" required />
-          <button type="submit" disabled={submission.pending}>
-            {submission.pending ? "Submitting" : "Submit"}
-          </button>
-        </form>
-      </>
-    )
-}
-```
+A reactive value representing the input data of the action.
+
+### `result`
 
-## Error Handling
+A reactive value representing the successful return value of the action.
 
-If the action fails, the `submission` object will be updated with the error and the `pending` property will be set to `false`.
-This allows you to provide feedback to the user that the action has failed. Additionally, the return type of `useSubmission` will have a new key `error` that will contain the error object thrown by the submission handler.
+### `error`
 
-At this stage, you can also use the `retry()` method to attempt the action again or the `clear()` to wipe the filled data in the platform.
+A reactive value representing any error thrown by the action.
 
-```tsx title="component.tsx" {12-18}
+### `pending`
+
+A reactive boolean indicating if the action is currently running.
+
+### `clear`
+
+A function to clear the submission's state.
+
+### `retry`
+
+A function to re-execute the submission with the same input.
+
+## Examples
+
+### Basic usage
+
+```tsx
 import { Show } from "solid-js";
+import { action, useSubmission } from "@solidjs/router";
+
+const addTodoAction = action(async (formData: FormData) => {
+	const name = formData.get("name")?.toString();
+
+	if (!name || name.length <= 2) {
+		return { ok: false, message: "Name must be larger than 2 characters." };
+	}
+
+	// ... Sends the todo data to the server.
+
+	return { ok: true };
+}, "addTodo");
+
+function AddTodoForm() {
+	const submission = useSubmission(addTodoAction);
+
+	return (
+		<form action={addTodoAction} method="post">
+			<input name="name" />
+			<button type="submit">{submission.pending ? "Adding..." : "Add"}</button>
+			<Show when={!submission.result?.ok}>
+				<div>
+					<p>{submission.result.message}</p>
+					<button onClick={() => submission.clear()}>Clear</button>
+					<button onClick={() => submission.retry()}>Retry</button>
+				</div>
+			</Show>
+		</form>
+	);
+}
+```
+
+### Filtering submissions
+
+```tsx
 import { useSubmission } from "@solidjs/router";
 
-function Component() {
-  const submission = useSubmission(postNameAction);
-
-    return (
-      <>
-        <Show when={submission.error}>
-          {(error) => (
-            <div>
-              <p>Error: {error.message}</p>
-              <button onClick={() => submission.clear()}>
-                Clear
-              </button>
-              <button onClick={async () => submission.retry()}>
-               Retry
-              </button>
-            </div>
-          )}
-        </Show>
-
-        <form method="post" action={sendData}>
-          <input type="text" name="name" required />
-          <button type="submit" disabled={submission.pending}>
-            {submission.pending ? "Submitting" : "Submit"}
-          </button>
-        </form>
-      </>
-    )
+const addTodoAction = action(async (formData: FormData) => {
+	// ... Sends the todo data to the server.
+}, "addTodo");
+
+function LatestTodo() {
+	const latestValidSubmission = useSubmission(
+		addTodoAction,
+		([formData]: [FormData]) => {
+			const name = formData.get("name")?.toString();
+			return name && name.length > 2;
+		}
+	);
+
+	return <p>Latest valid submission: {latestValidSubmission.result}</p>;
 }
 ```
diff --git a/src/routes/solid-router/reference/data-apis/use-submissions.mdx b/src/routes/solid-router/reference/data-apis/use-submissions.mdx
index c03ac618c..5a1899755 100644
--- a/src/routes/solid-router/reference/data-apis/use-submissions.mdx
+++ b/src/routes/solid-router/reference/data-apis/use-submissions.mdx
@@ -2,189 +2,146 @@
 title: useSubmissions
 ---
 
-This helper is used to handle form submissions and can provide optimistic updates while actions are in flight as well as pending state feedback.
-This method will return an iterable of all submitted actions while its component is mounted. With an optional second parameter for a filter function.
+The `useSubmissions` primitive returns the state of all submissions for a given [action](/solid-router/concepts/actions).
 
-:::tip
-If you only care for the latest submission, you can use the [`useSubmission`](/solid-router/reference/data-apis/use-submission) helper.
-:::
+## Import
 
-It's important to note that it requires the form method to be **post** otherwise it will trigger a browser navigation and will not work.
-
-In the example below, the `useSubmissions` helper is used to retain a list of all submission results to that action while also giving feedback on the pending state of the current in-flight submission.
-
-```tsx title="component.tsx" {4,9-20, 23}
+```tsx
 import { useSubmissions } from "@solidjs/router";
+```
 
-function Component() {
-  const submissions = useSubmissions(postNameAction);
-
-    return (
-      <form method="post" action={postNameAction}>
-        <ul>
-          <For each={Array.from(submissions.entries())}>
-            {([attemptIndex, data]) => (
-                <Show when={data.result}>
-                    { result => (
-                        <li>
-                            Backend {attemptIndex}: {result.name}
-                        </li>
-                    )}
-                </Show>
-              </>
-            )}
-          </For>
-        </ul>
-        <input name="name" type="text" />
-        <button type="submit">{submissions.pending ? "sending" : "send"}</button>
-      </form>
-    )
-}
+## Type
+
+```tsx
+function useSubmissions<T extends Array<any>, U, V>(
+  fn: Action<T, U, V>,
+  filter?: (input: V) => boolean
+): Submission<T, NarrowResponse<U>>[] & {
+    pending: boolean;
+};
 ```
 
-:::note
-To trigger a submission, [actions](https://docs.solidjs.com/) can be used.
-:::
+## Parameters
 
-## Filtering Submissions
+### `action`
 
-As an optional second parameter, the `useSubmissions` helper can receive a filter function to only return the submission that matches the condition.
-The filter receives the submitted dated as a parameter and should return a boolean value.
-E.g.: action below will only submit if the name is "solid".
+- **Type:** `Action<T, U, V>`
+- **Required:** Yes
 
-```tsx title="component.tsx" {4-8}
-import { useSubmissions } from "@solidjs/router";
+The action to track.
 
-function Component() {
-  const submissions = useSubmissions(postNameAction, ([formData]) => {
-    const name = formData.get("name") ?? "";
-
-        return name === "solid";
-  });
-
-  return (
-    <form method="post" action={postNameAction}>
-        <ul>
-            <For each={Array.from(submissions.entries())}>
-                {([attemptIndex, data]) => (
-                    <Show when={data.result}>
-                        { result => (
-                            <li>
-                                Backend {attemptIndex}: {result.name}
-                            </li>
-                        )}
-                    </Show>
-                </>
-                )}
-            </For>
-        </ul>
-        <input name="name" type="text" />
-        <button type="submit">{submissions.pending ? "sending" : "send"}</button>
-      </form>
-  )
-}
-```
+### `filter`
 
-## Optimistic Updates
+- **Type:** `(input: V) => boolean`
+- **Required:** No
 
-When the form is submitted, the `submission` object will be updated with the new value and the `pending` property will be set to `true`.
-This allows you to provide feedback to the user that the action is in progress.
-Once the action is complete, the `pending` property will be set to `false` and the `result` property will be updated with final value.
+A function that filters submissions.
+It is executed for each submission in the order of creation.
+It receives an array of the action's inputs as a parameter and must return `true` to select the submission or `false` otherwise.
 
-```tsx tab title="TypeScript" {6,13-20}
-// component.tsx
-import { Show } from "solid-js";
-import { useSubmissions } from "@solidjs/router";
+## Return value
 
-function Component() {
-  const submissions = useSubmissions(postNameAction);
-
-    return (
-      <form method="post" action={postNameAction}>
-        <ul>
-          <For each={Array.from(submissions.entries())}>
-            {([attemptIndex, data]) => (
-                <Show when={data.input[0].entries().next()}>
-                    {(input) => {
-                        const name = (input().value as [string, string])[1]
-
-                        return (
-                            <li>Optimistic: {name}</li>
-                        )}}
-                </Show>
-            )}
-          </For>
-        </ul>
-        <input name="name" type="text" />
-        <button type="submit">{submissions.pending ? "sending" : "send"}</button>
-      </form>
-    )
-}
-```
+`useSubmissions` returns a reactive array of submission objects.
+Each submission object has the following properties:
 
-```tsx tab title="JavaScript" {6,13-20}
-// component.jsx
-import { Show } from "solid-js";
-import { useSubmissions } from "@solidjs/router";
+### `input`
 
-function Component() {
-  const submissions = useSubmissions(postNameAction);
-
-    return (
-      <form method="post" action={postNameAction}>
-        <ul>
-          <For each={Array.from(submissions.entries())}>
-            {([attemptIndex, data]) => (
-                <Show when={data.input[0].entries().next()}>
-                    {(input) => {
-                        const name = input().value[1]
-
-                        return (
-                            <li>Optimistic: {name}</li>
-                        )}}
-                </Show>
-            )}
-          </For>
-        </ul>
-        <input name="name" type="text" />
-        <button type="submit">{submissions.pending ? "sending" : "send"}</button>
-      </form>
-    )
-}
-```
+The reactive input data of the action.
+
+### `result`
 
-## Error Handling
+A reactive value representing the successful return value of the action.
 
-If the action fails, the `submission` object will be updated with the error and the `pending` property will be set to `false`.
-This allows you to provide feedback to the user that the action has failed. Additionally, the return type of `useSubmission` will have a new key `error` that will contain the error object thrown by the submission handler.
+### `error`
+
+A reactive value for any error thrown by the action.
+
+### `pending`
+
+A reactive boolean indicating if the action is currently running.
+
+### `clear`
+
+A function to clear the submission's state.
+
+### `retry`
+
+A function to re-execute the submission with the same input.
+
+## Examples
+
+### Basic usage
+
+```tsx
+import { For, Show } from "solid-js";
+import { action, useSubmissions } from "@solidjs/router";
+
+const addTodoAction = action(async (formData: FormData) => {
+	// ... Sends the todo data to the server.
+}, "addTodo");
+
+function AddTodoForm() {
+	const submissions = useSubmissions(addTodoAction);
+
+	return (
+		<div>
+			<form action={addTodoAction} method="post">
+				<input name="name" />
+				<button type="submit">Add</button>
+			</form>
+			<For each={submissions}>
+				{(submission) => (
+					<div>
+						<span>Adding "{submission.input[0].get("name")?.toString()}"</span>
+						<Show when={submission.pending}>
+							<span> (pending...)</span>
+						</Show>
+						<Show when={submission.result?.ok}>
+							<span> (completed)</span>
+						</Show>
+						<Show when={!submission.result?.ok}>
+							<span>{` (Error: ${submission.result?.message})`}</span>
+							<button onClick={() => submission.retry()}>Retry</button>
+						</Show>
+					</div>
+				)}
+			</For>
+		</div>
+	);
+}
+```
 
-At this stage, you can also use the `retry()` method to attempt the action again or the `clear()` to wipe the filled data in the platform.
+### Filtering submissions
 
-```tsx title="component.tsx" {12-18}
-import { Show } from "solid-js";
+```tsx
 import { useSubmissions } from "@solidjs/router";
 
-function Component() {
-  const submissions = useSubmissions(postNameAction);
-
-    return (
-      <form method="post" action={postNameAction}>
-        <ul>
-          <For each={Array.from(submissions.entries())}>
-            {([attempt, data]) => (
-              <Show when={data.error}>
-                <li>
-                  <p>Backend {attempt}: {data.error.message}</p>
-                  <button onClick={() => data.retry()}>retry</button>
-                  <button onClick={() => data.clear()}>clear</button>
-                </li>
-              </Show>
-            )}
-          </For>
-        </ul>
-        <input name="name" type="text" required autocomplete="off" />
-        <button type="submit">{submissions.pending ? "sending" : "send"}</button>
-      </form>
-    )
+const addTodoAction = action(async (formData: FormData) => {
+	// ... Sends the todo data to the server.
+}, "addTodo");
+
+function FailedTodos() {
+	const failedSubmissions = useSubmissions(
+		addTodoAction,
+		([formData]: [FormData]) => {
+			// Filters for submissions that failed a client-side validation
+			const name = formData.get("name")?.toString() ?? "";
+			return name.length <= 2;
+		}
+	);
+
+	return (
+		<div>
+			<p>Failed submissions:</p>
+			<For each={failedSubmissions}>
+				{(submission) => (
+					<div>
+						<span>{submission.input[0].get("name")?.toString()}</span>
+						<button onClick={() => submission.retry()}>Retry</button>
+					</div>
+				)}
+			</For>
+		</div>
+	);
 }
 ```
diff --git a/src/routes/solid-router/reference/preload-functions/preload.mdx b/src/routes/solid-router/reference/preload-functions/preload.mdx
index 71f27bc60..cf21d504b 100644
--- a/src/routes/solid-router/reference/preload-functions/preload.mdx
+++ b/src/routes/solid-router/reference/preload-functions/preload.mdx
@@ -1,46 +1,92 @@
 ---
-title: Preload
+title: preload
 ---
 
-With smart caches waterfalls are still possible with view logic and with lazy loaded code.
-With preload functions, fetching the data parallel to loading the route is possible to allow use of the data as soon as possible.
-The preload function can be called when the Route is loaded or eagerly when links are hovered.
+The `preload` function is a property on a route definition that initiates data fetching before a user navigates to the route.
 
-As its only argument, the preload function is passed an object that can be used to access route information:
+`preload` runs in two separate phases:
 
-```js
-import { lazy } from "solid-js";
+- **Preload phase:**
+  Triggered by user intent (e.g., hovering over a link), the function is called to initiate data fetching.
+- **Rendering phase:**
+  Triggered by actual navigation, the function is called a second time to provide the fetched data to the component.
+
+## Import
+
+```tsx
 import { Route } from "@solidjs/router";
+```
 
-const User = lazy(() => import("./pages/users/[id].js"));
+## Type
 
-// preload function
-function preloadUser({ params, location }) {
-	// do preloading
-}
+```tsx
+type RoutePreloadFunc<T = unknown> = (args: RoutePreloadFuncArgs) => T;
 
-// Pass it in the route definition
-<Route path="/users/:id" component={User} preload={preloadUser} />;
+interface RoutePreloadFuncArgs {
+	params: Params;
+	location: Location;
+	intent: "initial" | "native" | "navigate" | "preload";
+}
 ```
 
-| key      | type                                           | description                                                                                                                                                                                                                                                                                                                                                                 |
-| -------- | ---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| params   | object                                         | The route parameters (same value as calling [`useParams()`](/solid-router/reference/primitives/use-params) inside the route component)                                                                                                                                                                                                                                      |
-| location | `{ pathname, search, hash, query, state, key}` | An object that used to get more information about the path (corresponds to [`useLocation()`](/solid-router/reference/primitives/use-location))                                                                                                                                                                                                                              |
-| intent   | `"initial", "navigate", "native", "preload"`   | Indicates why this function is being called. <ul><li>"initial" - the route is being initially shown (ie page load)</li><li>"native" - navigate originated from the browser (eg back/forward)</li><li>"navigate" - navigate originated from the router (eg call to navigate or anchor clicked)</li><li>"preload" - not navigating, just preloading (eg link hover)</li></ul> |
+## Parameters
 
-A common pattern is to export the preload function and data wrappers that correspond to a route in a dedicated `route.data.js` file.
-This imports the data functions without loading anything else.
+### `params`
 
-```js
-import { lazy } from "solid-js";
-import { Route } from "@solidjs/router";
-import preloadUser from "./pages/users/[id].data.js";
-const User = lazy(() => import("/pages/users/[id].js"));
+- **Type:** `Params`
 
-// In the Route definition
-<Route path="/users/:id" component={User} preload={preloadUser} />;
-```
+An object containing the parameters for the matched route.
+It corresponds to the value returned by the [`useParams` primitive](/solid-router/reference/primitives/use-params).
+
+### `location`
+
+- **Type:** `Location`
+
+The router's location object for the destination URL.
+It corresponds to the value returned by the [`useLocation` primitive](/solid-router/reference/primitives/use-location).
+
+### `intent`
+
+- **Type:** `"initial" | "native" | "navigate" | "preload"`
+
+A string indicating the context in which the function is called.
+
+- `"preload"`:
+  The function is running to initiate data fetching.
+- `"navigate"`:
+  The function is running during navigation to the route.
+- `"initial"`:
+  The function is running for the first route on page load.
 
-The return value of the `preload` function is passed to the page component when called at anytime other than `preload`.
-This initializes things in there, or alternatively the following new `Data APIs` can be used.
+## Return value
+
+The value returned by `preload` is passed to the route's component as the `data` prop.
+
+- In the **preload phase** (`intent: "preload"`), the return value is **ignored**.
+- In the **rendering phase** (`intent: "navigate"` or `"initial"`), the return value is **captured** and provided to the component.
+
+## Examples
+
+```tsx
+import { Route, query, createAsync } from "@solidjs/router";
+
+const getProductQuery = query(async (id: string) => {
+	// ... Fetches a product from the server.
+}, "product");
+
+function ProductPage(props) {
+	const product = createAsync(() => getProductQuery(props.params.id));
+
+	return <div>{product()?.title}</div>;
+}
+
+function preloadData({ params }) {
+	getProductQuery(params.id);
+}
+
+function ProductRoutes() {
+	return (
+		<Route path="/products/:id" component={ProductPage} preload={preloadData} />
+	);
+}
+```
diff --git a/src/routes/solid-start/building-your-application/data-fetching.mdx b/src/routes/solid-start/building-your-application/data-fetching.mdx
new file mode 100644
index 000000000..6204a6bb4
--- /dev/null
+++ b/src/routes/solid-start/building-your-application/data-fetching.mdx
@@ -0,0 +1,43 @@
+---
+title: "Data fetching"
+---
+
+Fetching data from a remote API or database is a core task for most applications.
+[Solid](/) and [Solid Router](/solid-router) provide foundational tools like the [`createResource` primitive](/guides/fetching-data) and [queries](/solid-router/concepts/queries) to manage asynchronous data.
+
+SolidStart builds on these capabilities, extending them to provide a comprehensive solution for data fetching in a full-stack environment.
+
+This page assumes you are familiar with the fundamental concepts of Solid and Solid Router.
+If you are a beginner, we highly recommend starting with the [queries documentation](/solid-router/concepts/queries).
+You can also find many practical examples in the [data fetching how-to guide](/solid-start/guides/data-fetching).
+
+## Server functions and queries
+
+Server functions provide a way to write functions that run exclusively on the server.
+This makes it safe to fetch data directly from a database without relying on a separate API endpoint.
+
+Server functions integrate seamlessly with queries, as they can be used as the fetcher for a query.
+
+```tsx
+import { query, redirect } from "@solidjs/router";
+import { useSession } from "vinxi/http";
+import { db } from "./db";
+
+const getCurrentUserQuery = query(async (id: string) => {
+	"use server";
+	const session = await useSession({
+		password: process.env.SESSION_SECRET as string,
+		name: "session",
+	});
+
+	if (session.data.userId) {
+		return await db.users.get({ id: session.data.userId });
+	} else {
+		throw redirect("/login");
+	}
+}, "currentUser");
+```
+
+In this example, the `getCurrentUserQuery` retrieves the session data, and if an authenticated user exists, it gets their information from the database and returns it.
+Otherwise, it redirects the user to the login page.
+All of these operations are performed completely on the server regardless of how the query is called.
diff --git a/src/routes/solid-start/building-your-application/data-loading.mdx b/src/routes/solid-start/building-your-application/data-loading.mdx
deleted file mode 100644
index 32445361e..000000000
--- a/src/routes/solid-start/building-your-application/data-loading.mdx
+++ /dev/null
@@ -1,157 +0,0 @@
----
-title: "Data loading"
----
-
-SolidStart aims to make it easy to load data from your data sources to keep your UI updated with your data.
-For most of your data requirements, routes will likely be used to decide what data to load.
-SolidStart includes nested routing to help structure your application's UI in a hierarchical way, so that you can share layouts.
-
-## Data loading on the client
-
-Solid provides a way to load data from your data sources using the [`createResource` primitive](/reference/basic-reactivity/create-resource).
-It takes an async function and returns a [signal](/reference/basic-reactivity/create-signal) from it.
-`createResource` integrates with [`Suspense`](/reference/components/suspense) and [`ErrorBoundary`](/reference/components/error-boundary) to help manage lifecycle and error states.
-
-```tsx tab title="TypeScript" {7-10}
-// src/routes/users.tsx
-import { For, createResource } from "solid-js";
-
-type User = { name: string; house: string };
-
-export default function Page() {
-	const [users] = createResource(async () => {
-		const response = await fetch("https://example.com/users");
-		return (await response.json()) as User[];
-	});
-
-	return <For each={users()}>{(user) => <li>{user.name}</li>}</For>;
-}
-```
-
-```tsx tab title="JavaScript" {5-8}
-// src/routes/users.jsx
-import { For, createResource } from "solid-js";
-
-export default function Page() {
-	const [users] = createResource(async () => {
-		const response = await fetch("https://example.com/users");
-		return (await response.json());
-	});
-
-	return <For each={users()}>{(user) => <li>{user.name}</li>}</For>;
-}
-```
-
-When fetching inside components, you can encounter unnecessary waterfalls, especially when nested under lazy loaded sections.
-To solve this, it is recommended to hoist the data fetching to the top of the component tree or, when in [SolidStart](/solid-start), use the server to fetch data in a non-blocking way.
-For the example below we will be using the data in APIs in [`solid-router`](/solid-router)
-
-Using some of the features of `solid-router`, we can create a cache for our data:
-
-```tsx tab title="TypeScript" {7, 10, 13}
-// /routes/users.tsx
-import { For } from "solid-js";
-import { createAsync, query } from "@solidjs/router";
-
-type User = { name: string; email: string };
-
-const getUsers = query(async () => {
-	const response = await fetch("https://example.com/users");
-	return (await response.json()) as User[];
-}, "users");
-
-export const route = {
-	preload: () => getUsers(),
-};
-
-export default function Page() {
-	const users = createAsync(() => getUsers());
-
-	return <For each={users()}>{(user) => <li>{user.name}</li>}</For>;
-}
-```
-
-```tsx tab title="JavaScript" {5, 8, 11}
-// /routes/users.jsx
-import { For } from "solid-js";
-import { createAsync, query } from "@solidjs/router";
-
-const getUsers = query(async () => {
-	const response = await fetch("https://example.com/users");
-	return (await response.json());
-}, "users");
-
-export const route = {
-	preload: () => getUsers(),
-};
-
-export default function Page() {
-	const users = createAsync(() => getUsers());
-
-	return <For each={users()}>{(user) => <li>{user.name}</li>}</For>;
-}
-```
-
-With this method, however, there are some caveats to be aware of:
-
-1. The [`preload`](/solid-router/reference/preload-functions/preload) function is called **once** per route, which is the first time the user comes to that route.
-   Following that, the fine-grained resources that remain alive synchronize with state/url changes to refetch data when needed.
-   If the data needs a refresh, the [`refetch`](/guides/fetching-data#refetch) function returned in the `createResource` can be used.
-2. Before the route is rendered, the `preload` function is called.
-   It does not share the same `context` as the route.
-   The context tree that is exposed to the `preload` function is anything above the `Page` component.
-3. On both the server and the client, the `preload` function is called.
-   The resources can avoid refetching if they serialized their data in the server render.
-   The server-side render will only wait for the resources to fetch and serialize if the resource signals are accessed under a `Suspense` boundary.
-
-### Data loading always on the server
-
-An advantage of being a full-stack JavaScript framework is that it is easy to write data loading code that can run both on the server and client.
-SolidStart offers a way to do that and more.
-Through the `"use server"` comment you can tell the bundler to create an RPC and not include the code in the clients bundle.
-This lets you write code that only runs on the server without needing to create an API route for it.
-For example, it could be database access or internal APIs, or when you sit within your function and need to use your server.
-
-```tsx tab title="TypeScript" {8}
-// /routes/users.tsx
-import { For } from "solid-js";
-import { createAsync, query } from "@solidjs/router";
-
-type User = { name: string; email: string };
-
-const getUsers = query(async () => {
-	"use server";
-	return store.users.list();
-}, "users");
-
-export const route = {
-	preload: () => getUsers(),
-};
-
-export default function Page() {
-	const users = createAsync(() => getUsers());
-
-	return <For each={users()}>{(user) => <li>{user.name}</li>}</For>;
-}
-```
-
-```tsx tab title="JavaScript" {6}
-// /routes/users.jsx
-import { For } from "solid-js";
-import { createAsync, query } from "@solidjs/router";
-
-const getUsers = query(async () => {
-	"use server";
-	return store.users.list();
-}, "users");
-
-export const route = {
-	preload: () => getUsers(),
-};
-
-export default function Page() {
-	const users = createAsync(() => getUsers());
-
-	return <For each={users()}>{(user) => <li>{user.name}</li>}</For>;
-}
-```
diff --git a/src/routes/solid-start/building-your-application/data-mutation.mdx b/src/routes/solid-start/building-your-application/data-mutation.mdx
new file mode 100644
index 000000000..2692c4dfc
--- /dev/null
+++ b/src/routes/solid-start/building-your-application/data-mutation.mdx
@@ -0,0 +1,104 @@
+---
+title: "Data mutation"
+---
+
+Mutating data on a server is a common task in most applications.
+[Solid Router](/solid-router) provides [actions](/solid-router/concepts/actions) to manage data mutations effectively.
+
+SolidStart builds upon the capabilities of actions, extending their scope to provide a comprehensive, full-stack solution for data mutations.
+
+This page does not cover the foundational concepts from Solid Router.
+If you are a beginner, we highly recommend starting with the [actions documentation](/solid-router/concepts/actions).
+You can also find many practical examples in the [data mutation how-to guide](/solid-start/guides/data-mutation).
+
+## Server functions and actions
+
+Server functions allow an action to run exclusively on the server.
+This enables performing sensitive operations—such as writing to a database or working with sessions—directly within the action.
+
+```tsx
+import { action, redirect } from "@solidjs/router";
+import { useSession } from "vinxi/http";
+import { db } from "./db";
+
+const logoutAction = action(async () => {
+	"use server";
+	const session = await useSession({
+		password: process.env.SESSION_SECRET as string,
+		name: "session",
+	});
+
+	if (session.data.sessionId) {
+		await session.clear();
+		await db.session.delete({ id: sessionId });
+	}
+
+	throw redirect("/");
+}, "logout");
+```
+
+In this example, the entire `logoutAction` runs on the server.
+It safely accesses the session to retrieve the `sessionId` and performs a database deletion without exposing this logic to the client.
+The `redirect` then navigates the user back to the home page.
+
+## Single-flight mutations
+
+When a piece of data changes on the server, the new data needs to be fetched so the UI doesn't fall out of sync.
+Traditionally, this is done in two separate HTTP requests: one to update the data, and a second to fetch the new data.
+
+Single-flight mutations are a unique feature of SolidStart that handles this pattern in a single request.
+This is enabled when two requirements are met:
+
+1. The action that updates the data must execute on the server using server functions.
+2. The data that the action updated must be preloaded.
+   If the action performs a redirect, preloading needs to happen on the destination page.
+
+```tsx title="src/routes/products/[id].tsx"
+import {
+	action,
+	query,
+	createAsync,
+	type RouteDefinition,
+	type RouteSectionProps,
+} from "@solidjs/router";
+import { db } from "./db";
+
+const updateProductAction = action(async (id: string, formData: FormData) => {
+	"use server";
+	const name = formData.get("name")?.toString();
+	await db.products.update(id, { name });
+}, "updateProduct");
+
+const getProductQuery = query(async (id: string) => {
+	"use server";
+	return await db.products.get(id);
+}, "product");
+
+export const route = {
+	preload: ({ params }) => getProductQuery(params.id as string),
+} satisfies RouteDefinition;
+
+export default function ProductDetail(props: RouteSectionProps) {
+	const product = createAsync(() => getProductQuery(props.params.id as string));
+
+	return (
+		<div>
+			<p>Current name: {props.data.product?.name}</p>
+			<form
+				action={updateProductAction.with(props.params.id as string)}
+				method="post"
+			>
+				<input name="name" placeholder="New name" />
+				<button>Save</button>
+			</form>
+		</div>
+	);
+}
+```
+
+In this example, `updateProductAction` updates the product within a server function, and `getProductQuery` is responsible for fetching the product data.
+Note that `getProductQuery` is preloaded on the route.
+
+When a user submits the form, a single POST request is sent to the server.
+After the action completes, `getProductQuery` is automatically revalidated.
+Because it's preloaded, SolidStart can trigger the revalidation on the server and stream the result back to the client in the same response.
diff --git a/src/routes/solid-start/building-your-application/data.json b/src/routes/solid-start/building-your-application/data.json
index 2da1baa8d..7d5641d01 100644
--- a/src/routes/solid-start/building-your-application/data.json
+++ b/src/routes/solid-start/building-your-application/data.json
@@ -4,7 +4,8 @@
 		"routing.mdx",
 		"api-routes.mdx",
 		"css-and-styling.mdx",
-		"data-loading.mdx",
+		"data-fetching.mdx",
+		"data-mutation.mdx",
 		"head-and-metadata.mdx",
 		"route-prerendering.mdx",
 		"static-assets.mdx"
diff --git a/src/routes/solid-start/guides/data-fetching.mdx b/src/routes/solid-start/guides/data-fetching.mdx
index 5a1a4c38a..6707b6d95 100644
--- a/src/routes/solid-start/guides/data-fetching.mdx
+++ b/src/routes/solid-start/guides/data-fetching.mdx
@@ -2,17 +2,9 @@
 title: "Data fetching"
 ---
 
-SolidStart is built on top of [Solid](/) and uses [Solid Router](/solid-router) by default.
-This means you can leverage their respective data-fetching primitives within SolidStart.
-Since SolidStart itself provides minimal data-fetching APIs, most functionality comes from Solid and Solid Router.
+This guide provides practical examples of common data-fetching tasks in SolidStart.
 
-This guide provides practical examples of common data-fetching tasks using these primitives.
-
-:::note
-For detailed API information, refer to the [Solid](/) and [Solid Router](/solid-router) documentation.
-:::
-
-Here's a simple example:
+Here's an example showing how to create a [`query`](/solid-router/concepts/queries) and access its data with the [`createAsync` primitive](/solid-router/reference/data-apis/create-async):
 
 ```tsx tab title="TypeScript"
 // src/routes/index.tsx
@@ -54,12 +46,9 @@ export default function Page() {
 }
 ```
 
-In this example, a [`query`](/solid-router/reference/data-apis/query) is created.
-In order to access it's data within the component, the [`createAsync`](/solid-router/reference/data-apis/create-async) primitive was used.
-
 ## Showing loading UI
 
-To show a loading UI during data-fetching:
+To show a loading UI during data fetching:
 
 1. Import [`Suspense`](/reference/components/suspense) from `solid-js`.
 2. Wrap your data rendering in `<Suspense>`, and use the `fallback` prop to show a component during data fetching.
@@ -110,7 +99,7 @@ export default function Page() {
 
 ## Handling errors
 
-To show a fallback UI if the data-fetching fails:
+To show a fallback UI if the data fetching fails:
 
 1. Import [`ErrorBoundary`](/reference/components/error-boundary) from `solid-js`.
 2. Wrap the data rendering in `<ErrorBoundary>`, and use the `fallback` prop to show a component if an error occurs.
@@ -165,7 +154,7 @@ export default function Page() {
 
 ## Preloading data
 
-Data fetching can be optimized during user navigation by preloading the data:
+To preload data before a route renders:
 
 1. Export a `route` object with a [`preload`](/solid-router/reference/preload-functions/preload) function.
 2. Run your query inside the `preload` function.
@@ -225,7 +214,7 @@ export default function Page() {
 
 ## Passing parameters to queries
 
-When creating a query that accepts parameters, define your query function to take any number of arguments:
+When creating a query that accepts parameters, define your query function to take any number of parameters:
 
 ```tsx tab title="TypeScript" {5} {11} {16}
 // src/routes/posts/[id]/index.tsx
@@ -283,7 +272,7 @@ export default function Page() {
 
 ## Using a database or an ORM
 
-To safely interact with your database or ORM in a query, ensure it's server-only by adding [`"use server"`](/solid-start/reference/server/use-server) as the first line of your query:
+To safely interact with your database or ORM in a query, use a [server function](/solid-start/reference/server/use-server):
 
 ```tsx tab title="TypeScript" {7-8}
 // src/routes/index.tsx
@@ -388,5 +377,5 @@ export default function Page() {
 See the [`createResource`](/reference/basic-reactivity/create-resource) API reference for more information.
 
 :::note[Advanced Data Handling]
-For advanced features like automatic background re-fetching or infinite queries, you can use [Tanstack Query](https://tanstack.com/query/latest/docs/framework/solid/overview).
+For advanced features like automatic background re-fetching or infinite queries, you can use [TanStack Query](https://tanstack.com/query/latest/docs/framework/solid/overview).
 :::
diff --git a/src/routes/solid-start/guides/data-mutation.mdx b/src/routes/solid-start/guides/data-mutation.mdx
index abcc75f27..e2bcced15 100644
--- a/src/routes/solid-start/guides/data-mutation.mdx
+++ b/src/routes/solid-start/guides/data-mutation.mdx
@@ -12,7 +12,7 @@ To handle [`<form>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/f
    See the [Action API reference](/solid-router/reference/data-apis/action#notes-of-form-implementation-and-ssr) for more information.
 2. Pass the action to the `<form>` element using the `action` prop.
 3. Ensure the `<form>` element uses the `post` method for submission.
-4. Use the [`FormData`](https://developer.mozilla.org/en-US/docs/Web/API/FormData/FormData) object in the action to extract field data using the navite `FormData` methods.
+4. Use the [`FormData`](https://developer.mozilla.org/en-US/docs/Web/API/FormData/FormData) object in the action to extract field data using the native `FormData` methods.
 
 ```tsx tab title="TypeScript" {4-10} {14}
 // src/routes/index.tsx
@@ -486,12 +486,12 @@ export default function Page() {
 }
 ```
 
-## Invoking an action programmatically
+## Triggering an action programmatically
 
-To programmatically invoke an action:
+To programmatically trigger an action:
 
 1. Import [`useAction`](/solid-router/reference/data-apis/use-action) from `@solidjs/router`.
-2. Call `useAction` with your action, and use the returned function to invoke the action.
+2. Call `useAction` with your action, and use the returned function to trigger the action.
 
 ```tsx tab title="TypeScript" {14} {18}
 // src/routes/index.tsx
diff --git a/src/routes/solid-start/reference/server/use-server.mdx b/src/routes/solid-start/reference/server/use-server.mdx
index 87dbad035..6c4cc6d33 100644
--- a/src/routes/solid-start/reference/server/use-server.mdx
+++ b/src/routes/solid-start/reference/server/use-server.mdx
@@ -44,7 +44,7 @@ In both examples, the `logHello` function will only show in the server console,
 
 ## Usage with Data APIs
 
-Server functions can be used for fetching data and performing actions on the server. 
+Server functions can be used for fetching data and performing actions on the server.
 The following examples show how to use server functions alongside solid-router's data APIs.
 
 ```tsx {3}
@@ -61,12 +61,12 @@ const updateUser = action(async (id, data) => {
 
 ```
 
-When `getUser` or `updateUser` are invoked on the client, an http request will be made to the server, which calls the corresponding server function.
+When `getUser` or `updateUser` are triggered on the client, an http request will be made to the server, which calls the corresponding server function.
 
 ## Single-flight mutations
 
-In the above example, when the `updateUser` action is called, a redirect is thrown on the server. 
-Solid Start can handle this redirect on the server instead of propagating it to the client. 
+In the above example, when the `updateUser` action is called, a redirect is thrown on the server.
+Solid Start can handle this redirect on the server instead of propagating it to the client.
 The data for the redirected page is fetched and streamed to the client in the same http request as the `updateUser` action, rather than the client requiring a separate http request for the redirected page.
 
 ## Serialization

From 20cf242155dc7dfb2298ab4cc33dd15ef558ef1b Mon Sep 17 00:00:00 2001
From: LadyBluenotes <gerrardsarah@gmail.com>
Date: Wed, 27 Aug 2025 21:36:48 -0700
Subject: [PATCH 03/37] quick start

---
 src/routes/getting-started/quick-start.mdx | 71 +++++++++++++++++++---
 1 file changed, 64 insertions(+), 7 deletions(-)

diff --git a/src/routes/getting-started/quick-start.mdx b/src/routes/getting-started/quick-start.mdx
index 4e5a93110..8c0038ce1 100644
--- a/src/routes/getting-started/quick-start.mdx
+++ b/src/routes/getting-started/quick-start.mdx
@@ -1,5 +1,5 @@
 ---
-title: Quick Start Guide
+title: Quick Start
 order: 1
 ---
 
@@ -15,12 +15,69 @@ If you prefer a more complete development setup, you can use the StackBlitz [Jav
 ## Create a New Project
 
 :::note[Before You Begin]
-Make sure you have a recent version of your prefer JavaScript runtime installed, such as [Node.js](https://nodejs.org/en), [Bun](https://bun.sh/), or [Deno](https://deno.com/).
+Make sure you have a recent version of your preferred JavaScript runtime installed, such as [Node.js](https://nodejs.org/en), [Bun](https://bun.sh/), or [Deno](https://deno.com/).
 :::
 
-[TODO]
+To create a new Solid project, follow these steps:
 
-- Navigate to directory and run command
-- CLI will take you through options
-- Once you've selected your options, the CLI will prompt you to install the dependencies and start the development server
-- Open browser and navigate to the provided local URL to see your new Solid app in action!
\ No newline at end of file
+1. **Open your terminal and navigate to the directory** where you want to create your project.
+
+2. **Run the following command:**
+
+```package-create
+solid
+```
+
+3. **Follow the CLI prompts** to select your project name, template (JavaScript or TypeScript), and other options.
+
+```sh
+◆ Project Name
+|  <solid-project>
+
+◆ Is this a SolidStart project?
+|  ● Yes / ○ No
+
+◆ Which template would you like to use?
+│  ● ts
+│  ○ ts-vitest
+│  ○ ts-uvu
+│  ○ ts-unocss
+│  ○ ts-tailwindcss
+
+◆ Use TypeScript?
+│  ● Yes / ○ No
+```
+
+4. **Follow the instructions to install the dependencies and start the development server:**
+
+```sh title="npm" tab="package-manager"
+cd solid-project
+npm install
+npm run dev
+```
+
+```sh title="pnpm" tab="package-manager"
+cd solid-project
+pnpm install
+pnpm dev
+```
+
+```sh title="yarn" tab="package-manager"
+cd solid-project
+yarn install
+yarn dev
+```
+
+```sh title="bun" tab="package-manager"
+cd solid-project
+bun install
+bun run dev
+```
+
+```sh title="deno" tab="package-manager"
+cd solid-project
+deno install
+deno run dev
+```
+
+6. **Open your browser and go to the local URL** provided in the terminal to see your new Solid app in action!
\ No newline at end of file

From a67220a0a4fbeb9b70d9f62734c9ef7403365fbd Mon Sep 17 00:00:00 2001
From: LadyBluenotes <gerrardsarah@gmail.com>
Date: Thu, 28 Aug 2025 13:14:38 -0700
Subject: [PATCH 04/37] update titles and reactivity basics page

---
 src/routes/components/data.json     |  2 +-
 src/routes/components/intro.mdx     | 10 ++++
 src/routes/reactivity/basics.mdx    | 88 +++++++++++++++++++++++++++++
 src/routes/reactivity/data.json     |  2 +-
 src/routes/reactivity/effects.mdx   |  2 +-
 src/routes/reactivity/memos.mdx     |  2 +-
 src/routes/reactivity/overview.mdx  | 74 ------------------------
 src/routes/reactivity/resources.mdx |  2 +-
 src/routes/reactivity/signals.mdx   | 76 +++++++++++++++++++++++--
 src/routes/reactivity/stores.mdx    |  2 +-
 10 files changed, 175 insertions(+), 85 deletions(-)
 create mode 100644 src/routes/components/intro.mdx
 create mode 100644 src/routes/reactivity/basics.mdx
 delete mode 100644 src/routes/reactivity/overview.mdx

diff --git a/src/routes/components/data.json b/src/routes/components/data.json
index f675b706b..12b3976db 100644
--- a/src/routes/components/data.json
+++ b/src/routes/components/data.json
@@ -1,4 +1,4 @@
 {
 	"title": "Components",
-	"pages": []
+	"pages": ["intro.md"]
 }
diff --git a/src/routes/components/intro.mdx b/src/routes/components/intro.mdx
new file mode 100644
index 000000000..cdd8bd041
--- /dev/null
+++ b/src/routes/components/intro.mdx
@@ -0,0 +1,10 @@
+---
+title: "Intro to Components"
+order: 1
+---
+
+[TODO]
+
+## Component lifecycle
+
+[TODO]
\ No newline at end of file
diff --git a/src/routes/reactivity/basics.mdx b/src/routes/reactivity/basics.mdx
new file mode 100644
index 000000000..17d223d9b
--- /dev/null
+++ b/src/routes/reactivity/basics.mdx
@@ -0,0 +1,88 @@
+---
+title: "Reactivity Basics"
+order: 1
+---
+
+
+Reactivity is the foundation of Solid.  
+It’s the programming model where **changes in data automatically update the parts of your app that depend on it**.  
+
+Solid’s approach is **fine-grained**: instead of re-rendering entire components, only the exact parts of the DOM that depend on a value update. This makes applications efficient and responsive, even as they grow.
+
+## Core Principles of Reactivity
+	
+Solid’s reactivity is built on three key ideas: **signals, subscribers, and tracking scopes**.  
+Together, these create a system where updates are precise, automatic, and efficient.
+
+### Signals: Reactive Values
+
+A **signal** is a reactive value container.
+They consist of 2 parts:
+- **Getter** → reads the current value.  
+- **Setter** → updates the value and notifies dependents.  
+
+```tsx
+const [count, setCount] = createSignal(0);
+
+console.log(count()); // 0
+setCount(1);
+console.log(count()); // 1
+```
+
+Signals can hold any type of value:
+- primitives (string, number, boolean)
+- objects and arrays
+- application state (user, theme, current page)
+
+Learn more in the [Signals page](/reactivity/signals).
+
+### Subscribers: Reactive Consumers
+
+If signals are the **source of truth**, subscribers are the **reactive consumers**.
+
+A subscriber is any function or construct that reads a signal inside a tracking scope and automatically re-runs whenever it changes.
+This is what makes Solid’s reactivity *fine-grained*: only the subscribers that depend on a signal update, not the entire component.
+
+How subscribers work:
+1. **Observation** → subscriber runs and reads signals.
+2. **Dependency tracking** → those signals register the subscriber.
+3. **Response** → when a signal changes, the subscriber re-runs.
+
+### Tracking Scopes: Connecting Signals & Subscribers
+
+A **tracking scope** is the environment where Solid records which signals are being used.
+When a signal is read within a tracking scope, it registers the current subscriber as a dependency.
+Once that signal changes, it will notify the subscriber to re-run and update accordingly.
+
+Tracking scopes within Solid include:
+- Component render functions (JSX return values)
+- Reactive computations (e.g., `createMemo`)
+- Effects (e.g., `createEffect`)
+
+Example of a tracking vs non-tracking scope:
+
+```tsx
+import { createSignal } from "solid-js";
+
+function Counter() {
+  const [count, setCount] = createSignal(0);
+
+  console.log(count()) // ❌ Not tracked — runs once
+
+  return (
+    <div>
+      <p>Count: {count()}</p> {/* ✅ tracked automatically - re-runs on update */}
+      <button onClick={() => setCount(count() + 1)}>Increment</button>
+    </div>
+  );
+}
+```
+
+Tracking scopes are what enable **precise DOM updates**: only parts of the UI that depend on signals re-run, not the entire component.
+You can learn more about [component lifecycles in the Intro to Components page](/components/intro).
+
+
+## Related pages
+- [Signals](/reactivity/signals)
+- [Reactive Side Effects](/reactivity/effects)
+- [Introduction to Components](/components/intro)
diff --git a/src/routes/reactivity/data.json b/src/routes/reactivity/data.json
index cf237240a..5cdfeb89b 100644
--- a/src/routes/reactivity/data.json
+++ b/src/routes/reactivity/data.json
@@ -1,7 +1,7 @@
 {
 	"title": "Reactivity",
 	"pages": [
-		"overview.mdx",
+		"basics.mdx",
 		"signals.mdx",
 		"memos.mdx",
 		"effects.mdx",
diff --git a/src/routes/reactivity/effects.mdx b/src/routes/reactivity/effects.mdx
index 64f626609..1086c53e9 100644
--- a/src/routes/reactivity/effects.mdx
+++ b/src/routes/reactivity/effects.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Effects"
+title: "Derived Reactive Values"
 order: 4
 ---
 
diff --git a/src/routes/reactivity/memos.mdx b/src/routes/reactivity/memos.mdx
index bdaf190ab..6f07f36bb 100644
--- a/src/routes/reactivity/memos.mdx
+++ b/src/routes/reactivity/memos.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Memos"
+title: "Memoized Computations"
 order: 3
 ---
 
diff --git a/src/routes/reactivity/overview.mdx b/src/routes/reactivity/overview.mdx
deleted file mode 100644
index 725a2186c..000000000
--- a/src/routes/reactivity/overview.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: "Overview"
-order: 1
----
-
-[TODO: Review]
-
-:::note
-While this guide can be helpful for understanding reactive systems, it does use some Solid-specific terminology and concepts.
-:::
-
-Reactivity is what powers the interactivity of Solid apps.
-This programming paradigm refers to a system's ability to respond to changes in data, or state, automatically and efficiently.
-Solid is built with reactivity at the core of its design, assisting applications with staying up-to-date with its underlying data.
-
-## The Importance of Reactivity
-
-Reactivity is what keeps the user interface (UI) in sync with the underlying application state. 
-When the state changes, the UI is automatically updated, reducing the need for manual updates.
-
-In addition, reactivity enables real-time updates, allowing applications to reflect changes instantly without requiring a full page refresh. 
-This helps with creating more responsive and interactive user experiences. 
-
-As an example, when building a Counter, you can use the reactive primitives provided by Solid to create a counter. 
-Once the counter is set up, whenever the count changes, the UI will automatically update to reflect the new count:
-
-```tsx
-function Counter() {
-  const [count, setCount] = createSignal<number>(0);
-  const increment = () => setCount((prev) => prev + 1);
-
-  return (
-    <div>
-      <span>Count: {count()}</span>{" "}
-      {/* Only `count()` is updated when the button is clicked. */}
-      <button type="button" onClick={increment}>
-        Increment
-      </button>
-    </div>
-  );
-}
-```
-
-## Reactive Principles
-
-### Signals
-
-Signals serve as the core elements within a reactive system.
-They play a crucial role in tracking and managing state changes, allowing the UI to respond automatically when the underlying data changes.
-They are responsible for storing and managing data, as well as triggering updates across the system.
-
-Signals are able to achieve this reactivity through the use of:
-
-- **Getters**: A function responsible for retrieving the current value of a signal.
-When called within a reactive context, it will give access to the current value of the signal.
-- **Setters**: This function is responsible for updating the value of a signal.
-To trigger reactivity, setters notify the system that the signal's value has changed, prompting anything that depends on the signal to re-evaluate and update accordingly.
-
-<EraserLink
-	href="https://app.eraser.io/workspace/maDvFw5OryuPJOwSLyK9?elements=lseAEjGlKLslaVsTlfej_g"
-	preview="https://app.eraser.io/workspace/maDvFw5OryuPJOwSLyK9/preview?elements=lseAEjGlKLslaVsTlfej_g&type=embed"
-/>
-
-### Subscribers
-
-Subscribers refer to other reactive contexts or components that depend on the value of a signal.
-These automated responders keep the system up-to-date by re-evaluating and updating whenever the signal's value changes.
-
-Subscribers work based on two main actions:
-- **Observation**: The core function of a subscriber is to observe signals.
-This keeps the subscriber informed about any changes to the signal(s) they're tracking.
-- **Respond**: Once the signal has updated and the subscriber is notified, it triggers a re-evaluation of the dependent computations or UI updates.
-
-[TODO: Some kind of image / code block??]
\ No newline at end of file
diff --git a/src/routes/reactivity/resources.mdx b/src/routes/reactivity/resources.mdx
index 143db8236..16342dad1 100644
--- a/src/routes/reactivity/resources.mdx
+++ b/src/routes/reactivity/resources.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Resources"
+title: "Handling Async Data"
 order: 6
 ---
 
diff --git a/src/routes/reactivity/signals.mdx b/src/routes/reactivity/signals.mdx
index 701839712..6a5eab9d4 100644
--- a/src/routes/reactivity/signals.mdx
+++ b/src/routes/reactivity/signals.mdx
@@ -3,8 +3,74 @@ title: "Signals"
 order: 2
 ---
 
-[TODO: 
-Concept page on signals
-- Any complex parts should be moved to reference section
-- Move any concept bits from reference section into here
-]
\ No newline at end of file
+Signals are the **primary way to manage state** in a Solid application.  
+They store values, notify dependents when those values change, and form the [foundation of reactivity](/reactivity/overview).
+
+You can use signals for any kind of state:  
+- simple values (strings, numbers)  
+- complex values (objects, arrays)  
+- application state (current user, theme, page, etc.)
+
+## What is a Signal?
+
+A **signal** is a reactive value container.  
+- It holds a value.  
+- It provides a **getter** to read the value.  
+- It provides a **setter** to update the value.  
+- When the value changes, any reactive computations that depend on it are updated automatically.  
+
+They can be thought of as a **reactive variable**.
+
+## Create a Signal
+
+
+Use [`createSignal`](/reference/basic-reactivity/create-signal) from `solid-js`:
+
+```tsx
+import { createSignal } from "solid-js";
+
+const [count, setCount] = createSignal(0);
+//       ^ getter  ^ setter
+```
+
+:::note
+The [getter, setter] syntax uses [array destructuring](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment)().
+:::
+
+
+## Read a Signal's Value
+
+To read the current value of a signal, simply call the getter function:
+
+```tsx
+console.log(count()); // 0
+```
+
+## Update a Signal's Value
+
+To update the value of a signal, call the setter function with the new value:
+
+```tsx
+setCount(1);
+console.log(count()); // 1
+```
+
+## Reactivity in Action
+
+Signals are **reactive**: when used inside a tracking scope, they automatically notify dependents when updated.
+
+```tsx
+function Counter() {
+  const [count, setCount] = createSignal(0);
+  const increment = () => setCount(prev => prev + 1);
+
+  return (
+    <div>
+      <span>Count: {count()}</span> {/* Updates when `count` changes */}
+      <button onClick={increment}>Increment</button>
+    </div>
+  );
+}
+```
+
+:::
diff --git a/src/routes/reactivity/stores.mdx b/src/routes/reactivity/stores.mdx
index eb8a33bb3..c8c7e9151 100644
--- a/src/routes/reactivity/stores.mdx
+++ b/src/routes/reactivity/stores.mdx
@@ -1,4 +1,4 @@
 ---
-title: "Stores"
+title: "Reactive State Management"
 order: 5
 ---

From 2d97093fd73772078875c2d83ed0ce3c64ca2f3f Mon Sep 17 00:00:00 2001
From: LadyBluenotes <gerrardsarah@gmail.com>
Date: Thu, 28 Aug 2025 13:20:58 -0700
Subject: [PATCH 05/37] focused signals page

---
 old pages/concepts/signals.mdx | 54 +++++++++++++++++++---------------
 1 file changed, 30 insertions(+), 24 deletions(-)

diff --git a/old pages/concepts/signals.mdx b/old pages/concepts/signals.mdx
index aa59b6515..71662e63a 100644
--- a/old pages/concepts/signals.mdx	
+++ b/old pages/concepts/signals.mdx	
@@ -3,39 +3,45 @@ title: Signals
 order: 2
 ---
 
-Signals are the primary means of [managing state](/concepts/intro-to-reactivity#state-management) in your Solid application.
-They provide a way to store and update values, and are the foundation of [reactivity](/concepts/intro-to-reactivity) in Solid.
+Signals are the **core primitive for state** in Solid.
+They provide a way to store a value, read it, and update it.
+When a signal changes, anything that depends on it will update automatically.
 
-Signals can be used to represent any kind of state in your application, such as the current user, the current page, or the current theme.
-This can be any value, including primitive values such as strings and numbers, or complex values such as objects and arrays.
+Signals can represent any kind of state in your application:  
+- simple values like numbers or strings  
+- complex values like objects or arrays  
+- application state such as the current user, theme, or page
+
+For an overview of how signals fit into Solid’s reactive model, see [Reactivity Basics](/reactivity/basics).
 
 ## Creating a signal
 
-You can create a signal by calling the [`createSignal`](/reference/basic-reactivity/create-signal) function, which is imported from `solid-js`.
-This function takes an initial value as an argument, and returns a pair of functions: a **getter** function, and a **setter** function.
+Use [`createSignal`](/reference/basic-reactivity/create-signal) from `solid-js` to create a signal.  
+It returns a pair of functions:  
+- a **getter** to read the value  
+- a **setter** to update the value  
 
 ```jsx
 import { createSignal } from "solid-js";
 
 const [count, setCount] = createSignal(0);
-//       ^ getter  ^ setter
+//       ^ getter   ^ setter
 ```
 
-    	:::note
-    	  The syntax using `[` and `]` is called [array destructuring](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment).
+:::note
+The syntax using `[` and `]` is called [array destructuring](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment).
 
 This lets you extract values from the array.
 In the context of `createSignal`, the first value is the getter function, and the second value is the setter function.
-
 :::
 
 ## Accessing values
 
 The getter function returned by `createSignal` is used to access the value of the signal.
-You call this function with no arguments to get the current value of the signal:
+Call the getter function with no arguments to read the current value:
 
 ```jsx
-console.log(count()); // output: 0
+console.log(count()); // 0
 ```
 
 ## Updating values
@@ -46,7 +52,7 @@ This function takes an argument that represents the new value of the signal:
 ```jsx
 setCount(count() + 1);
 
-console.log(count()); // output: 1
+console.log(count()); // 1
 ```
 
 The setter function can also take a function that passes the previous value.
@@ -54,14 +60,13 @@ The setter function can also take a function that passes the previous value.
 ```jsx
 setCount((prevCount) => prevCount + 1);
 
-console.log(count()); // output: 1
+console.log(count()); // 1
 ```
 
 ## Reactivity
 
-Signals are reactive, which means that they automatically update when their value changes.
-When a signal is called within a [tracking scope](/concepts/intro-to-reactivity#tracking-changes), the signal adds the dependency to a list of subscribers.
-Once a signal's value changes, it notifies all of its dependencies of the change so they can re-evaluate their values and update accordingly.
+Signals are **reactive**, which means that they automatically update when their value changes.
+For example, using a signal inside JSX automatically makes the DOM update when the signal changes:
 
 ```jsx
 function Counter() {
@@ -79,12 +84,13 @@ function Counter() {
 }
 ```
 
-:::note
-A tracking scope can be created by [`createEffect`](/reference/basic-reactivity/create-effect)  or [`createMemo`](/reference/basic-reactivity/create-memo), which are other Solid primitives.
-
-Both functions subscribe to the signals accessed within them, establishing a dependency relationship.
-Once this relationship is established, the function is notified whenever the signal changes.
+To learn how signals connect to effects and tracking scopes, see:
+- [Reactive Side Effects](/reactivity/effects)
+- [Memoized Computations](/reactivity/memo)
 
-:::
+## Related Pages
 
-To learn more about how to use Signals in your application, visit our [state management guide](/guides/state-management).
+- [Reactivity Basics](/reactivity/basics)
+- [Reactive Side Effects](/reactivity/effects)
+- [Memoized Computations](/reactivity/memo)
+- [Introduction to Components](/components/intro)

From ce0da5c9650edbb7e8fa4cda742ad4bbbc98d994 Mon Sep 17 00:00:00 2001
From: LadyBluenotes <gerrardsarah@gmail.com>
Date: Thu, 28 Aug 2025 14:01:30 -0700
Subject: [PATCH 06/37] understanding JSX page

---
 src/routes/components/data.json               |   2 +-
 src/routes/components/how-to/data.json        |   4 +
 .../components/how-to/event-listeners.mdx     |   4 +
 src/routes/components/how-to/styling.mdx      |   4 +
 src/routes/getting-started/counter.mdx        |  12 --
 .../getting-started/understanding-jsx.mdx     | 149 ++++++++++++++++++
 6 files changed, 162 insertions(+), 13 deletions(-)
 create mode 100644 src/routes/components/how-to/data.json
 create mode 100644 src/routes/components/how-to/event-listeners.mdx
 create mode 100644 src/routes/components/how-to/styling.mdx
 delete mode 100644 src/routes/getting-started/counter.mdx
 create mode 100644 src/routes/getting-started/understanding-jsx.mdx

diff --git a/src/routes/components/data.json b/src/routes/components/data.json
index 12b3976db..d4bf1d89b 100644
--- a/src/routes/components/data.json
+++ b/src/routes/components/data.json
@@ -1,4 +1,4 @@
 {
 	"title": "Components",
-	"pages": ["intro.md"]
+	"pages": ["intro.md", "how-to"]
 }
diff --git a/src/routes/components/how-to/data.json b/src/routes/components/how-to/data.json
new file mode 100644
index 000000000..994008934
--- /dev/null
+++ b/src/routes/components/how-to/data.json
@@ -0,0 +1,4 @@
+{
+	"title": "How-to",
+	"pages": ["event-listeners.mdx", "styling.mdx"]
+}
diff --git a/src/routes/components/how-to/event-listeners.mdx b/src/routes/components/how-to/event-listeners.mdx
new file mode 100644
index 000000000..db41d97a4
--- /dev/null
+++ b/src/routes/components/how-to/event-listeners.mdx
@@ -0,0 +1,4 @@
+---
+title: "Using Event Listeners"
+---
+
diff --git a/src/routes/components/how-to/styling.mdx b/src/routes/components/how-to/styling.mdx
new file mode 100644
index 000000000..0953ba88e
--- /dev/null
+++ b/src/routes/components/how-to/styling.mdx
@@ -0,0 +1,4 @@
+---
+title: "Styling Components"
+---
+
diff --git a/src/routes/getting-started/counter.mdx b/src/routes/getting-started/counter.mdx
deleted file mode 100644
index ee8d28182..000000000
--- a/src/routes/getting-started/counter.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Counter Tutorial"
-order: 2
----
-
-[TODO]
-
-1. Open your newly scaffolded project in your code editor of choice.
-2. Create a new file called `Counter.jsx` in the `src/components` directory.
-3. In `Counter.tsx`, use Solid's `createSignal` to create a reactive counter state.
-4. Export the `Counter` component and import it into your main application file (e.g., `src/App.jsx`).
-5. Use the `Counter` component in your application and test its functionality.
\ No newline at end of file
diff --git a/src/routes/getting-started/understanding-jsx.mdx b/src/routes/getting-started/understanding-jsx.mdx
new file mode 100644
index 000000000..0d0031d3f
--- /dev/null
+++ b/src/routes/getting-started/understanding-jsx.mdx
@@ -0,0 +1,149 @@
+---
+title: "Understanding JSX"
+order: 2
+---
+
+Solid's JSX is a JavaScript extension that lets you write **HTML-like syntax inside JavaScript**.  
+It keeps your rendering logic and markup together, making components easier to read and maintain.
+
+## How Solid uses JSX
+
+Solid was designed to align closely with HTML standards.
+
+```tsx
+const element = <h1>I'm JSX!!</h1>
+```
+
+Unlike some other frameworks, Solid compiles JSX directly to real DOM nodes.
+This means:
+- JSX expressions map closely to HTML.
+- You can use variables and functions inline using curly braces `{}`.
+- Only the parts of the DOM that depend on reactive state update.
+This avoids the whole component re-rendering, improving performance.
+
+```tsx
+const component = () => {
+    const animal = { breed: "cat", name: "Midnight" }
+
+    return (
+        <p>
+           I have a {animal.breed} named {animal.name}.
+        </p>
+    )
+}
+```
+
+## Solid's JSX Rules
+
+### 1. Return a Single Root Element
+
+Each component must return a single root element.
+Since JSX maintains the familiar tree-like structure of HTML, having a single root element helps keep the hierarchy clear.
+If you need multiple top-level elements, wrap them in a `<div>`, `<section>`, or use a fragment `<>...</>`.
+
+```tsx
+function App() {
+    return (
+        <div>
+            <h1>Hello World!</h1>
+            <p>Welcome to JSX in Solid.</p>
+        </div>
+    )
+}
+```
+
+```advanced
+JSX in Solid compiles into structured HTML.
+Static elements are optimized once, while dynamic ones get special markers so Solid can update them efficiently.
+Requiring a single root element keeps the hierarchy consistent and easier to update.
+```
+
+
+### 2. Close All Tags
+
+All tags must be properly closed.
+This includes self-closing tags like `<img />`, `<input />`, and `<br />`.
+
+```tsx
+// Correct
+<img src="image.jpg" alt="Description" />
+
+// Incorrect
+<img src="image.jpg" alt="Description">
+```
+
+### 3. Properties vs Attributes
+
+In Solid's JSX, you can use both HTML attributes and JSX properties (props) to define element behavior and appearance.
+
+#### HTML attributes
+
+Solid's JSX blends HTML attributes with JavaScript expressions.
+
+- **HTML attributes** → work similar to regular HTML, but you can use JavaScript expressions inside curly braces `{}`.
+- **Event listeners** → Solid's JSX allows you to add event listeners using camelCase (e.g., `onClick`, `onChange`) or all lowercase (e.g., `onclick`, `onchange`).
+- **Inline styles** → You can apply styles directly using the `style` attribute with a JavaScript object.
+
+```tsx
+<button class="myClass" onClick={handleClick}>
+  Click me!
+</button>
+
+<button style={{ color: "red", fontSize: "2rem" }}>
+  Styled Button
+</button>
+```
+
+You can also use JavaScript expressions to set attribute values dynamically:
+
+```tsx
+const isActive = true;
+
+<button class={isActive ? "active" : "inactive"}>
+  Click me!
+</button>
+```
+
+For more information on:
+- [Using Event Listeners](/components/how-to/event-listeners)
+- [Styling Components](/components/how-to/styling)
+
+#### JSX Properties (Props)
+
+JSX properties (or props) are how you pass data and event handlers to components in Solid.
+They work similarly to HTML attributes but can accept JavaScript expressions.
+
+In this example, the `name` prop is passed to the `Greeting` component, which uses it within its JSX:
+
+```tsx
+function App() {
+    return (
+        <div>
+            <Greeting name="Alice" />
+            <Greeting name="Bob" />
+        </div>
+    );
+}
+
+function Greeting(props) {
+    return <h1>Hello, {props.name}!</h1>;
+}
+```
+
+The core concepts of JSX properties in Solid include:
+- **Static props**: Directly integrated into the HTML by cloning the template and using them as attributes.
+- **Dynamic props**: Rely on state, allowing content or properties to change in response to user interactions or other events.
+An example is changing the style of an element based on a signal (`value={value()}`).
+- **Data transfer**: Props can be used to fill components with data from resources, such as API responses or context providers.
+This allows for components to update reactively when the underlying data changes.
+
+:::note
+In JSX, expressions are applied in the order they appear.
+This works for most elements, but some (i.e. `<input type="range" />`) require attributes in a specific order.
+When order matters, make sure to define expressions in the sequence the element expects.
+:::
+
+## Related Pages
+- [Using Event Listeners](/components/how-to/event-listeners)
+- [Styling Components](/components/how-to/styling)
+- [Passing Data with Props](/components/props)

From a96251c0d92d7883ecaed802cc4b578187ee6ab4 Mon Sep 17 00:00:00 2001
From: LadyBluenotes <gerrardsarah@gmail.com>
Date: Fri, 29 Aug 2025 20:38:41 -0700
Subject: [PATCH 07/37] new files

---
 old pages/concepts/intro-to-reactivity.mdx | 248 ---------------------
 old pages/concepts/signals.mdx             |  96 --------
 old pages/concepts/understanding-jsx.mdx   | 129 -----------
 old pages/quick-start.mdx                  |  80 -------
 src/routes/components/data.json            |   2 +-
 src/routes/getting-started/data.json       |   2 +-
 6 files changed, 2 insertions(+), 555 deletions(-)
 delete mode 100644 old pages/concepts/intro-to-reactivity.mdx
 delete mode 100644 old pages/concepts/signals.mdx
 delete mode 100644 old pages/concepts/understanding-jsx.mdx
 delete mode 100644 old pages/quick-start.mdx

diff --git a/old pages/concepts/intro-to-reactivity.mdx b/old pages/concepts/intro-to-reactivity.mdx
deleted file mode 100644
index 5b885169d..000000000
--- a/old pages/concepts/intro-to-reactivity.mdx	
+++ /dev/null
@@ -1,248 +0,0 @@
----
-title: "Intro to reactivity"
-order: 1
----
-
-**Note**: While this guide is useful for understanding reactive systems, it does use some Solid-specific terminology.
-
-Reactivity powers the interactivity in Solid applications.
-This programming paradigm refers to a system's ability to respond to changes in data or state automatically.
-With Solid, reactivity is the basis of its design, ensuring applications stay up-to-date with their underlying data.
-
-## Importance of reactivity
-
-1. Reactivity keeps the user interface (UI) and state in sync, which reduces the need for manual updates.
-
-2. Real-time updates create a more responsive and interactive user experience.
-
-```jsx
-function Counter() {
-	const [count, setCount] = createSignal(0);
-	const increment = () => setCount((prev) => prev + 1);
-
-	return (
-		<div>
-			<span>Count: {count()}</span>{" "}
-			{/* Only `count()` is updated when the button is clicked. */}
-			<button type="button" onClick={increment}>
-				Increment
-			</button>
-		</div>
-	);
-}
-```
-
-This `Counter` function sets up a button that, when clicked, calls the `increment` function to increase the `count` by one.
-This updates just the number displayed _without_ refreshing the entire component.
-
-<EraserLink
-	href="https://app.eraser.io/workspace/maDvFw5OryuPJOwSLyK9?elements=cry9JT4nroFQ4rRxzOpvCg"
-	preview="https://app.eraser.io/workspace/maDvFw5OryuPJOwSLyK9/preview?elements=cry9JT4nroFQ4rRxzOpvCg&type=embed"
-/>
-
-## Reactive principles
-
-### Signals
-
-Signals serve as core elements in reactive systems, playing an important role in data management and system responsiveness.
-They are responsible for storing and managing data, as well as triggering updates across the system.
-This is done through the use of getters and setters.
-
-```jsx
-const [count, setCount] = createSignal(0);
-//     ^ getter  ^ setter
-```
-
-<EraserLink
-	href="https://app.eraser.io/workspace/maDvFw5OryuPJOwSLyK9?elements=lseAEjGlKLslaVsTlfej_g"
-	preview="https://app.eraser.io/workspace/maDvFw5OryuPJOwSLyK9/preview?elements=lseAEjGlKLslaVsTlfej_g&type=embed"
-/>
-
-- **Getter**: A function responsible for accessing the current value of the signal.
-  You call a getter to access the data stored in a signal within a component.
-
-- **Setter**:
-  The function used to modify a signal's value.
-  To trigger reactive updates across an application, you call a setter to update the value of a signal.
-
-```js
-console.log(count()); // `count()` is a getter that returns the current value of `count`, which is `0`.
-
-setCount(1); // the setter, `setCount`, updates the value of `count`.
-
-console.log(count()); // the updated value of `count` is now `1`.
-```
-
-### Subscribers
-
-Subscribers are the other core element in reactive systems.
-They are responsible for tracking changes in signals and updating the system accordingly.
-They are automated responders that keep the system up-to-date with the latest data changes.
-
-Subscribers work based on two main actions:
-
-- **Observation**: At their core, subscribers observe signals.
-  This keeps the subscriber primed to pick up on any changes to the signal they are tracking.
-- **Response**: When a signal changes, the subscriber is notified.
-  This triggers the subscriber to respond to the change in the signal.
-  This can involve tasks like updating the UI or calling external functions.
-
-```jsx
-function Counter() {
-	const [count, setCount] = createSignal(0);
-	const increment = () => setCount((prev) => prev + 1);
-
-	createEffect(() => {
-		console.log(count());
-	});
-	// the `createEffect` will trigger the console log every time `count` changes.
-}
-```
-
-## State management
-
-State management is the process of managing the state of an application.
-This involves storing and updating data, as well as responding to the changes in it.
-
-With Solid, state management is handled through signals and subscribers.
-Signals are used to store and update data, while subscribers are used to respond to changes in the data.
-
-### Tracking changes
-
-Tracking changes involves monitoring any updates to the data and responding accordingly.
-This is done through the use of subscribers.
-
-When a signal is not accessed within a tracking scope, an update to the signal will not trigger an update.
-This happens because if a signal is not being tracked, it is not able to notify any subscribers of the change.
-
-```jsx
-const [count, setCount] = createSignal(0);
-
-console.log("Count:", count());
-
-setCount(1);
-
-// Output: Count: 0
-
-// `count` is not being tracked, so the console log will not update when `count` changes.
-```
-
-Since initialization is a **one-time event**, if a signal is accessed _outside of a tracking scope_, it will not be tracked.
-To track a signal, it must be accessed within the scope of a subscriber.
-Reactive primitives, such as [effects](/concepts/effects), can be used to create subscribers.
-
-```jsx
-const [count, setCount] = createSignal(0);
-
-createEffect(() => {
-	console.log("Count:", count());
-});
-
-setCount(1);
-
-// Output: Count: 0
-//         Count: 1
-```
-
-### Updating the UI
-
-The UI of a Solid application is built using [JSX](/concepts/understanding-jsx).
-JSX creates a tracking scope behind the scenes, which allows signals to be tracked within the return statement of a component.
-
-```jsx
-function Counter() {
-	const [count, setCount] = createSignal(0);
-	const increment = () => setCount((prev) => prev + 1);
-
-	return (
-		<div>
-			<span>Count: {count()}</span>{" "}
-			{/* ✅ will update when `count()` changes. */}
-			<button type="button" onClick={increment}>
-				Increment
-			</button>
-		</div>
-	);
-}
-```
-
-Components, much like other functions, will only run _once_.
-This means that if a signal is accessed outside of the return statement, it will run on initialization, but any updates to the signal will not trigger an update.
-
-```jsx
-function Counter() {
-	const [count, setCount] = createSignal(0);
-	const increment = () => setCount((prev) => prev + 1);
-
-	console.log("Count:", count()); // ❌ not tracked - only runs once during initialization.
-
-	createEffect(() => {
-		console.log(count()); // ✅ will update whenever `count()` changes.
-	});
-
-	return (
-		<div>
-			<span>Count: {count()}</span>{/* ✅ will update whenever `count()` changes. */}
-			<button type="button" onClick={increment}>
-				Increment
-			</button>
-		</div>
-	);
-}
-```
-
-To learn more about managing state in Solid, visit the [guide on state management](/guides/state-management).
-
-## Synchronous vs. asynchronous
-
-Reactive systems are designed to respond to changes in data.
-These responses can be immediate or delayed, depending on the nature of the system.
-Often, the choice between these two depends on the requirements of the application and the nature of the tasks involved.
-
-### Synchronous reactivity
-
-[Synchronous](https://developer.mozilla.org/en-US/docs/Glossary/Synchronous) reactivity is Solid's default reactivity mode, where a system responds to changes in a direct and linear fashion.
-When a signal changes, any corresponding subscribers are immediately updated in an ordered manner.
-
-With synchronous reactivity, the system is able to respond to changes in a predictable manner.
-This is useful in scenarios where the order of updates is important.
-For example, if a subscriber depends on another signal, it is important that the subscriber is updated after the signal it depends on.
-
-```jsx
-const [count, setCount] = createSignal(0);
-const [double, setDouble] = createSignal(0);
-
-createEffect(() => {
-	setDouble(count() * 2);
-});
-```
-
-In this example, the `double` signal will always be updated after `count` due to synchronous reactivity.
-This ensures that `double` is always up-to-date with the latest value of `count`.
-
-### Asynchronous reactivity
-
-[Asynchronous](https://developer.mozilla.org/en-US/docs/Glossary/Asynchronous) reactivity is when a system responds to changes in a delayed or non-linear fashion.
-When a signal changes, the corresponding subscribers are not immediately updated.
-Instead, the system waits for a specific event or task to complete before updating the subscribers.
-
-This is important in scenarios where subscribers depend on multiple signals.
-In these cases, updating one signal before another could result in data inconsistency.
-For example, if a subscriber depends on two signals, it is important that the subscriber is updated after both signals have been updated.
-Rather, the system waits for both signals to be updated before updating the subscriber.
-
-**Note:** When asynchronous reactivity is present, it is important to ensure that the system is able to handle the delay in updates.
-[`batch`](/reference/reactive-utilities/batch) can be used to delay an update so the subscriber runs after each signal has been updated.
-
-## Key concepts
-
-- Signals are the core elements of a reactive system.
-  They are responsible for storing and managing data.
-- Signals are both readable and writeable because of getters and setters.
-- Subscribers are automated responders that track changes in signals and update the system accordingly.
-- Signals and subscribers work together to ensure that the system is kept up-to-date with the latest data changes.
-- A reactive system is built on the principles of data-driven reactivity.
-  This means that the system's reactivity is driven by the data it is built on.
-- Reactive systems can be synchronous or asynchronous.
-
-If you want to dive deeper, visit the [guide on fine-grained reactivity](/advanced-concepts/fine-grained-reactivity).
diff --git a/old pages/concepts/signals.mdx b/old pages/concepts/signals.mdx
deleted file mode 100644
index 71662e63a..000000000
--- a/old pages/concepts/signals.mdx	
+++ /dev/null
@@ -1,96 +0,0 @@
----
-title: Signals
-order: 2
----
-
-Signals are the **core primitive for state** in Solid.
-They provide a way to store a value, read it, and update it.
-When a signal changes, anything that depends on it will update automatically.
-
-Signals can represent any kind of state in your application:  
-- simple values like numbers or strings  
-- complex values like objects or arrays  
-- application state such as the current user, theme, or page
-
-For an overview of how signals fit into Solid’s reactive model, see [Reactivity Basics](/reactivity/basics).
-
-## Creating a signal
-
-Use [`createSignal`](/reference/basic-reactivity/create-signal) from `solid-js` to create a signal.  
-It returns a pair of functions:  
-- a **getter** to read the value  
-- a **setter** to update the value  
-
-```jsx
-import { createSignal } from "solid-js";
-
-const [count, setCount] = createSignal(0);
-//       ^ getter   ^ setter
-```
-
-:::note
-The syntax using `[` and `]` is called [array destructuring](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment).
-
-This lets you extract values from the array.
-In the context of `createSignal`, the first value is the getter function, and the second value is the setter function.
-:::
-
-## Accessing values
-
-The getter function returned by `createSignal` is used to access the value of the signal.
-Call the getter function with no arguments to read the current value:
-
-```jsx
-console.log(count()); // 0
-```
-
-## Updating values
-
-The setter function returned by `createSignal` is used to update the value of the signal.
-This function takes an argument that represents the new value of the signal:
-
-```jsx
-setCount(count() + 1);
-
-console.log(count()); // 1
-```
-
-The setter function can also take a function that passes the previous value.
-
-```jsx
-setCount((prevCount) => prevCount + 1);
-
-console.log(count()); // 1
-```
-
-## Reactivity
-
-Signals are **reactive**, which means that they automatically update when their value changes.
-For example, using a signal inside JSX automatically makes the DOM update when the signal changes:
-
-```jsx
-function Counter() {
-	const [count, setCount] = createSignal(0);
-	const increment = () => setCount((prev) => prev + 1);
-
-	return (
-		<div>
-			<span>Count: {count()}</span> {/* Updates when `count` changes */}
-			<button type="button" onClick={increment}>
-				Increment
-			</button>
-		</div>
-	);
-}
-```
-
-To learn how signals connect to effects and tracking scopes, see:
-- [Reactive Side Effects](/reactivity/effects)
-- [Memoized Computations](/reactivity/memo)
-
-## Related Pages
-
-- [Reactivity Basics](/reactivity/basics)
-- [Reactive Side Effects](/reactivity/effects)
-- [Memoized Computations](/reactivity/memo)
-- [Introduction to Components](/components/intro)
diff --git a/old pages/concepts/understanding-jsx.mdx b/old pages/concepts/understanding-jsx.mdx
deleted file mode 100644
index 8dea79978..000000000
--- a/old pages/concepts/understanding-jsx.mdx	
+++ /dev/null
@@ -1,129 +0,0 @@
----
-title: Understanding JSX
-order: 2
----
-
-JSX is an extension for JavaScript.
-It allows you to write HTML-like code inside your JavaScript file which keeps your rendering logic and content in the same place.
-This provides a concise and readable way to create and represent components.
-
-## How Solid uses JSX
-
-Solid was designed to align closely with HTML standards.
-
-```jsx
-const element = <h1>I'm JSX!!</h1>
-```
-
-It offers a distinct advantage, however: to copy/paste solutions from resources like Stack Overflow; and to allow direct usage of templates from design tools.
-Solid sets itself apart by using JSX immediately as it returns [DOM](https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model/Introduction) elements.
-This lets you use dynamic expressions within your HTML by allowing variables and functions to be references with the use of curly braces (`{ }`):
-
-```jsx
-const Component = () => {
-	const animal = { breed: "cat", name: "Midnight" }
-
-	return (
-		<p>
-			I have a {animal.breed} named {animal.name}!
-		</p>
-	)
-}
-```
-
-This means JavaScript content can be rendered on web pages based on an application's state or logic.
-
-Additionally, Solid's [reactive](/concepts/intro-to-reactivity) system introduces [fine-grained reactivity](/advanced-concepts/fine-grained-reactivity) with JSX.
-This updates only the necessary parts of the DOM when changes occur in the underlying state.
-
-## Using JSX in Solid
-
-### Return a single root element
-
-Where HTML lets you have disconnected tags at the top level, JSX requires that a component to return a single root element.
-
-:::advanced
-When working with JSX, parts of your code are translated into structured HTML that is placed at the start of the file.
-Static elements are processed differently from dynamic ones, which might change based on data or user actions.
-For dynamic elements, special markers are added for better handling during rendering.
-
-Having a single root creates a consistent and manageable hierarchy to optimize rendering and updates.
-:::
-
-JSX maintains the familiar nested, tree-like structure found in HTML.
-As a result, parent-child relationships between elements become easier to follow.
-
-### Close all tags
-
-Self-closing tags are a must in JSX.
-Unlike in HTML, where elements like `<input>`, `<img>`, or `<br>` don't require explicit closure, JSX requires consistent self-closing tags.
-This helps to avoid potential rendering issues.
-
-```jsx
-<img src="./image-here.png" />
-```
-
-### Properties vs. attributes
-
-HTML attributes and JSX properties may seem similar, but they serve different purposes and behave differently.
-Both offer ways to specify configurations or pass information.
-However, HTML is used for standard web content and JSX creates Solid's component logic.
-
-#### HTML attributes
-
-[HTML attributes](https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes) are values set directly on HTML elements.
-They provide additional information about an element to guide its initial behavior and state.
-These attributes are often translated into properties on DOM objects once the browser parses the HTML.
-
-In JSX files, HTML attributes are used much like regular HTML, with a few key differences due to the blend of HTML and JavaScript:
-
-- Event listeners such as `onClick` can be in camelCase or lowercase.
-  (**Note:** When using ESLint, you will get a warning if you use lowercase.)
-- In cases where you can dynamically specify a value, you can replace the `"` and `"` with curly braces (`{ }`):
-
-```jsx
-<button class="myClass" onClick={handleClick}>
-	Click me!
-</button>
-```
-
-    	:::note
-    	  If you wish to pass objects in JSX, such as with inline styling, you will have to use double curly braces (`{{ }}`).
-
-```jsx
-<button style={{
-	color: 'red',
-	font-size: '2rem',
-	}}>
-  Click me!
-</button>
-```
-:::
-
-### JSX properties (props)
-
-JSX properties, commonly known as "props," help with the passing of data and configurations to components within an application.
-They connect the component with the data it requires, for seamless data flows and dynamic interactions.
-
-#### Core concepts
-
-- **Static props**:
-  In Solid's JSX, static props are integrated directly into the HTML by cloning the template and using them as attributes.
-
- - **Dynamic props**:
- Dynamic props rely on state, allowing the content or properties to be dynamic.
- An example is changing the style of an element in response to interactions within an application.
- This can be expressed in the form of signals (`value={value()}`).
-
-- **Data transfer**:
-  Props are also used to fill components with data that comes from resources, like [`createResource`](/reference/basic-reactivity/create-resource) calls.
-  This results in components that react in real-time to data changes.
-
-:::note
-Expressions, whether fixed or dynamic, get applied *in the order defined within the JSX*.
-This works for a wide range of DOM elements, but will not work with elements that require attributes to be defined in a special order, such as input types with `type='range'`.
-
-When order influences an element's behavior, users must define the expressions in the order that the element is expected.
-:::
-
-For how to use props effectively in Solid, explore the [props page](/concepts/components/props).
diff --git a/old pages/quick-start.mdx b/old pages/quick-start.mdx
deleted file mode 100644
index c04a9c7b5..000000000
--- a/old pages/quick-start.mdx	
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: Quick start
----
-
-## Try Solid online
-
-To experiment with Solid directly in your browser, head over to our [interactive playground](https://playground.solidjs.com/).
-Prefer a full development setup? You can set up a complete environment using StackBlitz.
-Start with the [TypeScript](https://stackblitz.com/github/solidjs/templates/tree/master/ts) or [JavaScript](https://stackblitz.com/github/solidjs/templates/tree/master/js) templates.
-
-## Create a Solid project
-
-:::note[Prerequisites]
-
-- Familiarity with the command line.
-- A recent version of [Node.js](https://nodejs.org/en), [Bun](https://bun.sh/), or [Deno](https://deno.com/).
-  The latest LTS version is recommended.
-
-:::
-
-To create a new Solid application, navigate to the directory where you want to create your project and run the following command:
-
-```package-create
-solid
-```
-
-This command installs and runs [create-solid](https://github.com/solidjs-community/solid-cli/tree/main/packages/create-solid), the official project scaffolding tool for Solid.
-The CLI will guide you through a series of prompts, allowing you to choose options such as [starter templates](https://github.com/solidjs/templates), TypeScript support, and whether to include [Solid's full-stack framework, SolidStart](/solid-start):
-
-```shell
-◆ Project Name
-|  <solid-project>
-
-◆ Is this a SolidStart project?
-|  ● Yes / ○ No
-
-◆ Which template would you like to use?
-│  ● ts
-│  ○ ts-vitest
-│  ○ ts-uvu
-│  ○ ts-unocss
-│  ○ ts-tailwindcss
-
-◆ Use TypeScript?
-│  ● Yes / ○ No
-```
-
-Once the project is created, follow the instructions to install the dependencies and start the development server:
-
-```sh title="npm" tab="package-manager"
-│  cd solid-project
-│  npm install
-│  npm run dev
-```
-
-```sh title="pnpm" tab="package-manager"
-│  cd solid-project
-│  pnpm install
-│  pnpm dev
-```
-
-```sh title="yarn" tab="package-manager"
-│  cd solid-project
-│  yarn install
-│  yarn dev
-```
-
-```sh title="bun" tab="package-manager"
-│  cd solid-project
-│  bun install
-│  bun run dev
-```
-
-```sh title="deno" tab="package-manager"
-│  cd solid-project
-│  deno install
-│  deno run dev
-```
-
-You should now have your Solid project running!
diff --git a/src/routes/components/data.json b/src/routes/components/data.json
index d4bf1d89b..7c6ff1f78 100644
--- a/src/routes/components/data.json
+++ b/src/routes/components/data.json
@@ -1,4 +1,4 @@
 {
 	"title": "Components",
-	"pages": ["intro.md", "how-to"]
+	"pages": ["intro.mdx", "how-to"]
 }
diff --git a/src/routes/getting-started/data.json b/src/routes/getting-started/data.json
index 4b2a8a548..5790f74ec 100644
--- a/src/routes/getting-started/data.json
+++ b/src/routes/getting-started/data.json
@@ -1,4 +1,4 @@
 {
 	"title": "Getting Started",
-	"pages": ["quick-start.mdx", "counter.mdx", "todo.mdx"]
+	"pages": ["quick-start.mdx", "understanding-jsx.mdx", "todo.mdx"]
 }

From ca815ce7ba567b54edc1d1477542cfac61f3b904 Mon Sep 17 00:00:00 2001
From: LadyBluenotes <gerrardsarah@gmail.com>
Date: Sat, 30 Aug 2025 20:59:22 -0700
Subject: [PATCH 08/37] workign on new pages

---
 src/routes/components/basics.mdx | 110 +++++++++++++++++++++++++++++++
 src/routes/components/props.mdx  |   4 ++
 2 files changed, 114 insertions(+)
 create mode 100644 src/routes/components/basics.mdx
 create mode 100644 src/routes/components/props.mdx

diff --git a/src/routes/components/basics.mdx b/src/routes/components/basics.mdx
new file mode 100644
index 000000000..ee0d47f8b
--- /dev/null
+++ b/src/routes/components/basics.mdx
@@ -0,0 +1,110 @@
+---
+title: "Basics of Components"
+order: 1
+---
+
+Components are the **fundamental building blocks** of Solid applications.  
+A component is a **JavaScript function that returns JSX**.
+This allows you to create encapsulated pieces of UI that can manage their own state and behavior.
+
+## Your First Component
+
+A component starts as a plain JavaScript function, defined by either a function declaration or an arrow function:
+
+```tsx
+// Greeting.jsx
+export function Greeting() {
+  return <div>Hello, Solid!</div>;
+}
+
+export const Greeting = () => {
+  return <div>Hello, Solid!</div>;
+};
+```
+
+These functions can be used in other components by importing them and using their names like HTML tags:
+
+```tsx
+// App.tsx
+import { Greeting } from './Greeting';
+
+function App() {
+  return (
+    <div>
+      <Greeting />
+    </div>
+  );
+}
+```
+
+### Passing Props
+
+Props, short for properties, let you pass data from a parent component to a child component.
+They are passed as attributes on the component tag and received as an object in the component function.
+
+```tsx
+//Greeting.tsx
+export function Greeting(props) {
+  return <div>Hello, {props.name}!</div>;
+}
+
+// App.tsx
+import { Greeting } from './Greeting';
+
+function App() {
+  return (
+    <div>
+      <Greeting name="Solid" />
+    </div>
+  );
+}
+```
+
+To learn more about props, see the next section: [Passing Data with Props](/components/props).
+
+### Composing Components
+
+Components can be composed together to build more complex UIs. 
+You can use one component inside another, passing props as needed.
+
+```tsx
+// App.tsx
+import { Greeting } from './Greeting';
+
+function App() {
+  return (
+    <div>
+      <Greeting name="Solid" />
+      <Greeting name="World" />
+    </div>
+  );
+}
+```
+
+## Component lifecycles
+
+Components in Solid have a lifecycle that includes mounting, updating, and unmounting phases.
+
+1. **Mounting**: When the component is being created and inserted into the DOM. 
+It occurs once in the component's lifecycle.
+2. **Updating**: The component's state or props change, causing it to re-render. Solid optimizes updates to ensure minimal re-rendering.
+3. **Unmounting**: The component is removed from the DOM. 
+Cleanup tasks, such as cancelling network requests or removing event listeners, should be performed here.
+
+There are certain lifecycle helpers available in Solid to manage these phases more easily, such as `onMount`, `onCleanup`, and `createEffect`.
+
+```tsx
+import { onMount, onCleanup } from "solid-js";
+
+function Timer() {
+  let interval;
+
+  onMount(() => {
+    interval = setInterval(() => console.log("tick"), 1000);
+  });
+
+  onCleanup(() => clearInterval(interval));
+
+  return <p>Timer running...</p>;
+}
+```
\ No newline at end of file
diff --git a/src/routes/components/props.mdx b/src/routes/components/props.mdx
new file mode 100644
index 000000000..63dcb64de
--- /dev/null
+++ b/src/routes/components/props.mdx
@@ -0,0 +1,4 @@
+---
+title: "Passing Data with Props"
+order: 2
+---
\ No newline at end of file

From daf1c5c591b72c98960f5526068ed03bff671137 Mon Sep 17 00:00:00 2001
From: Sarah <gerrardsarah@gmail.com>
Date: Wed, 3 Sep 2025 12:40:57 -0700
Subject: [PATCH 09/37] Update src/routes/getting-started/quick-start.mdx

Co-authored-by: Amir Hossein Hashemi <87268103+amirhhashemi@users.noreply.github.com>
---
 src/routes/getting-started/quick-start.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/routes/getting-started/quick-start.mdx b/src/routes/getting-started/quick-start.mdx
index 8c0038ce1..37cee243a 100644
--- a/src/routes/getting-started/quick-start.mdx
+++ b/src/routes/getting-started/quick-start.mdx
@@ -10,7 +10,7 @@ In just a few minutes, you’ll have a working Solid app running in your browser
 
 If you're looking to experiment with Solid without setting up a local environment, open the [Solid Playground](https://playground.solidjs.com/) in your browser.
 
-If you prefer a more complete development setup, you can use the StackBlitz [Javascript](https://stackblitz.com/github/solidjs/templates/tree/master/js) or [TypeScript](https://stackblitz.com/github/solidjs/templates/tree/master/ts) templates.
+If you prefer a more complete development setup, you can use the StackBlitz [JavaScript](https://stackblitz.com/github/solidjs/templates/tree/master/js) or [TypeScript](https://stackblitz.com/github/solidjs/templates/tree/master/ts) templates.
 
 ## Create a New Project
 

From a55927a2292bc326d629433aaebb2bf76fbabf47 Mon Sep 17 00:00:00 2001
From: Sarah <gerrardsarah@gmail.com>
Date: Wed, 3 Sep 2025 12:48:35 -0700
Subject: [PATCH 10/37] Apply suggestions from code review

Co-authored-by: Amir Hossein Hashemi <87268103+amirhhashemi@users.noreply.github.com>
---
 src/routes/getting-started/quick-start.mdx    | 20 ++++++++++---------
 .../getting-started/understanding-jsx.mdx     | 12 +++++++----
 src/routes/reactivity/basics.mdx              | 20 +++++++++++--------
 src/routes/reactivity/signals.mdx             |  9 +++------
 4 files changed, 34 insertions(+), 27 deletions(-)

diff --git a/src/routes/getting-started/quick-start.mdx b/src/routes/getting-started/quick-start.mdx
index 37cee243a..a77884414 100644
--- a/src/routes/getting-started/quick-start.mdx
+++ b/src/routes/getting-started/quick-start.mdx
@@ -6,7 +6,7 @@ order: 1
 The fastest way to try Solid is to create a new project and run it locally.
 In just a few minutes, you’ll have a working Solid app running in your browser.
 
-## Solid in your Browser
+## Solid in Your Browser
 
 If you're looking to experiment with Solid without setting up a local environment, open the [Solid Playground](https://playground.solidjs.com/) in your browser.
 
@@ -31,21 +31,23 @@ solid
 3. **Follow the CLI prompts** to select your project name, template (JavaScript or TypeScript), and other options.
 
 ```sh
-◆ Project Name
-|  <solid-project>
+◆  Project Name
+│  solid-project
 
-◆ Is this a SolidStart project?
-|  ● Yes / ○ No
+◆  What type of project would you like to create?
+│  ○ SolidStart
+│  ● SolidJS + Vite
+│  ○ Library
 
-◆ Which template would you like to use?
+◆  Use Typescript?
+│  ● Yes / ○ No
+
+◆  Which template would you like to use?
 │  ● ts
 │  ○ ts-vitest
 │  ○ ts-uvu
 │  ○ ts-unocss
 │  ○ ts-tailwindcss
-
-◆ Use TypeScript?
-│  ● Yes / ○ No
 ```
 
 4. **Follow the instructions to install the dependencies and start the development server:**
diff --git a/src/routes/getting-started/understanding-jsx.mdx b/src/routes/getting-started/understanding-jsx.mdx
index 0d0031d3f..4c16b32e7 100644
--- a/src/routes/getting-started/understanding-jsx.mdx
+++ b/src/routes/getting-started/understanding-jsx.mdx
@@ -16,10 +16,10 @@ const element = <h1>I'm JSX!!</h1>
 
 Unlike some other frameworks, Solid compiles JSX directly to real DOM nodes.
 This means:
+
 - JSX expressions map closely to HTML.
 - You can use variables and functions inline using curly braces `{}`.
 - Only the parts of the DOM that depend on reactive state update.
-This avoids the whole component re-rendering, improving performance.
 
 ```tsx
 const component = () => {
@@ -105,6 +105,7 @@ const isActive = true;
 ```
 
 For more information on:
+
 - [Using Event Listeners](/components/how-to/event-listeners)
 - [Styling Components](/components/how-to/styling)
 
@@ -131,10 +132,12 @@ function Greeting(props) {
 ```
 
 The core concepts of JSX properties in Solid include:
-- **Static props**: Directly integrated into the HTML by cloning the template and using them as attributes.
-- **Dynamic props**: Rely on state, allowing content or properties to change in response to user interactions or other events.
+
+- **Static props:** Directly integrated into the HTML by cloning the template and using them as attributes.
+- **Dynamic props:** Rely on state, allowing content or properties to change in response to user interactions or other events.
 An example is changing the style of an element based on a signal (`value={value()}`).
-- **Data transfer**: Props can be used to fill components with data from resources, such as API responses or context providers.
+- **Data transfer:** Props can be used to fill components with data from resources, such as API responses or context providers.
+
 This allows for components to update reactively when the underlying data changes.
 
 :::note
@@ -144,6 +147,7 @@ When order matters, make sure to define expressions in the sequence the element
 :::
 
 ## Related Pages
+
 - [Using Event Listeners](/components/how-to/event-listeners)
 - [Styling Components](/components/how-to/styling)
 - [Passing Data with Props](/components/props)
diff --git a/src/routes/reactivity/basics.mdx b/src/routes/reactivity/basics.mdx
index 17d223d9b..7c44d28ef 100644
--- a/src/routes/reactivity/basics.mdx
+++ b/src/routes/reactivity/basics.mdx
@@ -7,7 +7,8 @@ order: 1
 Reactivity is the foundation of Solid.  
 It’s the programming model where **changes in data automatically update the parts of your app that depend on it**.  
 
-Solid’s approach is **fine-grained**: instead of re-rendering entire components, only the exact parts of the DOM that depend on a value update. This makes applications efficient and responsive, even as they grow.
+Solid’s approach is **fine-grained**: only the exact parts of the DOM that depend on a value update.
+This makes applications efficient and responsive, even as they grow.
 
 ## Core Principles of Reactivity
 	
@@ -18,6 +19,7 @@ Together, these create a system where updates are precise, automatic, and effici
 
 A **signal** is a reactive value container.
 They consist of 2 parts:
+
 - **Getter** → reads the current value.  
 - **Setter** → updates the value and notifies dependents.  
 
@@ -30,9 +32,9 @@ console.log(count()); // 1
 ```
 
 Signals can hold any type of value:
-- primitives (string, number, boolean)
-- objects and arrays
-- application state (user, theme, current page)
+
+- Primitives (string, number, boolean).
+- Objects and arrays.
 
 Learn more in the [Signals page](/reactivity/signals).
 
@@ -41,9 +43,10 @@ Learn more in the [Signals page](/reactivity/signals).
 If signals are the **source of truth**, subscribers are the **reactive consumers**.
 
 A subscriber is any function or construct that reads a signal inside a tracking scope and automatically re-runs whenever it changes.
-This is what makes Solid’s reactivity *fine-grained*: only the subscribers that depend on a signal update, not the entire component.
+This is what makes Solid’s reactivity *fine-grained*: only the subscribers that depend on a signal update.
 
 How subscribers work:
+
 1. **Observation** → subscriber runs and reads signals.
 2. **Dependency tracking** → those signals register the subscriber.
 3. **Response** → when a signal changes, the subscriber re-runs.
@@ -55,8 +58,9 @@ When a signal is read within a tracking scope, it registers the current subscrib
 Once that signal changes, it will notify the subscriber to re-run and update accordingly.
 
 Tracking scopes within Solid include:
-- Component render functions (JSX return values)
-- Reactive computations (e.g., `createMemo`)
+
+- Component render functions (JSX return values).
+- Reactive computations (e.g., `createMemo`).
 - Effects (e.g., `createEffect`)
 
 Example of a tracking vs non-tracking scope:
@@ -78,7 +82,7 @@ function Counter() {
 }
 ```
 
-Tracking scopes are what enable **precise DOM updates**: only parts of the UI that depend on signals re-run, not the entire component.
+Tracking scopes are what enable **precise DOM updates**: only parts of the UI that depend on signals re-run.
 You can learn more about [component lifecycles in the Intro to Components page](/components/intro).
 
 
diff --git a/src/routes/reactivity/signals.mdx b/src/routes/reactivity/signals.mdx
index 6a5eab9d4..e19c1e3c3 100644
--- a/src/routes/reactivity/signals.mdx
+++ b/src/routes/reactivity/signals.mdx
@@ -13,11 +13,9 @@ You can use signals for any kind of state:
 
 ## What is a Signal?
 
-A **signal** is a reactive value container.  
-- It holds a value.  
-- It provides a **getter** to read the value.  
-- It provides a **setter** to update the value.  
-- When the value changes, any reactive computations that depend on it are updated automatically.  
+A **signal** is a reactive value container. 
+It holds a value and provides a **getter** to read the value and a **setter** to update it.
+When the value changes, it automatically triggers updates in any dependent computations.
 
 They can be thought of as a **reactive variable**.
 
@@ -73,4 +71,3 @@ function Counter() {
 }
 ```
 
-:::

From 0f5f21b683d8078006a8ee0e9c4b1c5e400c540a Mon Sep 17 00:00:00 2001
From: LadyBluenotes <gerrardsarah@gmail.com>
Date: Wed, 17 Sep 2025 11:21:31 -0700
Subject: [PATCH 11/37] effects

---
 src/routes/getting-started/data.json          |   2 +-
 .../{quick-start.mdx => installation.mdx}     |   2 +-
 src/routes/intro.mdx                          |   4 +-
 src/routes/reactivity/basics.mdx              |  10 +-
 src/routes/reactivity/data.json               |   2 +-
 .../{memos.mdx => derived-state.mdx}          |   2 +-
 src/routes/reactivity/effects.mdx             | 169 +++++++++++++++++-
 7 files changed, 172 insertions(+), 19 deletions(-)
 rename src/routes/getting-started/{quick-start.mdx => installation.mdx} (99%)
 rename src/routes/reactivity/{memos.mdx => derived-state.mdx} (85%)

diff --git a/src/routes/getting-started/data.json b/src/routes/getting-started/data.json
index 5790f74ec..5f04d10c2 100644
--- a/src/routes/getting-started/data.json
+++ b/src/routes/getting-started/data.json
@@ -1,4 +1,4 @@
 {
 	"title": "Getting Started",
-	"pages": ["quick-start.mdx", "understanding-jsx.mdx", "todo.mdx"]
+	"pages": ["installation.mdx", "understanding-jsx.mdx", "todo.mdx"]
 }
diff --git a/src/routes/getting-started/quick-start.mdx b/src/routes/getting-started/installation.mdx
similarity index 99%
rename from src/routes/getting-started/quick-start.mdx
rename to src/routes/getting-started/installation.mdx
index a77884414..8e8f4fee3 100644
--- a/src/routes/getting-started/quick-start.mdx
+++ b/src/routes/getting-started/installation.mdx
@@ -1,5 +1,5 @@
 ---
-title: Quick Start
+title: Installation
 order: 1
 ---
 
diff --git a/src/routes/intro.mdx b/src/routes/intro.mdx
index 1809b9ecf..e7944c791 100644
--- a/src/routes/intro.mdx
+++ b/src/routes/intro.mdx
@@ -24,11 +24,11 @@ Traditionally, when a change occurs, the entire page would need to reload to dis
 With Solid's fine-grained reactive system, updates are only applied to the parts of the page that need to be updated.
 This decreases work and can result in faster load times as well as a smoother user experience overall.
 
-## The Mental Model
+## The mental model
 
 [TODO: Simple explanation of the mental model behind Solid]
 
-## Where to Go Next
+## Where to go next
 
 - [Quick Start Guide](https://solidjs.com/docs/getting-started)
 - [Reactivity Overview](/concepts/reactivity/)
diff --git a/src/routes/reactivity/basics.mdx b/src/routes/reactivity/basics.mdx
index 7c44d28ef..36df5c5fa 100644
--- a/src/routes/reactivity/basics.mdx
+++ b/src/routes/reactivity/basics.mdx
@@ -10,12 +10,12 @@ It’s the programming model where **changes in data automatically update the pa
 Solid’s approach is **fine-grained**: only the exact parts of the DOM that depend on a value update.
 This makes applications efficient and responsive, even as they grow.
 
-## Core Principles of Reactivity
+## Core principles of reactivity
 	
 Solid’s reactivity is built on three key ideas: **signals, subscribers, and tracking scopes**.  
 Together, these create a system where updates are precise, automatic, and efficient.
 
-### Signals: Reactive Values
+### Signals: Reactive values
 
 A **signal** is a reactive value container.
 They consist of 2 parts:
@@ -38,7 +38,7 @@ Signals can hold any type of value:
 
 Learn more in the [Signals page](/reactivity/signals).
 
-### Subscribers: Reactive Consumers
+### Subscribers: Reactive consumers
 
 If signals are the **source of truth**, subscribers are the **reactive consumers**.
 
@@ -51,7 +51,7 @@ How subscribers work:
 2. **Dependency tracking** → those signals register the subscriber.
 3. **Response** → when a signal changes, the subscriber re-runs.
 
-### Tracking Scopes: Connecting Signals & Subscribers
+### Tracking Scopes: Connecting signals & subscribers
 
 A **tracking scope** is the environment where Solid records which signals are being used.
 When a signal is read within a tracking scope, it registers the current subscriber as a dependency.
@@ -88,5 +88,5 @@ You can learn more about [component lifecycles in the Intro to Components page](
 
 ## Related pages
 - [Signals](/reactivity/signals)
-- [Reactive Side Effects](/reactivity/effects)
+- [Effects](/reactivity/effects)
 - [Introduction to Components](/components/intro)
diff --git a/src/routes/reactivity/data.json b/src/routes/reactivity/data.json
index 5cdfeb89b..7eacc5dcb 100644
--- a/src/routes/reactivity/data.json
+++ b/src/routes/reactivity/data.json
@@ -3,7 +3,7 @@
 	"pages": [
 		"basics.mdx",
 		"signals.mdx",
-		"memos.mdx",
+		"derived-state.mdx",
 		"effects.mdx",
 		"stores.mdx",
 		"resources.mdx",
diff --git a/src/routes/reactivity/memos.mdx b/src/routes/reactivity/derived-state.mdx
similarity index 85%
rename from src/routes/reactivity/memos.mdx
rename to src/routes/reactivity/derived-state.mdx
index 6f07f36bb..d0f749336 100644
--- a/src/routes/reactivity/memos.mdx
+++ b/src/routes/reactivity/derived-state.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Memoized Computations"
+title: "Derived State"
 order: 3
 ---
 
diff --git a/src/routes/reactivity/effects.mdx b/src/routes/reactivity/effects.mdx
index 1086c53e9..17936e4d9 100644
--- a/src/routes/reactivity/effects.mdx
+++ b/src/routes/reactivity/effects.mdx
@@ -1,12 +1,165 @@
 ---
-title: "Derived Reactive Values"
+title: "Effects"
 order: 4
 ---
 
-[TODO:
-Concept page for Effects
-- What are Effects
-- How to use them
-- When to use Effects
-- Move relevant sections to ref and vice versa
-]
\ No newline at end of file
+Effects are reactive functions that run when the values they depend on change.
+They’re the main way to manage side effects that occur outside an application's scope, such as:
+- DOM manipulation
+- Data fetching
+- Subscriptions
+
+## What are Effects?
+
+An effect is a reactive function that **runs automatically whenever the values it depends on change**.
+
+Unlike [signals](/basics/signals) (which store state) or [memos](/basics/derived-state) (which derive state), effects connect your reactive data to the outside world.
+They are used for running code that has side effects, meaning it interacts with or modifies something beyond Solid's reactive graph, such as:
+
+- updating or interacting with the DOM
+- logging values
+- fetching or subscribing to external data
+- setting up or cleaning up resources
+
+Effects run **once when created** to establish its subscriptions, then **again whenever its dependencies change**.
+
+## Creating an Effect
+
+You create an effect using the `createEffect` function.
+It takes a **callback function** as its first argument, which contains the code you want to run reactively.
+
+```tsx
+import { createSignal, createEffect } from "solid-js";
+
+function Counter() {
+  const [count, setCount] = createSignal(0);
+
+  createEffect(() => {
+    console.log(`Count is: ${count()}`);
+  });
+
+  return (
+    <button onClick={() => setCount(count() + 1)}>
+      Increment
+    </button>
+  );
+}
+```
+
+In this example, the effect logs the current value of `count` to the console.
+The effect runs once when created, logging `Count is: 0`, and will run again whenever `count` changes, in this case when the button is clicked.
+
+## Lifecycle of an Effect
+
+An effect goes through a predictable cycle every time it's created and re-runs:
+
+### 1. **Initialization**
+
+When you call `createEffect`, the effect is immediately scheduled to run **once**.
+This first run happens **after the current render phase** finishes, or after the component function returns its JSX.
+This ensures that the DOM is already created and refs are assigned, allowing you to safely interact with the DOM.
+
+```tsx
+createEffect(() => console.log("Initial run"));
+console.log("Hello");
+
+// Output:
+// Hello
+// Initial run
+```
+
+### 2. **Dependency tracking**
+
+During its first run, the effect records every reactive value it accesses (such as signals or memos).
+It becomes subscribed to those values, which are now its **dependencies**.
+From then on, the effect automatically re‑runs whenever any of its dependencies change.
+
+```tsx
+const [count, setCount] = createSignal(0);
+
+createEffect(() => {
+  console.log(`Count: ${count()}`);
+});
+
+// Count: 0 runs immediately
+// every setCount(...) re‑runs the effect
+```
+
+### 3. **Reactive Updates**
+
+Whenever *any* dependency changes, the effects is scheduled to run again.
+This happens **after the current synchronous code completes**, ensuring that all changes are batched together.
+This means that if the dependencies change multiple times in quick succession, the effect will only run *once* after all changes are made:
+
+```tsx
+const [count, setCount] = createSignal(0);
+const [name, setName] = createSignal("Solid");
+
+createEffect(() => {
+    console.log(`Count: ${count()}, Name: ${name()}`);
+});
+
+setCount(1);
+setName("SolidJS"); 
+```
+
+In this example, the effect will only log `Count: 1, Name: SolidJS` once, after all changes have been made.
+
+### Lifecycle functions
+
+Effects are reactive and run whenever their dependencies change, but sometimes finer control is needed.
+Solid provides lifecycle functions to manage when code runs and how it gets cleaned up.
+
+These functions are especially useful for:
+- Running a side effect **only once** when the component mounts
+- Cleaning up resources, event listeners, or other side effects when the component unmounts
+
+#### `onMount`
+
+The [`onMount`](TODO) function allows you to run code **once** when the component is first added to the DOM.
+Unlike effects, `onMount` does **not track dependencies**.
+It will execute the callback once, and never again.
+
+```tsx
+import { onMount, createSignal, createEffect } from "solid-js";
+
+function Component() {
+  const [data, setData] = createSignal(null);
+
+  createEffect(() => {
+    // Still runs reactively whenever `data` changes
+    console.log("Data:", data());
+  });
+
+  onMount(async () => {
+    // Runs only once when the component is mounted
+    const res = await fetch("/api/data");
+    setData(await res.json());
+  });
+
+  return <div>...</div>;
+}
+```
+
+#### `onCleanup`
+
+Use [`onCleanup`](TODO) to **dispose of resources** before a component unmounts, or before an effect re-runs.
+This will prevent memory leaks and ensure that any subscriptions or event listeners are properly removed.
+
+```tsx
+import { createSignal, onCleanup } from "solid-js";
+
+function App() {
+  const [count, setCount] = createSignal(0);
+
+  const timer = setInterval(() => setCount(c => c + 1), 1000);
+
+  onCleanup(() => {
+    // Runs when the component unmounts
+    clearInterval(timer);
+  });
+
+  return <div>Count: {count()}</div>;
+}
+```
+

From e773cb20faf704eb2f57a381b35783d8dd0a9c97 Mon Sep 17 00:00:00 2001
From: Thomas <thomas.giudici@proton.me>
Date: Sun, 7 Sep 2025 07:27:37 +0200
Subject: [PATCH 12/37] Closes issues #649 and #968  (#1251)

Co-authored-by: Sarah <hello@sarahgerrard.me>
---
 old pages/concepts/stores.mdx                     |  6 +++---
 .../route-prerendering.mdx                        | 15 ++++++++++-----
 2 files changed, 13 insertions(+), 8 deletions(-)

diff --git a/old pages/concepts/stores.mdx b/old pages/concepts/stores.mdx
index 748ada6ae..14041cf1e 100644
--- a/old pages/concepts/stores.mdx	
+++ b/old pages/concepts/stores.mdx	
@@ -3,9 +3,9 @@ title: Stores
 order: 6
 ---
 
-Similar to [signals](/concepts/signals), stores are a state management primitive.
-However, while signals manage a single piece of state, stores create a centralized location to reduce code redundancy.
-Within Solid, these stores can spawn a collection of reactive signals, each corresponding to a particular property which can be useful when working with complex state.
+Stores are a state management primitive that provide a centralized way to handle shared data and reduce redundancy.
+Unlike [signals](/concepts/signals), which track a single value and trigger a full re-render when updated, stores maintain fine-grained reactivity by updating only the properties that change.
+They can produce a collection of reactive signals, each linked to an individual property, making them well-suited for managing complex state efficiently.
 
 ## Creating a store
 
diff --git a/src/routes/solid-start/building-your-application/route-prerendering.mdx b/src/routes/solid-start/building-your-application/route-prerendering.mdx
index 34461ea25..9a17813eb 100644
--- a/src/routes/solid-start/building-your-application/route-prerendering.mdx
+++ b/src/routes/solid-start/building-your-application/route-prerendering.mdx
@@ -1,9 +1,12 @@
 ---
-title: "Route pre-rendering"
+title: "Route Pre-rendering"
 ---
 
-SolidStart offers a way to pre-render pages at build time.
-The easiest way to accomplish this is by passing a list of routes to be pre-rendered to the `routes` option.
+Route pre-rendering powers Static Site Generation (SSG) by producing static HTML pages during the build process.
+This results in faster load times and better SEO, making it especially useful for content-rich sites such as documentation, blogs, and marketing pages.
+Static files are served without server-side processing at runtime.
+
+Configure prerendering for specific routes using the `routes` option
 
 ```js { 6 }
 import { defineConfig } from "@solidjs/start/config";
@@ -17,7 +20,7 @@ export default defineConfig({
 });
 ```
 
-When you wish for all your routes to be pre-rendered, you can pass `true` to the `crawlLinks` option:
+Or to pre-render all routes, you can pass `true` to the `crawlLinks` option
 
 ```js { 6 }
 import { defineConfig } from "@solidjs/start/config";
@@ -31,4 +34,6 @@ export default defineConfig({
 });
 ```
 
-For more information on prerender options, check out [Nitro's documentation](https://nitro.build/config#prerender)
+For advanced pre-rendering options, refer to [Nitro's documentation](https://nitro.build/config#prerender).
+
+[SolidBase](https://solidbase.dev) simplifies SSG development with built-in support for fast, pre-rendered Markdown and MDX pages.

From 348aea9078b2a82d746acfcfe336c549b40b0b93 Mon Sep 17 00:00:00 2001
From: Thomas <thomas.giudici@proton.me>
Date: Mon, 8 Sep 2025 08:22:35 +0200
Subject: [PATCH 13/37] Addresses Issue #1183 (#1252)

Co-authored-by: Sarah <hello@sarahgerrard.me>
---
 old pages/concepts/stores.mdx | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/old pages/concepts/stores.mdx b/old pages/concepts/stores.mdx
index 14041cf1e..36e30a01d 100644
--- a/old pages/concepts/stores.mdx	
+++ b/old pages/concepts/stores.mdx	
@@ -253,8 +253,10 @@ Instead of relying on discovering individual indices, path syntax introduces sev
 
 ### Appending new values
 
-To append new values to an array in a store, use the setter function with the spread operator (`...`) to create a new array that includes the existing items and the new ones.
-For appending a single element, you can instead leverage the "path syntax" by specifying the array’s length as the index to set.
+To append values to an array in a store, use the setter function with the spread operator (`...`) or the path syntax. Both methods add an element to the array but differ in how they modify it and their reactivity behavior.
+
+The spread operator creates a new array by copying the existing elements and adding the new one, effectively replacing the entire `store.users` array.
+This replacement triggers reactivity for all effects that depend on the array or its properties.
 
 ```jsx
 setStore("users", (otherUsers) => [
@@ -266,9 +268,12 @@ setStore("users", (otherUsers) => [
 		loggedIn: false,
 	},
 ])
+```
 
-// can become
+The path syntax adds the new element by assigning it to the index equal to `store.users.length`, directly modifying the existing array.
+This triggers reactivity only for effects that depend on the new index or properties like `store.users.length`, making updates more efficient and targeted.
 
+```jsx
 setStore("users", store.users.length, {
 	id: 3,
 	username: "michael584",

From 832a918ccaba3026c94c1b2eb5d220504556fa81 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Mon, 8 Sep 2025 15:52:18 -0700
Subject: [PATCH 14/37] Bump @types/node from 24.3.0 to 24.3.1 (#1254)

---
 package.json   |  2 +-
 pnpm-lock.yaml | 84 +++++++++++++++++++++++++-------------------------
 2 files changed, 43 insertions(+), 43 deletions(-)

diff --git a/package.json b/package.json
index ecc5fb5d9..c7664c157 100644
--- a/package.json
+++ b/package.json
@@ -46,7 +46,7 @@
 		"@kobalte/tailwindcss": "^0.9.0",
 		"@orama/crawly": "^0.0.6",
 		"@tailwindcss/typography": "^0.5.16",
-		"@types/node": "^24.3.0",
+		"@types/node": "^24.3.1",
 		"@typescript-eslint/eslint-plugin": "^8.41.0",
 		"@typescript-eslint/parser": "^8.41.0",
 		"autoprefixer": "^10.4.21",
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index 6bed31399..45333847d 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -13,7 +13,7 @@ importers:
         version: 0.13.11(solid-js@1.9.9)
       '@kobalte/solidbase':
         specifier: ^0.2.17
-        version: 0.2.17(@algolia/client-search@5.14.2)(@solidjs/start@1.1.7(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)))(@vue/compiler-sfc@3.5.16)(acorn@8.15.0)(expressive-code@0.40.2)(react@18.3.1)(search-insights@2.17.3)(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+        version: 0.2.17(@algolia/client-search@5.14.2)(@solidjs/start@1.1.7(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)))(@vue/compiler-sfc@3.5.16)(acorn@8.15.0)(expressive-code@0.40.2)(react@18.3.1)(search-insights@2.17.3)(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       '@lunariajs/core':
         specifier: ^0.1.1
         version: 0.1.1
@@ -40,7 +40,7 @@ importers:
         version: 0.15.3(solid-js@1.9.9)
       '@solidjs/start':
         specifier: ^1.1.7
-        version: 1.1.7(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+        version: 1.1.7(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       dotenv:
         specifier: ^17.2.1
         version: 17.2.1
@@ -70,7 +70,7 @@ importers:
         version: 0.3.0(solid-js@1.9.9)
       vinxi:
         specifier: ^0.5.7
-        version: 0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+        version: 0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
       zod:
         specifier: ^4.1.5
         version: 4.1.5
@@ -88,8 +88,8 @@ importers:
         specifier: ^0.5.16
         version: 0.5.16(tailwindcss@3.4.17)
       '@types/node':
-        specifier: ^24.3.0
-        version: 24.3.0
+        specifier: ^24.3.1
+        version: 24.3.1
       '@typescript-eslint/eslint-plugin':
         specifier: ^8.41.0
         version: 8.41.0(@typescript-eslint/parser@8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)
@@ -125,7 +125,7 @@ importers:
         version: 8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)
       vite:
         specifier: ^6.3.5
-        version: 6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+        version: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
 
 packages:
 
@@ -1568,8 +1568,8 @@ packages:
   '@types/node@17.0.45':
     resolution: {integrity: sha512-w+tIMs3rq2afQdsPJlODhoUEKzFP1ayaoyl1CcnwtIlsVe7K7bA1NGm4s3PraqTLlXnbIN84zuBlxBWo1u9BLw==}
 
-  '@types/node@24.3.0':
-    resolution: {integrity: sha512-aPTXCrfwnDLj4VvXrm+UUCQjNEvJgNA8s5F1cvwQU+3KNltTOkBm1j30uNLyqqPNe7gE3KFzImYoZEfLhp4Yow==}
+  '@types/node@24.3.1':
+    resolution: {integrity: sha512-3vXmQDXy+woz+gnrTvuvNrPzekOi+Ds0ReMxw0LzBiK3a+1k0kQn9f2NWk+lgD4rJehFUmYy2gMhJ2ZI+7YP9g==}
 
   '@types/normalize-package-data@2.4.4':
     resolution: {integrity: sha512-37i+OaWTh9qeK4LSHPsyRC7NahnGotNuZvjLSgcPzblpHB3rrCJxAOgI5gCdKm7coonsaX1Of0ILiTcnZjbfxA==}
@@ -5948,7 +5948,7 @@ snapshots:
       solid-presence: 0.1.8(solid-js@1.9.9)
       solid-prevent-scroll: 0.1.10(solid-js@1.9.9)
 
-  '@kobalte/solidbase@0.2.17(@algolia/client-search@5.14.2)(@solidjs/start@1.1.7(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)))(@vue/compiler-sfc@3.5.16)(acorn@8.15.0)(expressive-code@0.40.2)(react@18.3.1)(search-insights@2.17.3)(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
+  '@kobalte/solidbase@0.2.17(@algolia/client-search@5.14.2)(@solidjs/start@1.1.7(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)))(@vue/compiler-sfc@3.5.16)(acorn@8.15.0)(expressive-code@0.40.2)(react@18.3.1)(search-insights@2.17.3)(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
       '@alloc/quick-lru': 5.2.0
       '@bprogress/core': 1.1.18
@@ -5973,7 +5973,7 @@ snapshots:
       '@solid-primitives/storage': 4.3.1(solid-js@1.9.9)
       '@solidjs/meta': 0.29.4(solid-js@1.9.9)
       '@solidjs/router': 0.15.3(solid-js@1.9.9)
-      '@solidjs/start': 1.1.7(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      '@solidjs/start': 1.1.7(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       cross-spawn: 7.0.3
       esast-util-from-js: 2.0.1
       estree-util-value-to-estree: 3.2.1
@@ -5992,7 +5992,7 @@ snapshots:
       remark-frontmatter: 5.0.0
       remark-gfm: 4.0.0
       solid-js: 1.9.9
-      solid-mdx: 0.0.7(solid-js@1.9.9)(vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      solid-mdx: 0.0.7(solid-js@1.9.9)(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       toml: 3.0.0
       typescript: 5.9.2
       unified: 11.0.5
@@ -6002,8 +6002,8 @@ snapshots:
       unist-util-visit: 5.0.0
       unplugin-auto-import: 19.1.1
       unplugin-icons: 22.1.0(@vue/compiler-sfc@3.5.16)
-      vinxi: 0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
-      vite: 6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vinxi: 0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vite: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
       yaml: 2.8.0
     transitivePeerDependencies:
       - '@algolia/client-search'
@@ -6691,11 +6691,11 @@ snapshots:
     dependencies:
       solid-js: 1.9.9
 
-  '@solidjs/start@1.1.7(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
+  '@solidjs/start@1.1.7(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
-      '@tanstack/server-functions-plugin': 1.121.21(vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
-      '@vinxi/plugin-directives': 0.5.0(vinxi@0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
-      '@vinxi/server-components': 0.5.0(vinxi@0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      '@tanstack/server-functions-plugin': 1.121.21(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      '@vinxi/plugin-directives': 0.5.0(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      '@vinxi/server-components': 0.5.0(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       defu: 6.1.4
       error-stack-parser: 2.1.4
       html-to-image: 1.11.11
@@ -6706,8 +6706,8 @@ snapshots:
       source-map-js: 1.2.1
       terracotta: 1.0.6(solid-js@1.9.9)
       tinyglobby: 0.2.12
-      vinxi: 0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
-      vite-plugin-solid: 2.11.2(solid-js@1.9.9)(vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      vinxi: 0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vite-plugin-solid: 2.11.2(solid-js@1.9.9)(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
     transitivePeerDependencies:
       - '@testing-library/jest-dom'
       - solid-js
@@ -6728,7 +6728,7 @@ snapshots:
       postcss-selector-parser: 6.0.10
       tailwindcss: 3.4.17
 
-  '@tanstack/directive-functions-plugin@1.121.21(vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
+  '@tanstack/directive-functions-plugin@1.121.21(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
       '@babel/code-frame': 7.26.2
       '@babel/core': 7.28.3
@@ -6737,7 +6737,7 @@ snapshots:
       '@tanstack/router-utils': 1.131.2
       babel-dead-code-elimination: 1.0.10
       tiny-invariant: 1.3.3
-      vite: 6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vite: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
     transitivePeerDependencies:
       - supports-color
 
@@ -6752,7 +6752,7 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
-  '@tanstack/server-functions-plugin@1.121.21(vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
+  '@tanstack/server-functions-plugin@1.121.21(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
       '@babel/code-frame': 7.26.2
       '@babel/core': 7.28.3
@@ -6761,7 +6761,7 @@ snapshots:
       '@babel/template': 7.27.2
       '@babel/traverse': 7.28.3
       '@babel/types': 7.28.2
-      '@tanstack/directive-functions-plugin': 1.121.21(vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      '@tanstack/directive-functions-plugin': 1.121.21(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       babel-dead-code-elimination: 1.0.10
       tiny-invariant: 1.3.3
     transitivePeerDependencies:
@@ -6827,7 +6827,7 @@ snapshots:
 
   '@types/node@17.0.45': {}
 
-  '@types/node@24.3.0':
+  '@types/node@24.3.1':
     dependencies:
       undici-types: 7.10.0
 
@@ -6837,7 +6837,7 @@ snapshots:
 
   '@types/sax@1.2.7':
     dependencies:
-      '@types/node': 24.3.0
+      '@types/node': 24.3.1
 
   '@types/triple-beam@1.3.5': {}
 
@@ -6849,7 +6849,7 @@ snapshots:
 
   '@types/yauzl@2.10.3':
     dependencies:
-      '@types/node': 24.3.0
+      '@types/node': 24.3.1
     optional: true
 
   '@typescript-eslint/eslint-plugin@8.41.0(@typescript-eslint/parser@8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)':
@@ -7081,7 +7081,7 @@ snapshots:
       untun: 0.1.3
       uqr: 0.1.2
 
-  '@vinxi/plugin-directives@0.5.0(vinxi@0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
+  '@vinxi/plugin-directives@0.5.0(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
       '@babel/parser': 7.25.8
       acorn: 8.12.1
@@ -7092,18 +7092,18 @@ snapshots:
       magicast: 0.2.11
       recast: 0.23.9
       tslib: 2.8.0
-      vinxi: 0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vinxi: 0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
 
-  '@vinxi/server-components@0.5.0(vinxi@0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
+  '@vinxi/server-components@0.5.0(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
-      '@vinxi/plugin-directives': 0.5.0(vinxi@0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      '@vinxi/plugin-directives': 0.5.0(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       acorn: 8.12.1
       acorn-loose: 8.4.0
       acorn-typescript: 1.4.13(acorn@8.12.1)
       astring: 1.9.0
       magicast: 0.2.11
       recast: 0.23.9
-      vinxi: 0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vinxi: 0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
 
   '@vue/compiler-core@3.5.16':
     dependencies:
@@ -10387,10 +10387,10 @@ snapshots:
       '@corvu/utils': 0.4.2(solid-js@1.9.9)
       solid-js: 1.9.9
 
-  solid-mdx@0.0.7(solid-js@1.9.9)(vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)):
+  solid-mdx@0.0.7(solid-js@1.9.9)(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)):
     dependencies:
       solid-js: 1.9.9
-      vite: 6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vite: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
 
   solid-presence@0.1.8(solid-js@1.9.9):
     dependencies:
@@ -10950,7 +10950,7 @@ snapshots:
       '@types/unist': 3.0.3
       vfile-message: 4.0.2
 
-  vinxi@0.5.7(@types/node@24.3.0)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0):
+  vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0):
     dependencies:
       '@babel/core': 7.25.8
       '@babel/plugin-syntax-jsx': 7.25.7(@babel/core@7.25.8)
@@ -10984,7 +10984,7 @@ snapshots:
       unctx: 2.4.1
       unenv: 1.10.0
       unstorage: 1.16.0(db0@0.3.2)(ioredis@5.6.1)
-      vite: 6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vite: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
       zod: 3.25.76
     transitivePeerDependencies:
       - '@azure/app-configuration'
@@ -11028,7 +11028,7 @@ snapshots:
       - xml2js
       - yaml
 
-  vite-plugin-solid@2.11.2(solid-js@1.9.9)(vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)):
+  vite-plugin-solid@2.11.2(solid-js@1.9.9)(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)):
     dependencies:
       '@babel/core': 7.25.8
       '@types/babel__core': 7.20.5
@@ -11036,12 +11036,12 @@ snapshots:
       merge-anything: 5.1.7
       solid-js: 1.9.9
       solid-refresh: 0.6.3(solid-js@1.9.9)
-      vite: 6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
-      vitefu: 1.0.5(vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      vite: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vitefu: 1.0.5(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
     transitivePeerDependencies:
       - supports-color
 
-  vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0):
+  vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0):
     dependencies:
       esbuild: 0.25.5
       fdir: 6.4.6(picomatch@4.0.2)
@@ -11050,15 +11050,15 @@ snapshots:
       rollup: 4.43.0
       tinyglobby: 0.2.14
     optionalDependencies:
-      '@types/node': 24.3.0
+      '@types/node': 24.3.1
       fsevents: 2.3.3
       jiti: 2.4.2
       terser: 5.42.0
       yaml: 2.8.0
 
-  vitefu@1.0.5(vite@6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)):
+  vitefu@1.0.5(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)):
     optionalDependencies:
-      vite: 6.3.5(@types/node@24.3.0)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vite: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
 
   web-namespaces@2.0.1: {}
 

From a297414e65519db281ac116b11571f16987a8d36 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Mon, 8 Sep 2025 15:53:11 -0700
Subject: [PATCH 15/37] Bump eslint from 9.34.0 to 9.35.0 (#1256)

---
 package.json   |   2 +-
 pnpm-lock.yaml | 126 ++++++++++++++++++++++++-------------------------
 2 files changed, 64 insertions(+), 64 deletions(-)

diff --git a/package.json b/package.json
index c7664c157..410eff580 100644
--- a/package.json
+++ b/package.json
@@ -50,7 +50,7 @@
 		"@typescript-eslint/eslint-plugin": "^8.41.0",
 		"@typescript-eslint/parser": "^8.41.0",
 		"autoprefixer": "^10.4.21",
-		"eslint": "^9.34.0",
+		"eslint": "^9.35.0",
 		"eslint-plugin-solid": "^0.14.5",
 		"globals": "^16.3.0",
 		"prettier": "3.6.2",
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index 45333847d..ae49d5bf2 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -92,19 +92,19 @@ importers:
         version: 24.3.1
       '@typescript-eslint/eslint-plugin':
         specifier: ^8.41.0
-        version: 8.41.0(@typescript-eslint/parser@8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)
+        version: 8.41.0(@typescript-eslint/parser@8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
       '@typescript-eslint/parser':
         specifier: ^8.41.0
-        version: 8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)
+        version: 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
       autoprefixer:
         specifier: ^10.4.21
         version: 10.4.21(postcss@8.5.6)
       eslint:
-        specifier: ^9.34.0
-        version: 9.34.0(jiti@2.4.2)
+        specifier: ^9.35.0
+        version: 9.35.0(jiti@2.4.2)
       eslint-plugin-solid:
         specifier: ^0.14.5
-        version: 0.14.5(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)
+        version: 0.14.5(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
       globals:
         specifier: ^16.3.0
         version: 16.3.0
@@ -122,7 +122,7 @@ importers:
         version: 5.9.2
       typescript-eslint:
         specifier: ^8.41.0
-        version: 8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)
+        version: 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
       vite:
         specifier: ^6.3.5
         version: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
@@ -669,8 +669,8 @@ packages:
     cpu: [x64]
     os: [win32]
 
-  '@eslint-community/eslint-utils@4.7.0':
-    resolution: {integrity: sha512-dyybb3AcajC7uha6CvhdVRJqaKyn7w2YKqKyAN37NKYgZT36w+iRb0Dymmc5qEJ549c/S31cMMSFd75bteCpCw==}
+  '@eslint-community/eslint-utils@4.9.0':
+    resolution: {integrity: sha512-ayVFHdtZ+hsq1t2Dy24wCmGXGe4q9Gu3smhLYALJrr473ZH27MsnSL+LKUlimp4BWJqMDMLmPpx/Q9R3OAlL4g==}
     engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
     peerDependencies:
       eslint: ^6.0.0 || ^7.0.0 || >=8.0.0
@@ -699,6 +699,10 @@ packages:
     resolution: {integrity: sha512-EoyvqQnBNsV1CWaEJ559rxXL4c8V92gxirbawSmVUOWXlsRxxQXl6LmCpdUblgxgSkDIqKnhzba2SjRTI/A5Rw==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
 
+  '@eslint/js@9.35.0':
+    resolution: {integrity: sha512-30iXE9whjlILfWobBkNerJo+TXYsgVM5ERQwMcMKCHckHflCmf7wXDAHlARoWnh0s1U72WqlbeyE7iAcCzuCPw==}
+    engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
+
   '@eslint/object-schema@2.1.6':
     resolution: {integrity: sha512-RBMg5FRL0I0gs51M/guSAj5/e14VQ4tpZnQNWwuDT66P14I43ItmPfIZRhO9fUVIPOAQXU47atlywZ/czoqFPA==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
@@ -750,18 +754,14 @@ packages:
     resolution: {integrity: sha512-5DyQ4+1JEUzejeK1JGICcideyfUbGixgS9jNgex5nqkW+cY7WZhxBigmieN5Qnw9ZosSNVC9KQKyb+GUaGyKUA==}
     engines: {node: '>=18.18.0'}
 
-  '@humanfs/node@0.16.6':
-    resolution: {integrity: sha512-YuI2ZHQL78Q5HbhDiBA1X4LmYdXCKCMQIfw0pw7piHJwyREFebJUvrQN4cMssyES6x+vfUbx1CIpaQUKYdQZOw==}
+  '@humanfs/node@0.16.7':
+    resolution: {integrity: sha512-/zUx+yOsIrG4Y43Eh2peDeKCxlRt/gET6aHfaKpuq267qXdYDFViVHfMaLyygZOnl0kGWxFIgsBy8QFuTLUXEQ==}
     engines: {node: '>=18.18.0'}
 
   '@humanwhocodes/module-importer@1.0.1':
     resolution: {integrity: sha512-bxveV4V8v5Yb4ncFTT3rPSgZBOpCkjfK0y4oVVVJwIuDVBRMDXrPyXRL988i5ap9m9bnyEEjWfm5WkBmtffLfA==}
     engines: {node: '>=12.22'}
 
-  '@humanwhocodes/retry@0.3.1':
-    resolution: {integrity: sha512-JBxkERygn7Bv/GbN5Rv8Ul6LVknS+5Bp6RgDC/O8gEBU/yeH5Ui5C/OlWrTb6qct7LjjfT6Re2NxB0ln0yYybA==}
-    engines: {node: '>=18.18'}
-
   '@humanwhocodes/retry@0.4.3':
     resolution: {integrity: sha512-bV0Tgo9K4hfPCek+aMAn81RppFKv2ySDQeMoSZuvTASywNTnVJCArCZE2FWqpvIatKu7VMRLWlR1EazvVhDyhQ==}
     engines: {node: '>=18.18'}
@@ -1850,8 +1850,8 @@ packages:
     resolution: {integrity: sha512-Cxwpt2SfTzTtXcfOlzGEee8O+c+MmUgGrNiBcXnuWxuFJHe6a5Hz7qwhwe5OgaSYI0IJvkLqWX1ASG+cJOkEiA==}
     engines: {node: '>=10'}
 
-  ansi-styles@6.2.1:
-    resolution: {integrity: sha512-bN798gFfQX+viw3R7yrGWRqnrN2oRkEkUjjl4JNn4E8GxxbjtG3FbrEIIY3l8/hrwUwIeCZvi4QuOTP4MErVug==}
+  ansi-styles@6.2.3:
+    resolution: {integrity: sha512-4Dj6M28JB+oAH8kFkTLUo+a2jwOFkuqb3yucU0CANcRRUbxS0cP0nZYCGjcc3BNXwRIsUVmDGgzawme7zvJHvg==}
     engines: {node: '>=12'}
 
   ansis@4.1.0:
@@ -2037,8 +2037,8 @@ packages:
     resolution: {integrity: sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==}
     engines: {node: '>=10'}
 
-  chalk@5.6.0:
-    resolution: {integrity: sha512-46QrSQFyVSEyYAgQ22hQ+zDa60YHA4fBstHmtSApj1Y5vKtG27fWowW03jCk5KcbXEWPZUIR894aARCA/G1kfQ==}
+  chalk@5.6.2:
+    resolution: {integrity: sha512-7NzBL0rN6fMUW+f7A6Io4h40qQlG+xGmtMxfbnH/K7TAtt8JQWVQK+6g0UXKMeVJoyV5EkkNsErQ8pVD3bLHbA==}
     engines: {node: ^12.17.0 || ^14.13 || >=16.0.0}
 
   character-entities-html4@2.1.0:
@@ -2541,8 +2541,8 @@ packages:
     resolution: {integrity: sha512-Uhdk5sfqcee/9H/rCOJikYz67o0a2Tw2hGRPOG2Y1R2dg7brRe1uG0yaNQDHu+TO/uQPF/5eCapvYSmHUjt7JQ==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
 
-  eslint@9.34.0:
-    resolution: {integrity: sha512-RNCHRX5EwdrESy3Jc9o8ie8Bog+PeYvvSR8sDGoZxNFTvZ4dlxUB3WzQ3bQMztFrSRODGrLLj8g6OFuGY/aiQg==}
+  eslint@9.35.0:
+    resolution: {integrity: sha512-QePbBFMJFjgmlE+cXAlbHZbHpdFVS2E/6vzCy7aKlebddvl1vadiC4JFV5u/wqTkNUwEV8WrQi257jf5f06hrg==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
     hasBin: true
     peerDependencies:
@@ -4569,8 +4569,8 @@ packages:
     engines: {node: '>=16 || 14 >=14.17'}
     hasBin: true
 
-  supports-color@10.2.0:
-    resolution: {integrity: sha512-5eG9FQjEjDbAlI5+kdpdyPIBMRH4GfTVDGREVupaZHmVoppknhM29b/S9BkQz7cathp85BVgRi/As3Siln7e0Q==}
+  supports-color@10.2.2:
+    resolution: {integrity: sha512-SS+jx45GF1QjgEXQx4NJZV9ImqmO2NPz5FNsIHrsDjh2YsHnawpan7SNQ1o8NuhrbHZy9AZhIoCUiCeaW/C80g==}
     engines: {node: '>=18'}
 
   supports-color@5.5.0:
@@ -5739,9 +5739,9 @@ snapshots:
   '@esbuild/win32-x64@0.25.5':
     optional: true
 
-  '@eslint-community/eslint-utils@4.7.0(eslint@9.34.0(jiti@2.4.2))':
+  '@eslint-community/eslint-utils@4.9.0(eslint@9.35.0(jiti@2.4.2))':
     dependencies:
-      eslint: 9.34.0(jiti@2.4.2)
+      eslint: 9.35.0(jiti@2.4.2)
       eslint-visitor-keys: 3.4.3
 
   '@eslint-community/regexpp@4.12.1': {}
@@ -5776,6 +5776,8 @@ snapshots:
 
   '@eslint/js@9.34.0': {}
 
+  '@eslint/js@9.35.0': {}
+
   '@eslint/object-schema@2.1.6': {}
 
   '@eslint/plugin-kit@0.3.5':
@@ -5837,15 +5839,13 @@ snapshots:
 
   '@humanfs/core@0.19.1': {}
 
-  '@humanfs/node@0.16.6':
+  '@humanfs/node@0.16.7':
     dependencies:
       '@humanfs/core': 0.19.1
-      '@humanwhocodes/retry': 0.3.1
+      '@humanwhocodes/retry': 0.4.3
 
   '@humanwhocodes/module-importer@1.0.1': {}
 
-  '@humanwhocodes/retry@0.3.1': {}
-
   '@humanwhocodes/retry@0.4.3': {}
 
   '@iconify/types@2.0.0': {}
@@ -6362,7 +6362,7 @@ snapshots:
     dependencies:
       '@poppinss/colors': 4.1.4
       '@sindresorhus/is': 7.0.2
-      supports-color: 10.2.0
+      supports-color: 10.2.2
 
   '@poppinss/exception@1.2.1': {}
 
@@ -6852,15 +6852,15 @@ snapshots:
       '@types/node': 24.3.1
     optional: true
 
-  '@typescript-eslint/eslint-plugin@8.41.0(@typescript-eslint/parser@8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)':
+  '@typescript-eslint/eslint-plugin@8.41.0(@typescript-eslint/parser@8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)':
     dependencies:
       '@eslint-community/regexpp': 4.12.1
-      '@typescript-eslint/parser': 8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)
+      '@typescript-eslint/parser': 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
       '@typescript-eslint/scope-manager': 8.41.0
-      '@typescript-eslint/type-utils': 8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)
-      '@typescript-eslint/utils': 8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)
+      '@typescript-eslint/type-utils': 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
+      '@typescript-eslint/utils': 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
       '@typescript-eslint/visitor-keys': 8.41.0
-      eslint: 9.34.0(jiti@2.4.2)
+      eslint: 9.35.0(jiti@2.4.2)
       graphemer: 1.4.0
       ignore: 7.0.5
       natural-compare: 1.4.0
@@ -6869,14 +6869,14 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
-  '@typescript-eslint/parser@8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)':
+  '@typescript-eslint/parser@8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)':
     dependencies:
       '@typescript-eslint/scope-manager': 8.41.0
       '@typescript-eslint/types': 8.41.0
       '@typescript-eslint/typescript-estree': 8.41.0(typescript@5.9.2)
       '@typescript-eslint/visitor-keys': 8.41.0
       debug: 4.4.1
-      eslint: 9.34.0(jiti@2.4.2)
+      eslint: 9.35.0(jiti@2.4.2)
       typescript: 5.9.2
     transitivePeerDependencies:
       - supports-color
@@ -6930,13 +6930,13 @@ snapshots:
     dependencies:
       typescript: 5.9.2
 
-  '@typescript-eslint/type-utils@8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)':
+  '@typescript-eslint/type-utils@8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)':
     dependencies:
       '@typescript-eslint/types': 8.41.0
       '@typescript-eslint/typescript-estree': 8.41.0(typescript@5.9.2)
-      '@typescript-eslint/utils': 8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)
+      '@typescript-eslint/utils': 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
       debug: 4.4.1
-      eslint: 9.34.0(jiti@2.4.2)
+      eslint: 9.35.0(jiti@2.4.2)
       ts-api-utils: 2.1.0(typescript@5.9.2)
       typescript: 5.9.2
     transitivePeerDependencies:
@@ -6996,24 +6996,24 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
-  '@typescript-eslint/utils@8.34.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)':
+  '@typescript-eslint/utils@8.34.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)':
     dependencies:
-      '@eslint-community/eslint-utils': 4.7.0(eslint@9.34.0(jiti@2.4.2))
+      '@eslint-community/eslint-utils': 4.9.0(eslint@9.35.0(jiti@2.4.2))
       '@typescript-eslint/scope-manager': 8.34.0
       '@typescript-eslint/types': 8.34.0
       '@typescript-eslint/typescript-estree': 8.34.0(typescript@5.9.2)
-      eslint: 9.34.0(jiti@2.4.2)
+      eslint: 9.35.0(jiti@2.4.2)
       typescript: 5.9.2
     transitivePeerDependencies:
       - supports-color
 
-  '@typescript-eslint/utils@8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)':
+  '@typescript-eslint/utils@8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)':
     dependencies:
-      '@eslint-community/eslint-utils': 4.7.0(eslint@9.34.0(jiti@2.4.2))
+      '@eslint-community/eslint-utils': 4.9.0(eslint@9.35.0(jiti@2.4.2))
       '@typescript-eslint/scope-manager': 8.41.0
       '@typescript-eslint/types': 8.41.0
       '@typescript-eslint/typescript-estree': 8.41.0(typescript@5.9.2)
-      eslint: 9.34.0(jiti@2.4.2)
+      eslint: 9.35.0(jiti@2.4.2)
       typescript: 5.9.2
     transitivePeerDependencies:
       - supports-color
@@ -7238,7 +7238,7 @@ snapshots:
 
   ansi-styles@5.2.0: {}
 
-  ansi-styles@6.2.1: {}
+  ansi-styles@6.2.3: {}
 
   ansis@4.1.0: {}
 
@@ -7349,7 +7349,7 @@ snapshots:
     dependencies:
       ansi-align: 3.0.1
       camelcase: 8.0.0
-      chalk: 5.6.0
+      chalk: 5.6.2
       cli-boxes: 3.0.0
       string-width: 7.2.0
       type-fest: 4.41.0
@@ -7448,7 +7448,7 @@ snapshots:
       ansi-styles: 4.3.0
       supports-color: 7.2.0
 
-  chalk@5.6.0: {}
+  chalk@5.6.2: {}
 
   character-entities-html4@2.1.0: {}
 
@@ -7897,10 +7897,10 @@ snapshots:
     optionalDependencies:
       source-map: 0.6.1
 
-  eslint-plugin-solid@0.14.5(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2):
+  eslint-plugin-solid@0.14.5(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2):
     dependencies:
-      '@typescript-eslint/utils': 8.34.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)
-      eslint: 9.34.0(jiti@2.4.2)
+      '@typescript-eslint/utils': 8.34.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
+      eslint: 9.35.0(jiti@2.4.2)
       estraverse: 5.3.0
       is-html: 2.0.0
       kebab-case: 1.0.2
@@ -7919,17 +7919,17 @@ snapshots:
 
   eslint-visitor-keys@4.2.1: {}
 
-  eslint@9.34.0(jiti@2.4.2):
+  eslint@9.35.0(jiti@2.4.2):
     dependencies:
-      '@eslint-community/eslint-utils': 4.7.0(eslint@9.34.0(jiti@2.4.2))
+      '@eslint-community/eslint-utils': 4.9.0(eslint@9.35.0(jiti@2.4.2))
       '@eslint-community/regexpp': 4.12.1
       '@eslint/config-array': 0.21.0
       '@eslint/config-helpers': 0.3.1
       '@eslint/core': 0.15.2
       '@eslint/eslintrc': 3.3.1
-      '@eslint/js': 9.34.0
+      '@eslint/js': 9.35.0
       '@eslint/plugin-kit': 0.3.5
-      '@humanfs/node': 0.16.6
+      '@humanfs/node': 0.16.7
       '@humanwhocodes/module-importer': 1.0.1
       '@humanwhocodes/retry': 0.4.3
       '@types/estree': 1.0.8
@@ -10532,7 +10532,7 @@ snapshots:
       pirates: 4.0.6
       ts-interface-checker: 0.1.13
 
-  supports-color@10.2.0: {}
+  supports-color@10.2.2: {}
 
   supports-color@5.5.0:
     dependencies:
@@ -10678,13 +10678,13 @@ snapshots:
 
   type-fest@4.41.0: {}
 
-  typescript-eslint@8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2):
+  typescript-eslint@8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2):
     dependencies:
-      '@typescript-eslint/eslint-plugin': 8.41.0(@typescript-eslint/parser@8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)
-      '@typescript-eslint/parser': 8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)
+      '@typescript-eslint/eslint-plugin': 8.41.0(@typescript-eslint/parser@8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
+      '@typescript-eslint/parser': 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
       '@typescript-eslint/typescript-estree': 8.41.0(typescript@5.9.2)
-      '@typescript-eslint/utils': 8.41.0(eslint@9.34.0(jiti@2.4.2))(typescript@5.9.2)
-      eslint: 9.34.0(jiti@2.4.2)
+      '@typescript-eslint/utils': 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
+      eslint: 9.35.0(jiti@2.4.2)
       typescript: 5.9.2
     transitivePeerDependencies:
       - supports-color
@@ -11115,13 +11115,13 @@ snapshots:
 
   wrap-ansi@8.1.0:
     dependencies:
-      ansi-styles: 6.2.1
+      ansi-styles: 6.2.3
       string-width: 5.1.2
       strip-ansi: 7.1.0
 
   wrap-ansi@9.0.0:
     dependencies:
-      ansi-styles: 6.2.1
+      ansi-styles: 6.2.3
       string-width: 7.2.0
       strip-ansi: 7.1.0
 

From 8e5abe9f4791bb3af4ebf329e25e726ba75f9357 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Mon, 8 Sep 2025 22:54:14 +0000
Subject: [PATCH 16/37] Bump dotenv from 17.2.1 to 17.2.2 (#1255)

---
 package.json   |  2 +-
 pnpm-lock.yaml | 10 +++++-----
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/package.json b/package.json
index 410eff580..c8676b455 100644
--- a/package.json
+++ b/package.json
@@ -29,7 +29,7 @@
 		"@solidjs/meta": "^0.29.4",
 		"@solidjs/router": "^0.15.3",
 		"@solidjs/start": "^1.1.7",
-		"dotenv": "^17.2.1",
+		"dotenv": "^17.2.2",
 		"glob": "^11.0.3",
 		"gray-matter": "^4.0.3",
 		"postcss": "^8.5.6",
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index ae49d5bf2..1f82aec1e 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -42,8 +42,8 @@ importers:
         specifier: ^1.1.7
         version: 1.1.7(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       dotenv:
-        specifier: ^17.2.1
-        version: 17.2.1
+        specifier: ^17.2.2
+        version: 17.2.2
       glob:
         specifier: ^11.0.3
         version: 11.0.3
@@ -2409,8 +2409,8 @@ packages:
     resolution: {integrity: sha512-uBq4egWHTcTt33a72vpSG0z3HnPuIl6NqYcTrKEg2azoEyl2hpW0zqlxysq2pK9HlDIHyHyakeYaYnSAwd8bow==}
     engines: {node: '>=12'}
 
-  dotenv@17.2.1:
-    resolution: {integrity: sha512-kQhDYKZecqnM0fCnzI5eIv5L4cAe/iRI+HqMbO/hbRdTAeXDG+M9FjipUxNfbARuEg4iHIbhnhs78BCHNbSxEQ==}
+  dotenv@17.2.2:
+    resolution: {integrity: sha512-Sf2LSQP+bOlhKWWyhFsn0UsfdK/kCWRv1iuA2gXAwt3dyNabr6QSj00I2V10pidqz69soatm9ZwZvpQMTIOd5Q==}
     engines: {node: '>=12'}
 
   dunder-proto@1.0.1:
@@ -7781,7 +7781,7 @@ snapshots:
 
   dotenv@16.6.1: {}
 
-  dotenv@17.2.1: {}
+  dotenv@17.2.2: {}
 
   dunder-proto@1.0.1:
     dependencies:

From 62261b17c5c3a095e813d5605a1ccd7742575d80 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Tue, 9 Sep 2025 13:54:19 -0700
Subject: [PATCH 17/37] Bump @typescript-eslint/parser from 8.41.0 to 8.43.0
 (#1257)

---
 package.json   |   2 +-
 pnpm-lock.yaml | 105 +++++++++++++++++++++++++++++++++++--------------
 2 files changed, 76 insertions(+), 31 deletions(-)

diff --git a/package.json b/package.json
index c8676b455..fbe7781b6 100644
--- a/package.json
+++ b/package.json
@@ -48,7 +48,7 @@
 		"@tailwindcss/typography": "^0.5.16",
 		"@types/node": "^24.3.1",
 		"@typescript-eslint/eslint-plugin": "^8.41.0",
-		"@typescript-eslint/parser": "^8.41.0",
+		"@typescript-eslint/parser": "^8.43.0",
 		"autoprefixer": "^10.4.21",
 		"eslint": "^9.35.0",
 		"eslint-plugin-solid": "^0.14.5",
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index 1f82aec1e..8044b4fca 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -92,10 +92,10 @@ importers:
         version: 24.3.1
       '@typescript-eslint/eslint-plugin':
         specifier: ^8.41.0
-        version: 8.41.0(@typescript-eslint/parser@8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
+        version: 8.41.0(@typescript-eslint/parser@8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
       '@typescript-eslint/parser':
-        specifier: ^8.41.0
-        version: 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
+        specifier: ^8.43.0
+        version: 8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
       autoprefixer:
         specifier: ^10.4.21
         version: 10.4.21(postcss@8.5.6)
@@ -1610,6 +1610,13 @@ packages:
       eslint: ^8.57.0 || ^9.0.0
       typescript: '>=4.8.4 <6.0.0'
 
+  '@typescript-eslint/parser@8.43.0':
+    resolution: {integrity: sha512-B7RIQiTsCBBmY+yW4+ILd6mF5h1FUwJsVvpqkrgpszYifetQ2Ke+Z4u6aZh0CblkUGIdR59iYVyXqqZGkZ3aBw==}
+    engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
+    peerDependencies:
+      eslint: ^8.57.0 || ^9.0.0
+      typescript: '>=4.8.4 <6.0.0'
+
   '@typescript-eslint/project-service@8.34.0':
     resolution: {integrity: sha512-iEgDALRf970/B2YExmtPMPF54NenZUf4xpL3wsCRx/lgjz6ul/l13R81ozP/ZNuXfnLCS+oPmG7JIxfdNYKELw==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
@@ -1622,8 +1629,8 @@ packages:
     peerDependencies:
       typescript: '>=4.8.4 <6.0.0'
 
-  '@typescript-eslint/project-service@8.42.0':
-    resolution: {integrity: sha512-vfVpLHAhbPjilrabtOSNcUDmBboQNrJUiNAGoImkZKnMjs2TIcWG33s4Ds0wY3/50aZmTMqJa6PiwkwezaAklg==}
+  '@typescript-eslint/project-service@8.43.0':
+    resolution: {integrity: sha512-htB/+D/BIGoNTQYffZw4uM4NzzuolCoaA/BusuSIcC8YjmBYQioew5VUZAYdAETPjeed0hqCaW7EHg+Robq8uw==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
     peerDependencies:
       typescript: '>=4.8.4 <6.0.0'
@@ -1636,6 +1643,10 @@ packages:
     resolution: {integrity: sha512-n6m05bXn/Cd6DZDGyrpXrELCPVaTnLdPToyhBoFkLIMznRUQUEQdSp96s/pcWSQdqOhrgR1mzJ+yItK7T+WPMQ==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
 
+  '@typescript-eslint/scope-manager@8.43.0':
+    resolution: {integrity: sha512-daSWlQ87ZhsjrbMLvpuuMAt3y4ba57AuvadcR7f3nl8eS3BjRc8L9VLxFLk92RL5xdXOg6IQ+qKjjqNEimGuAg==}
+    engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
+
   '@typescript-eslint/tsconfig-utils@8.34.0':
     resolution: {integrity: sha512-+W9VYHKFIzA5cBeooqQxqNriAP0QeQ7xTiDuIOr71hzgffm3EL2hxwWBIIj4GuofIbKxGNarpKqIq6Q6YrShOA==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
@@ -1648,8 +1659,8 @@ packages:
     peerDependencies:
       typescript: '>=4.8.4 <6.0.0'
 
-  '@typescript-eslint/tsconfig-utils@8.42.0':
-    resolution: {integrity: sha512-kHeFUOdwAJfUmYKjR3CLgZSglGHjbNTi1H8sTYRYV2xX6eNz4RyJ2LIgsDLKf8Yi0/GL1WZAC/DgZBeBft8QAQ==}
+  '@typescript-eslint/tsconfig-utils@8.43.0':
+    resolution: {integrity: sha512-ALC2prjZcj2YqqL5X/bwWQmHA2em6/94GcbB/KKu5SX3EBDOsqztmmX1kMkvAJHzxk7TazKzJfFiEIagNV3qEA==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
     peerDependencies:
       typescript: '>=4.8.4 <6.0.0'
@@ -1669,8 +1680,8 @@ packages:
     resolution: {integrity: sha512-9EwxsWdVqh42afLbHP90n2VdHaWU/oWgbH2P0CfcNfdKL7CuKpwMQGjwev56vWu9cSKU7FWSu6r9zck6CVfnag==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
 
-  '@typescript-eslint/types@8.42.0':
-    resolution: {integrity: sha512-LdtAWMiFmbRLNP7JNeY0SqEtJvGMYSzfiWBSmx+VSZ1CH+1zyl8Mmw1TT39OrtsRvIYShjJWzTDMPWZJCpwBlw==}
+  '@typescript-eslint/types@8.43.0':
+    resolution: {integrity: sha512-vQ2FZaxJpydjSZJKiSW/LJsabFFvV7KgLC5DiLhkBcykhQj8iK9BOaDmQt74nnKdLvceM5xmhaTF+pLekrxEkw==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
 
   '@typescript-eslint/typescript-estree@8.34.0':
@@ -1685,8 +1696,8 @@ packages:
     peerDependencies:
       typescript: '>=4.8.4 <6.0.0'
 
-  '@typescript-eslint/typescript-estree@8.42.0':
-    resolution: {integrity: sha512-ku/uYtT4QXY8sl9EDJETD27o3Ewdi72hcXg1ah/kkUgBvAYHLwj2ofswFFNXS+FL5G+AGkxBtvGt8pFBHKlHsQ==}
+  '@typescript-eslint/typescript-estree@8.43.0':
+    resolution: {integrity: sha512-7Vv6zlAhPb+cvEpP06WXXy/ZByph9iL6BQRBDj4kmBsW98AqEeQHlj/13X+sZOrKSo9/rNKH4Ul4f6EICREFdw==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
     peerDependencies:
       typescript: '>=4.8.4 <6.0.0'
@@ -1713,8 +1724,8 @@ packages:
     resolution: {integrity: sha512-+GeGMebMCy0elMNg67LRNoVnUFPIm37iu5CmHESVx56/9Jsfdpsvbv605DQ81Pi/x11IdKUsS5nzgTYbCQU9fg==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
 
-  '@typescript-eslint/visitor-keys@8.42.0':
-    resolution: {integrity: sha512-3WbiuzoEowaEn8RSnhJBrxSwX8ULYE9CXaPepS2C2W3NSA5NNIvBaslpBSBElPq0UGr0xVJlXFWOAKIkyylydQ==}
+  '@typescript-eslint/visitor-keys@8.43.0':
+    resolution: {integrity: sha512-T+S1KqRD4sg/bHfLwrpF/K3gQLBM1n7Rp7OjjikjTEssI2YJzQpi5WXoynOaQ93ERIuq3O8RBTOUYDKszUCEHw==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
 
   '@typescript/vfs@1.6.1':
@@ -6869,6 +6880,23 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
+  '@typescript-eslint/eslint-plugin@8.41.0(@typescript-eslint/parser@8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)':
+    dependencies:
+      '@eslint-community/regexpp': 4.12.1
+      '@typescript-eslint/parser': 8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
+      '@typescript-eslint/scope-manager': 8.41.0
+      '@typescript-eslint/type-utils': 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
+      '@typescript-eslint/utils': 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
+      '@typescript-eslint/visitor-keys': 8.41.0
+      eslint: 9.35.0(jiti@2.4.2)
+      graphemer: 1.4.0
+      ignore: 7.0.5
+      natural-compare: 1.4.0
+      ts-api-utils: 2.1.0(typescript@5.9.2)
+      typescript: 5.9.2
+    transitivePeerDependencies:
+      - supports-color
+
   '@typescript-eslint/parser@8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)':
     dependencies:
       '@typescript-eslint/scope-manager': 8.41.0
@@ -6881,10 +6909,22 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
+  '@typescript-eslint/parser@8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)':
+    dependencies:
+      '@typescript-eslint/scope-manager': 8.43.0
+      '@typescript-eslint/types': 8.43.0
+      '@typescript-eslint/typescript-estree': 8.43.0(typescript@5.9.2)
+      '@typescript-eslint/visitor-keys': 8.43.0
+      debug: 4.4.1
+      eslint: 9.35.0(jiti@2.4.2)
+      typescript: 5.9.2
+    transitivePeerDependencies:
+      - supports-color
+
   '@typescript-eslint/project-service@8.34.0(typescript@5.9.2)':
     dependencies:
-      '@typescript-eslint/tsconfig-utils': 8.41.0(typescript@5.9.2)
-      '@typescript-eslint/types': 8.42.0
+      '@typescript-eslint/tsconfig-utils': 8.43.0(typescript@5.9.2)
+      '@typescript-eslint/types': 8.43.0
       debug: 4.4.1
       typescript: 5.9.2
     transitivePeerDependencies:
@@ -6892,17 +6932,17 @@ snapshots:
 
   '@typescript-eslint/project-service@8.41.0(typescript@5.9.2)':
     dependencies:
-      '@typescript-eslint/tsconfig-utils': 8.41.0(typescript@5.9.2)
-      '@typescript-eslint/types': 8.42.0
+      '@typescript-eslint/tsconfig-utils': 8.43.0(typescript@5.9.2)
+      '@typescript-eslint/types': 8.43.0
       debug: 4.4.1
       typescript: 5.9.2
     transitivePeerDependencies:
       - supports-color
 
-  '@typescript-eslint/project-service@8.42.0(typescript@5.9.2)':
+  '@typescript-eslint/project-service@8.43.0(typescript@5.9.2)':
     dependencies:
-      '@typescript-eslint/tsconfig-utils': 8.42.0(typescript@5.9.2)
-      '@typescript-eslint/types': 8.42.0
+      '@typescript-eslint/tsconfig-utils': 8.43.0(typescript@5.9.2)
+      '@typescript-eslint/types': 8.43.0
       debug: 4.4.1
       typescript: 5.9.2
     transitivePeerDependencies:
@@ -6918,6 +6958,11 @@ snapshots:
       '@typescript-eslint/types': 8.41.0
       '@typescript-eslint/visitor-keys': 8.41.0
 
+  '@typescript-eslint/scope-manager@8.43.0':
+    dependencies:
+      '@typescript-eslint/types': 8.43.0
+      '@typescript-eslint/visitor-keys': 8.43.0
+
   '@typescript-eslint/tsconfig-utils@8.34.0(typescript@5.9.2)':
     dependencies:
       typescript: 5.9.2
@@ -6926,7 +6971,7 @@ snapshots:
     dependencies:
       typescript: 5.9.2
 
-  '@typescript-eslint/tsconfig-utils@8.42.0(typescript@5.9.2)':
+  '@typescript-eslint/tsconfig-utils@8.43.0(typescript@5.9.2)':
     dependencies:
       typescript: 5.9.2
 
@@ -6946,7 +6991,7 @@ snapshots:
 
   '@typescript-eslint/types@8.41.0': {}
 
-  '@typescript-eslint/types@8.42.0': {}
+  '@typescript-eslint/types@8.43.0': {}
 
   '@typescript-eslint/typescript-estree@8.34.0(typescript@5.9.2)':
     dependencies:
@@ -6980,12 +7025,12 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
-  '@typescript-eslint/typescript-estree@8.42.0(typescript@5.9.2)':
+  '@typescript-eslint/typescript-estree@8.43.0(typescript@5.9.2)':
     dependencies:
-      '@typescript-eslint/project-service': 8.42.0(typescript@5.9.2)
-      '@typescript-eslint/tsconfig-utils': 8.42.0(typescript@5.9.2)
-      '@typescript-eslint/types': 8.42.0
-      '@typescript-eslint/visitor-keys': 8.42.0
+      '@typescript-eslint/project-service': 8.43.0(typescript@5.9.2)
+      '@typescript-eslint/tsconfig-utils': 8.43.0(typescript@5.9.2)
+      '@typescript-eslint/types': 8.43.0
+      '@typescript-eslint/visitor-keys': 8.43.0
       debug: 4.4.1
       fast-glob: 3.3.3
       is-glob: 4.0.3
@@ -7028,9 +7073,9 @@ snapshots:
       '@typescript-eslint/types': 8.41.0
       eslint-visitor-keys: 4.2.1
 
-  '@typescript-eslint/visitor-keys@8.42.0':
+  '@typescript-eslint/visitor-keys@8.43.0':
     dependencies:
-      '@typescript-eslint/types': 8.42.0
+      '@typescript-eslint/types': 8.43.0
       eslint-visitor-keys: 4.2.1
 
   '@typescript/vfs@1.6.1(typescript@5.9.2)':
@@ -7723,7 +7768,7 @@ snapshots:
 
   detective-typescript@14.0.0(typescript@5.9.2):
     dependencies:
-      '@typescript-eslint/typescript-estree': 8.42.0(typescript@5.9.2)
+      '@typescript-eslint/typescript-estree': 8.43.0(typescript@5.9.2)
       ast-module-types: 6.0.1
       node-source-walk: 7.0.1
       typescript: 5.9.2

From f0660630cc38f47940a0e23f17157f9ce9cb51bd Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Tue, 9 Sep 2025 13:58:47 -0700
Subject: [PATCH 18/37] Bump typescript-eslint from 8.41.0 to 8.43.0 (#1258)

---
 package.json   |  2 +-
 pnpm-lock.yaml | 90 ++++++++++++++++++++++++++++++++------------------
 2 files changed, 59 insertions(+), 33 deletions(-)

diff --git a/package.json b/package.json
index fbe7781b6..55d3cfa39 100644
--- a/package.json
+++ b/package.json
@@ -57,7 +57,7 @@
 		"prettier-plugin-tailwindcss": "^0.6.14",
 		"tailwindcss": "^3.4.17",
 		"typescript": "^5.9.2",
-		"typescript-eslint": "^8.41.0",
+		"typescript-eslint": "^8.43.0",
 		"vite": "^6.3.5"
 	},
 	"engines": {
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index 8044b4fca..ad69dfc87 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -121,8 +121,8 @@ importers:
         specifier: ^5.9.2
         version: 5.9.2
       typescript-eslint:
-        specifier: ^8.41.0
-        version: 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
+        specifier: ^8.43.0
+        version: 8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
       vite:
         specifier: ^6.3.5
         version: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
@@ -1603,10 +1603,11 @@ packages:
       eslint: ^8.57.0 || ^9.0.0
       typescript: '>=4.8.4 <6.0.0'
 
-  '@typescript-eslint/parser@8.41.0':
-    resolution: {integrity: sha512-gTtSdWX9xiMPA/7MV9STjJOOYtWwIJIYxkQxnSV1U3xcE+mnJSH3f6zI0RYP+ew66WSlZ5ed+h0VCxsvdC1jJg==}
+  '@typescript-eslint/eslint-plugin@8.43.0':
+    resolution: {integrity: sha512-8tg+gt7ENL7KewsKMKDHXR1vm8tt9eMxjJBYINf6swonlWgkYn5NwyIgXpbbDxTNU5DgpDFfj95prcTq2clIQQ==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
     peerDependencies:
+      '@typescript-eslint/parser': ^8.43.0
       eslint: ^8.57.0 || ^9.0.0
       typescript: '>=4.8.4 <6.0.0'
 
@@ -1672,6 +1673,13 @@ packages:
       eslint: ^8.57.0 || ^9.0.0
       typescript: '>=4.8.4 <6.0.0'
 
+  '@typescript-eslint/type-utils@8.43.0':
+    resolution: {integrity: sha512-qaH1uLBpBuBBuRf8c1mLJ6swOfzCXryhKND04Igr4pckzSEW9JX5Aw9AgW00kwfjWJF0kk0ps9ExKTfvXfw4Qg==}
+    engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
+    peerDependencies:
+      eslint: ^8.57.0 || ^9.0.0
+      typescript: '>=4.8.4 <6.0.0'
+
   '@typescript-eslint/types@8.34.0':
     resolution: {integrity: sha512-9V24k/paICYPniajHfJ4cuAWETnt7Ssy+R0Rbcqo5sSFr3QEZ/8TSoUi9XeXVBGXCaLtwTOKSLGcInCAvyZeMA==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
@@ -1716,6 +1724,13 @@ packages:
       eslint: ^8.57.0 || ^9.0.0
       typescript: '>=4.8.4 <6.0.0'
 
+  '@typescript-eslint/utils@8.43.0':
+    resolution: {integrity: sha512-S1/tEmkUeeswxd0GGcnwuVQPFWo8NzZTOMxCvw8BX7OMxnNae+i8Tm7REQen/SwUIPoPqfKn7EaZ+YLpiB3k9g==}
+    engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
+    peerDependencies:
+      eslint: ^8.57.0 || ^9.0.0
+      typescript: '>=4.8.4 <6.0.0'
+
   '@typescript-eslint/visitor-keys@8.34.0':
     resolution: {integrity: sha512-qHV7pW7E85A0x6qyrFn+O+q1k1p3tQCsqIZ1KZ5ESLXY57aTvUd3/a4rdPTeXisvhXn2VQG0VSKUqs8KHF2zcA==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
@@ -4716,8 +4731,8 @@ packages:
     resolution: {integrity: sha512-TeTSQ6H5YHvpqVwBRcnLDCBnDOHWYu7IvGbHT6N8AOymcr9PJGjc1GTtiWZTYg0NCgYwvnYWEkVChQAr9bjfwA==}
     engines: {node: '>=16'}
 
-  typescript-eslint@8.41.0:
-    resolution: {integrity: sha512-n66rzs5OBXW3SFSnZHr2T685q1i4ODm2nulFJhMZBotaTavsS8TrI3d7bDlRSs9yWo7HmyWrN9qDu14Qv7Y0Dw==}
+  typescript-eslint@8.43.0:
+    resolution: {integrity: sha512-FyRGJKUGvcFekRRcBKFBlAhnp4Ng8rhe8tuvvkR9OiU0gfd4vyvTRQHEckO6VDlH57jbeUQem2IpqPq9kLJH+w==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
     peerDependencies:
       eslint: ^8.57.0 || ^9.0.0
@@ -6863,10 +6878,10 @@ snapshots:
       '@types/node': 24.3.1
     optional: true
 
-  '@typescript-eslint/eslint-plugin@8.41.0(@typescript-eslint/parser@8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)':
+  '@typescript-eslint/eslint-plugin@8.41.0(@typescript-eslint/parser@8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)':
     dependencies:
       '@eslint-community/regexpp': 4.12.1
-      '@typescript-eslint/parser': 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
+      '@typescript-eslint/parser': 8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
       '@typescript-eslint/scope-manager': 8.41.0
       '@typescript-eslint/type-utils': 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
       '@typescript-eslint/utils': 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
@@ -6880,14 +6895,14 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
-  '@typescript-eslint/eslint-plugin@8.41.0(@typescript-eslint/parser@8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)':
+  '@typescript-eslint/eslint-plugin@8.43.0(@typescript-eslint/parser@8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)':
     dependencies:
       '@eslint-community/regexpp': 4.12.1
       '@typescript-eslint/parser': 8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
-      '@typescript-eslint/scope-manager': 8.41.0
-      '@typescript-eslint/type-utils': 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
-      '@typescript-eslint/utils': 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
-      '@typescript-eslint/visitor-keys': 8.41.0
+      '@typescript-eslint/scope-manager': 8.43.0
+      '@typescript-eslint/type-utils': 8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
+      '@typescript-eslint/utils': 8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
+      '@typescript-eslint/visitor-keys': 8.43.0
       eslint: 9.35.0(jiti@2.4.2)
       graphemer: 1.4.0
       ignore: 7.0.5
@@ -6897,18 +6912,6 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
-  '@typescript-eslint/parser@8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)':
-    dependencies:
-      '@typescript-eslint/scope-manager': 8.41.0
-      '@typescript-eslint/types': 8.41.0
-      '@typescript-eslint/typescript-estree': 8.41.0(typescript@5.9.2)
-      '@typescript-eslint/visitor-keys': 8.41.0
-      debug: 4.4.1
-      eslint: 9.35.0(jiti@2.4.2)
-      typescript: 5.9.2
-    transitivePeerDependencies:
-      - supports-color
-
   '@typescript-eslint/parser@8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)':
     dependencies:
       '@typescript-eslint/scope-manager': 8.43.0
@@ -6923,7 +6926,7 @@ snapshots:
 
   '@typescript-eslint/project-service@8.34.0(typescript@5.9.2)':
     dependencies:
-      '@typescript-eslint/tsconfig-utils': 8.43.0(typescript@5.9.2)
+      '@typescript-eslint/tsconfig-utils': 8.34.0(typescript@5.9.2)
       '@typescript-eslint/types': 8.43.0
       debug: 4.4.1
       typescript: 5.9.2
@@ -6932,7 +6935,7 @@ snapshots:
 
   '@typescript-eslint/project-service@8.41.0(typescript@5.9.2)':
     dependencies:
-      '@typescript-eslint/tsconfig-utils': 8.43.0(typescript@5.9.2)
+      '@typescript-eslint/tsconfig-utils': 8.41.0(typescript@5.9.2)
       '@typescript-eslint/types': 8.43.0
       debug: 4.4.1
       typescript: 5.9.2
@@ -6987,6 +6990,18 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
+  '@typescript-eslint/type-utils@8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)':
+    dependencies:
+      '@typescript-eslint/types': 8.43.0
+      '@typescript-eslint/typescript-estree': 8.43.0(typescript@5.9.2)
+      '@typescript-eslint/utils': 8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
+      debug: 4.4.1
+      eslint: 9.35.0(jiti@2.4.2)
+      ts-api-utils: 2.1.0(typescript@5.9.2)
+      typescript: 5.9.2
+    transitivePeerDependencies:
+      - supports-color
+
   '@typescript-eslint/types@8.34.0': {}
 
   '@typescript-eslint/types@8.41.0': {}
@@ -7063,6 +7078,17 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
+  '@typescript-eslint/utils@8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)':
+    dependencies:
+      '@eslint-community/eslint-utils': 4.9.0(eslint@9.35.0(jiti@2.4.2))
+      '@typescript-eslint/scope-manager': 8.43.0
+      '@typescript-eslint/types': 8.43.0
+      '@typescript-eslint/typescript-estree': 8.43.0(typescript@5.9.2)
+      eslint: 9.35.0(jiti@2.4.2)
+      typescript: 5.9.2
+    transitivePeerDependencies:
+      - supports-color
+
   '@typescript-eslint/visitor-keys@8.34.0':
     dependencies:
       '@typescript-eslint/types': 8.34.0
@@ -10723,12 +10749,12 @@ snapshots:
 
   type-fest@4.41.0: {}
 
-  typescript-eslint@8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2):
+  typescript-eslint@8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2):
     dependencies:
-      '@typescript-eslint/eslint-plugin': 8.41.0(@typescript-eslint/parser@8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
-      '@typescript-eslint/parser': 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
-      '@typescript-eslint/typescript-estree': 8.41.0(typescript@5.9.2)
-      '@typescript-eslint/utils': 8.41.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
+      '@typescript-eslint/eslint-plugin': 8.43.0(@typescript-eslint/parser@8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
+      '@typescript-eslint/parser': 8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
+      '@typescript-eslint/typescript-estree': 8.43.0(typescript@5.9.2)
+      '@typescript-eslint/utils': 8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
       eslint: 9.35.0(jiti@2.4.2)
       typescript: 5.9.2
     transitivePeerDependencies:

From 0187c050dcda9f26c83a960c6612ae5fb8a93abf Mon Sep 17 00:00:00 2001
From: Yaroslav Lapin <jlarky@gmail.com>
Date: Thu, 11 Sep 2025 11:18:21 -0600
Subject: [PATCH 19/37] remove random `;` symbol from splitProps docs (#1260)

---
 src/routes/reference/reactive-utilities/split-props.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/routes/reference/reactive-utilities/split-props.mdx b/src/routes/reference/reactive-utilities/split-props.mdx
index 3841792ce..7dfcbe18f 100644
--- a/src/routes/reference/reactive-utilities/split-props.mdx
+++ b/src/routes/reference/reactive-utilities/split-props.mdx
@@ -37,7 +37,7 @@ Because `splitProps` takes any number of arrays, we can split a props object as
 Let's say a component was passed six props:
 
 ```tsx
-;<MyComponent a={1} b={2} c={3} d={4} e={5} foo="bar" />
+<MyComponent a={1} b={2} c={3} d={4} e={5} foo="bar" />
 // ...
 
 function MyComponent(props) {

From b1e10764197b8b62ab92c9113ec771ba5c370760 Mon Sep 17 00:00:00 2001
From: Thomas <thomas.giudici@proton.me>
Date: Fri, 12 Sep 2025 16:45:47 +0200
Subject: [PATCH 20/37] Addresses #547 (#1253)

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
---
 src/routes/reference/jsx-attributes/use.mdx | 75 ++++++++++++++++++---
 1 file changed, 64 insertions(+), 11 deletions(-)

diff --git a/src/routes/reference/jsx-attributes/use.mdx b/src/routes/reference/jsx-attributes/use.mdx
index b622f82c2..ebfc504f4 100644
--- a/src/routes/reference/jsx-attributes/use.mdx
+++ b/src/routes/reference/jsx-attributes/use.mdx
@@ -3,38 +3,91 @@ title: use:*
 order: 5
 ---
 
-These are custom directives. In a sense this is just syntax sugar over ref but allows us to easily attach multiple directives to a single element. A directive is a function with the following signature:
+Custom directives attach reusable behavior to DOM elements, acting as syntactic sugar over `ref`. They’re ideal for complex DOM interactions like scrolling, tooltips, or form handling, which are cumbersome to repeat in JSX.
+
+A directive is a function with the following signature
 
 ```ts
-function directive(element: Element, accessor: () => any): void
+function directive(element: HTMLElement, accessor: Accessor<any>): void;
 ```
 
 Directive functions are called at render time but before being added to the DOM. You can do whatever you'd like in them including create signals, effects, register clean-up etc.
 
+## Example
+
+A `model` directive for two-way data binding
+
 ```tsx
-const [name, setName] = createSignal("")
+import type { Accessor, Signal } from "solid-js";
 
-function model(el, value) {
-	const [field, setField] = value()
-	createRenderEffect(() => (el.value = field()))
-	el.addEventListener("input", (e) => setField(e.target.value))
-};
+function model(element: HTMLInputElement, value: Accessor<Signal<string>>) {
+	const [field, setField] = value();
+	createRenderEffect(() => (element.value = field()));
+	element.addEventListener("input", ({ target }) => setField(target.value));
+}
+
+const [name, setName] = createSignal("");
 
-<input type="text" use:model={[name, setName]} />
+<input type="text" use:model={[name, setName]} />;
 ```
 
-To register with TypeScript extend the JSX namespace.
+## TypeScript Support
+
+To type custom directives, extend the `DirectiveFunctions` interface
 
 ```ts
+declare module "solid-js" {
+	namespace JSX {
+		interface DirectiveFunctions {
+			model: typeof model;
+		}
+	}
+}
+```
+
+If you just want to constrain the second argument to the directive function, you can extend the older `Directives` interface
+
+```tsx
 declare module "solid-js" {
 	namespace JSX {
 		interface Directives {
-			model: [() => any, (v: any) => any]
+			model: Signal<string>;
 		}
 	}
 }
 ```
 
+## Avoiding Tree-Shaking
+
+When importing a directive `d` from another module and using it only as `use:d`, TypeScript (via [babel-preset-typescript](https://babeljs.io/docs/babel-preset-typescript)) may remove the import, as it doesn’t recognize `use:d` as a reference to `d`.
+To prevent this:
+
+1. Use the `onlyRemoveTypeImports: true` option in `babel-preset-typescript`. For `vite-plugin-solid`, add this to `vite.config.ts`
+
+	```ts
+	import solidPlugin from "vite-plugin-solid";
+
+	export default {
+		plugins: [
+			solidPlugin({
+				typescript: { onlyRemoveTypeImports: true }
+			})
+		],
+   };
+   ```
+
+   Note: This requires consistent use of `export type` and `import type` in your codebase to avoid issues.
+
+2. Add a fake access like `false && d;` in the module
+
+	```tsx
+	import { model } from "./directives";
+	false && model; // Prevents tree-shaking
+	<input type="text" use:model={[name, setName]} />;
+	```
+
+   This is removed by bundlers like Terser, unlike a plain `model;` which may remain in the bundle.
+
 :::caution[Limitations]
 Directives only work with native HTML elements (HTML/SVG/MathML/Custom Elements).
 Directives are not forwarded and **won't work in user defined components**, such as `<MyComponent use:myinput={[..]}/>` [see also](https://github.com/solidjs/solid/discussions/722)

From 22305186400a56dabc1d70596de337c8e7afaa26 Mon Sep 17 00:00:00 2001
From: Thomas <thomas.giudici@proton.me>
Date: Sun, 14 Sep 2025 02:21:16 +0200
Subject: [PATCH 21/37] Addressed issue #1259 (#1262)

---
 old pages/guides/routing-and-navigation.mdx | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/old pages/guides/routing-and-navigation.mdx b/old pages/guides/routing-and-navigation.mdx
index 1772310ba..afaedc388 100644
--- a/old pages/guides/routing-and-navigation.mdx	
+++ b/old pages/guides/routing-and-navigation.mdx	
@@ -275,8 +275,7 @@ Instead of checking for the presence of a parameter, this allows for more comple
 ```jsx
 import { lazy } from "solid-js";
 import { render } from "solid-js/web";
-import { Router, Route } from "@solidjs/router";
-import type { SegmentValidators } from "./types";
+import { Router, Route, type MatchFilters } from "@solidjs/router";
 
 const User = lazy(() => import("./pages/User"));
 

From 6677dd29f0bbfbc6b318b1a31c5e47b436638434 Mon Sep 17 00:00:00 2001
From: WavJaby <51706075+WavJaby@users.noreply.github.com>
Date: Sun, 14 Sep 2025 08:23:32 +0800
Subject: [PATCH 22/37] Fix code example error in create-effect.mdx (#1261)

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
---
 src/routes/reference/basic-reactivity/create-effect.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/routes/reference/basic-reactivity/create-effect.mdx b/src/routes/reference/basic-reactivity/create-effect.mdx
index d93501967..8a201215e 100644
--- a/src/routes/reference/basic-reactivity/create-effect.mdx
+++ b/src/routes/reference/basic-reactivity/create-effect.mdx
@@ -35,7 +35,7 @@ const [a, setA] = createSignal(initialValue)
 // effect that depends on signal `a`
 createEffect((prevSum) => {
 	// do something with `a` and `prevSum`
-	const sum = a() + b()
+	const sum = a() + prevSum
 	if (sum !== prevSum) console.log("sum changed to", sum)
 	return sum
 }, 0)

From a9105fe9308ea78f40d437cf251aab7e935f86d0 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Tue, 16 Sep 2025 08:13:49 -0700
Subject: [PATCH 23/37] Bump zod from 4.1.5 to 4.1.8 (#1268)

---
 package.json   |  2 +-
 pnpm-lock.yaml | 10 +++++-----
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/package.json b/package.json
index 55d3cfa39..aac4931ba 100644
--- a/package.json
+++ b/package.json
@@ -39,7 +39,7 @@
 		"solid-js": "^1.9.9",
 		"solid-list": "^0.3.0",
 		"vinxi": "^0.5.7",
-		"zod": "^4.1.5"
+		"zod": "^4.1.8"
 	},
 	"devDependencies": {
 		"@eslint/js": "^9.34.0",
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index ad69dfc87..0f308e957 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -72,8 +72,8 @@ importers:
         specifier: ^0.5.7
         version: 0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
       zod:
-        specifier: ^4.1.5
-        version: 4.1.5
+        specifier: ^4.1.8
+        version: 4.1.8
     devDependencies:
       '@eslint/js':
         specifier: ^9.34.0
@@ -5162,8 +5162,8 @@ packages:
   zod@3.25.76:
     resolution: {integrity: sha512-gzUt/qt81nXsFGKIFcC3YnfEAx5NkunCfnDlvuBSSFS02bcXu4Lmea0AFIUwbLWxWPx3d9p8S5QoaujKcNQxcQ==}
 
-  zod@4.1.5:
-    resolution: {integrity: sha512-rcUUZqlLJgBC33IT3PNMgsCq6TzLQEG/Ei/KTCU0PedSWRMAXoOUN+4t/0H+Q8bdnLPdqUYnvboJT0bn/229qg==}
+  zod@4.1.8:
+    resolution: {integrity: sha512-5R1P+WwQqmmMIEACyzSvo4JXHY5WiAFHRMg+zBZKgKS+Q1viRa0C1hmUKtHltoIFKtIdki3pRxkmpP74jnNYHQ==}
 
   zwitch@2.0.4:
     resolution: {integrity: sha512-bXE4cR/kVZhKZX/RjPEflHaKVhUVl85noU3v6b8apfQEc1x4A+zBxjZ4lN8LqGd6WZ3dl98pY4o717VFmoPp+A==}
@@ -11255,6 +11255,6 @@ snapshots:
 
   zod@3.25.76: {}
 
-  zod@4.1.5: {}
+  zod@4.1.8: {}
 
   zwitch@2.0.4: {}

From c576bebadb9d3d58f54f12c84f00e234c406feb0 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Tue, 16 Sep 2025 15:14:43 +0000
Subject: [PATCH 24/37] Bump @solidjs/start from 1.1.7 to 1.2.0 (#1266)

---
 package.json   |   2 +-
 pnpm-lock.yaml | 708 ++++++++++++++++++++++---------------------------
 2 files changed, 325 insertions(+), 385 deletions(-)

diff --git a/package.json b/package.json
index aac4931ba..c137c5b1f 100644
--- a/package.json
+++ b/package.json
@@ -28,7 +28,7 @@
 		"@solid-primitives/platform": "^0.2.1",
 		"@solidjs/meta": "^0.29.4",
 		"@solidjs/router": "^0.15.3",
-		"@solidjs/start": "^1.1.7",
+		"@solidjs/start": "^1.2.0",
 		"dotenv": "^17.2.2",
 		"glob": "^11.0.3",
 		"gray-matter": "^4.0.3",
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index 0f308e957..908ccb030 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -13,7 +13,7 @@ importers:
         version: 0.13.11(solid-js@1.9.9)
       '@kobalte/solidbase':
         specifier: ^0.2.17
-        version: 0.2.17(@algolia/client-search@5.14.2)(@solidjs/start@1.1.7(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)))(@vue/compiler-sfc@3.5.16)(acorn@8.15.0)(expressive-code@0.40.2)(react@18.3.1)(search-insights@2.17.3)(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+        version: 0.2.17(@algolia/client-search@5.14.2)(@solidjs/start@1.2.0(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)))(@vue/compiler-sfc@3.5.16)(acorn@8.15.0)(expressive-code@0.40.2)(react@18.3.1)(search-insights@2.17.3)(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       '@lunariajs/core':
         specifier: ^0.1.1
         version: 0.1.1
@@ -39,8 +39,8 @@ importers:
         specifier: ^0.15.3
         version: 0.15.3(solid-js@1.9.9)
       '@solidjs/start':
-        specifier: ^1.1.7
-        version: 1.1.7(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+        specifier: ^1.2.0
+        version: 1.2.0(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       dotenv:
         specifier: ^17.2.2
         version: 17.2.2
@@ -231,16 +231,16 @@ packages:
     resolution: {integrity: sha512-ZsysZyXY4Tlx+Q53XdnOFmqwfB9QDTHYxaZYajWRoBLuLEAwI2UIbtxOjWh/cFaa9IKUlcB+DDuoskLuKu56JA==}
     engines: {node: '>=6.9.0'}
 
-  '@babel/compat-data@7.28.0':
-    resolution: {integrity: sha512-60X7qkglvrap8mn1lh2ebxXdZYtUcpd7gsmy9kLaBJ4i/WdY8PqTSdxyA8qraikqKQK5C1KRBKXqznrVapyNaw==}
+  '@babel/compat-data@7.28.4':
+    resolution: {integrity: sha512-YsmSKC29MJwf0gF8Rjjrg5LQCmyh+j/nD8/eP7f+BeoQTKYqs9RoWbjGOdy0+1Ekr68RJZMUOPVQaQisnIo4Rw==}
     engines: {node: '>=6.9.0'}
 
   '@babel/core@7.25.8':
     resolution: {integrity: sha512-Oixnb+DzmRT30qu9d3tJSQkxuygWm32DFykT4bRoORPa9hZ/L4KhVB/XiRm6KG+roIEM7DBQlmg27kw2HZkdZg==}
     engines: {node: '>=6.9.0'}
 
-  '@babel/core@7.28.3':
-    resolution: {integrity: sha512-yDBHV9kQNcr2/sUr9jghVyz9C3Y5G2zUM2H2lo+9mKv4sFgbA8s8Z9t8D1jiTkGoO/NoIfKMyKWr4s6CN23ZwQ==}
+  '@babel/core@7.28.4':
+    resolution: {integrity: sha512-2BCOP7TN8M+gVDj7/ht3hsaO/B/n5oDbiAyyvnRlNOs+u1o+JWNYTQrmpuNp1/Wq2gcFrI01JAW+paEKDMx/CA==}
     engines: {node: '>=6.9.0'}
 
   '@babel/generator@7.25.7':
@@ -331,10 +331,6 @@ packages:
     resolution: {integrity: sha512-CbkjYdsJNHFk8uqpEkpCvRs3YRp9tY6FmFY7wLMSYuGYkrdUi7r2lc4/wqsvlHoMznX3WJ9IP8giGPq68T/Y6g==}
     engines: {node: '>=6.9.0'}
 
-  '@babel/helper-string-parser@7.25.9':
-    resolution: {integrity: sha512-4A/SCr/2KLd5jrtOMFzaKjVtAei3+2r/NChoBNoZ3EyP/+GlhoaEGoWOZUmFmoITP7zOJyHIMm+DYRd8o3PvHA==}
-    engines: {node: '>=6.9.0'}
-
   '@babel/helper-string-parser@7.27.1':
     resolution: {integrity: sha512-qMlSxKbpRlAridDExk92nSobyDdpPijUq2DW6oDnUqd0iOGxmQjyqhMIihI9+zv4LPyZdRje2cavWPbCbWm3eA==}
     engines: {node: '>=6.9.0'}
@@ -343,10 +339,6 @@ packages:
     resolution: {integrity: sha512-AM6TzwYqGChO45oiuPqwL2t20/HdMC1rTPAesnBCgPCSF1x3oN9MVUwQV2iyz4xqWrctwK5RNC8LV22kaQCNYg==}
     engines: {node: '>=6.9.0'}
 
-  '@babel/helper-validator-identifier@7.25.9':
-    resolution: {integrity: sha512-Ed61U6XJc3CVRfkERJWDz4dJwKe7iLmmJsbOGu9wSloNSFttHV0I8g6UAgb7qnK5ly5bGLPd4oXZlxCdANBOWQ==}
-    engines: {node: '>=6.9.0'}
-
   '@babel/helper-validator-identifier@7.27.1':
     resolution: {integrity: sha512-D2hP9eA+Sqx1kBZgzxZh0y1trbuU+JoDkiEwqhQ36nodYqJwyEIhPSdMNd7lOm/4io72luTPWH20Yda0xOuUow==}
     engines: {node: '>=6.9.0'}
@@ -363,8 +355,8 @@ packages:
     resolution: {integrity: sha512-Sv6pASx7Esm38KQpF/U/OXLwPPrdGHNKoeblRxgZRLXnAtnkEe4ptJPDtAZM7fBLadbc1Q07kQpSiGQ0Jg6tRA==}
     engines: {node: '>=6.9.0'}
 
-  '@babel/helpers@7.28.3':
-    resolution: {integrity: sha512-PTNtvUQihsAsDHMOP5pfobP8C6CM4JWXmP8DrEIt46c3r2bf87Ua1zoqevsMo9g+tWDwgWrFP5EIxuBx5RudAw==}
+  '@babel/helpers@7.28.4':
+    resolution: {integrity: sha512-HFN59MmQXGHVyYadKLVumYsA9dBFun/ldYxipEjzA4196jpLZd8UjEEBLkbEkvfYreDqJhZxYAWFPtrfhNpj4w==}
     engines: {node: '>=6.9.0'}
 
   '@babel/highlight@7.25.7':
@@ -376,13 +368,8 @@ packages:
     engines: {node: '>=6.0.0'}
     hasBin: true
 
-  '@babel/parser@7.27.5':
-    resolution: {integrity: sha512-OsQd175SxWkGlzbny8J3K8TnnDD0N3lrIUtB92xwyRpzaenGZhxDvxN/JgU00U3CDZNj9tPuDJ5H0WS4Nt3vKg==}
-    engines: {node: '>=6.0.0'}
-    hasBin: true
-
-  '@babel/parser@7.28.3':
-    resolution: {integrity: sha512-7+Ey1mAgYqFAx2h0RuoxcQT5+MlG3GTV0TQrgr7/ZliKsm/MNDxVVutlWaziMq7wJNAz8MTqz55XLpWvva6StA==}
+  '@babel/parser@7.28.4':
+    resolution: {integrity: sha512-yZbBqeM6TkpP9du/I2pUZnJsRMGGvOuIrhjzC1AwHwW+6he4mni6Bp/m8ijn0iOuZuPI2BfkCoSRunpyjnrQKg==}
     engines: {node: '>=6.0.0'}
     hasBin: true
 
@@ -440,24 +427,20 @@ packages:
     resolution: {integrity: sha512-jatJPT1Zjqvh/1FyJs6qAHL+Dzb7sTb+xr7Q+gM1b+1oBsMsQQ4FkVKb6dFlJvLlVssqkRzV05Jzervt9yhnzg==}
     engines: {node: '>=6.9.0'}
 
-  '@babel/traverse@7.28.3':
-    resolution: {integrity: sha512-7w4kZYHneL3A6NP2nxzHvT3HCZ7puDZZjFMqDpBPECub79sTtSO5CGXDkKrTQq8ksAwfD/XI2MRFX23njdDaIQ==}
+  '@babel/traverse@7.28.4':
+    resolution: {integrity: sha512-YEzuboP2qvQavAcjgQNVgsvHIDv6ZpwXvcvjmyySP2DIMuByS/6ioU5G9pYrWHM6T2YDfc7xga9iNzYOs12CFQ==}
     engines: {node: '>=6.9.0'}
 
   '@babel/types@7.25.8':
     resolution: {integrity: sha512-JWtuCu8VQsMladxVz/P4HzHUGCAwpuqacmowgXFs5XjxIgKuNjnLokQzuVjlTvIzODaDmpjT3oxcC48vyk9EWg==}
     engines: {node: '>=6.9.0'}
 
-  '@babel/types@7.26.9':
-    resolution: {integrity: sha512-Y3IR1cRnOxOCDvMmNiym7XpXQ93iGDDPHx+Zj+NM+rg0fBaShfQLkg+hKPaZCEvg5N/LeCo4+Rj/i3FuJsIQaw==}
-    engines: {node: '>=6.9.0'}
-
   '@babel/types@7.27.6':
     resolution: {integrity: sha512-ETyHEk2VHHvl9b9jZP5IHPavHYk57EhanlRRuae9XCpb/j5bDCbPPMOBfCWhnl/7EDJz0jEMCi/RhccCE8r1+Q==}
     engines: {node: '>=6.9.0'}
 
-  '@babel/types@7.28.2':
-    resolution: {integrity: sha512-ruv7Ae4J5dUYULmeXw1gmb7rYRz57OWCPM57pHojnLq/3Z1CK2lNSLTCVjxVk1F/TZHwOZZrOWi0ur95BbLxNQ==}
+  '@babel/types@7.28.4':
+    resolution: {integrity: sha512-bkFqkLhh3pMBUQQkpVgWDWq/lqzc2678eUyDlTBhRqhCHFguYYGM0Efga7tYk4TogG/3x0EEl66/OQ+WGbWB/Q==}
     engines: {node: '>=6.9.0'}
 
   '@bprogress/core@1.1.18':
@@ -797,10 +780,6 @@ packages:
     resolution: {integrity: sha512-wgm9Ehl2jpeqP3zw/7mo3kRHFp5MEDhqAdwy1fTGkHAwnkGOVsgpvQhL8B5n1qlb01jV3n/bI0ZfZp5lWA1k4w==}
     engines: {node: '>=18.0.0'}
 
-  '@jest/schemas@29.6.3':
-    resolution: {integrity: sha512-mo5j5X+jIZmJQveBKeS/clAueipV7KgiX1vMgCxam1RNYiqE1w62n0/tJJnHtjW8ZHcQco5gY85jA3mi0L+nSA==}
-    engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0}
-
   '@jridgewell/gen-mapping@0.3.13':
     resolution: {integrity: sha512-2kkt/7niJ6MgEPxF0bYdQ6etZaA+fQvDcLKckhy1yIQOzaoKjBBjSj63/aLVjYE3qhRt5dvM+uUyfCg6UKCBbA==}
 
@@ -808,9 +787,8 @@ packages:
     resolution: {integrity: sha512-IzL8ZoEDIBRWEzlCcRhOaCupYyN5gdIK+Q6fbFdPDg6HqX6jpkItn7DFIpW9LQzXG6Df9sA7+OKnq0qlz/GaQg==}
     engines: {node: '>=6.0.0'}
 
-  '@jridgewell/gen-mapping@0.3.8':
-    resolution: {integrity: sha512-imAbBGkb+ebQyxKgzv5Hu2nmROxoDOXHh80evxdoXNOrvAnVx7zimzc1Oo5h9RlfV4vPXaE2iM5pOFbvOCClWA==}
-    engines: {node: '>=6.0.0'}
+  '@jridgewell/remapping@2.3.5':
+    resolution: {integrity: sha512-LI9u/+laYG4Ds1TDKSJW2YPrIlcVYOwi2fUC6xB43lueCjgxV4lffOCZCtYFiH6TNOX+tQKXx97T4IKHbhyHEQ==}
 
   '@jridgewell/resolve-uri@3.1.2':
     resolution: {integrity: sha512-bRISgCIjP20/tbWSPWMEi54QVPRZExkuD9lJL+UIxUKtwVJA8wW1Trb1jMs1RFXo1CBTNZ/5hpC9QvmKWdopKw==}
@@ -832,8 +810,8 @@ packages:
   '@jridgewell/trace-mapping@0.3.25':
     resolution: {integrity: sha512-vNk6aEwybGtawWmy/PzwnGDOjCkLWSD2wqvjGGAgOAwCGWySYXfYoxt00IJkTF+8Lb57DwOb3Aa0o9CApepiYQ==}
 
-  '@jridgewell/trace-mapping@0.3.30':
-    resolution: {integrity: sha512-GQ7Nw5G2lTu/BtHTKfXhKHok2WGetd4XYcVKGx00SjAk8GMwgJM3zr6zORiPGuOE+/vkc90KtTosSSvaCjKb2Q==}
+  '@jridgewell/trace-mapping@0.3.31':
+    resolution: {integrity: sha512-zzNR+SdQSDJzc8joaeP8QQoCQr8NuYx2dIIytl1QeBEZHJ9uW6hebsrYgbz8hJwUQao3TWCMtmfV8Nu1twOLAw==}
 
   '@kobalte/core@0.13.11':
     resolution: {integrity: sha512-hK7TYpdib/XDb/r/4XDBFaO9O+3ZHz4ZWryV4/3BfES+tSQVgg2IJupDnztKXB0BqbSRy/aWlHKw1SPtNPYCFQ==}
@@ -1339,9 +1317,6 @@ packages:
   '@shikijs/vscode-textmate@10.0.2':
     resolution: {integrity: sha512-83yeghZ2xxin3Nj8z1NMd/NCuca+gsYXswywDy5bHvwlWL8tpTQmzGeUuHd9FC3E/SBEMvzJRwWEOz5gGes9Qg==}
 
-  '@sinclair/typebox@0.27.8':
-    resolution: {integrity: sha512-+Fj43pSMwJs4KRrH/938Uf+uAELIgVBmQzg/q1YG10djyfA3TnrU8N8XzqCh/okZdszqBQTZf96idMfE5lnwTA==}
-
   '@sindresorhus/is@7.0.2':
     resolution: {integrity: sha512-d9xRovfKNz1SKieM0qJdO+PQonjnnIfSNWfHYnBSJ9hkjm0ZPw6HlxscDXYstp3z+7V2GOFHc+J0CYrYTjqCJw==}
     engines: {node: '>=18'}
@@ -1487,8 +1462,8 @@ packages:
     peerDependencies:
       solid-js: ^1.8.6
 
-  '@solidjs/start@1.1.7':
-    resolution: {integrity: sha512-30nUFzCpCVH7ORtHlO4ZE+VLG3g3EP+x+ceLLJBFRXIVuFQ1p203xZvVCXWqUPydtK78O5w3nIkWA/tLtF0Ybg==}
+  '@solidjs/start@1.2.0':
+    resolution: {integrity: sha512-SRv1g3R+4sxZnxCBPK1IedtLKsPhPJ7W/Yv4xEHjM4jJGPWi3ed35/yd0D5zhRK0C7zJIkZKbhnR/S3g8JUD5w==}
     peerDependencies:
       vinxi: ^0.5.7
 
@@ -1523,14 +1498,14 @@ packages:
   '@types/babel__core@7.20.5':
     resolution: {integrity: sha512-qoQprZvz5wQFJwMDqeseRXWv3rqMvhgpbXFfVyWhbx9X47POIA6i/+dXefEmZKoAgOaTdaIgNSMqMIU61yRyzA==}
 
-  '@types/babel__generator@7.6.8':
-    resolution: {integrity: sha512-ASsj+tpEDsEiFr1arWrlN6V3mdfjRMZt6LtK/Vp/kreFLnr5QH5+DhvD5nINYZXzwJvXeGq+05iUXcAzVrqWtw==}
+  '@types/babel__generator@7.27.0':
+    resolution: {integrity: sha512-ufFd2Xi92OAVPYsy+P4n7/U7e68fex0+Ee8gSG9KX7eo084CWiQ4sdxktvdl0bOPupXtVJPY19zk6EwWqUQ8lg==}
 
   '@types/babel__template@7.4.4':
     resolution: {integrity: sha512-h/NUaSyG5EyxBIp8YRxo4RMe2/qQgvyowRwVMzhYhBCONbW8PUsg4lkFMrhgZhUe5z3L3MiLDuvyJ/CaPa2A8A==}
 
-  '@types/babel__traverse@7.20.6':
-    resolution: {integrity: sha512-r1bzfrm0tomOI8g1SzvCaQHo6Lcv6zu0EA+W2kHrt8dyrHQxGzBBL4kdkzIS+jBMV+EYcMAEAqXqYaLJq5rOZg==}
+  '@types/babel__traverse@7.28.0':
+    resolution: {integrity: sha512-8PvcXf70gTDZBgt9ptxJ8elBeBjcLOAcOtoO/mPJjtji1+CdGbHgm77om1GrsPxsiE+uXIpNSK64UYaIwQXd4Q==}
 
   '@types/braces@3.0.4':
     resolution: {integrity: sha512-0WR3b8eaISjEW7RpZnclONaLFDf7buaowRHdqLp4vLj54AsSAYWfh3DRbfiYJY9XDxMgx1B4sE1Afw2PGpuHOA==}
@@ -1760,15 +1735,15 @@ packages:
     resolution: {integrity: sha512-WSN1z931BtasZJlgPp704zJFnQFRg7yzSjkm3MzAWQYe4uXFXlFr1hc5Ac2zae5/HDOz5x1/zDM5Cb54vTCnWw==}
     hasBin: true
 
-  '@vinxi/plugin-directives@0.5.0':
-    resolution: {integrity: sha512-zpgPWoul5vKbNH5GASHtHa7InwQWElmVdOexvyO4Nfvz7CeYfAAQ5/BAV01sVJPks4dfsLnBCegAgRPRykdUeA==}
+  '@vinxi/plugin-directives@0.5.1':
+    resolution: {integrity: sha512-pH/KIVBvBt7z7cXrUH/9uaqcdxjegFC7+zvkZkdOyWzs+kQD5KPf3cl8kC+5ayzXHT+OMlhGhyitytqN3cGmHg==}
     peerDependencies:
-      vinxi: ^0.5.0
+      vinxi: ^0.5.5
 
-  '@vinxi/server-components@0.5.0':
-    resolution: {integrity: sha512-2p6ZYzoqF7ZAriU0rC9KJWSX/n5qHhUBs7x04SLYzmy9lFxQNw3YHsmsA4b3aHDU+Mxw26wyFwvIbrL6eU3Gyw==}
+  '@vinxi/server-components@0.5.1':
+    resolution: {integrity: sha512-0BsG95qac3dkhfdRZxqzqYWJE4NvPL7ILlV43B6K6ho1etXWB2e5b0IxsUAUbyqpqiXM7mSRivojuXjb2G4OsQ==}
     peerDependencies:
-      vinxi: ^0.5.0
+      vinxi: ^0.5.5
 
   '@vue/compiler-core@3.5.16':
     resolution: {integrity: sha512-AOQS2eaQOaaZQoL1u+2rCJIKDruNXVBZSiUD3chnUrsoX5ZTQMaCvXlWNIfxBJuU15r1o7+mpo5223KVtIhAgQ==}
@@ -1823,8 +1798,8 @@ packages:
     peerDependencies:
       acorn: ^6.0.0 || ^7.0.0 || ^8.0.0
 
-  acorn-loose@8.4.0:
-    resolution: {integrity: sha512-M0EUka6rb+QC4l9Z3T0nJEzNOO7JcoJlYMrBlyBCiFSXRyxjLKayd4TbQs2FDRWQU1h9FR7QVNHt+PEaoNL5rQ==}
+  acorn-loose@8.5.2:
+    resolution: {integrity: sha512-PPvV6g8UGMGgjrMu+n/f9E/tCSkNQ2Y97eFvuVdJfG11+xdIeDcLyNdC8SHcrHbRqkfwLASdplyR6B6sKM1U4A==}
     engines: {node: '>=0.4.0'}
 
   acorn-typescript@1.4.13:
@@ -1832,11 +1807,6 @@ packages:
     peerDependencies:
       acorn: '>=8.9.0'
 
-  acorn@8.12.1:
-    resolution: {integrity: sha512-tcpGyI9zbizT9JbV6oYE477V6mTlXvvi0T0G3SNIYE2apm/G5huBa1+K89VGeovbg+jycCrfhl3ADxErOuO6Jg==}
-    engines: {node: '>=0.4.0'}
-    hasBin: true
-
   acorn@8.15.0:
     resolution: {integrity: sha512-NZyJarBfL7nWwIq+FDL6Zp/yHEhePMNnnJ0y3qfieCrmNvYct8uvtiV41UvlSe6apAfk0fY1FbWx+NwfmpvtTg==}
     engines: {node: '>=0.4.0'}
@@ -1872,10 +1842,6 @@ packages:
     resolution: {integrity: sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==}
     engines: {node: '>=8'}
 
-  ansi-styles@5.2.0:
-    resolution: {integrity: sha512-Cxwpt2SfTzTtXcfOlzGEee8O+c+MmUgGrNiBcXnuWxuFJHe6a5Hz7qwhwe5OgaSYI0IJvkLqWX1ASG+cJOkEiA==}
-    engines: {node: '>=10'}
-
   ansi-styles@6.2.3:
     resolution: {integrity: sha512-4Dj6M28JB+oAH8kFkTLUo+a2jwOFkuqb3yucU0CANcRRUbxS0cP0nZYCGjcc3BNXwRIsUVmDGgzawme7zvJHvg==}
     engines: {node: '>=12'}
@@ -1939,15 +1905,19 @@ packages:
   babel-dead-code-elimination@1.0.10:
     resolution: {integrity: sha512-DV5bdJZTzZ0zn0DC24v3jD7Mnidh6xhKa4GfKCbq3sfW8kaWhDdZjP3i81geA8T33tdYqWKw4D3fVv0CwEgKVA==}
 
-  babel-plugin-jsx-dom-expressions@0.39.2:
-    resolution: {integrity: sha512-rCkSYFuLl5/XD+BXjZk1XxFAsIBgNe9WZ7xBHjQV1dBliI64kO+EWktAD3b6Bj/SXk+LpVXFyMVydhnI35svWQ==}
+  babel-plugin-jsx-dom-expressions@0.40.1:
+    resolution: {integrity: sha512-b4iHuirqK7RgaMzB2Lsl7MqrlDgQtVRSSazyrmx7wB3T759ggGjod5Rkok5MfHjQXhR7tRPmdwoeGPqBnW2KfA==}
     peerDependencies:
       '@babel/core': ^7.20.12
 
-  babel-preset-solid@1.9.2:
-    resolution: {integrity: sha512-rWx968GIDghgFStRDQaoqelGspEm9rgPci/yNzNPFlkzMqHaL2yob+t7BbzyqZw5b9/llkzjqUNIOybT9Z9mcg==}
+  babel-preset-solid@1.9.9:
+    resolution: {integrity: sha512-pCnxWrciluXCeli/dj5PIEHgbNzim3evtTn12snjqqg8QZWJNMjH1AWIp4iG/tbVjqQ72aBEymMSagvmgxubXw==}
     peerDependencies:
       '@babel/core': ^7.0.0
+      solid-js: ^1.9.8
+    peerDependenciesMeta:
+      solid-js:
+        optional: true
 
   bail@2.0.2:
     resolution: {integrity: sha512-0xO6mYd7JB2YesxDKplafRpsiOzPt9V02ddPCLbY1xYGPOX24NTyN50qnUxgCPcSoYMhKpAuBTjQoRZCAkUDRw==}
@@ -1961,6 +1931,10 @@ packages:
   base64-js@1.5.1:
     resolution: {integrity: sha512-AKpaYlHn8t4SVbOHCy+b5+KKgvR4vrsD8vbvrbiQJps7fKDTkjkDry6ji0rUJjC0kzbNePLwzxq8iypo41qeWA==}
 
+  baseline-browser-mapping@2.8.4:
+    resolution: {integrity: sha512-L+YvJwGAgwJBV1p6ffpSTa2KRc69EeeYGYjRVWKs0GKrK+LON0GC0gV+rKSNtALEDvMDqkvCFq9r1r94/Gjwxw==}
+    hasBin: true
+
   bcp-47-match@2.0.3:
     resolution: {integrity: sha512-JtTezzbAibu8G0R9op9zb3vcWZd9JF6M0xOYGPn0fNCd7wOpRB1mU2mH9T8gaBGbAAyIIVgB2G7xG0GP98zMAQ==}
 
@@ -1993,8 +1967,8 @@ packages:
     engines: {node: ^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || >=13.7}
     hasBin: true
 
-  browserslist@4.25.3:
-    resolution: {integrity: sha512-cDGv1kkDI4/0e5yON9yM5G/0A5u8sf5TnmdX5C9qHzI9PPu++sQ9zjm1k9NiOrf3riY4OkK0zSGqfvJyJsgCBQ==}
+  browserslist@4.26.0:
+    resolution: {integrity: sha512-P9go2WrP9FiPwLv3zqRD/Uoxo0RSHjzFCiQz7d4vbmwNqQFo9T9WCeP/Qn5EbcKQY6DBbkxEXNcpJOmncNrb7A==}
     engines: {node: ^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || >=13.7}
     hasBin: true
 
@@ -2049,8 +2023,8 @@ packages:
   caniuse-lite@1.0.30001722:
     resolution: {integrity: sha512-DCQHBBZtiK6JVkAGw7drvAMK0Q0POD/xZvEmDp6baiMMP6QXXk9HpD6mNYBZWhOPG6LvIDb82ITqtWjhDckHCA==}
 
-  caniuse-lite@1.0.30001735:
-    resolution: {integrity: sha512-EV/laoX7Wq2J9TQlyIXRxTJqIw4sxfXS4OYgudGxBYRuTv0q7AM6yMEpU/Vo1I94thg9U6EZ2NfZx9GJq83u7w==}
+  caniuse-lite@1.0.30001741:
+    resolution: {integrity: sha512-QGUGitqsc8ARjLdgAfxETDhRbJ0REsP6O3I96TAth/mVjh2cYzN2u+3AzPP3aVSm2FehEItaJw1xd+IGBXWeSw==}
 
   ccount@2.0.1:
     resolution: {integrity: sha512-eyrF0jiFpY+3drT6383f1qhkbGsLSifNAjA61IUjZjmLCWjItY6LB9ft9YhoDgwfmclB2zhu51Lc7+95b8NRAg==}
@@ -2302,6 +2276,15 @@ packages:
       supports-color:
         optional: true
 
+  debug@4.4.3:
+    resolution: {integrity: sha512-RGwwWnwQvkVfavKVt22FGLw+xYSdzARwm0ru6DhTVA3umU5hZc28V3kO4stgYryrTlLpuvgI9GiijltAjNbcqA==}
+    engines: {node: '>=6.0'}
+    peerDependencies:
+      supports-color: '*'
+    peerDependenciesMeta:
+      supports-color:
+        optional: true
+
   decache@4.6.2:
     resolution: {integrity: sha512-2LPqkLeu8XWHU8qNCS3kcF6sCcb5zIzvWaAHYSvPfwhdd7mHuah29NssMzrTYyHN4F5oFy2ko9OBYxegtU0FEw==}
 
@@ -2399,10 +2382,6 @@ packages:
   didyoumean@1.2.2:
     resolution: {integrity: sha512-gxtyfqMg7GKyhQmb056K7M3xszy/myH8w+B4RT+QXBQsvAOdc3XymqDDPHx1BgPgsdAA5SIifona89YtRATDzw==}
 
-  diff-sequences@29.6.3:
-    resolution: {integrity: sha512-EjePK1srD3P08o2j4f0ExnylqRs5B9tJjcp9t1krH2qRi8CCdsYfwe9JgSLurFBWwq4uOlipzfk5fHNvwFKr8Q==}
-    engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0}
-
   diff@8.0.2:
     resolution: {integrity: sha512-sSuxWU5j5SR9QQji/o2qMvqRNYRDOcBTgsJ/DeCf4iSN4gW+gNMXM7wFIP+fdXZxoNiAnHUTGjCr+TSWXdRDKg==}
     engines: {node: '>=0.3.1'}
@@ -2455,8 +2434,8 @@ packages:
   electron-to-chromium@1.5.166:
     resolution: {integrity: sha512-QPWqHL0BglzPYyJJ1zSSmwFFL6MFXhbACOCcsCdUMCkzPdS9/OIBVxg516X/Ado2qwAq8k0nJJ7phQPCqiaFAw==}
 
-  electron-to-chromium@1.5.207:
-    resolution: {integrity: sha512-mryFrrL/GXDTmAtIVMVf+eIXM09BBPlO5IQ7lUyKmK8d+A4VpRGG+M3ofoVef6qyF8s60rJei8ymlJxjUA8Faw==}
+  electron-to-chromium@1.5.218:
+    resolution: {integrity: sha512-uwwdN0TUHs8u6iRgN8vKeWZMRll4gBkz+QMqdS7DDe49uiK68/UX92lFb61oiFPrpYZNeZIqa4bA7O6Aiasnzg==}
 
   emoji-regex-xs@1.0.0:
     resolution: {integrity: sha512-LRlerrMYoIDrT6jgpeZ2YYl/L8EulRTt5hQcYjy5AInh7HWXKimpqx68aknBFpGL2+/IcogTcaydJEgaTmOpDg==}
@@ -2488,6 +2467,10 @@ packages:
     resolution: {integrity: sha512-V0hjH4dGPh9Ao5p0MoRY6BVqtwCjhz6vI5LT8AJ55H+4g9/4vbHx1I54fS0XuclLhDHArPQCiMjDxjaL8fPxhw==}
     engines: {node: '>=0.12'}
 
+  entities@6.0.1:
+    resolution: {integrity: sha512-aN97NXWF6AWBTahfVOIrB/NShkzi5H7F9r1s9mD3cDj4Ko5f2qhhVoYMibXF7GlLveb/D2ioWay8lxI97Ven3g==}
+    engines: {node: '>=0.12'}
+
   env-paths@3.0.0:
     resolution: {integrity: sha512-dtJUTepzMW3Lm/NPxRf3wP4642UWhjL2sQxc+ym2YMj1m/H2zDNQOlezafzkHwn6sMstjHTwG6iQQsctDW/b1A==}
     engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
@@ -2702,16 +2685,17 @@ packages:
   fd-slicer@1.1.0:
     resolution: {integrity: sha512-cE1qsB/VwyQozZ+q1dGxR8LBYNZeofhEdUNGSMbQD3Gw2lAzX9Zb3uIU6Ebc/Fmyjo9AWWfnn0AUCHqtevs/8g==}
 
-  fdir@6.4.3:
-    resolution: {integrity: sha512-PMXmW2y1hDDfTSRc9gaXIuCCRpuoz3Kaz8cUelp3smouvfT632ozg2vrT6lJsHKKOF59YLbOGfAWGUcKEfRMQw==}
+  fdir@6.4.6:
+    resolution: {integrity: sha512-hiFoqpyZcfNm1yc4u8oWCf9A2c4D3QjCrks3zmoVKVxpQRzmPNar1hUJcBG2RQHvEVGDN+Jm81ZheVLAQMK6+w==}
     peerDependencies:
       picomatch: ^3 || ^4
     peerDependenciesMeta:
       picomatch:
         optional: true
 
-  fdir@6.4.6:
-    resolution: {integrity: sha512-hiFoqpyZcfNm1yc4u8oWCf9A2c4D3QjCrks3zmoVKVxpQRzmPNar1hUJcBG2RQHvEVGDN+Jm81ZheVLAQMK6+w==}
+  fdir@6.5.0:
+    resolution: {integrity: sha512-tIbYtZbucOs0BRGqPJkshJUYdL+SDH7dVM8gjy+ERp3WAUjLEFJE+02kanyHtwjWOnwrKYBiwAmM0p4kLJAnXg==}
+    engines: {node: '>=12.0.0'}
     peerDependencies:
       picomatch: ^3 || ^4
     peerDependenciesMeta:
@@ -2989,8 +2973,8 @@ packages:
     resolution: {integrity: sha512-ztqyC3kLto0e9WbNp0aeP+M3kTt+nbaIveGmUxAtZa+8iFgKLUOD4YKM5j+f3QD89bra7UeumolZHKuOXnTmeQ==}
     engines: {node: '>=8'}
 
-  html-to-image@1.11.11:
-    resolution: {integrity: sha512-9gux8QhvjRO/erSnDPv28noDZcPZmYE7e1vFsBLKLlRlKDSqNJYebj6Qz1TGd5lsRV+X+xYyjCKjuZdABinWjA==}
+  html-to-image@1.11.13:
+    resolution: {integrity: sha512-cuOPoI7WApyhBElTTb9oqsawRvZ0rHhaHwghRLlTuffoD1B2aDemlCruLeZrUIIdvG7gs9xeELEPm6PhuASqrg==}
 
   html-void-elements@3.0.0:
     resolution: {integrity: sha512-bEqo66MRXsUGxWHV5IP0PUiAWwoEjba4VCzg0LjFJBpchPaTfyfCKTG6bc5F8ucKec3q5y6qOdGyYTSBEvhCrg==}
@@ -3200,14 +3184,6 @@ packages:
     resolution: {integrity: sha512-zptv57P3GpL+O0I7VdMJNBZCu+BPHVQUk55Ft8/QCJjTVxrnJHuVuX/0Bl2A6/+2oyR/ZMEuFKwmzqqZ/U5nPQ==}
     engines: {node: 20 || >=22}
 
-  jest-diff@29.7.0:
-    resolution: {integrity: sha512-LMIgiIrhigmPrs03JHpxUh2yISK3vLFPkAodPeo0+BuF7wA2FoQbkEg1u8gBYBThncu7e1oEDUfIXVuTqLRUjw==}
-    engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0}
-
-  jest-get-type@29.6.3:
-    resolution: {integrity: sha512-zrteXnqYxfQh7l5FHyL38jL39di8H8rHoecLH3JNxH3BwOrBsNeabdap5e0I23lD4HHI8W5VFBZqG4Eaq5LNcw==}
-    engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0}
-
   jiti@1.21.6:
     resolution: {integrity: sha512-2yTgeWTWzMWkHu6Jp9NKgePDaYHbntiwvYuuJLbbN9vl7DC9DvXKOB2BC3ZZ92D3cvV/aflH0osDfwpHepQ53w==}
     hasBin: true
@@ -3725,6 +3701,9 @@ packages:
   node-releases@2.0.19:
     resolution: {integrity: sha512-xxOWJsBKtzAq7DY0J+DTzuz58K8e7sJbdgwkbMWQe8UYB6ekmsQ45q0M/tJDsGaZmbC+l7n57UV8Hl5tHxO9uw==}
 
+  node-releases@2.0.21:
+    resolution: {integrity: sha512-5b0pgg78U3hwXkCM8Z9b2FJdPZlr9Psr9V2gQPESdGHqbntyFJKFW4r5TeWGFzafGY3hzs1JC62VEQMbl1JFkw==}
+
   node-source-walk@7.0.1:
     resolution: {integrity: sha512-3VW/8JpPqPvnJvseXowjZcirPisssnBuDikk6JIZ8jQzF7KJQX52iPFX4RYYxLycYH7IbMRSPUOga/esVjy5Yg==}
     engines: {node: '>=18'}
@@ -3870,6 +3849,9 @@ packages:
   parse5@7.2.0:
     resolution: {integrity: sha512-ZkDsAOcxsUMZ4Lz5fVciOehNcJ+Gb8gTzcA4yl3wnc273BAybYWrQ+Ks/OjCjSEpjvQkDSeZbybK9qj2VHHdGA==}
 
+  parse5@7.3.0:
+    resolution: {integrity: sha512-IInvU7fabl34qmi9gY8XOVxhYyMyuH2xUNpb2q8/Y+7552KlejkRvqvD19nMoUW/uQGGbqNpA6Tufu5FL5BZgw==}
+
   parseurl@1.3.3:
     resolution: {integrity: sha512-CiyeOxFT/JZyN5m0z9PfXw4SCBJ6Sygz1Dpl0wqjlhDEGGBP1GnsUVEL0p63hoG1fcj3fHynXi9NYO4nWOL+qQ==}
     engines: {node: '>= 0.8'}
@@ -3931,6 +3913,10 @@ packages:
     resolution: {integrity: sha512-M7BAV6Rlcy5u+m6oPhAPFgJTzAioX/6B0DxyvDlo9l8+T3nLKbrczg2WLUyzd45L8RqfUMyGPzekbMvX2Ldkwg==}
     engines: {node: '>=12'}
 
+  picomatch@4.0.3:
+    resolution: {integrity: sha512-5gTmgEY/sqK6gFXLIsQNH19lWb4ebPDLA4SdLP7dsWkIXHWlG66oPuVvXSGFPppYZz8ZDZq0dYYrbHfBCVUb1Q==}
+    engines: {node: '>=12'}
+
   pify@2.3.0:
     resolution: {integrity: sha512-udgsAY+fTnvv7kI7aaxbqwWNb0AHiB0qBO89PZKPkoTmGOgdbrHDKD+0B2X4uTfJ/FT1R09r9gTsjUjNJotuog==}
     engines: {node: '>=0.10.0'}
@@ -4081,10 +4067,6 @@ packages:
     resolution: {integrity: sha512-mQUvGU6aUFQ+rNvTIAcZuWGRT9a6f6Yrg9bHs4ImKF+HZCEK+plBvnAZYSIQztknZF2qnzNtr6F8s0+IuptdlQ==}
     engines: {node: ^14.13.1 || >=16.0.0}
 
-  pretty-format@29.7.0:
-    resolution: {integrity: sha512-Pdlw/oPxN+aXdmM9R00JVC9WVFoCLTKJvDVLgmJ+qAffBMxsV85l/Lu7sNx4zSzPyoL2euImuEwHhOXdEgNFZQ==}
-    engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0}
-
   process-nextick-args@2.0.1:
     resolution: {integrity: sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag==}
 
@@ -4131,9 +4113,6 @@ packages:
   rc9@2.1.2:
     resolution: {integrity: sha512-btXCnMmRIBINM2LDZoEmOogIZU7Qe7zn4BpomSKZ/ykbLObuBdvG+mFq11DL6fjH1DRwHhrlgtYWG96bJiC7Cg==}
 
-  react-is@18.3.1:
-    resolution: {integrity: sha512-/LLMVyas0ljjAtoYiPqYiL8VWXzUUdThrmU5+n20DZv+a+ClRoevUzw5JxU+Ieh5/c87ytoTBV9G1FiKfNJdmg==}
-
   react@18.3.1:
     resolution: {integrity: sha512-wS+hAgJShR0KhEvPJArfuPVN1+Hz1t0Y6n5jLrGQbkb4urgPE/0Rve+1kMB1v/oWgHgm4WIcV+i7F2pTVj+2iQ==}
     engines: {node: '>=0.10.0'}
@@ -4171,8 +4150,8 @@ packages:
     resolution: {integrity: sha512-GDhwkLfywWL2s6vEjyhri+eXmfH6j1L7JE27WhqLeYzoh/A3DBaYGEj2H/HFZCn/kMfim73FXxEJTw06WtxQwg==}
     engines: {node: '>= 14.18.0'}
 
-  recast@0.23.9:
-    resolution: {integrity: sha512-Hx/BGIbwj+Des3+xy5uAtAbdCyqK9y9wbBcDFDYanLS9JnMqf7OeF87HQwUimE87OEc72mr6tkKUKMBBL+hF9Q==}
+  recast@0.23.11:
+    resolution: {integrity: sha512-YTUo+Flmw4ZXiWfQKGcwwc11KnoRAYgzAE2E7mXKCjSviTKShtxBsN6YUUBB2gtaBzKzeKunxhUwNHQuRryhWA==}
     engines: {node: '>= 4'}
 
   recma-build-jsx@1.0.0:
@@ -4348,21 +4327,17 @@ packages:
   serialize-javascript@6.0.2:
     resolution: {integrity: sha512-Saa1xPByTTq2gdeFZYLLo+RFE35NHZkAbqZeWNd3BpzppeVisAqpDjcp8dyf6uIvEqJRd46jemmyA4iFIeVk8g==}
 
-  seroval-plugins@1.1.1:
-    resolution: {integrity: sha512-qNSy1+nUj7hsCOon7AO4wdAIo9P0jrzAMp18XhiOzA6/uO5TKtP7ScozVJ8T293oRIvi5wyCHSM4TrJo/c/GJA==}
-    engines: {node: '>=10'}
-    peerDependencies:
-      seroval: ^1.0
-
   seroval-plugins@1.3.2:
     resolution: {integrity: sha512-0QvCV2lM3aj/U3YozDiVwx9zpH0q8A60CTWIv4Jszj/givcudPb48B+rkU5D51NJ0pTpweGMttHjboPa9/zoIQ==}
     engines: {node: '>=10'}
     peerDependencies:
       seroval: ^1.0
 
-  seroval@1.1.1:
-    resolution: {integrity: sha512-rqEO6FZk8mv7Hyv4UCj3FD3b6Waqft605TLfsCe/BiaylRpyyMC0b+uA5TJKawX3KzMrdi3wsLbCaLplrQmBvQ==}
+  seroval-plugins@1.3.3:
+    resolution: {integrity: sha512-16OL3NnUBw8JG1jBLUoZJsLnQq0n5Ua6aHalhJK4fMQkz1lqR7Osz1sA30trBtd9VUDc2NgkuRCn8+/pBwqZ+w==}
     engines: {node: '>=10'}
+    peerDependencies:
+      seroval: ^1.0
 
   seroval@1.3.2:
     resolution: {integrity: sha512-RbcPH1n5cfwKrru7v7+zrZvjLurgHhGyso3HTyGtRivGWgYjbOmGuivCQaORNELjNONoK35nj28EoWul9sb1zQ==}
@@ -4475,8 +4450,8 @@ packages:
     peerDependencies:
       solid-js: ^1.3
 
-  solid-use@0.9.0:
-    resolution: {integrity: sha512-8TGwB4m3qQ7qKo8Lg0pi/ZyyGVmQIjC4sPyxRCH7VPds0BzSsT734PhP3jhR6zMJxoYHM+uoivjq0XdpzXeOJg==}
+  solid-use@0.9.1:
+    resolution: {integrity: sha512-UwvXDVPlrrbj/9ewG9ys5uL2IO4jSiwys2KPzK4zsnAcmEl7iDafZWW1Mo4BSEWOmQCGK6IvpmGHo1aou8iOFw==}
     engines: {node: '>=10'}
     peerDependencies:
       solid-js: ^1.7
@@ -4657,14 +4632,14 @@ packages:
   tinyexec@0.3.2:
     resolution: {integrity: sha512-KQQR9yN7R5+OSwaK0XQoj22pwHoTlgYqmUscPYoknOoWCWfj/5/ABTMRi69FrKU5ffPVh5QcFikpWJI/P1ocHA==}
 
-  tinyglobby@0.2.12:
-    resolution: {integrity: sha512-qkf4trmKSIiMTs/E63cxH+ojC2unam7rJ0WrauAzpT3ECNTxGRMlaXxVbfxMUC/w0LaYk6jQ4y/nGR9uBO3tww==}
-    engines: {node: '>=12.0.0'}
-
   tinyglobby@0.2.14:
     resolution: {integrity: sha512-tX5e7OM1HnYr2+a2C/4V0htOcSQcoSTH9KgJnVvNm5zm/cyEWKJ7j7YutsH9CxMdtOkkLFy2AHrMci9IM8IPZQ==}
     engines: {node: '>=12.0.0'}
 
+  tinyglobby@0.2.15:
+    resolution: {integrity: sha512-j2Zq4NyQYG5XMST4cbs02Ak8iJUdxRM0XI5QyxXuZOzKOINmWurp3smXu3y5wDcJrptwpSjgXHzIQxR0omXljQ==}
+    engines: {node: '>=12.0.0'}
+
   tmp-promise@3.0.3:
     resolution: {integrity: sha512-RwM7MoPojPxsOBYnyd2hy0bxtIlVrihNs9pj5SUvY8Zz1sQcQG2tG1hSr8PDxfgEB8RNKDhqbIlroIarSNDNsQ==}
 
@@ -4709,9 +4684,6 @@ packages:
   ts-interface-checker@0.1.13:
     resolution: {integrity: sha512-Y/arvbn+rrz3JCKl9C4kVNfTfSm2/mEp5FSz5EsZSANGPSlQrpRI5M4PKF+mJnE52jOO90PnPSc3Ur3bTQw0gA==}
 
-  tslib@2.8.0:
-    resolution: {integrity: sha512-jWVzBLplnCmoaTr13V9dYbiQ99wvZRd0vNWaDRg+aVYRcjDF3nDksxFDE/+fkXnKhpnUUkmx5pK/v8mCtLVqZA==}
-
   tslib@2.8.1:
     resolution: {integrity: sha512-oJFu94HQb+KVduSUQL7wnpmqnfmLsOA/nAh6b6EH0wCEoK0/mPeXU6c3wKDV83MkOuHPRHtSXKKU99IBazS/2w==}
 
@@ -4969,8 +4941,8 @@ packages:
     resolution: {integrity: sha512-0/A9rDy9P7cJ+8w1c9WD9V//9Wj15Ce2MPz8Ri6032usz+NfePxx5AcN3bN+r6ZL6jEo066/yNYB3tn4pQEx+A==}
     hasBin: true
 
-  validate-html-nesting@1.2.2:
-    resolution: {integrity: sha512-hGdgQozCsQJMyfK5urgFcWEqsSSrK63Awe0t/IMR0bZ0QMtnuaiHzThW81guu3qx9abLi99NEuiaN6P9gVYsNg==}
+  validate-html-nesting@1.2.3:
+    resolution: {integrity: sha512-kdkWdCl6eCeLlRShJKbjVOU2kFKxMF8Ghu50n+crEoyx+VKm3FxAxF9z4DCy6+bbTOqNW0+jcIYRnjoIRzigRw==}
 
   validate-npm-package-license@3.0.4:
     resolution: {integrity: sha512-DpKm2Ui/xN7/HQKCtpZxoRWBhZ9Z0kqtygG8XCgNQ8ZlDnxuQmWhj566j8fN4Cu3/JmbhsDo7fcAJq4s9h27Ew==}
@@ -4988,12 +4960,12 @@ packages:
     resolution: {integrity: sha512-8+xsAx/+J+QENGV2igI29u1/gvlFKeXYBAsIk1OOzt9USmLxyaqBHf+GvkiZ8QgPTFP9OyA2w+TuPynyushr7g==}
     hasBin: true
 
-  vite-plugin-solid@2.11.2:
-    resolution: {integrity: sha512-/OXVasW5OIRSFXnqzMgm8X3hPvf+JTbGecjQhmk7QnbDFq4hqdLssuYAWw9GsJGfzUPiMHM3ME2Y2XHPsTWmkw==}
+  vite-plugin-solid@2.11.8:
+    resolution: {integrity: sha512-hFrCxBfv3B1BmFqnJF4JOCYpjrmi/zwyeKjcomQ0khh8HFyQ8SbuBWQ7zGojfrz6HUOBFrJBNySDi/JgAHytWg==}
     peerDependencies:
       '@testing-library/jest-dom': ^5.16.6 || ^5.17.0 || ^6.*
       solid-js: ^1.7.2
-      vite: ^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0
+      vite: ^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0
     peerDependenciesMeta:
       '@testing-library/jest-dom':
         optional: true
@@ -5038,10 +5010,10 @@ packages:
       yaml:
         optional: true
 
-  vitefu@1.0.5:
-    resolution: {integrity: sha512-h4Vflt9gxODPFNGPwp4zAMZRpZR7eslzwH2c5hn5kNZ5rhnKyRJ50U+yGCdc2IRaBs8O4haIgLNGrV5CrpMsCA==}
+  vitefu@1.1.1:
+    resolution: {integrity: sha512-B/Fegf3i8zh0yFbpzZ21amWzHmuNlLlmJT6n7bu5e+pCHUKQIfXSYokrqOBGEMMe9UG2sostKQF9mml/vYaWJQ==}
     peerDependencies:
-      vite: ^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0
+      vite: ^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0-beta.0
     peerDependenciesMeta:
       vite:
         optional: true
@@ -5308,7 +5280,7 @@ snapshots:
 
   '@babel/compat-data@7.25.8': {}
 
-  '@babel/compat-data@7.28.0': {}
+  '@babel/compat-data@7.28.4': {}
 
   '@babel/core@7.25.8':
     dependencies:
@@ -5330,20 +5302,20 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
-  '@babel/core@7.28.3':
+  '@babel/core@7.28.4':
     dependencies:
-      '@ampproject/remapping': 2.3.0
       '@babel/code-frame': 7.27.1
       '@babel/generator': 7.28.3
       '@babel/helper-compilation-targets': 7.27.2
-      '@babel/helper-module-transforms': 7.28.3(@babel/core@7.28.3)
-      '@babel/helpers': 7.28.3
-      '@babel/parser': 7.28.3
+      '@babel/helper-module-transforms': 7.28.3(@babel/core@7.28.4)
+      '@babel/helpers': 7.28.4
+      '@babel/parser': 7.28.4
       '@babel/template': 7.27.2
-      '@babel/traverse': 7.28.3
-      '@babel/types': 7.28.2
+      '@babel/traverse': 7.28.4
+      '@babel/types': 7.28.4
+      '@jridgewell/remapping': 2.3.5
       convert-source-map: 2.0.0
-      debug: 4.4.1
+      debug: 4.4.3
       gensync: 1.0.0-beta.2
       json5: 2.2.3
       semver: 6.3.1
@@ -5352,22 +5324,22 @@ snapshots:
 
   '@babel/generator@7.25.7':
     dependencies:
-      '@babel/types': 7.25.8
+      '@babel/types': 7.28.4
       '@jridgewell/gen-mapping': 0.3.5
       '@jridgewell/trace-mapping': 0.3.25
       jsesc: 3.0.2
 
   '@babel/generator@7.28.3':
     dependencies:
-      '@babel/parser': 7.28.3
-      '@babel/types': 7.28.2
+      '@babel/parser': 7.28.4
+      '@babel/types': 7.28.4
       '@jridgewell/gen-mapping': 0.3.13
-      '@jridgewell/trace-mapping': 0.3.30
+      '@jridgewell/trace-mapping': 0.3.31
       jsesc: 3.1.0
 
   '@babel/helper-annotate-as-pure@7.27.3':
     dependencies:
-      '@babel/types': 7.28.2
+      '@babel/types': 7.28.4
 
   '@babel/helper-compilation-targets@7.25.7':
     dependencies:
@@ -5379,21 +5351,21 @@ snapshots:
 
   '@babel/helper-compilation-targets@7.27.2':
     dependencies:
-      '@babel/compat-data': 7.28.0
+      '@babel/compat-data': 7.28.4
       '@babel/helper-validator-option': 7.27.1
-      browserslist: 4.25.3
+      browserslist: 4.26.0
       lru-cache: 5.1.1
       semver: 6.3.1
 
-  '@babel/helper-create-class-features-plugin@7.28.3(@babel/core@7.28.3)':
+  '@babel/helper-create-class-features-plugin@7.28.3(@babel/core@7.28.4)':
     dependencies:
-      '@babel/core': 7.28.3
+      '@babel/core': 7.28.4
       '@babel/helper-annotate-as-pure': 7.27.3
       '@babel/helper-member-expression-to-functions': 7.27.1
       '@babel/helper-optimise-call-expression': 7.27.1
-      '@babel/helper-replace-supers': 7.27.1(@babel/core@7.28.3)
+      '@babel/helper-replace-supers': 7.27.1(@babel/core@7.28.4)
       '@babel/helper-skip-transparent-expression-wrappers': 7.27.1
-      '@babel/traverse': 7.28.3
+      '@babel/traverse': 7.28.4
       semver: 6.3.1
     transitivePeerDependencies:
       - supports-color
@@ -5402,26 +5374,26 @@ snapshots:
 
   '@babel/helper-member-expression-to-functions@7.27.1':
     dependencies:
-      '@babel/traverse': 7.28.3
-      '@babel/types': 7.28.2
+      '@babel/traverse': 7.28.4
+      '@babel/types': 7.28.4
     transitivePeerDependencies:
       - supports-color
 
   '@babel/helper-module-imports@7.18.6':
     dependencies:
-      '@babel/types': 7.25.8
+      '@babel/types': 7.28.4
 
   '@babel/helper-module-imports@7.25.7':
     dependencies:
-      '@babel/traverse': 7.25.7
-      '@babel/types': 7.25.8
+      '@babel/traverse': 7.28.4
+      '@babel/types': 7.28.4
     transitivePeerDependencies:
       - supports-color
 
   '@babel/helper-module-imports@7.27.1':
     dependencies:
-      '@babel/traverse': 7.28.3
-      '@babel/types': 7.28.2
+      '@babel/traverse': 7.28.4
+      '@babel/types': 7.28.4
     transitivePeerDependencies:
       - supports-color
 
@@ -5431,60 +5403,56 @@ snapshots:
       '@babel/helper-module-imports': 7.25.7
       '@babel/helper-simple-access': 7.25.7
       '@babel/helper-validator-identifier': 7.25.7
-      '@babel/traverse': 7.25.7
+      '@babel/traverse': 7.28.4
     transitivePeerDependencies:
       - supports-color
 
-  '@babel/helper-module-transforms@7.28.3(@babel/core@7.28.3)':
+  '@babel/helper-module-transforms@7.28.3(@babel/core@7.28.4)':
     dependencies:
-      '@babel/core': 7.28.3
+      '@babel/core': 7.28.4
       '@babel/helper-module-imports': 7.27.1
       '@babel/helper-validator-identifier': 7.27.1
-      '@babel/traverse': 7.28.3
+      '@babel/traverse': 7.28.4
     transitivePeerDependencies:
       - supports-color
 
   '@babel/helper-optimise-call-expression@7.27.1':
     dependencies:
-      '@babel/types': 7.28.2
+      '@babel/types': 7.28.4
 
   '@babel/helper-plugin-utils@7.25.7': {}
 
   '@babel/helper-plugin-utils@7.27.1': {}
 
-  '@babel/helper-replace-supers@7.27.1(@babel/core@7.28.3)':
+  '@babel/helper-replace-supers@7.27.1(@babel/core@7.28.4)':
     dependencies:
-      '@babel/core': 7.28.3
+      '@babel/core': 7.28.4
       '@babel/helper-member-expression-to-functions': 7.27.1
       '@babel/helper-optimise-call-expression': 7.27.1
-      '@babel/traverse': 7.28.3
+      '@babel/traverse': 7.28.4
     transitivePeerDependencies:
       - supports-color
 
   '@babel/helper-simple-access@7.25.7':
     dependencies:
-      '@babel/traverse': 7.25.7
-      '@babel/types': 7.25.8
+      '@babel/traverse': 7.28.4
+      '@babel/types': 7.28.4
     transitivePeerDependencies:
       - supports-color
 
   '@babel/helper-skip-transparent-expression-wrappers@7.27.1':
     dependencies:
-      '@babel/traverse': 7.28.3
-      '@babel/types': 7.28.2
+      '@babel/traverse': 7.28.4
+      '@babel/types': 7.28.4
     transitivePeerDependencies:
       - supports-color
 
   '@babel/helper-string-parser@7.25.7': {}
 
-  '@babel/helper-string-parser@7.25.9': {}
-
   '@babel/helper-string-parser@7.27.1': {}
 
   '@babel/helper-validator-identifier@7.25.7': {}
 
-  '@babel/helper-validator-identifier@7.25.9': {}
-
   '@babel/helper-validator-identifier@7.27.1': {}
 
   '@babel/helper-validator-option@7.25.7': {}
@@ -5493,41 +5461,37 @@ snapshots:
 
   '@babel/helpers@7.25.7':
     dependencies:
-      '@babel/template': 7.25.7
-      '@babel/types': 7.25.8
+      '@babel/template': 7.27.2
+      '@babel/types': 7.28.4
 
-  '@babel/helpers@7.28.3':
+  '@babel/helpers@7.28.4':
     dependencies:
       '@babel/template': 7.27.2
-      '@babel/types': 7.28.2
+      '@babel/types': 7.28.4
 
   '@babel/highlight@7.25.7':
     dependencies:
-      '@babel/helper-validator-identifier': 7.25.7
+      '@babel/helper-validator-identifier': 7.27.1
       chalk: 2.4.2
       js-tokens: 4.0.0
       picocolors: 1.1.1
 
   '@babel/parser@7.25.8':
     dependencies:
-      '@babel/types': 7.25.8
+      '@babel/types': 7.28.4
 
-  '@babel/parser@7.27.5':
+  '@babel/parser@7.28.4':
     dependencies:
-      '@babel/types': 7.27.6
-
-  '@babel/parser@7.28.3':
-    dependencies:
-      '@babel/types': 7.28.2
+      '@babel/types': 7.28.4
 
   '@babel/plugin-syntax-jsx@7.25.7(@babel/core@7.25.8)':
     dependencies:
       '@babel/core': 7.25.8
       '@babel/helper-plugin-utils': 7.25.7
 
-  '@babel/plugin-syntax-jsx@7.27.1(@babel/core@7.28.3)':
+  '@babel/plugin-syntax-jsx@7.27.1(@babel/core@7.28.4)':
     dependencies:
-      '@babel/core': 7.28.3
+      '@babel/core': 7.28.4
       '@babel/helper-plugin-utils': 7.27.1
 
   '@babel/plugin-syntax-typescript@7.25.7(@babel/core@7.25.8)':
@@ -5535,74 +5499,74 @@ snapshots:
       '@babel/core': 7.25.8
       '@babel/helper-plugin-utils': 7.25.7
 
-  '@babel/plugin-syntax-typescript@7.27.1(@babel/core@7.28.3)':
+  '@babel/plugin-syntax-typescript@7.27.1(@babel/core@7.28.4)':
     dependencies:
-      '@babel/core': 7.28.3
+      '@babel/core': 7.28.4
       '@babel/helper-plugin-utils': 7.27.1
 
-  '@babel/plugin-transform-modules-commonjs@7.27.1(@babel/core@7.28.3)':
+  '@babel/plugin-transform-modules-commonjs@7.27.1(@babel/core@7.28.4)':
     dependencies:
-      '@babel/core': 7.28.3
-      '@babel/helper-module-transforms': 7.28.3(@babel/core@7.28.3)
+      '@babel/core': 7.28.4
+      '@babel/helper-module-transforms': 7.28.3(@babel/core@7.28.4)
       '@babel/helper-plugin-utils': 7.27.1
     transitivePeerDependencies:
       - supports-color
 
-  '@babel/plugin-transform-typescript@7.28.0(@babel/core@7.28.3)':
+  '@babel/plugin-transform-typescript@7.28.0(@babel/core@7.28.4)':
     dependencies:
-      '@babel/core': 7.28.3
+      '@babel/core': 7.28.4
       '@babel/helper-annotate-as-pure': 7.27.3
-      '@babel/helper-create-class-features-plugin': 7.28.3(@babel/core@7.28.3)
+      '@babel/helper-create-class-features-plugin': 7.28.3(@babel/core@7.28.4)
       '@babel/helper-plugin-utils': 7.27.1
       '@babel/helper-skip-transparent-expression-wrappers': 7.27.1
-      '@babel/plugin-syntax-typescript': 7.27.1(@babel/core@7.28.3)
+      '@babel/plugin-syntax-typescript': 7.27.1(@babel/core@7.28.4)
     transitivePeerDependencies:
       - supports-color
 
-  '@babel/preset-typescript@7.27.1(@babel/core@7.28.3)':
+  '@babel/preset-typescript@7.27.1(@babel/core@7.28.4)':
     dependencies:
-      '@babel/core': 7.28.3
+      '@babel/core': 7.28.4
       '@babel/helper-plugin-utils': 7.27.1
       '@babel/helper-validator-option': 7.27.1
-      '@babel/plugin-syntax-jsx': 7.27.1(@babel/core@7.28.3)
-      '@babel/plugin-transform-modules-commonjs': 7.27.1(@babel/core@7.28.3)
-      '@babel/plugin-transform-typescript': 7.28.0(@babel/core@7.28.3)
+      '@babel/plugin-syntax-jsx': 7.27.1(@babel/core@7.28.4)
+      '@babel/plugin-transform-modules-commonjs': 7.27.1(@babel/core@7.28.4)
+      '@babel/plugin-transform-typescript': 7.28.0(@babel/core@7.28.4)
     transitivePeerDependencies:
       - supports-color
 
   '@babel/template@7.25.7':
     dependencies:
-      '@babel/code-frame': 7.25.7
-      '@babel/parser': 7.25.8
-      '@babel/types': 7.25.8
+      '@babel/code-frame': 7.27.1
+      '@babel/parser': 7.28.4
+      '@babel/types': 7.28.4
 
   '@babel/template@7.27.2':
     dependencies:
       '@babel/code-frame': 7.27.1
-      '@babel/parser': 7.28.3
-      '@babel/types': 7.28.2
+      '@babel/parser': 7.28.4
+      '@babel/types': 7.28.4
 
   '@babel/traverse@7.25.7':
     dependencies:
-      '@babel/code-frame': 7.25.7
+      '@babel/code-frame': 7.27.1
       '@babel/generator': 7.25.7
-      '@babel/parser': 7.25.8
-      '@babel/template': 7.25.7
-      '@babel/types': 7.25.8
+      '@babel/parser': 7.28.4
+      '@babel/template': 7.27.2
+      '@babel/types': 7.28.4
       debug: 4.4.1
       globals: 11.12.0
     transitivePeerDependencies:
       - supports-color
 
-  '@babel/traverse@7.28.3':
+  '@babel/traverse@7.28.4':
     dependencies:
       '@babel/code-frame': 7.27.1
       '@babel/generator': 7.28.3
       '@babel/helper-globals': 7.28.0
-      '@babel/parser': 7.28.3
+      '@babel/parser': 7.28.4
       '@babel/template': 7.27.2
-      '@babel/types': 7.28.2
-      debug: 4.4.1
+      '@babel/types': 7.28.4
+      debug: 4.4.3
     transitivePeerDependencies:
       - supports-color
 
@@ -5612,17 +5576,12 @@ snapshots:
       '@babel/helper-validator-identifier': 7.25.7
       to-fast-properties: 2.0.0
 
-  '@babel/types@7.26.9':
-    dependencies:
-      '@babel/helper-string-parser': 7.25.9
-      '@babel/helper-validator-identifier': 7.25.9
-
   '@babel/types@7.27.6':
     dependencies:
       '@babel/helper-string-parser': 7.27.1
       '@babel/helper-validator-identifier': 7.27.1
 
-  '@babel/types@7.28.2':
+  '@babel/types@7.28.4':
     dependencies:
       '@babel/helper-string-parser': 7.27.1
       '@babel/helper-validator-identifier': 7.27.1
@@ -5918,14 +5877,10 @@ snapshots:
     dependencies:
       minipass: 7.1.2
 
-  '@jest/schemas@29.6.3':
-    dependencies:
-      '@sinclair/typebox': 0.27.8
-
   '@jridgewell/gen-mapping@0.3.13':
     dependencies:
       '@jridgewell/sourcemap-codec': 1.5.5
-      '@jridgewell/trace-mapping': 0.3.30
+      '@jridgewell/trace-mapping': 0.3.31
 
   '@jridgewell/gen-mapping@0.3.5':
     dependencies:
@@ -5933,11 +5888,10 @@ snapshots:
       '@jridgewell/sourcemap-codec': 1.5.0
       '@jridgewell/trace-mapping': 0.3.25
 
-  '@jridgewell/gen-mapping@0.3.8':
+  '@jridgewell/remapping@2.3.5':
     dependencies:
-      '@jridgewell/set-array': 1.2.1
-      '@jridgewell/sourcemap-codec': 1.5.0
-      '@jridgewell/trace-mapping': 0.3.25
+      '@jridgewell/gen-mapping': 0.3.13
+      '@jridgewell/trace-mapping': 0.3.31
 
   '@jridgewell/resolve-uri@3.1.2': {}
 
@@ -5945,8 +5899,8 @@ snapshots:
 
   '@jridgewell/source-map@0.3.6':
     dependencies:
-      '@jridgewell/gen-mapping': 0.3.8
-      '@jridgewell/trace-mapping': 0.3.25
+      '@jridgewell/gen-mapping': 0.3.13
+      '@jridgewell/trace-mapping': 0.3.31
 
   '@jridgewell/sourcemap-codec@1.5.0': {}
 
@@ -5957,7 +5911,7 @@ snapshots:
       '@jridgewell/resolve-uri': 3.1.2
       '@jridgewell/sourcemap-codec': 1.5.0
 
-  '@jridgewell/trace-mapping@0.3.30':
+  '@jridgewell/trace-mapping@0.3.31':
     dependencies:
       '@jridgewell/resolve-uri': 3.1.2
       '@jridgewell/sourcemap-codec': 1.5.5
@@ -5974,7 +5928,7 @@ snapshots:
       solid-presence: 0.1.8(solid-js@1.9.9)
       solid-prevent-scroll: 0.1.10(solid-js@1.9.9)
 
-  '@kobalte/solidbase@0.2.17(@algolia/client-search@5.14.2)(@solidjs/start@1.1.7(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)))(@vue/compiler-sfc@3.5.16)(acorn@8.15.0)(expressive-code@0.40.2)(react@18.3.1)(search-insights@2.17.3)(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
+  '@kobalte/solidbase@0.2.17(@algolia/client-search@5.14.2)(@solidjs/start@1.2.0(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)))(@vue/compiler-sfc@3.5.16)(acorn@8.15.0)(expressive-code@0.40.2)(react@18.3.1)(search-insights@2.17.3)(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
       '@alloc/quick-lru': 5.2.0
       '@bprogress/core': 1.1.18
@@ -5999,7 +5953,7 @@ snapshots:
       '@solid-primitives/storage': 4.3.1(solid-js@1.9.9)
       '@solidjs/meta': 0.29.4(solid-js@1.9.9)
       '@solidjs/router': 0.15.3(solid-js@1.9.9)
-      '@solidjs/start': 1.1.7(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      '@solidjs/start': 1.2.0(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       cross-spawn: 7.0.3
       esast-util-from-js: 2.0.1
       estree-util-value-to-estree: 3.2.1
@@ -6182,7 +6136,7 @@ snapshots:
 
   '@netlify/zip-it-and-ship-it@12.1.4(rollup@4.43.0)':
     dependencies:
-      '@babel/parser': 7.27.5
+      '@babel/parser': 7.28.4
       '@babel/types': 7.27.6
       '@netlify/binary-info': 1.0.0
       '@netlify/serverless-functions-api': 2.1.1
@@ -6401,10 +6355,10 @@ snapshots:
       '@rollup/pluginutils': 5.1.4(rollup@4.43.0)
       commondir: 1.0.1
       estree-walker: 2.0.2
-      fdir: 6.4.6(picomatch@4.0.2)
+      fdir: 6.5.0(picomatch@4.0.3)
       is-reference: 1.2.1
       magic-string: 0.30.17
-      picomatch: 4.0.2
+      picomatch: 4.0.3
     optionalDependencies:
       rollup: 4.43.0
 
@@ -6451,7 +6405,7 @@ snapshots:
     dependencies:
       '@types/estree': 1.0.8
       estree-walker: 2.0.2
-      picomatch: 4.0.2
+      picomatch: 4.0.3
     optionalDependencies:
       rollup: 4.43.0
 
@@ -6581,8 +6535,6 @@ snapshots:
 
   '@shikijs/vscode-textmate@10.0.2': {}
 
-  '@sinclair/typebox@0.27.8': {}
-
   '@sindresorhus/is@7.0.2': {}
 
   '@sindresorhus/merge-streams@2.3.0': {}
@@ -6717,23 +6669,24 @@ snapshots:
     dependencies:
       solid-js: 1.9.9
 
-  '@solidjs/start@1.1.7(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
+  '@solidjs/start@1.2.0(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
       '@tanstack/server-functions-plugin': 1.121.21(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
-      '@vinxi/plugin-directives': 0.5.0(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
-      '@vinxi/server-components': 0.5.0(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      '@vinxi/plugin-directives': 0.5.1(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      '@vinxi/server-components': 0.5.1(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      cookie-es: 2.0.0
       defu: 6.1.4
       error-stack-parser: 2.1.4
-      html-to-image: 1.11.11
+      html-to-image: 1.11.13
       radix3: 1.1.2
-      seroval: 1.1.1
-      seroval-plugins: 1.1.1(seroval@1.1.1)
+      seroval: 1.3.2
+      seroval-plugins: 1.3.3(seroval@1.3.2)
       shiki: 1.29.2
       source-map-js: 1.2.1
       terracotta: 1.0.6(solid-js@1.9.9)
-      tinyglobby: 0.2.12
+      tinyglobby: 0.2.15
       vinxi: 0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
-      vite-plugin-solid: 2.11.2(solid-js@1.9.9)(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      vite-plugin-solid: 2.11.8(solid-js@1.9.9)(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
     transitivePeerDependencies:
       - '@testing-library/jest-dom'
       - solid-js
@@ -6744,7 +6697,7 @@ snapshots:
 
   '@swc/helpers@0.5.13':
     dependencies:
-      tslib: 2.8.0
+      tslib: 2.8.1
 
   '@tailwindcss/typography@0.5.16(tailwindcss@3.4.17)':
     dependencies:
@@ -6757,9 +6710,9 @@ snapshots:
   '@tanstack/directive-functions-plugin@1.121.21(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
       '@babel/code-frame': 7.26.2
-      '@babel/core': 7.28.3
-      '@babel/traverse': 7.28.3
-      '@babel/types': 7.28.2
+      '@babel/core': 7.28.4
+      '@babel/traverse': 7.28.4
+      '@babel/types': 7.28.4
       '@tanstack/router-utils': 1.131.2
       babel-dead-code-elimination: 1.0.10
       tiny-invariant: 1.3.3
@@ -6769,10 +6722,10 @@ snapshots:
 
   '@tanstack/router-utils@1.131.2':
     dependencies:
-      '@babel/core': 7.28.3
+      '@babel/core': 7.28.4
       '@babel/generator': 7.28.3
-      '@babel/parser': 7.28.3
-      '@babel/preset-typescript': 7.27.1(@babel/core@7.28.3)
+      '@babel/parser': 7.28.4
+      '@babel/preset-typescript': 7.27.1(@babel/core@7.28.4)
       ansis: 4.1.0
       diff: 8.0.2
     transitivePeerDependencies:
@@ -6781,12 +6734,12 @@ snapshots:
   '@tanstack/server-functions-plugin@1.121.21(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
       '@babel/code-frame': 7.26.2
-      '@babel/core': 7.28.3
-      '@babel/plugin-syntax-jsx': 7.27.1(@babel/core@7.28.3)
-      '@babel/plugin-syntax-typescript': 7.27.1(@babel/core@7.28.3)
+      '@babel/core': 7.28.4
+      '@babel/plugin-syntax-jsx': 7.27.1(@babel/core@7.28.4)
+      '@babel/plugin-syntax-typescript': 7.27.1(@babel/core@7.28.4)
       '@babel/template': 7.27.2
-      '@babel/traverse': 7.28.3
-      '@babel/types': 7.28.2
+      '@babel/traverse': 7.28.4
+      '@babel/types': 7.28.4
       '@tanstack/directive-functions-plugin': 1.121.21(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       babel-dead-code-elimination: 1.0.10
       tiny-invariant: 1.3.3
@@ -6800,24 +6753,24 @@ snapshots:
 
   '@types/babel__core@7.20.5':
     dependencies:
-      '@babel/parser': 7.25.8
-      '@babel/types': 7.25.8
-      '@types/babel__generator': 7.6.8
+      '@babel/parser': 7.28.4
+      '@babel/types': 7.28.4
+      '@types/babel__generator': 7.27.0
       '@types/babel__template': 7.4.4
-      '@types/babel__traverse': 7.20.6
+      '@types/babel__traverse': 7.28.0
 
-  '@types/babel__generator@7.6.8':
+  '@types/babel__generator@7.27.0':
     dependencies:
-      '@babel/types': 7.25.8
+      '@babel/types': 7.28.4
 
   '@types/babel__template@7.4.4':
     dependencies:
-      '@babel/parser': 7.25.8
-      '@babel/types': 7.26.9
+      '@babel/parser': 7.28.4
+      '@babel/types': 7.28.4
 
-  '@types/babel__traverse@7.20.6':
+  '@types/babel__traverse@7.28.0':
     dependencies:
-      '@babel/types': 7.26.9
+      '@babel/types': 7.28.4
 
   '@types/braces@3.0.4': {}
 
@@ -7106,7 +7059,7 @@ snapshots:
 
   '@typescript/vfs@1.6.1(typescript@5.9.2)':
     dependencies:
-      debug: 4.4.1
+      debug: 4.4.3
       typescript: 5.9.2
     transitivePeerDependencies:
       - supports-color
@@ -7125,7 +7078,7 @@ snapshots:
       glob: 10.4.5
       graceful-fs: 4.2.11
       node-gyp-build: 4.8.4
-      picomatch: 4.0.2
+      picomatch: 4.0.3
       resolve-from: 5.0.0
     transitivePeerDependencies:
       - encoding
@@ -7152,33 +7105,33 @@ snapshots:
       untun: 0.1.3
       uqr: 0.1.2
 
-  '@vinxi/plugin-directives@0.5.0(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
+  '@vinxi/plugin-directives@0.5.1(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
-      '@babel/parser': 7.25.8
-      acorn: 8.12.1
-      acorn-jsx: 5.3.2(acorn@8.12.1)
-      acorn-loose: 8.4.0
-      acorn-typescript: 1.4.13(acorn@8.12.1)
+      '@babel/parser': 7.28.4
+      acorn: 8.15.0
+      acorn-jsx: 5.3.2(acorn@8.15.0)
+      acorn-loose: 8.5.2
+      acorn-typescript: 1.4.13(acorn@8.15.0)
       astring: 1.9.0
       magicast: 0.2.11
-      recast: 0.23.9
-      tslib: 2.8.0
+      recast: 0.23.11
+      tslib: 2.8.1
       vinxi: 0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
 
-  '@vinxi/server-components@0.5.0(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
+  '@vinxi/server-components@0.5.1(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
-      '@vinxi/plugin-directives': 0.5.0(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
-      acorn: 8.12.1
-      acorn-loose: 8.4.0
-      acorn-typescript: 1.4.13(acorn@8.12.1)
+      '@vinxi/plugin-directives': 0.5.1(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      acorn: 8.15.0
+      acorn-loose: 8.5.2
+      acorn-typescript: 1.4.13(acorn@8.15.0)
       astring: 1.9.0
       magicast: 0.2.11
-      recast: 0.23.9
+      recast: 0.23.11
       vinxi: 0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
 
   '@vue/compiler-core@3.5.16':
     dependencies:
-      '@babel/parser': 7.27.5
+      '@babel/parser': 7.28.4
       '@vue/shared': 3.5.16
       entities: 4.5.0
       estree-walker: 2.0.2
@@ -7191,7 +7144,7 @@ snapshots:
 
   '@vue/compiler-sfc@3.5.16':
     dependencies:
-      '@babel/parser': 7.27.5
+      '@babel/parser': 7.28.4
       '@vue/compiler-core': 3.5.16
       '@vue/compiler-dom': 3.5.16
       '@vue/compiler-ssr': 3.5.16
@@ -7246,23 +7199,17 @@ snapshots:
     dependencies:
       acorn: 8.15.0
 
-  acorn-jsx@5.3.2(acorn@8.12.1):
-    dependencies:
-      acorn: 8.12.1
-
   acorn-jsx@5.3.2(acorn@8.15.0):
     dependencies:
       acorn: 8.15.0
 
-  acorn-loose@8.4.0:
+  acorn-loose@8.5.2:
     dependencies:
       acorn: 8.15.0
 
-  acorn-typescript@1.4.13(acorn@8.12.1):
+  acorn-typescript@1.4.13(acorn@8.15.0):
     dependencies:
-      acorn: 8.12.1
-
-  acorn@8.12.1: {}
+      acorn: 8.15.0
 
   acorn@8.15.0: {}
 
@@ -7307,8 +7254,6 @@ snapshots:
     dependencies:
       color-convert: 2.0.1
 
-  ansi-styles@5.2.0: {}
-
   ansi-styles@6.2.3: {}
 
   ansis@4.1.0: {}
@@ -7352,7 +7297,7 @@ snapshots:
 
   ast-types@0.16.1:
     dependencies:
-      tslib: 2.8.0
+      tslib: 2.8.1
 
   astring@1.9.0: {}
 
@@ -7374,28 +7319,29 @@ snapshots:
 
   babel-dead-code-elimination@1.0.10:
     dependencies:
-      '@babel/core': 7.28.3
-      '@babel/parser': 7.28.3
-      '@babel/traverse': 7.28.3
-      '@babel/types': 7.28.2
+      '@babel/core': 7.28.4
+      '@babel/parser': 7.28.4
+      '@babel/traverse': 7.28.4
+      '@babel/types': 7.28.4
     transitivePeerDependencies:
       - supports-color
 
-  babel-plugin-jsx-dom-expressions@0.39.2(@babel/core@7.25.8):
+  babel-plugin-jsx-dom-expressions@0.40.1(@babel/core@7.28.4):
     dependencies:
-      '@babel/core': 7.25.8
+      '@babel/core': 7.28.4
       '@babel/helper-module-imports': 7.18.6
-      '@babel/plugin-syntax-jsx': 7.25.7(@babel/core@7.25.8)
-      '@babel/types': 7.25.8
+      '@babel/plugin-syntax-jsx': 7.27.1(@babel/core@7.28.4)
+      '@babel/types': 7.28.4
       html-entities: 2.3.3
-      jest-diff: 29.7.0
-      parse5: 7.2.0
-      validate-html-nesting: 1.2.2
+      parse5: 7.3.0
+      validate-html-nesting: 1.2.3
 
-  babel-preset-solid@1.9.2(@babel/core@7.25.8):
+  babel-preset-solid@1.9.9(@babel/core@7.28.4)(solid-js@1.9.9):
     dependencies:
-      '@babel/core': 7.25.8
-      babel-plugin-jsx-dom-expressions: 0.39.2(@babel/core@7.25.8)
+      '@babel/core': 7.28.4
+      babel-plugin-jsx-dom-expressions: 0.40.1(@babel/core@7.28.4)
+    optionalDependencies:
+      solid-js: 1.9.9
 
   bail@2.0.2: {}
 
@@ -7406,6 +7352,8 @@ snapshots:
 
   base64-js@1.5.1: {}
 
+  baseline-browser-mapping@2.8.4: {}
+
   bcp-47-match@2.0.3: {}
 
   binary-extensions@2.3.0: {}
@@ -7447,12 +7395,13 @@ snapshots:
       node-releases: 2.0.19
       update-browserslist-db: 1.1.3(browserslist@4.25.0)
 
-  browserslist@4.25.3:
+  browserslist@4.26.0:
     dependencies:
-      caniuse-lite: 1.0.30001735
-      electron-to-chromium: 1.5.207
-      node-releases: 2.0.19
-      update-browserslist-db: 1.1.3(browserslist@4.25.3)
+      baseline-browser-mapping: 2.8.4
+      caniuse-lite: 1.0.30001741
+      electron-to-chromium: 1.5.218
+      node-releases: 2.0.21
+      update-browserslist-db: 1.1.3(browserslist@4.26.0)
 
   buffer-crc32@0.2.13: {}
 
@@ -7504,7 +7453,7 @@ snapshots:
 
   caniuse-lite@1.0.30001722: {}
 
-  caniuse-lite@1.0.30001735: {}
+  caniuse-lite@1.0.30001741: {}
 
   ccount@2.0.1: {}
 
@@ -7728,6 +7677,10 @@ snapshots:
     dependencies:
       ms: 2.1.3
 
+  debug@4.4.3:
+    dependencies:
+      ms: 2.1.3
+
   decache@4.6.2:
     dependencies:
       callsite: 1.0.0
@@ -7820,8 +7773,6 @@ snapshots:
 
   didyoumean@1.2.2: {}
 
-  diff-sequences@29.6.3: {}
-
   diff@8.0.2: {}
 
   direction@2.0.1: {}
@@ -7868,7 +7819,7 @@ snapshots:
 
   electron-to-chromium@1.5.166: {}
 
-  electron-to-chromium@1.5.207: {}
+  electron-to-chromium@1.5.218: {}
 
   emoji-regex-xs@1.0.0: {}
 
@@ -7890,6 +7841,8 @@ snapshots:
 
   entities@4.5.0: {}
 
+  entities@6.0.1: {}
+
   env-paths@3.0.0: {}
 
   error-stack-parser-es@1.0.5: {}
@@ -8140,7 +8093,7 @@ snapshots:
 
   extract-zip@2.0.1:
     dependencies:
-      debug: 4.4.1
+      debug: 4.4.3
       get-stream: 5.2.0
       yauzl: 2.10.0
     optionalDependencies:
@@ -8184,13 +8137,13 @@ snapshots:
     dependencies:
       pend: 1.2.0
 
-  fdir@6.4.3(picomatch@4.0.2):
+  fdir@6.4.6(picomatch@4.0.2):
     optionalDependencies:
       picomatch: 4.0.2
 
-  fdir@6.4.6(picomatch@4.0.2):
+  fdir@6.5.0(picomatch@4.0.3):
     optionalDependencies:
-      picomatch: 4.0.2
+      picomatch: 4.0.3
 
   fecha@4.2.3: {}
 
@@ -8560,7 +8513,7 @@ snapshots:
 
   html-tags@3.3.1: {}
 
-  html-to-image@1.11.11: {}
+  html-to-image@1.11.13: {}
 
   html-void-elements@3.0.0: {}
 
@@ -8592,7 +8545,7 @@ snapshots:
   https-proxy-agent@7.0.6:
     dependencies:
       agent-base: 7.1.3
-      debug: 4.4.1
+      debug: 4.4.3
     transitivePeerDependencies:
       - supports-color
 
@@ -8742,15 +8695,6 @@ snapshots:
     dependencies:
       '@isaacs/cliui': 8.0.2
 
-  jest-diff@29.7.0:
-    dependencies:
-      chalk: 4.1.2
-      diff-sequences: 29.6.3
-      jest-get-type: 29.6.3
-      pretty-format: 29.7.0
-
-  jest-get-type@29.6.3: {}
-
   jiti@1.21.6: {}
 
   jiti@2.4.2: {}
@@ -8906,14 +8850,14 @@ snapshots:
 
   magicast@0.2.11:
     dependencies:
-      '@babel/parser': 7.25.8
-      '@babel/types': 7.25.8
-      recast: 0.23.9
+      '@babel/parser': 7.28.4
+      '@babel/types': 7.28.4
+      recast: 0.23.11
 
   magicast@0.3.5:
     dependencies:
-      '@babel/parser': 7.27.5
-      '@babel/types': 7.27.6
+      '@babel/parser': 7.28.4
+      '@babel/types': 7.28.4
       source-map-js: 1.2.1
 
   markdown-extensions@2.0.0: {}
@@ -9396,7 +9340,7 @@ snapshots:
   micromark@4.0.0:
     dependencies:
       '@types/debug': 4.1.12
-      debug: 4.4.1
+      debug: 4.4.3
       decode-named-character-reference: 1.0.2
       devlop: 1.1.0
       micromark-core-commonmark: 2.0.1
@@ -9626,9 +9570,11 @@ snapshots:
 
   node-releases@2.0.19: {}
 
+  node-releases@2.0.21: {}
+
   node-source-walk@7.0.1:
     dependencies:
-      '@babel/parser': 7.27.5
+      '@babel/parser': 7.28.4
 
   nopt@8.1.0:
     dependencies:
@@ -9789,6 +9735,10 @@ snapshots:
     dependencies:
       entities: 4.5.0
 
+  parse5@7.3.0:
+    dependencies:
+      entities: 6.0.1
+
   parseurl@1.3.3: {}
 
   path-exists@4.0.0: {}
@@ -9829,6 +9779,8 @@ snapshots:
 
   picomatch@4.0.2: {}
 
+  picomatch@4.0.3: {}
+
   pify@2.3.0: {}
 
   pirates@4.0.6: {}
@@ -9932,12 +9884,6 @@ snapshots:
 
   pretty-bytes@6.1.1: {}
 
-  pretty-format@29.7.0:
-    dependencies:
-      '@jest/schemas': 29.6.3
-      ansi-styles: 5.2.0
-      react-is: 18.3.1
-
   process-nextick-args@2.0.1: {}
 
   process@0.11.10: {}
@@ -9976,8 +9922,6 @@ snapshots:
       defu: 6.1.4
       destr: 2.0.5
 
-  react-is@18.3.1: {}
-
   react@18.3.1:
     dependencies:
       loose-envify: 1.4.0
@@ -10035,13 +9979,13 @@ snapshots:
 
   readdirp@4.1.2: {}
 
-  recast@0.23.9:
+  recast@0.23.11:
     dependencies:
       ast-types: 0.16.1
       esprima: 4.0.1
       source-map: 0.6.1
       tiny-invariant: 1.3.3
-      tslib: 2.8.0
+      tslib: 2.8.1
 
   recma-build-jsx@1.0.0:
     dependencies:
@@ -10227,7 +10171,7 @@ snapshots:
   rollup-plugin-visualizer@5.14.0(rollup@4.43.0):
     dependencies:
       open: 8.4.2
-      picomatch: 4.0.2
+      picomatch: 4.0.3
       source-map: 0.7.4
       yargs: 17.7.2
     optionalDependencies:
@@ -10304,7 +10248,7 @@ snapshots:
 
   send@1.2.0:
     dependencies:
-      debug: 4.4.1
+      debug: 4.4.3
       encodeurl: 2.0.0
       escape-html: 1.0.3
       etag: 1.8.1
@@ -10322,15 +10266,13 @@ snapshots:
     dependencies:
       randombytes: 2.1.0
 
-  seroval-plugins@1.1.1(seroval@1.1.1):
-    dependencies:
-      seroval: 1.1.1
-
   seroval-plugins@1.3.2(seroval@1.3.2):
     dependencies:
       seroval: 1.3.2
 
-  seroval@1.1.1: {}
+  seroval-plugins@1.3.3(seroval@1.3.2):
+    dependencies:
+      seroval: 1.3.2
 
   seroval@1.3.2: {}
 
@@ -10475,14 +10417,14 @@ snapshots:
 
   solid-refresh@0.6.3(solid-js@1.9.9):
     dependencies:
-      '@babel/generator': 7.25.7
-      '@babel/helper-module-imports': 7.25.7
-      '@babel/types': 7.25.8
+      '@babel/generator': 7.28.3
+      '@babel/helper-module-imports': 7.27.1
+      '@babel/types': 7.28.4
       solid-js: 1.9.9
     transitivePeerDependencies:
       - supports-color
 
-  solid-use@0.9.0(solid-js@1.9.9):
+  solid-use@0.9.1(solid-js@1.9.9):
     dependencies:
       solid-js: 1.9.9
 
@@ -10662,7 +10604,7 @@ snapshots:
   terracotta@1.0.6(solid-js@1.9.9):
     dependencies:
       solid-js: 1.9.9
-      solid-use: 0.9.0(solid-js@1.9.9)
+      solid-use: 0.9.1(solid-js@1.9.9)
 
   terser@5.42.0:
     dependencies:
@@ -10689,16 +10631,16 @@ snapshots:
 
   tinyexec@0.3.2: {}
 
-  tinyglobby@0.2.12:
-    dependencies:
-      fdir: 6.4.3(picomatch@4.0.2)
-      picomatch: 4.0.2
-
   tinyglobby@0.2.14:
     dependencies:
       fdir: 6.4.6(picomatch@4.0.2)
       picomatch: 4.0.2
 
+  tinyglobby@0.2.15:
+    dependencies:
+      fdir: 6.5.0(picomatch@4.0.3)
+      picomatch: 4.0.3
+
   tmp-promise@3.0.3:
     dependencies:
       tmp: 0.2.3
@@ -10729,8 +10671,6 @@ snapshots:
 
   ts-interface-checker@0.1.13: {}
 
-  tslib@2.8.0: {}
-
   tslib@2.8.1: {}
 
   twoslash-protocol@0.2.12: {}
@@ -10826,7 +10766,7 @@ snapshots:
       pkg-types: 1.3.1
       scule: 1.3.0
       strip-literal: 3.0.0
-      tinyglobby: 0.2.14
+      tinyglobby: 0.2.15
       unplugin: 2.3.5
       unplugin-utils: 0.2.4
 
@@ -10839,11 +10779,11 @@ snapshots:
       magic-string: 0.30.17
       mlly: 1.7.4
       pathe: 2.0.3
-      picomatch: 4.0.2
+      picomatch: 4.0.3
       pkg-types: 2.1.0
       scule: 1.3.0
       strip-literal: 3.0.0
-      tinyglobby: 0.2.14
+      tinyglobby: 0.2.15
       unplugin: 2.3.5
       unplugin-utils: 0.2.4
 
@@ -10979,9 +10919,9 @@ snapshots:
       escalade: 3.2.0
       picocolors: 1.1.1
 
-  update-browserslist-db@1.1.3(browserslist@4.25.3):
+  update-browserslist-db@1.1.3(browserslist@4.26.0):
     dependencies:
-      browserslist: 4.25.3
+      browserslist: 4.26.0
       escalade: 3.2.0
       picocolors: 1.1.1
 
@@ -10999,7 +10939,7 @@ snapshots:
 
   uuid@11.1.0: {}
 
-  validate-html-nesting@1.2.2: {}
+  validate-html-nesting@1.2.3: {}
 
   validate-npm-package-license@3.0.4:
     dependencies:
@@ -11099,16 +11039,16 @@ snapshots:
       - xml2js
       - yaml
 
-  vite-plugin-solid@2.11.2(solid-js@1.9.9)(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)):
+  vite-plugin-solid@2.11.8(solid-js@1.9.9)(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)):
     dependencies:
-      '@babel/core': 7.25.8
+      '@babel/core': 7.28.4
       '@types/babel__core': 7.20.5
-      babel-preset-solid: 1.9.2(@babel/core@7.25.8)
+      babel-preset-solid: 1.9.9(@babel/core@7.28.4)(solid-js@1.9.9)
       merge-anything: 5.1.7
       solid-js: 1.9.9
       solid-refresh: 0.6.3(solid-js@1.9.9)
       vite: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
-      vitefu: 1.0.5(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      vitefu: 1.1.1(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
     transitivePeerDependencies:
       - supports-color
 
@@ -11127,7 +11067,7 @@ snapshots:
       terser: 5.42.0
       yaml: 2.8.0
 
-  vitefu@1.0.5(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)):
+  vitefu@1.1.1(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)):
     optionalDependencies:
       vite: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
 

From cce50568795b108dc2d5103be8b631e4d71db2ec Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Tue, 16 Sep 2025 15:15:47 +0000
Subject: [PATCH 25/37] Bump @eslint/js from 9.34.0 to 9.35.0 (#1265)

---
 package.json   |  2 +-
 pnpm-lock.yaml | 10 ++--------
 2 files changed, 3 insertions(+), 9 deletions(-)

diff --git a/package.json b/package.json
index c137c5b1f..a3088b486 100644
--- a/package.json
+++ b/package.json
@@ -42,7 +42,7 @@
 		"zod": "^4.1.8"
 	},
 	"devDependencies": {
-		"@eslint/js": "^9.34.0",
+		"@eslint/js": "^9.35.0",
 		"@kobalte/tailwindcss": "^0.9.0",
 		"@orama/crawly": "^0.0.6",
 		"@tailwindcss/typography": "^0.5.16",
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index 908ccb030..c964ccc60 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -76,8 +76,8 @@ importers:
         version: 4.1.8
     devDependencies:
       '@eslint/js':
-        specifier: ^9.34.0
-        version: 9.34.0
+        specifier: ^9.35.0
+        version: 9.35.0
       '@kobalte/tailwindcss':
         specifier: ^0.9.0
         version: 0.9.0(tailwindcss@3.4.17)
@@ -678,10 +678,6 @@ packages:
     resolution: {integrity: sha512-gtF186CXhIl1p4pJNGZw8Yc6RlshoePRvE0X91oPGb3vZ8pM3qOS9W9NGPat9LziaBV7XrJWGylNQXkGcnM3IQ==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
 
-  '@eslint/js@9.34.0':
-    resolution: {integrity: sha512-EoyvqQnBNsV1CWaEJ559rxXL4c8V92gxirbawSmVUOWXlsRxxQXl6LmCpdUblgxgSkDIqKnhzba2SjRTI/A5Rw==}
-    engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
-
   '@eslint/js@9.35.0':
     resolution: {integrity: sha512-30iXE9whjlILfWobBkNerJo+TXYsgVM5ERQwMcMKCHckHflCmf7wXDAHlARoWnh0s1U72WqlbeyE7iAcCzuCPw==}
     engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
@@ -5759,8 +5755,6 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
-  '@eslint/js@9.34.0': {}
-
   '@eslint/js@9.35.0': {}
 
   '@eslint/object-schema@2.1.6': {}

From 42bee6a4176f0ecbc0938bde1977d6dc29797014 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Tue, 16 Sep 2025 08:21:21 -0700
Subject: [PATCH 26/37] Bump globals from 16.3.0 to 16.4.0 (#1267)

---
 package.json   |  2 +-
 pnpm-lock.yaml | 10 +++++-----
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/package.json b/package.json
index a3088b486..2538ea287 100644
--- a/package.json
+++ b/package.json
@@ -52,7 +52,7 @@
 		"autoprefixer": "^10.4.21",
 		"eslint": "^9.35.0",
 		"eslint-plugin-solid": "^0.14.5",
-		"globals": "^16.3.0",
+		"globals": "^16.4.0",
 		"prettier": "3.6.2",
 		"prettier-plugin-tailwindcss": "^0.6.14",
 		"tailwindcss": "^3.4.17",
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index c964ccc60..7059c7b20 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -106,8 +106,8 @@ importers:
         specifier: ^0.14.5
         version: 0.14.5(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
       globals:
-        specifier: ^16.3.0
-        version: 16.3.0
+        specifier: ^16.4.0
+        version: 16.4.0
       prettier:
         specifier: 3.6.2
         version: 3.6.2
@@ -2857,8 +2857,8 @@ packages:
     resolution: {integrity: sha512-7ACyT3wmyp3I61S4fG682L0VA2RGD9otkqGJIwNUMF1SWUombIIk+af1unuDYgMm082aHYwD+mzJvv9Iu8dsgg==}
     engines: {node: '>=18'}
 
-  globals@16.3.0:
-    resolution: {integrity: sha512-bqWEnJ1Nt3neqx2q5SFfGS8r/ahumIakg3HcwtNlrVlwXIeNumWn/c7Pn/wKzGhf6SaW6H6uWXLqC30STCMchQ==}
+  globals@16.4.0:
+    resolution: {integrity: sha512-ob/2LcVVaVGCYN+r14cnwnoDPUufjiYgSqRhiFD0Q1iI4Odora5RE8Iv1D24hAz5oMophRGkGz+yuvQmmUMnMw==}
     engines: {node: '>=18'}
 
   globby@14.1.0:
@@ -8286,7 +8286,7 @@ snapshots:
 
   globals@15.15.0: {}
 
-  globals@16.3.0: {}
+  globals@16.4.0: {}
 
   globby@14.1.0:
     dependencies:

From 2581e1be8aadf7718507445ac8cace2c0f7d0232 Mon Sep 17 00:00:00 2001
From: Dante <dante@mindofapollo.org>
Date: Wed, 17 Sep 2025 17:55:00 +0100
Subject: [PATCH 27/37] Remove "variables" from createEffect dependency
 examples (#1269)

---
 old pages/concepts/effects.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/old pages/concepts/effects.mdx b/old pages/concepts/effects.mdx
index f1e2cd54a..f6c4631e4 100644
--- a/old pages/concepts/effects.mdx	
+++ b/old pages/concepts/effects.mdx	
@@ -28,7 +28,7 @@ When the value of `count` changes, the effect is triggered, causing it to run ag
 
 Effects can be set to observe any number of dependencies.
 Dependencies are what allow an effect to track changes and respond accordingly.
-These can include signals, variables, props, context, or any other reactive values.
+These can include signals, props, context, or any other reactive values.
 When any of these change, the effect is notified and will run again to update its state.
 
 Upon initialization, an effect will run _once_, regardless of whether it has any dependencies.

From c34397b8179a9caeba4a971cf3f1ab7b2d8dae8b Mon Sep 17 00:00:00 2001
From: LadyBluenotes <gerrardsarah@gmail.com>
Date: Sat, 23 Aug 2025 21:46:01 -0700
Subject: [PATCH 28/37] start of v2 structure

---
 old pages/concepts/intro-to-reactivity.mdx | 248 +++++++++++++++++++++
 old pages/concepts/signals.mdx             |  90 ++++++++
 old pages/concepts/understanding-jsx.mdx   | 129 +++++++++++
 old pages/quick-start.mdx                  |  80 +++++++
 src/routes/getting-started/counter.mdx     |  12 +
 src/routes/getting-started/quick-start.mdx |  26 +++
 src/routes/reactivity/memos.mdx            |  11 +
 src/routes/reactivity/overview.mdx         |  74 ++++++
 src/routes/reactivity/stores.mdx           |   2 +-
 9 files changed, 671 insertions(+), 1 deletion(-)
 create mode 100644 old pages/concepts/intro-to-reactivity.mdx
 create mode 100644 old pages/concepts/signals.mdx
 create mode 100644 old pages/concepts/understanding-jsx.mdx
 create mode 100644 old pages/quick-start.mdx
 create mode 100644 src/routes/getting-started/counter.mdx
 create mode 100644 src/routes/getting-started/quick-start.mdx
 create mode 100644 src/routes/reactivity/memos.mdx
 create mode 100644 src/routes/reactivity/overview.mdx

diff --git a/old pages/concepts/intro-to-reactivity.mdx b/old pages/concepts/intro-to-reactivity.mdx
new file mode 100644
index 000000000..5b885169d
--- /dev/null
+++ b/old pages/concepts/intro-to-reactivity.mdx	
@@ -0,0 +1,248 @@
+---
+title: "Intro to reactivity"
+order: 1
+---
+
+**Note**: While this guide is useful for understanding reactive systems, it does use some Solid-specific terminology.
+
+Reactivity powers the interactivity in Solid applications.
+This programming paradigm refers to a system's ability to respond to changes in data or state automatically.
+With Solid, reactivity is the basis of its design, ensuring applications stay up-to-date with their underlying data.
+
+## Importance of reactivity
+
+1. Reactivity keeps the user interface (UI) and state in sync, which reduces the need for manual updates.
+
+2. Real-time updates create a more responsive and interactive user experience.
+
+```jsx
+function Counter() {
+	const [count, setCount] = createSignal(0);
+	const increment = () => setCount((prev) => prev + 1);
+
+	return (
+		<div>
+			<span>Count: {count()}</span>{" "}
+			{/* Only `count()` is updated when the button is clicked. */}
+			<button type="button" onClick={increment}>
+				Increment
+			</button>
+		</div>
+	);
+}
+```
+
+This `Counter` function sets up a button that, when clicked, calls the `increment` function to increase the `count` by one.
+This updates just the number displayed _without_ refreshing the entire component.
+
+<EraserLink
+	href="https://app.eraser.io/workspace/maDvFw5OryuPJOwSLyK9?elements=cry9JT4nroFQ4rRxzOpvCg"
+	preview="https://app.eraser.io/workspace/maDvFw5OryuPJOwSLyK9/preview?elements=cry9JT4nroFQ4rRxzOpvCg&type=embed"
+/>
+
+## Reactive principles
+
+### Signals
+
+Signals serve as core elements in reactive systems, playing an important role in data management and system responsiveness.
+They are responsible for storing and managing data, as well as triggering updates across the system.
+This is done through the use of getters and setters.
+
+```jsx
+const [count, setCount] = createSignal(0);
+//     ^ getter  ^ setter
+```
+
+<EraserLink
+	href="https://app.eraser.io/workspace/maDvFw5OryuPJOwSLyK9?elements=lseAEjGlKLslaVsTlfej_g"
+	preview="https://app.eraser.io/workspace/maDvFw5OryuPJOwSLyK9/preview?elements=lseAEjGlKLslaVsTlfej_g&type=embed"
+/>
+
+- **Getter**: A function responsible for accessing the current value of the signal.
+  You call a getter to access the data stored in a signal within a component.
+
+- **Setter**:
+  The function used to modify a signal's value.
+  To trigger reactive updates across an application, you call a setter to update the value of a signal.
+
+```js
+console.log(count()); // `count()` is a getter that returns the current value of `count`, which is `0`.
+
+setCount(1); // the setter, `setCount`, updates the value of `count`.
+
+console.log(count()); // the updated value of `count` is now `1`.
+```
+
+### Subscribers
+
+Subscribers are the other core element in reactive systems.
+They are responsible for tracking changes in signals and updating the system accordingly.
+They are automated responders that keep the system up-to-date with the latest data changes.
+
+Subscribers work based on two main actions:
+
+- **Observation**: At their core, subscribers observe signals.
+  This keeps the subscriber primed to pick up on any changes to the signal they are tracking.
+- **Response**: When a signal changes, the subscriber is notified.
+  This triggers the subscriber to respond to the change in the signal.
+  This can involve tasks like updating the UI or calling external functions.
+
+```jsx
+function Counter() {
+	const [count, setCount] = createSignal(0);
+	const increment = () => setCount((prev) => prev + 1);
+
+	createEffect(() => {
+		console.log(count());
+	});
+	// the `createEffect` will trigger the console log every time `count` changes.
+}
+```
+
+## State management
+
+State management is the process of managing the state of an application.
+This involves storing and updating data, as well as responding to the changes in it.
+
+With Solid, state management is handled through signals and subscribers.
+Signals are used to store and update data, while subscribers are used to respond to changes in the data.
+
+### Tracking changes
+
+Tracking changes involves monitoring any updates to the data and responding accordingly.
+This is done through the use of subscribers.
+
+When a signal is not accessed within a tracking scope, an update to the signal will not trigger an update.
+This happens because if a signal is not being tracked, it is not able to notify any subscribers of the change.
+
+```jsx
+const [count, setCount] = createSignal(0);
+
+console.log("Count:", count());
+
+setCount(1);
+
+// Output: Count: 0
+
+// `count` is not being tracked, so the console log will not update when `count` changes.
+```
+
+Since initialization is a **one-time event**, if a signal is accessed _outside of a tracking scope_, it will not be tracked.
+To track a signal, it must be accessed within the scope of a subscriber.
+Reactive primitives, such as [effects](/concepts/effects), can be used to create subscribers.
+
+```jsx
+const [count, setCount] = createSignal(0);
+
+createEffect(() => {
+	console.log("Count:", count());
+});
+
+setCount(1);
+
+// Output: Count: 0
+//         Count: 1
+```
+
+### Updating the UI
+
+The UI of a Solid application is built using [JSX](/concepts/understanding-jsx).
+JSX creates a tracking scope behind the scenes, which allows signals to be tracked within the return statement of a component.
+
+```jsx
+function Counter() {
+	const [count, setCount] = createSignal(0);
+	const increment = () => setCount((prev) => prev + 1);
+
+	return (
+		<div>
+			<span>Count: {count()}</span>{" "}
+			{/* ✅ will update when `count()` changes. */}
+			<button type="button" onClick={increment}>
+				Increment
+			</button>
+		</div>
+	);
+}
+```
+
+Components, much like other functions, will only run _once_.
+This means that if a signal is accessed outside of the return statement, it will run on initialization, but any updates to the signal will not trigger an update.
+
+```jsx
+function Counter() {
+	const [count, setCount] = createSignal(0);
+	const increment = () => setCount((prev) => prev + 1);
+
+	console.log("Count:", count()); // ❌ not tracked - only runs once during initialization.
+
+	createEffect(() => {
+		console.log(count()); // ✅ will update whenever `count()` changes.
+	});
+
+	return (
+		<div>
+			<span>Count: {count()}</span>{/* ✅ will update whenever `count()` changes. */}
+			<button type="button" onClick={increment}>
+				Increment
+			</button>
+		</div>
+	);
+}
+```
+
+To learn more about managing state in Solid, visit the [guide on state management](/guides/state-management).
+
+## Synchronous vs. asynchronous
+
+Reactive systems are designed to respond to changes in data.
+These responses can be immediate or delayed, depending on the nature of the system.
+Often, the choice between these two depends on the requirements of the application and the nature of the tasks involved.
+
+### Synchronous reactivity
+
+[Synchronous](https://developer.mozilla.org/en-US/docs/Glossary/Synchronous) reactivity is Solid's default reactivity mode, where a system responds to changes in a direct and linear fashion.
+When a signal changes, any corresponding subscribers are immediately updated in an ordered manner.
+
+With synchronous reactivity, the system is able to respond to changes in a predictable manner.
+This is useful in scenarios where the order of updates is important.
+For example, if a subscriber depends on another signal, it is important that the subscriber is updated after the signal it depends on.
+
+```jsx
+const [count, setCount] = createSignal(0);
+const [double, setDouble] = createSignal(0);
+
+createEffect(() => {
+	setDouble(count() * 2);
+});
+```
+
+In this example, the `double` signal will always be updated after `count` due to synchronous reactivity.
+This ensures that `double` is always up-to-date with the latest value of `count`.
+
+### Asynchronous reactivity
+
+[Asynchronous](https://developer.mozilla.org/en-US/docs/Glossary/Asynchronous) reactivity is when a system responds to changes in a delayed or non-linear fashion.
+When a signal changes, the corresponding subscribers are not immediately updated.
+Instead, the system waits for a specific event or task to complete before updating the subscribers.
+
+This is important in scenarios where subscribers depend on multiple signals.
+In these cases, updating one signal before another could result in data inconsistency.
+For example, if a subscriber depends on two signals, it is important that the subscriber is updated after both signals have been updated.
+Rather, the system waits for both signals to be updated before updating the subscriber.
+
+**Note:** When asynchronous reactivity is present, it is important to ensure that the system is able to handle the delay in updates.
+[`batch`](/reference/reactive-utilities/batch) can be used to delay an update so the subscriber runs after each signal has been updated.
+
+## Key concepts
+
+- Signals are the core elements of a reactive system.
+  They are responsible for storing and managing data.
+- Signals are both readable and writeable because of getters and setters.
+- Subscribers are automated responders that track changes in signals and update the system accordingly.
+- Signals and subscribers work together to ensure that the system is kept up-to-date with the latest data changes.
+- A reactive system is built on the principles of data-driven reactivity.
+  This means that the system's reactivity is driven by the data it is built on.
+- Reactive systems can be synchronous or asynchronous.
+
+If you want to dive deeper, visit the [guide on fine-grained reactivity](/advanced-concepts/fine-grained-reactivity).
diff --git a/old pages/concepts/signals.mdx b/old pages/concepts/signals.mdx
new file mode 100644
index 000000000..aa59b6515
--- /dev/null
+++ b/old pages/concepts/signals.mdx	
@@ -0,0 +1,90 @@
+---
+title: Signals
+order: 2
+---
+
+Signals are the primary means of [managing state](/concepts/intro-to-reactivity#state-management) in your Solid application.
+They provide a way to store and update values, and are the foundation of [reactivity](/concepts/intro-to-reactivity) in Solid.
+
+Signals can be used to represent any kind of state in your application, such as the current user, the current page, or the current theme.
+This can be any value, including primitive values such as strings and numbers, or complex values such as objects and arrays.
+
+## Creating a signal
+
+You can create a signal by calling the [`createSignal`](/reference/basic-reactivity/create-signal) function, which is imported from `solid-js`.
+This function takes an initial value as an argument, and returns a pair of functions: a **getter** function, and a **setter** function.
+
+```jsx
+import { createSignal } from "solid-js";
+
+const [count, setCount] = createSignal(0);
+//       ^ getter  ^ setter
+```
+
+    	:::note
+    	  The syntax using `[` and `]` is called [array destructuring](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Destructuring_assignment).
+
+This lets you extract values from the array.
+In the context of `createSignal`, the first value is the getter function, and the second value is the setter function.
+
+:::
+
+## Accessing values
+
+The getter function returned by `createSignal` is used to access the value of the signal.
+You call this function with no arguments to get the current value of the signal:
+
+```jsx
+console.log(count()); // output: 0
+```
+
+## Updating values
+
+The setter function returned by `createSignal` is used to update the value of the signal.
+This function takes an argument that represents the new value of the signal:
+
+```jsx
+setCount(count() + 1);
+
+console.log(count()); // output: 1
+```
+
+The setter function can also take a function that passes the previous value.
+
+```jsx
+setCount((prevCount) => prevCount + 1);
+
+console.log(count()); // output: 1
+```
+
+## Reactivity
+
+Signals are reactive, which means that they automatically update when their value changes.
+When a signal is called within a [tracking scope](/concepts/intro-to-reactivity#tracking-changes), the signal adds the dependency to a list of subscribers.
+Once a signal's value changes, it notifies all of its dependencies of the change so they can re-evaluate their values and update accordingly.
+
+```jsx
+function Counter() {
+	const [count, setCount] = createSignal(0);
+	const increment = () => setCount((prev) => prev + 1);
+
+	return (
+		<div>
+			<span>Count: {count()}</span> {/* Updates when `count` changes */}
+			<button type="button" onClick={increment}>
+				Increment
+			</button>
+		</div>
+	);
+}
+```
+
+:::note
+A tracking scope can be created by [`createEffect`](/reference/basic-reactivity/create-effect)  or [`createMemo`](/reference/basic-reactivity/create-memo), which are other Solid primitives.
+
+Both functions subscribe to the signals accessed within them, establishing a dependency relationship.
+Once this relationship is established, the function is notified whenever the signal changes.
+
+:::
+
+To learn more about how to use Signals in your application, visit our [state management guide](/guides/state-management).
diff --git a/old pages/concepts/understanding-jsx.mdx b/old pages/concepts/understanding-jsx.mdx
new file mode 100644
index 000000000..8dea79978
--- /dev/null
+++ b/old pages/concepts/understanding-jsx.mdx	
@@ -0,0 +1,129 @@
+---
+title: Understanding JSX
+order: 2
+---
+
+JSX is an extension for JavaScript.
+It allows you to write HTML-like code inside your JavaScript file which keeps your rendering logic and content in the same place.
+This provides a concise and readable way to create and represent components.
+
+## How Solid uses JSX
+
+Solid was designed to align closely with HTML standards.
+
+```jsx
+const element = <h1>I'm JSX!!</h1>
+```
+
+It offers a distinct advantage, however: to copy/paste solutions from resources like Stack Overflow; and to allow direct usage of templates from design tools.
+Solid sets itself apart by using JSX immediately as it returns [DOM](https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model/Introduction) elements.
+This lets you use dynamic expressions within your HTML by allowing variables and functions to be references with the use of curly braces (`{ }`):
+
+```jsx
+const Component = () => {
+	const animal = { breed: "cat", name: "Midnight" }
+
+	return (
+		<p>
+			I have a {animal.breed} named {animal.name}!
+		</p>
+	)
+}
+```
+
+This means JavaScript content can be rendered on web pages based on an application's state or logic.
+
+Additionally, Solid's [reactive](/concepts/intro-to-reactivity) system introduces [fine-grained reactivity](/advanced-concepts/fine-grained-reactivity) with JSX.
+This updates only the necessary parts of the DOM when changes occur in the underlying state.
+
+## Using JSX in Solid
+
+### Return a single root element
+
+Where HTML lets you have disconnected tags at the top level, JSX requires that a component to return a single root element.
+
+:::advanced
+When working with JSX, parts of your code are translated into structured HTML that is placed at the start of the file.
+Static elements are processed differently from dynamic ones, which might change based on data or user actions.
+For dynamic elements, special markers are added for better handling during rendering.
+
+Having a single root creates a consistent and manageable hierarchy to optimize rendering and updates.
+:::
+
+JSX maintains the familiar nested, tree-like structure found in HTML.
+As a result, parent-child relationships between elements become easier to follow.
+
+### Close all tags
+
+Self-closing tags are a must in JSX.
+Unlike in HTML, where elements like `<input>`, `<img>`, or `<br>` don't require explicit closure, JSX requires consistent self-closing tags.
+This helps to avoid potential rendering issues.
+
+```jsx
+<img src="./image-here.png" />
+```
+
+### Properties vs. attributes
+
+HTML attributes and JSX properties may seem similar, but they serve different purposes and behave differently.
+Both offer ways to specify configurations or pass information.
+However, HTML is used for standard web content and JSX creates Solid's component logic.
+
+#### HTML attributes
+
+[HTML attributes](https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes) are values set directly on HTML elements.
+They provide additional information about an element to guide its initial behavior and state.
+These attributes are often translated into properties on DOM objects once the browser parses the HTML.
+
+In JSX files, HTML attributes are used much like regular HTML, with a few key differences due to the blend of HTML and JavaScript:
+
+- Event listeners such as `onClick` can be in camelCase or lowercase.
+  (**Note:** When using ESLint, you will get a warning if you use lowercase.)
+- In cases where you can dynamically specify a value, you can replace the `"` and `"` with curly braces (`{ }`):
+
+```jsx
+<button class="myClass" onClick={handleClick}>
+	Click me!
+</button>
+```
+
+    	:::note
+    	  If you wish to pass objects in JSX, such as with inline styling, you will have to use double curly braces (`{{ }}`).
+
+```jsx
+<button style={{
+	color: 'red',
+	font-size: '2rem',
+	}}>
+  Click me!
+</button>
+```
+:::
+
+### JSX properties (props)
+
+JSX properties, commonly known as "props," help with the passing of data and configurations to components within an application.
+They connect the component with the data it requires, for seamless data flows and dynamic interactions.
+
+#### Core concepts
+
+- **Static props**:
+  In Solid's JSX, static props are integrated directly into the HTML by cloning the template and using them as attributes.
+
+ - **Dynamic props**:
+ Dynamic props rely on state, allowing the content or properties to be dynamic.
+ An example is changing the style of an element in response to interactions within an application.
+ This can be expressed in the form of signals (`value={value()}`).
+
+- **Data transfer**:
+  Props are also used to fill components with data that comes from resources, like [`createResource`](/reference/basic-reactivity/create-resource) calls.
+  This results in components that react in real-time to data changes.
+
+:::note
+Expressions, whether fixed or dynamic, get applied *in the order defined within the JSX*.
+This works for a wide range of DOM elements, but will not work with elements that require attributes to be defined in a special order, such as input types with `type='range'`.
+
+When order influences an element's behavior, users must define the expressions in the order that the element is expected.
+:::
+
+For how to use props effectively in Solid, explore the [props page](/concepts/components/props).
diff --git a/old pages/quick-start.mdx b/old pages/quick-start.mdx
new file mode 100644
index 000000000..c04a9c7b5
--- /dev/null
+++ b/old pages/quick-start.mdx	
@@ -0,0 +1,80 @@
+---
+title: Quick start
+---
+
+## Try Solid online
+
+To experiment with Solid directly in your browser, head over to our [interactive playground](https://playground.solidjs.com/).
+Prefer a full development setup? You can set up a complete environment using StackBlitz.
+Start with the [TypeScript](https://stackblitz.com/github/solidjs/templates/tree/master/ts) or [JavaScript](https://stackblitz.com/github/solidjs/templates/tree/master/js) templates.
+
+## Create a Solid project
+
+:::note[Prerequisites]
+
+- Familiarity with the command line.
+- A recent version of [Node.js](https://nodejs.org/en), [Bun](https://bun.sh/), or [Deno](https://deno.com/).
+  The latest LTS version is recommended.
+
+:::
+
+To create a new Solid application, navigate to the directory where you want to create your project and run the following command:
+
+```package-create
+solid
+```
+
+This command installs and runs [create-solid](https://github.com/solidjs-community/solid-cli/tree/main/packages/create-solid), the official project scaffolding tool for Solid.
+The CLI will guide you through a series of prompts, allowing you to choose options such as [starter templates](https://github.com/solidjs/templates), TypeScript support, and whether to include [Solid's full-stack framework, SolidStart](/solid-start):
+
+```shell
+◆ Project Name
+|  <solid-project>
+
+◆ Is this a SolidStart project?
+|  ● Yes / ○ No
+
+◆ Which template would you like to use?
+│  ● ts
+│  ○ ts-vitest
+│  ○ ts-uvu
+│  ○ ts-unocss
+│  ○ ts-tailwindcss
+
+◆ Use TypeScript?
+│  ● Yes / ○ No
+```
+
+Once the project is created, follow the instructions to install the dependencies and start the development server:
+
+```sh title="npm" tab="package-manager"
+│  cd solid-project
+│  npm install
+│  npm run dev
+```
+
+```sh title="pnpm" tab="package-manager"
+│  cd solid-project
+│  pnpm install
+│  pnpm dev
+```
+
+```sh title="yarn" tab="package-manager"
+│  cd solid-project
+│  yarn install
+│  yarn dev
+```
+
+```sh title="bun" tab="package-manager"
+│  cd solid-project
+│  bun install
+│  bun run dev
+```
+
+```sh title="deno" tab="package-manager"
+│  cd solid-project
+│  deno install
+│  deno run dev
+```
+
+You should now have your Solid project running!
diff --git a/src/routes/getting-started/counter.mdx b/src/routes/getting-started/counter.mdx
new file mode 100644
index 000000000..ee8d28182
--- /dev/null
+++ b/src/routes/getting-started/counter.mdx
@@ -0,0 +1,12 @@
+---
+title: "Counter Tutorial"
+order: 2
+---
+
+[TODO]
+
+1. Open your newly scaffolded project in your code editor of choice.
+2. Create a new file called `Counter.jsx` in the `src/components` directory.
+3. In `Counter.tsx`, use Solid's `createSignal` to create a reactive counter state.
+4. Export the `Counter` component and import it into your main application file (e.g., `src/App.jsx`).
+5. Use the `Counter` component in your application and test its functionality.
\ No newline at end of file
diff --git a/src/routes/getting-started/quick-start.mdx b/src/routes/getting-started/quick-start.mdx
new file mode 100644
index 000000000..4e5a93110
--- /dev/null
+++ b/src/routes/getting-started/quick-start.mdx
@@ -0,0 +1,26 @@
+---
+title: Quick Start Guide
+order: 1
+---
+
+The fastest way to try Solid is to create a new project and run it locally.
+In just a few minutes, you’ll have a working Solid app running in your browser.
+
+## Solid in your Browser
+
+If you're looking to experiment with Solid without setting up a local environment, open the [Solid Playground](https://playground.solidjs.com/) in your browser.
+
+If you prefer a more complete development setup, you can use the StackBlitz [Javascript](https://stackblitz.com/github/solidjs/templates/tree/master/js) or [TypeScript](https://stackblitz.com/github/solidjs/templates/tree/master/ts) templates.
+
+## Create a New Project
+
+:::note[Before You Begin]
+Make sure you have a recent version of your prefer JavaScript runtime installed, such as [Node.js](https://nodejs.org/en), [Bun](https://bun.sh/), or [Deno](https://deno.com/).
+:::
+
+[TODO]
+
+- Navigate to directory and run command
+- CLI will take you through options
+- Once you've selected your options, the CLI will prompt you to install the dependencies and start the development server
+- Open browser and navigate to the provided local URL to see your new Solid app in action!
\ No newline at end of file
diff --git a/src/routes/reactivity/memos.mdx b/src/routes/reactivity/memos.mdx
new file mode 100644
index 000000000..bdaf190ab
--- /dev/null
+++ b/src/routes/reactivity/memos.mdx
@@ -0,0 +1,11 @@
+---
+title: "Memos"
+order: 3
+---
+
+[TODO:
+Concept page on Memos
+- Improve on existing page
+- Move relevant sections to reference and vice versa
+- Link out to how-to for derived signals where appropriate
+]
\ No newline at end of file
diff --git a/src/routes/reactivity/overview.mdx b/src/routes/reactivity/overview.mdx
new file mode 100644
index 000000000..725a2186c
--- /dev/null
+++ b/src/routes/reactivity/overview.mdx
@@ -0,0 +1,74 @@
+---
+title: "Overview"
+order: 1
+---
+
+[TODO: Review]
+
+:::note
+While this guide can be helpful for understanding reactive systems, it does use some Solid-specific terminology and concepts.
+:::
+
+Reactivity is what powers the interactivity of Solid apps.
+This programming paradigm refers to a system's ability to respond to changes in data, or state, automatically and efficiently.
+Solid is built with reactivity at the core of its design, assisting applications with staying up-to-date with its underlying data.
+
+## The Importance of Reactivity
+
+Reactivity is what keeps the user interface (UI) in sync with the underlying application state. 
+When the state changes, the UI is automatically updated, reducing the need for manual updates.
+
+In addition, reactivity enables real-time updates, allowing applications to reflect changes instantly without requiring a full page refresh. 
+This helps with creating more responsive and interactive user experiences. 
+
+As an example, when building a Counter, you can use the reactive primitives provided by Solid to create a counter. 
+Once the counter is set up, whenever the count changes, the UI will automatically update to reflect the new count:
+
+```tsx
+function Counter() {
+  const [count, setCount] = createSignal<number>(0);
+  const increment = () => setCount((prev) => prev + 1);
+
+  return (
+    <div>
+      <span>Count: {count()}</span>{" "}
+      {/* Only `count()` is updated when the button is clicked. */}
+      <button type="button" onClick={increment}>
+        Increment
+      </button>
+    </div>
+  );
+}
+```
+
+## Reactive Principles
+
+### Signals
+
+Signals serve as the core elements within a reactive system.
+They play a crucial role in tracking and managing state changes, allowing the UI to respond automatically when the underlying data changes.
+They are responsible for storing and managing data, as well as triggering updates across the system.
+
+Signals are able to achieve this reactivity through the use of:
+
+- **Getters**: A function responsible for retrieving the current value of a signal.
+When called within a reactive context, it will give access to the current value of the signal.
+- **Setters**: This function is responsible for updating the value of a signal.
+To trigger reactivity, setters notify the system that the signal's value has changed, prompting anything that depends on the signal to re-evaluate and update accordingly.
+
+<EraserLink
+	href="https://app.eraser.io/workspace/maDvFw5OryuPJOwSLyK9?elements=lseAEjGlKLslaVsTlfej_g"
+	preview="https://app.eraser.io/workspace/maDvFw5OryuPJOwSLyK9/preview?elements=lseAEjGlKLslaVsTlfej_g&type=embed"
+/>
+
+### Subscribers
+
+Subscribers refer to other reactive contexts or components that depend on the value of a signal.
+These automated responders keep the system up-to-date by re-evaluating and updating whenever the signal's value changes.
+
+Subscribers work based on two main actions:
+- **Observation**: The core function of a subscriber is to observe signals.
+This keeps the subscriber informed about any changes to the signal(s) they're tracking.
+- **Respond**: Once the signal has updated and the subscriber is notified, it triggers a re-evaluation of the dependent computations or UI updates.
+
+[TODO: Some kind of image / code block??]
\ No newline at end of file
diff --git a/src/routes/reactivity/stores.mdx b/src/routes/reactivity/stores.mdx
index c8c7e9151..eb8a33bb3 100644
--- a/src/routes/reactivity/stores.mdx
+++ b/src/routes/reactivity/stores.mdx
@@ -1,4 +1,4 @@
 ---
-title: "Reactive State Management"
+title: "Stores"
 order: 5
 ---

From 8e9c161b71b7fc2634bc49628fbe87b086523631 Mon Sep 17 00:00:00 2001
From: LadyBluenotes <gerrardsarah@gmail.com>
Date: Wed, 17 Sep 2025 11:56:39 -0700
Subject: [PATCH 29/37] fix broken jsx

---
 old pages/concepts/understanding-jsx.mdx      | 20 +++++++++++--------
 src/routes/getting-started/counter.mdx        | 12 -----------
 .../getting-started/understanding-jsx.mdx     | 11 +++++-----
 src/routes/reactivity/basics.mdx              |  6 +++---
 src/routes/solid-router/concepts/data.json    |  1 -
 5 files changed, 20 insertions(+), 30 deletions(-)
 delete mode 100644 src/routes/getting-started/counter.mdx

diff --git a/old pages/concepts/understanding-jsx.mdx b/old pages/concepts/understanding-jsx.mdx
index 8dea79978..6609b4c12 100644
--- a/old pages/concepts/understanding-jsx.mdx	
+++ b/old pages/concepts/understanding-jsx.mdx	
@@ -11,7 +11,7 @@ This provides a concise and readable way to create and represent components.
 
 Solid was designed to align closely with HTML standards.
 
-```jsx
+```tsx
 const element = <h1>I'm JSX!!</h1>
 ```
 
@@ -19,7 +19,7 @@ It offers a distinct advantage, however: to copy/paste solutions from resources
 Solid sets itself apart by using JSX immediately as it returns [DOM](https://developer.mozilla.org/en-US/docs/Web/API/Document_Object_Model/Introduction) elements.
 This lets you use dynamic expressions within your HTML by allowing variables and functions to be references with the use of curly braces (`{ }`):
 
-```jsx
+```tsx
 const Component = () => {
 	const animal = { breed: "cat", name: "Midnight" }
 
@@ -42,7 +42,7 @@ This updates only the necessary parts of the DOM when changes occur in the under
 
 Where HTML lets you have disconnected tags at the top level, JSX requires that a component to return a single root element.
 
-:::advanced
+:::note
 When working with JSX, parts of your code are translated into structured HTML that is placed at the start of the file.
 Static elements are processed differently from dynamic ones, which might change based on data or user actions.
 For dynamic elements, special markers are added for better handling during rendering.
@@ -59,7 +59,7 @@ Self-closing tags are a must in JSX.
 Unlike in HTML, where elements like `<input>`, `<img>`, or `<br>` don't require explicit closure, JSX requires consistent self-closing tags.
 This helps to avoid potential rendering issues.
 
-```jsx
+```tsx
 <img src="./image-here.png" />
 ```
 
@@ -81,16 +81,17 @@ In JSX files, HTML attributes are used much like regular HTML, with a few key di
   (**Note:** When using ESLint, you will get a warning if you use lowercase.)
 - In cases where you can dynamically specify a value, you can replace the `"` and `"` with curly braces (`{ }`):
 
-```jsx
+```tsx
 <button class="myClass" onClick={handleClick}>
 	Click me!
 </button>
 ```
 
-    	:::note
-    	  If you wish to pass objects in JSX, such as with inline styling, you will have to use double curly braces (`{{ }}`).
+:::note
+
+If you wish to pass objects in JSX, such as with inline styling, you will have to use double curly braces (`{{ }}`).
 
-```jsx
+```tsx
 <button style={{
 	color: 'red',
 	font-size: '2rem',
@@ -98,6 +99,7 @@ In JSX files, HTML attributes are used much like regular HTML, with a few key di
   Click me!
 </button>
 ```
+
 :::
 
 ### JSX properties (props)
@@ -120,10 +122,12 @@ They connect the component with the data it requires, for seamless data flows an
   This results in components that react in real-time to data changes.
 
 :::note
+
 Expressions, whether fixed or dynamic, get applied *in the order defined within the JSX*.
 This works for a wide range of DOM elements, but will not work with elements that require attributes to be defined in a special order, such as input types with `type='range'`.
 
 When order influences an element's behavior, users must define the expressions in the order that the element is expected.
+
 :::
 
 For how to use props effectively in Solid, explore the [props page](/concepts/components/props).
diff --git a/src/routes/getting-started/counter.mdx b/src/routes/getting-started/counter.mdx
deleted file mode 100644
index ee8d28182..000000000
--- a/src/routes/getting-started/counter.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Counter Tutorial"
-order: 2
----
-
-[TODO]
-
-1. Open your newly scaffolded project in your code editor of choice.
-2. Create a new file called `Counter.jsx` in the `src/components` directory.
-3. In `Counter.tsx`, use Solid's `createSignal` to create a reactive counter state.
-4. Export the `Counter` component and import it into your main application file (e.g., `src/App.jsx`).
-5. Use the `Counter` component in your application and test its functionality.
\ No newline at end of file
diff --git a/src/routes/getting-started/understanding-jsx.mdx b/src/routes/getting-started/understanding-jsx.mdx
index 4c16b32e7..389c2922c 100644
--- a/src/routes/getting-started/understanding-jsx.mdx
+++ b/src/routes/getting-started/understanding-jsx.mdx
@@ -35,7 +35,7 @@ const component = () => {
 
 ## Solid's JSX Rules
 
-### 1. Return a Single Root Element
+### Return a Single Root Element
 
 Each component must return a single root element.
 Since JSX maintains the familiar tree-like structure of HTML, having a single root element helps keep the hierarchy clear.
@@ -52,14 +52,13 @@ function App() {
 }
 ```
 
-```advanced
+:::note
 JSX in Solid compiles into structured HTML.
 Static elements are optimized once, while dynamic ones get special markers so Solid can update them efficiently.
 Requiring a single root element keeps the hierarchy consistent and easier to update.
-```
-
+:::
 
-### 2. Close All Tags
+### Close All Tags
 
 All tags must be properly closed.
 This includes self-closing tags like `<img />`, `<input />`, and `<br />`.
@@ -72,7 +71,7 @@ This includes self-closing tags like `<img />`, `<input />`, and `<br />`.
 <img src="image.jpg" alt="Description">
 ```
 
-### 3. Properties vs Attributes
+### Properties vs Attributes
 
 In Solid's JSX, you can use both HTML attributes and JSX properties (props) to define element behavior and appearance.
 
diff --git a/src/routes/reactivity/basics.mdx b/src/routes/reactivity/basics.mdx
index 36df5c5fa..4cd25da77 100644
--- a/src/routes/reactivity/basics.mdx
+++ b/src/routes/reactivity/basics.mdx
@@ -15,7 +15,7 @@ This makes applications efficient and responsive, even as they grow.
 Solid’s reactivity is built on three key ideas: **signals, subscribers, and tracking scopes**.  
 Together, these create a system where updates are precise, automatic, and efficient.
 
-### Signals: Reactive values
+### Signals
 
 A **signal** is a reactive value container.
 They consist of 2 parts:
@@ -38,7 +38,7 @@ Signals can hold any type of value:
 
 Learn more in the [Signals page](/reactivity/signals).
 
-### Subscribers: Reactive consumers
+### Subscribers
 
 If signals are the **source of truth**, subscribers are the **reactive consumers**.
 
@@ -51,7 +51,7 @@ How subscribers work:
 2. **Dependency tracking** → those signals register the subscriber.
 3. **Response** → when a signal changes, the subscriber re-runs.
 
-### Tracking Scopes: Connecting signals & subscribers
+### Tracking Scopes
 
 A **tracking scope** is the environment where Solid records which signals are being used.
 When a signal is read within a tracking scope, it registers the current subscriber as a dependency.
diff --git a/src/routes/solid-router/concepts/data.json b/src/routes/solid-router/concepts/data.json
index 835a9fb96..8cef16056 100644
--- a/src/routes/solid-router/concepts/data.json
+++ b/src/routes/solid-router/concepts/data.json
@@ -8,7 +8,6 @@
 		"nesting.mdx",
 		"layouts.mdx",
 		"alternative-routers.mdx",
-		"queries.mdx",
 		"actions.mdx"
 	]
 }

From 795ea930a72e5184cbae74f9ac30dae6e14be516 Mon Sep 17 00:00:00 2001
From: LadyBluenotes <gerrardsarah@gmail.com>
Date: Wed, 17 Sep 2025 12:43:45 -0700
Subject: [PATCH 30/37] derived state section

---
 src/routes/reactivity/derived-state.mdx | 66 ++++++++++++++++++++++---
 1 file changed, 60 insertions(+), 6 deletions(-)

diff --git a/src/routes/reactivity/derived-state.mdx b/src/routes/reactivity/derived-state.mdx
index d0f749336..106ce7bdc 100644
--- a/src/routes/reactivity/derived-state.mdx
+++ b/src/routes/reactivity/derived-state.mdx
@@ -3,9 +3,63 @@ title: "Derived State"
 order: 3
 ---
 
-[TODO:
-Concept page on Memos
-- Improve on existing page
-- Move relevant sections to reference and vice versa
-- Link out to how-to for derived signals where appropriate
-]
\ No newline at end of file
+Derived state often refers to values that are computed based on other reactive values.
+Rather than storing multiple pieces of state and manually keeping them consistent, Solid encourages you to derive new values from existing signals, memos, or stores.
+
+The benefits of derived state:
+- You store only the minimal amount of state necessary.
+- Relationships between values are described declaratively, making it easier to understand how data flows through your application.
+- Derived values are automatically kept in sync with their dependencies.
+
+## Derived signals
+
+The simplest way to create derived state is by using a function that accesses one or more signals.
+
+```tsx
+const [count, setCount] = createSignal(0);
+
+// A derived signal: always reflects count * 2
+const double = () => count() * 2;
+
+console.log(double()); // 0
+setCount(5);
+console.log(double()); // 10
+```
+
+In the above example, `double` is a derived signal that computes its value based on the `count` signal.
+Whenever `count` changes, calling `double()` produces the correct and current value.
+Any component or effect that uses `double()`, too, will update automatically when `count` changes.
+
+### Limitations of derived signals
+
+While derived signals are simple and effective for many use cases, they have some limitations:
+
+- **They do not cache their results.** 
+    For derived signal call, the function is re-executed every time it is accessed, even if the underlying signals have not changed.
+    For trivial computations, this is not a problem, but for expensive calculations (eg. processing large datasets), this can lead to performance issues.
+- **They do not create their own reactive scope.**
+    A derived function runs only when you call it. 
+    Reactivity comes from the signals it touches, but there is no intermediate node in the reactivity graph.
+- **Dependent computations can cause unnecessary updates.**
+    If a derived signal is used within another derived signal or effect, any change to its dependencies will trigger the entire chain to re-evaluate, even if the final value does not change.
+
+In other words, derived signals are best suited for lightweight computations, but they may not be ideal for more complex or performance-sensitive scenarios.
+
+## Memoizing derived state
+
+Memos are a specialized type of derived state that address the limitations of simple derived signals.
+They cache results and only re-compute when their dependencies change, making them much more efficient for expensive or frequently accessed calculations.
+
+```tsx
+// add example
+```
+
+
+### Advantages of memos
+
+Memos offer several advantages over simple derived signals:
+
+- **Efficient execution** – a memo runs only once per dependency change, rather than re-executing every time it’s accessed.
+- **Cached results** – results are stored and reused, avoiding unnecessary recomputation of expensive logic.
+- **Change detection** – if dependencies change but the computed value is strictly equal (`===`) to the previous result, no downstream updates are triggered.
+- **Automatic tracking** – any signal or memo read inside a memo’s function is automatically tracked, so the memo re-evaluates only when those dependencies change.
\ No newline at end of file

From 741243cdccff5375ca799686f64bbc50432c5708 Mon Sep 17 00:00:00 2001
From: LadyBluenotes <gerrardsarah@gmail.com>
Date: Mon, 22 Sep 2025 10:10:18 -0700
Subject: [PATCH 31/37] working on stores page

---
 src/routes/reactivity/stores.mdx | 96 ++++++++++++++++++++++++++++++++
 1 file changed, 96 insertions(+)

diff --git a/src/routes/reactivity/stores.mdx b/src/routes/reactivity/stores.mdx
index eb8a33bb3..5a5384762 100644
--- a/src/routes/reactivity/stores.mdx
+++ b/src/routes/reactivity/stores.mdx
@@ -2,3 +2,99 @@
 title: "Stores"
 order: 5
 ---
+
+Stores are a state management primitive in Solid that provide a convenient, centralized way to handle structured data.
+Unlike signals, which are best suited for primitive values, stores are better for managing complex data structures like objects and arrays:
+
+- They provide fine-grained reactivity, meaning only the parts of the store that are accessed will trigger updates when they change.
+- They support **nested reactivity,** so you can track and update deeply nested properties without losing reactivity.
+- They make working with complex state easier while avoiding duplication or unnecessary recomputation.
+
+Stores are built on top of Solid's reactive system, leveraging [JavaScript's proxies](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy) to track property access and changes.
+
+## Creating a Store
+
+To create a store, you can use the `createStore` function from the `solid-js/store` package. 
+This function takes an initial value and returns a tuple containing the store and a setter function to update it.
+
+```tsx
+import { createStore } from "solid-js/store"
+
+// Initialize store
+const [store, setStore] = createStore({
+	userCount: 3,
+	users: [
+		{
+			id: 0,
+			username: "felix909",
+			location: "England",
+			loggedIn: false,
+		},
+		{
+			id: 1,
+			username: "tracy634",
+			location: "Canada",
+			loggedIn: true,
+		},
+		{
+			id: 2,
+			username: "johny123",
+			location: "India",
+			loggedIn: true,
+		},
+	],
+})
+```
+
+## Accessing store values
+
+Unlike signals, which are functions that need to be called to get their values, stores can be accessed directly like regular objects or arrays.
+
+```tsx
+console.log(store.userCount) // 3
+```
+
+Inside a tracking scope, store properties can be accessed directly, and any changes to those properties will trigger updates to the scope.
+
+:::note
+
+Stores create signals **lazily**.
+This means that a property only becomes reactive once accessed inside a tracking scope.
+:::
+
+```tsx
+const App = () => {
+	const [mySignal, setMySignal] = createSignal("This is a signal.")
+	const [store, setStore] = createStore({
+		userCount: 3,
+		users: [
+			{
+				id: 0,
+				username: "felix909",
+				location: "England",
+				loggedIn: false,
+			},
+			{
+				id: 1,
+				username: "tracy634",
+				location: "Canada",
+				loggedIn: true,
+			},
+			{
+				id: 2,
+				username: "johny123",
+				location: "India",
+				loggedIn: true,
+			},
+		],
+	})
+	return (
+		<div>
+			<h1>Hello, {store.users[0].username}</h1> {/* Accessing a store value */}
+			<span>{mySignal()}</span> {/* Accessing a signal */}
+		</div>
+	)
+}
+```
+
+##
\ No newline at end of file

From 4f5d07a02ddaaf02f53059da42414a914fe7f00a Mon Sep 17 00:00:00 2001
From: LadyBluenotes <gerrardsarah@gmail.com>
Date: Mon, 22 Sep 2025 10:30:07 -0700
Subject: [PATCH 32/37] fix broken link:

---
 src/routes/(getting-started)/data.json                   | 9 +++++++++
 .../installation.mdx                                     | 0
 .../quick-start.mdx                                      | 0
 .../{getting-started => (getting-started)}/todo.mdx      | 0
 .../understanding-jsx.mdx                                | 0
 src/routes/getting-started/data.json                     | 4 ----
 6 files changed, 9 insertions(+), 4 deletions(-)
 create mode 100644 src/routes/(getting-started)/data.json
 rename src/routes/{getting-started => (getting-started)}/installation.mdx (100%)
 rename src/routes/{getting-started => (getting-started)}/quick-start.mdx (100%)
 rename src/routes/{getting-started => (getting-started)}/todo.mdx (100%)
 rename src/routes/{getting-started => (getting-started)}/understanding-jsx.mdx (100%)
 delete mode 100644 src/routes/getting-started/data.json

diff --git a/src/routes/(getting-started)/data.json b/src/routes/(getting-started)/data.json
new file mode 100644
index 000000000..73ecec27d
--- /dev/null
+++ b/src/routes/(getting-started)/data.json
@@ -0,0 +1,9 @@
+{
+	"title": "Getting Started",
+	"pages": [
+		"installation.mdx",
+		"quick-start.mdx",
+		"understanding-jsx.mdx",
+		"todo.mdx"
+	]
+}
diff --git a/src/routes/getting-started/installation.mdx b/src/routes/(getting-started)/installation.mdx
similarity index 100%
rename from src/routes/getting-started/installation.mdx
rename to src/routes/(getting-started)/installation.mdx
diff --git a/src/routes/getting-started/quick-start.mdx b/src/routes/(getting-started)/quick-start.mdx
similarity index 100%
rename from src/routes/getting-started/quick-start.mdx
rename to src/routes/(getting-started)/quick-start.mdx
diff --git a/src/routes/getting-started/todo.mdx b/src/routes/(getting-started)/todo.mdx
similarity index 100%
rename from src/routes/getting-started/todo.mdx
rename to src/routes/(getting-started)/todo.mdx
diff --git a/src/routes/getting-started/understanding-jsx.mdx b/src/routes/(getting-started)/understanding-jsx.mdx
similarity index 100%
rename from src/routes/getting-started/understanding-jsx.mdx
rename to src/routes/(getting-started)/understanding-jsx.mdx
diff --git a/src/routes/getting-started/data.json b/src/routes/getting-started/data.json
deleted file mode 100644
index 5f04d10c2..000000000
--- a/src/routes/getting-started/data.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
-	"title": "Getting Started",
-	"pages": ["installation.mdx", "understanding-jsx.mdx", "todo.mdx"]
-}

From 01d9c0efc10da30c2a45c68b63112648707d2f9f Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Wed, 17 Sep 2025 15:12:55 -0700
Subject: [PATCH 33/37] Bump @types/node from 24.3.1 to 24.5.0 (#1264)

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
---
 package.json   |  2 +-
 pnpm-lock.yaml | 92 +++++++++++++++++++++++++-------------------------
 2 files changed, 47 insertions(+), 47 deletions(-)

diff --git a/package.json b/package.json
index 2538ea287..6876ddb2a 100644
--- a/package.json
+++ b/package.json
@@ -46,7 +46,7 @@
 		"@kobalte/tailwindcss": "^0.9.0",
 		"@orama/crawly": "^0.0.6",
 		"@tailwindcss/typography": "^0.5.16",
-		"@types/node": "^24.3.1",
+		"@types/node": "^24.5.1",
 		"@typescript-eslint/eslint-plugin": "^8.41.0",
 		"@typescript-eslint/parser": "^8.43.0",
 		"autoprefixer": "^10.4.21",
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index 7059c7b20..eb2ad3598 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -13,7 +13,7 @@ importers:
         version: 0.13.11(solid-js@1.9.9)
       '@kobalte/solidbase':
         specifier: ^0.2.17
-        version: 0.2.17(@algolia/client-search@5.14.2)(@solidjs/start@1.2.0(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)))(@vue/compiler-sfc@3.5.16)(acorn@8.15.0)(expressive-code@0.40.2)(react@18.3.1)(search-insights@2.17.3)(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+        version: 0.2.17(@algolia/client-search@5.14.2)(@solidjs/start@1.2.0(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)))(@vue/compiler-sfc@3.5.16)(acorn@8.15.0)(expressive-code@0.40.2)(react@18.3.1)(search-insights@2.17.3)(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       '@lunariajs/core':
         specifier: ^0.1.1
         version: 0.1.1
@@ -40,7 +40,7 @@ importers:
         version: 0.15.3(solid-js@1.9.9)
       '@solidjs/start':
         specifier: ^1.2.0
-        version: 1.2.0(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+        version: 1.2.0(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       dotenv:
         specifier: ^17.2.2
         version: 17.2.2
@@ -70,7 +70,7 @@ importers:
         version: 0.3.0(solid-js@1.9.9)
       vinxi:
         specifier: ^0.5.7
-        version: 0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+        version: 0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
       zod:
         specifier: ^4.1.8
         version: 4.1.8
@@ -88,8 +88,8 @@ importers:
         specifier: ^0.5.16
         version: 0.5.16(tailwindcss@3.4.17)
       '@types/node':
-        specifier: ^24.3.1
-        version: 24.3.1
+        specifier: ^24.5.1
+        version: 24.5.1
       '@typescript-eslint/eslint-plugin':
         specifier: ^8.41.0
         version: 8.41.0(@typescript-eslint/parser@8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
@@ -125,7 +125,7 @@ importers:
         version: 8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)
       vite:
         specifier: ^6.3.5
-        version: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+        version: 6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
 
 packages:
 
@@ -1539,8 +1539,8 @@ packages:
   '@types/node@17.0.45':
     resolution: {integrity: sha512-w+tIMs3rq2afQdsPJlODhoUEKzFP1ayaoyl1CcnwtIlsVe7K7bA1NGm4s3PraqTLlXnbIN84zuBlxBWo1u9BLw==}
 
-  '@types/node@24.3.1':
-    resolution: {integrity: sha512-3vXmQDXy+woz+gnrTvuvNrPzekOi+Ds0ReMxw0LzBiK3a+1k0kQn9f2NWk+lgD4rJehFUmYy2gMhJ2ZI+7YP9g==}
+  '@types/node@24.5.1':
+    resolution: {integrity: sha512-/SQdmUP2xa+1rdx7VwB9yPq8PaKej8TD5cQ+XfKDPWWC+VDJU4rvVVagXqKUzhKjtFoNA8rXDJAkCxQPAe00+Q==}
 
   '@types/normalize-package-data@2.4.4':
     resolution: {integrity: sha512-37i+OaWTh9qeK4LSHPsyRC7NahnGotNuZvjLSgcPzblpHB3rrCJxAOgI5gCdKm7coonsaX1Of0ILiTcnZjbfxA==}
@@ -4732,8 +4732,8 @@ packages:
   undici-types@5.28.4:
     resolution: {integrity: sha512-3OeMF5Lyowe8VW0skf5qaIE7Or3yS9LS7fvMUI0gg4YxpIBVg0L8BxCmROw2CcYhSkpR68Epz7CGc8MPj94Uww==}
 
-  undici-types@7.10.0:
-    resolution: {integrity: sha512-t5Fy/nfn+14LuOc2KNYg75vZqClpAiqscVvMygNnlsHBFpSXdJaYtXMcdNLpl/Qvc3P2cB3s6lOV51nqsFq4ag==}
+  undici-types@7.12.0:
+    resolution: {integrity: sha512-goOacqME2GYyOZZfb5Lgtu+1IDmAlAEu5xnD3+xTzS10hT0vzpf0SPjkXwAw9Jm+4n/mQGDP3LO8CPbYROeBfQ==}
 
   unenv@1.10.0:
     resolution: {integrity: sha512-wY5bskBQFL9n3Eca5XnhH6KbUo/tfvkwm9OpcdCvLaeA7piBNbavbOKJySEwQ1V0RH6HvNlSAFRTpvTqgKRQXQ==}
@@ -5922,7 +5922,7 @@ snapshots:
       solid-presence: 0.1.8(solid-js@1.9.9)
       solid-prevent-scroll: 0.1.10(solid-js@1.9.9)
 
-  '@kobalte/solidbase@0.2.17(@algolia/client-search@5.14.2)(@solidjs/start@1.2.0(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)))(@vue/compiler-sfc@3.5.16)(acorn@8.15.0)(expressive-code@0.40.2)(react@18.3.1)(search-insights@2.17.3)(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
+  '@kobalte/solidbase@0.2.17(@algolia/client-search@5.14.2)(@solidjs/start@1.2.0(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)))(@vue/compiler-sfc@3.5.16)(acorn@8.15.0)(expressive-code@0.40.2)(react@18.3.1)(search-insights@2.17.3)(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
       '@alloc/quick-lru': 5.2.0
       '@bprogress/core': 1.1.18
@@ -5947,7 +5947,7 @@ snapshots:
       '@solid-primitives/storage': 4.3.1(solid-js@1.9.9)
       '@solidjs/meta': 0.29.4(solid-js@1.9.9)
       '@solidjs/router': 0.15.3(solid-js@1.9.9)
-      '@solidjs/start': 1.2.0(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      '@solidjs/start': 1.2.0(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       cross-spawn: 7.0.3
       esast-util-from-js: 2.0.1
       estree-util-value-to-estree: 3.2.1
@@ -5966,7 +5966,7 @@ snapshots:
       remark-frontmatter: 5.0.0
       remark-gfm: 4.0.0
       solid-js: 1.9.9
-      solid-mdx: 0.0.7(solid-js@1.9.9)(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      solid-mdx: 0.0.7(solid-js@1.9.9)(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       toml: 3.0.0
       typescript: 5.9.2
       unified: 11.0.5
@@ -5976,8 +5976,8 @@ snapshots:
       unist-util-visit: 5.0.0
       unplugin-auto-import: 19.1.1
       unplugin-icons: 22.1.0(@vue/compiler-sfc@3.5.16)
-      vinxi: 0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
-      vite: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vinxi: 0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vite: 6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
       yaml: 2.8.0
     transitivePeerDependencies:
       - '@algolia/client-search'
@@ -6663,11 +6663,11 @@ snapshots:
     dependencies:
       solid-js: 1.9.9
 
-  '@solidjs/start@1.2.0(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
+  '@solidjs/start@1.2.0(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
-      '@tanstack/server-functions-plugin': 1.121.21(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
-      '@vinxi/plugin-directives': 0.5.1(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
-      '@vinxi/server-components': 0.5.1(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      '@tanstack/server-functions-plugin': 1.121.21(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      '@vinxi/plugin-directives': 0.5.1(vinxi@0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      '@vinxi/server-components': 0.5.1(vinxi@0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       cookie-es: 2.0.0
       defu: 6.1.4
       error-stack-parser: 2.1.4
@@ -6679,8 +6679,8 @@ snapshots:
       source-map-js: 1.2.1
       terracotta: 1.0.6(solid-js@1.9.9)
       tinyglobby: 0.2.15
-      vinxi: 0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
-      vite-plugin-solid: 2.11.8(solid-js@1.9.9)(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      vinxi: 0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vite-plugin-solid: 2.11.8(solid-js@1.9.9)(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
     transitivePeerDependencies:
       - '@testing-library/jest-dom'
       - solid-js
@@ -6701,7 +6701,7 @@ snapshots:
       postcss-selector-parser: 6.0.10
       tailwindcss: 3.4.17
 
-  '@tanstack/directive-functions-plugin@1.121.21(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
+  '@tanstack/directive-functions-plugin@1.121.21(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
       '@babel/code-frame': 7.26.2
       '@babel/core': 7.28.4
@@ -6710,7 +6710,7 @@ snapshots:
       '@tanstack/router-utils': 1.131.2
       babel-dead-code-elimination: 1.0.10
       tiny-invariant: 1.3.3
-      vite: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vite: 6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
     transitivePeerDependencies:
       - supports-color
 
@@ -6725,7 +6725,7 @@ snapshots:
     transitivePeerDependencies:
       - supports-color
 
-  '@tanstack/server-functions-plugin@1.121.21(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
+  '@tanstack/server-functions-plugin@1.121.21(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
       '@babel/code-frame': 7.26.2
       '@babel/core': 7.28.4
@@ -6734,7 +6734,7 @@ snapshots:
       '@babel/template': 7.27.2
       '@babel/traverse': 7.28.4
       '@babel/types': 7.28.4
-      '@tanstack/directive-functions-plugin': 1.121.21(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      '@tanstack/directive-functions-plugin': 1.121.21(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       babel-dead-code-elimination: 1.0.10
       tiny-invariant: 1.3.3
     transitivePeerDependencies:
@@ -6800,9 +6800,9 @@ snapshots:
 
   '@types/node@17.0.45': {}
 
-  '@types/node@24.3.1':
+  '@types/node@24.5.1':
     dependencies:
-      undici-types: 7.10.0
+      undici-types: 7.12.0
 
   '@types/normalize-package-data@2.4.4': {}
 
@@ -6810,7 +6810,7 @@ snapshots:
 
   '@types/sax@1.2.7':
     dependencies:
-      '@types/node': 24.3.1
+      '@types/node': 24.5.1
 
   '@types/triple-beam@1.3.5': {}
 
@@ -6822,7 +6822,7 @@ snapshots:
 
   '@types/yauzl@2.10.3':
     dependencies:
-      '@types/node': 24.3.1
+      '@types/node': 24.5.1
     optional: true
 
   '@typescript-eslint/eslint-plugin@8.41.0(@typescript-eslint/parser@8.43.0(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2))(eslint@9.35.0(jiti@2.4.2))(typescript@5.9.2)':
@@ -7099,7 +7099,7 @@ snapshots:
       untun: 0.1.3
       uqr: 0.1.2
 
-  '@vinxi/plugin-directives@0.5.1(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
+  '@vinxi/plugin-directives@0.5.1(vinxi@0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
       '@babel/parser': 7.28.4
       acorn: 8.15.0
@@ -7110,18 +7110,18 @@ snapshots:
       magicast: 0.2.11
       recast: 0.23.11
       tslib: 2.8.1
-      vinxi: 0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vinxi: 0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
 
-  '@vinxi/server-components@0.5.1(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
+  '@vinxi/server-components@0.5.1(vinxi@0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))':
     dependencies:
-      '@vinxi/plugin-directives': 0.5.1(vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      '@vinxi/plugin-directives': 0.5.1(vinxi@0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
       acorn: 8.15.0
       acorn-loose: 8.5.2
       acorn-typescript: 1.4.13(acorn@8.15.0)
       astring: 1.9.0
       magicast: 0.2.11
       recast: 0.23.11
-      vinxi: 0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vinxi: 0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
 
   '@vue/compiler-core@3.5.16':
     dependencies:
@@ -10394,10 +10394,10 @@ snapshots:
       '@corvu/utils': 0.4.2(solid-js@1.9.9)
       solid-js: 1.9.9
 
-  solid-mdx@0.0.7(solid-js@1.9.9)(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)):
+  solid-mdx@0.0.7(solid-js@1.9.9)(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)):
     dependencies:
       solid-js: 1.9.9
-      vite: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vite: 6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
 
   solid-presence@0.1.8(solid-js@1.9.9):
     dependencies:
@@ -10715,7 +10715,7 @@ snapshots:
 
   undici-types@5.28.4: {}
 
-  undici-types@7.10.0: {}
+  undici-types@7.12.0: {}
 
   unenv@1.10.0:
     dependencies:
@@ -10955,7 +10955,7 @@ snapshots:
       '@types/unist': 3.0.3
       vfile-message: 4.0.2
 
-  vinxi@0.5.7(@types/node@24.3.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0):
+  vinxi@0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0):
     dependencies:
       '@babel/core': 7.25.8
       '@babel/plugin-syntax-jsx': 7.25.7(@babel/core@7.25.8)
@@ -10989,7 +10989,7 @@ snapshots:
       unctx: 2.4.1
       unenv: 1.10.0
       unstorage: 1.16.0(db0@0.3.2)(ioredis@5.6.1)
-      vite: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vite: 6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
       zod: 3.25.76
     transitivePeerDependencies:
       - '@azure/app-configuration'
@@ -11033,7 +11033,7 @@ snapshots:
       - xml2js
       - yaml
 
-  vite-plugin-solid@2.11.8(solid-js@1.9.9)(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)):
+  vite-plugin-solid@2.11.8(solid-js@1.9.9)(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)):
     dependencies:
       '@babel/core': 7.28.4
       '@types/babel__core': 7.20.5
@@ -11041,12 +11041,12 @@ snapshots:
       merge-anything: 5.1.7
       solid-js: 1.9.9
       solid-refresh: 0.6.3(solid-js@1.9.9)
-      vite: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
-      vitefu: 1.1.1(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
+      vite: 6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vitefu: 1.1.1(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
     transitivePeerDependencies:
       - supports-color
 
-  vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0):
+  vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0):
     dependencies:
       esbuild: 0.25.5
       fdir: 6.4.6(picomatch@4.0.2)
@@ -11055,15 +11055,15 @@ snapshots:
       rollup: 4.43.0
       tinyglobby: 0.2.14
     optionalDependencies:
-      '@types/node': 24.3.1
+      '@types/node': 24.5.1
       fsevents: 2.3.3
       jiti: 2.4.2
       terser: 5.42.0
       yaml: 2.8.0
 
-  vitefu@1.1.1(vite@6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)):
+  vitefu@1.1.1(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)):
     optionalDependencies:
-      vite: 6.3.5(@types/node@24.3.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
+      vite: 6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)
 
   web-namespaces@2.0.1: {}
 

From 09138ff674b8dea372ff63b89fb5954bb99de31d Mon Sep 17 00:00:00 2001
From: LadyBluenotes <gerrardsarah@gmail.com>
Date: Sat, 23 Aug 2025 21:46:01 -0700
Subject: [PATCH 34/37] start of v2 structure

---
 src/routes/getting-started/counter.mdx     | 12 ++++++++++
 src/routes/getting-started/data.json       |  4 ++++
 src/routes/getting-started/quick-start.mdx | 26 ++++++++++++++++++++++
 src/routes/getting-started/todo.mdx        | 15 +++++++++++++
 4 files changed, 57 insertions(+)
 create mode 100644 src/routes/getting-started/counter.mdx
 create mode 100644 src/routes/getting-started/data.json
 create mode 100644 src/routes/getting-started/quick-start.mdx
 create mode 100644 src/routes/getting-started/todo.mdx

diff --git a/src/routes/getting-started/counter.mdx b/src/routes/getting-started/counter.mdx
new file mode 100644
index 000000000..ee8d28182
--- /dev/null
+++ b/src/routes/getting-started/counter.mdx
@@ -0,0 +1,12 @@
+---
+title: "Counter Tutorial"
+order: 2
+---
+
+[TODO]
+
+1. Open your newly scaffolded project in your code editor of choice.
+2. Create a new file called `Counter.jsx` in the `src/components` directory.
+3. In `Counter.tsx`, use Solid's `createSignal` to create a reactive counter state.
+4. Export the `Counter` component and import it into your main application file (e.g., `src/App.jsx`).
+5. Use the `Counter` component in your application and test its functionality.
\ No newline at end of file
diff --git a/src/routes/getting-started/data.json b/src/routes/getting-started/data.json
new file mode 100644
index 000000000..4b2a8a548
--- /dev/null
+++ b/src/routes/getting-started/data.json
@@ -0,0 +1,4 @@
+{
+	"title": "Getting Started",
+	"pages": ["quick-start.mdx", "counter.mdx", "todo.mdx"]
+}
diff --git a/src/routes/getting-started/quick-start.mdx b/src/routes/getting-started/quick-start.mdx
new file mode 100644
index 000000000..4e5a93110
--- /dev/null
+++ b/src/routes/getting-started/quick-start.mdx
@@ -0,0 +1,26 @@
+---
+title: Quick Start Guide
+order: 1
+---
+
+The fastest way to try Solid is to create a new project and run it locally.
+In just a few minutes, you’ll have a working Solid app running in your browser.
+
+## Solid in your Browser
+
+If you're looking to experiment with Solid without setting up a local environment, open the [Solid Playground](https://playground.solidjs.com/) in your browser.
+
+If you prefer a more complete development setup, you can use the StackBlitz [Javascript](https://stackblitz.com/github/solidjs/templates/tree/master/js) or [TypeScript](https://stackblitz.com/github/solidjs/templates/tree/master/ts) templates.
+
+## Create a New Project
+
+:::note[Before You Begin]
+Make sure you have a recent version of your prefer JavaScript runtime installed, such as [Node.js](https://nodejs.org/en), [Bun](https://bun.sh/), or [Deno](https://deno.com/).
+:::
+
+[TODO]
+
+- Navigate to directory and run command
+- CLI will take you through options
+- Once you've selected your options, the CLI will prompt you to install the dependencies and start the development server
+- Open browser and navigate to the provided local URL to see your new Solid app in action!
\ No newline at end of file
diff --git a/src/routes/getting-started/todo.mdx b/src/routes/getting-started/todo.mdx
new file mode 100644
index 000000000..4e031d3d1
--- /dev/null
+++ b/src/routes/getting-started/todo.mdx
@@ -0,0 +1,15 @@
+---
+title: Todo Tutorial
+order: 3
+---
+
+[TODO]
+
+1. Open your newly scaffolded project in your code editor of choice.
+
+- Signal to track all tasks
+- Function to add a new task
+- Function to remove a task
+- Function to toggle task completion
+- Show number of completed tasks
+- Show number of tasks
\ No newline at end of file

From 39cbee393eede42ddfc2259012a822df15875c37 Mon Sep 17 00:00:00 2001
From: LadyBluenotes <gerrardsarah@gmail.com>
Date: Mon, 22 Sep 2025 10:38:05 -0700
Subject: [PATCH 35/37] fix getting-started

---
 src/routes/(getting-started)/data.json        |  9 -------
 src/routes/(getting-started)/quick-start.mdx  | 26 -------------------
 src/routes/(getting-started)/todo.mdx         | 15 -----------
 src/routes/getting-started/counter.mdx        | 12 ---------
 src/routes/getting-started/data.json          |  7 ++++-
 .../installation.mdx                          |  0
 .../understanding-jsx.mdx                     |  0
 7 files changed, 6 insertions(+), 63 deletions(-)
 delete mode 100644 src/routes/(getting-started)/data.json
 delete mode 100644 src/routes/(getting-started)/quick-start.mdx
 delete mode 100644 src/routes/(getting-started)/todo.mdx
 delete mode 100644 src/routes/getting-started/counter.mdx
 rename src/routes/{(getting-started) => getting-started}/installation.mdx (100%)
 rename src/routes/{(getting-started) => getting-started}/understanding-jsx.mdx (100%)

diff --git a/src/routes/(getting-started)/data.json b/src/routes/(getting-started)/data.json
deleted file mode 100644
index 73ecec27d..000000000
--- a/src/routes/(getting-started)/data.json
+++ /dev/null
@@ -1,9 +0,0 @@
-{
-	"title": "Getting Started",
-	"pages": [
-		"installation.mdx",
-		"quick-start.mdx",
-		"understanding-jsx.mdx",
-		"todo.mdx"
-	]
-}
diff --git a/src/routes/(getting-started)/quick-start.mdx b/src/routes/(getting-started)/quick-start.mdx
deleted file mode 100644
index 4e5a93110..000000000
--- a/src/routes/(getting-started)/quick-start.mdx
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Quick Start Guide
-order: 1
----
-
-The fastest way to try Solid is to create a new project and run it locally.
-In just a few minutes, you’ll have a working Solid app running in your browser.
-
-## Solid in your Browser
-
-If you're looking to experiment with Solid without setting up a local environment, open the [Solid Playground](https://playground.solidjs.com/) in your browser.
-
-If you prefer a more complete development setup, you can use the StackBlitz [Javascript](https://stackblitz.com/github/solidjs/templates/tree/master/js) or [TypeScript](https://stackblitz.com/github/solidjs/templates/tree/master/ts) templates.
-
-## Create a New Project
-
-:::note[Before You Begin]
-Make sure you have a recent version of your prefer JavaScript runtime installed, such as [Node.js](https://nodejs.org/en), [Bun](https://bun.sh/), or [Deno](https://deno.com/).
-:::
-
-[TODO]
-
-- Navigate to directory and run command
-- CLI will take you through options
-- Once you've selected your options, the CLI will prompt you to install the dependencies and start the development server
-- Open browser and navigate to the provided local URL to see your new Solid app in action!
\ No newline at end of file
diff --git a/src/routes/(getting-started)/todo.mdx b/src/routes/(getting-started)/todo.mdx
deleted file mode 100644
index 4e031d3d1..000000000
--- a/src/routes/(getting-started)/todo.mdx
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Todo Tutorial
-order: 3
----
-
-[TODO]
-
-1. Open your newly scaffolded project in your code editor of choice.
-
-- Signal to track all tasks
-- Function to add a new task
-- Function to remove a task
-- Function to toggle task completion
-- Show number of completed tasks
-- Show number of tasks
\ No newline at end of file
diff --git a/src/routes/getting-started/counter.mdx b/src/routes/getting-started/counter.mdx
deleted file mode 100644
index ee8d28182..000000000
--- a/src/routes/getting-started/counter.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
----
-title: "Counter Tutorial"
-order: 2
----
-
-[TODO]
-
-1. Open your newly scaffolded project in your code editor of choice.
-2. Create a new file called `Counter.jsx` in the `src/components` directory.
-3. In `Counter.tsx`, use Solid's `createSignal` to create a reactive counter state.
-4. Export the `Counter` component and import it into your main application file (e.g., `src/App.jsx`).
-5. Use the `Counter` component in your application and test its functionality.
\ No newline at end of file
diff --git a/src/routes/getting-started/data.json b/src/routes/getting-started/data.json
index 4b2a8a548..8be8d8953 100644
--- a/src/routes/getting-started/data.json
+++ b/src/routes/getting-started/data.json
@@ -1,4 +1,9 @@
 {
 	"title": "Getting Started",
-	"pages": ["quick-start.mdx", "counter.mdx", "todo.mdx"]
+	"pages": [
+		"installation.mdx",
+		"quick-start.mdx",
+		"todo.mdx",
+		"understanding-jsx.mdx"
+	]
 }
diff --git a/src/routes/(getting-started)/installation.mdx b/src/routes/getting-started/installation.mdx
similarity index 100%
rename from src/routes/(getting-started)/installation.mdx
rename to src/routes/getting-started/installation.mdx
diff --git a/src/routes/(getting-started)/understanding-jsx.mdx b/src/routes/getting-started/understanding-jsx.mdx
similarity index 100%
rename from src/routes/(getting-started)/understanding-jsx.mdx
rename to src/routes/getting-started/understanding-jsx.mdx

From 673d79ec061868babf942d4cfe3b6658eca5a31e Mon Sep 17 00:00:00 2001
From: LadyBluenotes <gerrardsarah@gmail.com>
Date: Mon, 22 Sep 2025 10:40:45 -0700
Subject: [PATCH 36/37] rm old component

---
 src/routes/reactivity/overview.mdx     |   5 --
 src/solidbase-theme/mdx-components.tsx |  25 ------
 src/ui/eraser-link/eraser-link.css     |  20 -----
 src/ui/eraser-link/index.tsx           | 115 -------------------------
 4 files changed, 165 deletions(-)
 delete mode 100644 src/ui/eraser-link/eraser-link.css
 delete mode 100644 src/ui/eraser-link/index.tsx

diff --git a/src/routes/reactivity/overview.mdx b/src/routes/reactivity/overview.mdx
index 725a2186c..f6351bcd0 100644
--- a/src/routes/reactivity/overview.mdx
+++ b/src/routes/reactivity/overview.mdx
@@ -56,11 +56,6 @@ When called within a reactive context, it will give access to the current value
 - **Setters**: This function is responsible for updating the value of a signal.
 To trigger reactivity, setters notify the system that the signal's value has changed, prompting anything that depends on the signal to re-evaluate and update accordingly.
 
-<EraserLink
-	href="https://app.eraser.io/workspace/maDvFw5OryuPJOwSLyK9?elements=lseAEjGlKLslaVsTlfej_g"
-	preview="https://app.eraser.io/workspace/maDvFw5OryuPJOwSLyK9/preview?elements=lseAEjGlKLslaVsTlfej_g&type=embed"
-/>
-
 ### Subscribers
 
 Subscribers refer to other reactive contexts or components that depend on the value of a signal.
diff --git a/src/solidbase-theme/mdx-components.tsx b/src/solidbase-theme/mdx-components.tsx
index 28a3a1107..dd51c1037 100644
--- a/src/solidbase-theme/mdx-components.tsx
+++ b/src/solidbase-theme/mdx-components.tsx
@@ -10,7 +10,6 @@ import {
 import { isServer } from "solid-js/web";
 
 import { A } from "~/ui/i18n-anchor";
-import { clientOnly } from "@solidjs/start";
 import { Callout } from "~/ui/callout";
 import { Tabs, TabList, TabPanel, Tab } from "~/ui/tabs";
 
@@ -20,8 +19,6 @@ export { Callout } from "~/ui/callout";
 export { QuickLinks } from "~/ui/quick-links";
 export { ImageLinks } from "~/ui/image-links";
 
-const EraserLinkImpl = clientOnly(() => import("../ui/eraser-link"));
-
 type CalloutType = "note" | "tip" | "advanced" | "caution" | "danger";
 
 export const DirectiveContainer = (
@@ -69,28 +66,6 @@ export const DirectiveContainer = (
 export const strong = (props: ParentProps) => (
 	<b class="font-semibold">{props.children}</b>
 );
-export const EraserLink = (
-	props: ParentProps<{ href: string; preview: string }>
-) => {
-	const [, rest] = splitProps(props, ["children"]);
-
-	if (!isServer) {
-		return <EraserLinkImpl {...rest} />;
-	} else {
-		return (
-			<a
-				aria-hidden={true}
-				tabIndex="-1"
-				href={props.href}
-				class="font-semibold text-blue-700 no-underline shadow-[inset_0_-2px_0_0_var(--tw-prose-background,#38bdf8),inset_0_calc(-1*(var(--tw-prose-underline-size,2px)+2px))_0_0_var(--tw-prose-underline,theme(colors.blue.400))] hover:[--tw-prose-underline-size:4px] dark:text-blue-400 dark:shadow-[inset_0_calc(-1*var(--tw-prose-underline-size,2px))_0_0_var(--tw-prose-underline,theme(colors.blue.800))] dark:[--tw-prose-background:theme(colors.slate.900)] dark:hover:[--tw-prose-underline-size:6px]"
-				rel="noopener noreferrer"
-			>
-				View on Eraser
-				<img src={props.preview} />
-			</a>
-		);
-	}
-};
 export const ssr = (props: ParentProps) => <>{props.children}</>;
 export const spa = () => <></>;
 export const h1 = (props: ParentProps) => (
diff --git a/src/ui/eraser-link/eraser-link.css b/src/ui/eraser-link/eraser-link.css
deleted file mode 100644
index e4973bb8a..000000000
--- a/src/ui/eraser-link/eraser-link.css
+++ /dev/null
@@ -1,20 +0,0 @@
-.eraserLinkContainer {
-	position: absolute;
-	top: 40px;
-	right: 10px;
-	height: 29px;
-	width: 43px;
-	transition: width 200ms ease-in-out;
-	overflow: hidden;
-	background-color: #fefefe;
-	border: 1px solid #e4e4e4;
-	border-radius: 3px;
-}
-.eraserLinkContainer:hover {
-	width: 149px;
-}
-.eraserLinkContainer img {
-	position: absolute;
-	top: -1px;
-	left: -5px;
-}
diff --git a/src/ui/eraser-link/index.tsx b/src/ui/eraser-link/index.tsx
deleted file mode 100644
index 76bdd6f46..000000000
--- a/src/ui/eraser-link/index.tsx
+++ /dev/null
@@ -1,115 +0,0 @@
-import { ParentProps, Show, createSignal } from "solid-js";
-import "./eraser-link.css";
-
-const ERASER_TRACKING_PARAMS = "";
-
-type EraserLinkData = {
-	workspaceId: string;
-	elementsId?: string;
-};
-
-const getEraserLinkData = (href: string): EraserLinkData | null => {
-	const matches = /app.eraser.io\/workspace\/(\w+)(.*elements=(\w+))?/.exec(
-		href
-	);
-
-	if (!matches) {
-		return null;
-	}
-
-	if (matches[3]) {
-		return {
-			workspaceId: matches[1],
-			elementsId: matches[3],
-		};
-	}
-	return {
-		workspaceId: matches[1],
-	};
-};
-
-const EraserLink = (
-	props: ParentProps<{
-		linkData: EraserLinkData;
-	}>
-) => {
-	const workspaceUrl = `https://app.eraser.io/workspace/${props.linkData.workspaceId}`;
-	const elementParams = props.linkData.elementsId
-		? `elements=${props.linkData.elementsId}`
-		: "";
-
-	const linkUrl = elementParams
-		? `${workspaceUrl}?${elementParams}&${ERASER_TRACKING_PARAMS}`
-		: `${workspaceUrl}?${ERASER_TRACKING_PARAMS}`;
-
-	const [isLoaded, setIsLoaded] = createSignal(false);
-
-	// if there are no children or this was a right click-copy as markdown embed.
-	return (
-		<Show
-			when={
-				props.children === undefined ||
-				(Array.isArray(props.children) &&
-					props.children[0] === "View on Eraser")
-			}
-			fallback={
-				<a
-					href={linkUrl}
-					class="dark:text-solid-darklink text-solid-lightlink break-normal font-semibold leading-normal transition duration-100 ease-in hover:underline"
-					rel="noopener noreferrer"
-				>
-					{props.children}
-				</a>
-			}
-		>
-			<a
-				href={linkUrl}
-				class="relative inline-block"
-				target="_blank"
-				rel="noopener noreferrer"
-			>
-				<img
-					src={
-						elementParams
-							? `${workspaceUrl}/preview?${elementParams}&type=embed`
-							: `${workspaceUrl}/preview`
-					}
-					alt={""}
-					onLoad={() => setIsLoaded(true)}
-				/>
-				{isLoaded() ? (
-					<div class="eraserLinkContainer">
-						<img
-							src="https://firebasestorage.googleapis.com/v0/b/second-petal-295822.appspot.com/o/images%2Fgithub%2FOpen%20in%20Eraser.svg?alt=media&token=968381c8-a7e7-472a-8ed6-4a6626da5501"
-							class="m-0 max-w-none"
-							alt="Open in Eraser"
-						/>
-					</div>
-				) : null}
-			</a>
-		</Show>
-	);
-};
-
-export default function EraserOrAnchor(props: ParentProps<{ href: string }>) {
-	const eraserLinkData = getEraserLinkData(props.href);
-
-	return (
-		<Show
-			when={eraserLinkData}
-			fallback={
-				<a
-					{...props}
-					class="dark:text-solid-darklink text-solid-lightlink break-normal font-semibold leading-normal transition duration-100 ease-in hover:underline"
-					rel="noopener noreferrer"
-				>
-					{props.children}
-				</a>
-			}
-		>
-			{(eraserLinkData) => (
-				<EraserLink linkData={eraserLinkData()}>{props.children}</EraserLink>
-			)}
-		</Show>
-	);
-}

From bd8bfff1413e0ac9b36957632d9711f12ee4f6a4 Mon Sep 17 00:00:00 2001
From: LadyBluenotes <gerrardsarah@gmail.com>
Date: Mon, 22 Sep 2025 10:57:52 -0700
Subject: [PATCH 37/37] remove lunaria

---
 lunaria.config.json | 57 -----------------------------------
 lunaria/styles.css  |  4 ---
 package.json        |  5 +---
 pnpm-lock.yaml      | 72 ---------------------------------------------
 4 files changed, 1 insertion(+), 137 deletions(-)
 delete mode 100644 lunaria.config.json
 delete mode 100644 lunaria/styles.css

diff --git a/lunaria.config.json b/lunaria.config.json
deleted file mode 100644
index 63fd45cd1..000000000
--- a/lunaria.config.json
+++ /dev/null
@@ -1,57 +0,0 @@
-{
-	"$schema": "./node_modules/@lunariajs/core/config.schema.json",
-	"repository": {
-		"name": "solidjs/solid-docs-next",
-		"branch": "main",
-		"hosting": "github"
-	},
-	"defaultLocale": {
-		"label": "English",
-		"lang": "en"
-	},
-	"files": [
-		{
-			"type": "universal",
-			"location": "src/routes/**/*.{mdx,md}",
-			"pattern": "src/routes/@lang/@path"
-		},
-		{
-			"location": "src/i18n/dictionaries/**/ui.ts",
-			"pattern": "src/i18n/dictionaries/@lang/@path",
-			"type": "dictionary"
-		}
-	],
-	"locales": [
-		{
-			"label": "Português do Brasil",
-			"lang": "pt-br"
-		}
-	],
-	"outDir": "./public/i18n-status",
-	"dashboard": {
-		"site": "https://docs.solidjs.com/i18n-status",
-		"title": "Solid Docs Translation Status",
-		"description": "Translation progress tracker for the Solid Docs site",
-    	"basesToHide": ["src/routes/", "src/i18n/dictionaries/"],
-		"favicon": {
-			"external": [
-				{
-					"link": "https://docs.solidjs.com/favicon.ico",
-					"type": "image/x-icon"
-				},
-				{
-					"link": "https://docs.solidjs.com/favicon.svg",
-					"type": "image/svg+xml"
-				}
-			]
-		},
-		"customCss": ["./lunaria/styles.css"],
-		"ui": {
-			"statusByLocale.heading": "Translation progress by locale",
-			"statusByLocale.incompleteLocalizationLink": "incomplete translation",
-			"statusByLocale.outdatedLocalizationLink": "outdated translation",
-			"statusByLocale.completeLocalization": "This translation is complete, amazing job! 🎉",
-			"statusByFile.heading": "Translation status by file"
-		}
-	}
-}
diff --git a/lunaria/styles.css b/lunaria/styles.css
deleted file mode 100644
index cd92464a8..000000000
--- a/lunaria/styles.css
+++ /dev/null
@@ -1,4 +0,0 @@
-:root {
-	--tw-bg-opacity: 1;
-	background-color: rgb(15 23 42 / var(--tw-bg-opacity));
-}
diff --git a/package.json b/package.json
index 6876ddb2a..b5ce00e8f 100644
--- a/package.json
+++ b/package.json
@@ -8,19 +8,16 @@
 		"sync": "node scripts/collections/index.mjs",
 		"sync:orama": "pnpm build && node scripts/sync-orama.mjs",
 		"dev": "pnpm sync && vinxi dev",
-		"build": "pnpm sync && pnpm build:sitemap && pnpm build:lunaria && NODE_OPTIONS=\"--max-old-space-size=8192\" vinxi build",
+		"build": "pnpm sync && pnpm build:sitemap && NODE_OPTIONS=\"--max-old-space-size=8192\" vinxi build",
 		"build:sitemap": "node scripts/generateSitemap.js",
 		"start": "vinxi start",
 		"e2e": "npx playwright test",
-		"build:lunaria": "lunaria build",
-		"preview:lunaria": "lunaria preview",
 		"check:lint": "eslint .",
 		"check:types": "tsc --noEmit"
 	},
 	"dependencies": {
 		"@kobalte/core": "^0.13.11",
 		"@kobalte/solidbase": "^0.2.17",
-		"@lunariajs/core": "^0.1.1",
 		"@oramacloud/client": "^2.1.4",
 		"@solid-primitives/event-listener": "^2.4.3",
 		"@solid-primitives/marker": "^0.2.2",
diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml
index eb2ad3598..b55e47160 100644
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@@ -14,9 +14,6 @@ importers:
       '@kobalte/solidbase':
         specifier: ^0.2.17
         version: 0.2.17(@algolia/client-search@5.14.2)(@solidjs/start@1.2.0(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0)))(@vue/compiler-sfc@3.5.16)(acorn@8.15.0)(expressive-code@0.40.2)(react@18.3.1)(search-insights@2.17.3)(solid-js@1.9.9)(vinxi@0.5.7(@types/node@24.5.1)(db0@0.3.2)(ioredis@5.6.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))(vite@6.3.5(@types/node@24.5.1)(jiti@2.4.2)(terser@5.42.0)(yaml@2.8.0))
-      '@lunariajs/core':
-        specifier: ^0.1.1
-        version: 0.1.1
       '@oramacloud/client':
         specifier: ^2.1.4
         version: 2.1.4
@@ -446,9 +443,6 @@ packages:
   '@bprogress/core@1.1.18':
     resolution: {integrity: sha512-+khsDSJ7jv1L9LU34jnEsNqY6tXViSZDOeoxd09Ws8zVXzFjatRzWwBpiDQqTqyVZc0nlOxkkumFDtAgDJwY2A==}
 
-  '@clack/core@0.3.4':
-    resolution: {integrity: sha512-H4hxZDXgHtWTwV3RAVenqcC4VbJZNegbBjlPvzOzCouXtS2y3sDvlO3IsbrPNWuLWPPlYVYPghQdSF64683Ldw==}
-
   '@cloudflare/kv-asset-handler@0.4.0':
     resolution: {integrity: sha512-+tv3z+SPp+gqTIcImN9o0hqE9xyfQjI1XD9pL6NuKjua9B1y7mNYv0S9cP+QEbA4ppVgGZEmKOvHX5G5Ei1CVA==}
     engines: {node: '>=18.0.0'}
@@ -833,17 +827,6 @@ packages:
     peerDependencies:
       solid-js: ^1.8.8
 
-  '@kwsites/file-exists@1.1.1':
-    resolution: {integrity: sha512-m9/5YGR18lIwxSFDwfE3oA7bWuq9kdau6ugN4H2rJeyhFQZcG9AgSHkQtSD15a8WvTgfz9aikZMrKPHvbpqFiw==}
-
-  '@kwsites/promise-deferred@1.1.1':
-    resolution: {integrity: sha512-GaHYm+c0O9MjZRu0ongGBRbinu8gVAMd2UZjji6jVmqKtZluZnptXGWhz1E8j8D2HJ3f/yMxKAUC0b+57wncIw==}
-
-  '@lunariajs/core@0.1.1':
-    resolution: {integrity: sha512-sAqM9+DVsLe3xHM9wu2pEnKGYMs/bWS9qpR+CGHol3RihOELnOQTzHddXbdB1MtgesbI8dnQuG64Ocd8KkWsng==}
-    engines: {node: '>=18.17.0'}
-    hasBin: true
-
   '@mapbox/node-pre-gyp@2.0.0':
     resolution: {integrity: sha512-llMXd39jtP0HpQLVI37Bf1m2ADlEb35GYSh1SDSLsBhR+5iCxiNGlT31yqbNtVHygHAtMy6dWFERpU2JgufhPg==}
     engines: {node: '>=18'}
@@ -2805,10 +2788,6 @@ packages:
   get-port-please@3.1.2:
     resolution: {integrity: sha512-Gxc29eLs1fbn6LQ4jSU4vXjlwyZhF5HsGuMAa7gqBP4Rw4yxxltyDUuF5MBclFzDTXO+ACchGQoeela4DSfzdQ==}
 
-  get-port@7.1.0:
-    resolution: {integrity: sha512-QB9NKEeDg3xxVwCCwJQ9+xycaz6pBB6iQ76wiWMl1927n0Kir6alPiP+yuiICLLU4jpMe08dXfpebuQppFA2zw==}
-    engines: {node: '>=16'}
-
   get-proto@1.0.1:
     resolution: {integrity: sha512-sTSfBjoXBp89JvIKIefqw7U2CCebsc74kiY6awiGogKtoSGbgjYE/G/+l9sF3MWFPNc9IcoOC4ODfKHfxFmp0g==}
     engines: {node: '>= 0.4'}
@@ -4387,15 +4366,9 @@ packages:
     resolution: {integrity: sha512-bzyZ1e88w9O1iNJbKnOlvYTrWPDl46O1bG0D3XInv+9tkPrxrN8jUUTiFlDkkmKWgn1M6CfIA13SuGqOa9Korw==}
     engines: {node: '>=14'}
 
-  simple-git@3.27.0:
-    resolution: {integrity: sha512-ivHoFS9Yi9GY49ogc6/YAi3Fl9ROnF4VyubNylgCkA+RVqLaKWnDSzXOVzya8csELIaWaYNutsEuAhZrtOjozA==}
-
   simple-swizzle@0.2.2:
     resolution: {integrity: sha512-JA//kQgZtbuY83m+xT+tXJkmJncGMTFT+C+g2h2R9uxkYIrE2yy9sgmcLhCnw57/WSD+Eh3J97FPEDFnbXnDUg==}
 
-  sisteransi@1.0.5:
-    resolution: {integrity: sha512-bLGGlR1QxBcynn2d5YmDX4MGjlZvy2MRBDRNHLJ8VI6l6+9FUiyTFNJ0IveOSP0bcXgVDPRcfGqA0pjaqUpfVg==}
-
   sitemap@8.0.0:
     resolution: {integrity: sha512-+AbdxhM9kJsHtruUF39bwS/B0Fytw6Fr1o4ZAIAEqA6cke2xcoO2GleBw9Zw7nRzILVEgz7zBM5GiTJjie1G9A==}
     engines: {node: '>=14.0.0', npm: '>=6.0.0'}
@@ -4720,9 +4693,6 @@ packages:
   ultrahtml@1.6.0:
     resolution: {integrity: sha512-R9fBn90VTJrqqLDwyMph+HGne8eqY1iPfYhPzZrvKpIfwkWZbcYlfpsb8B9dTvBfpy1/hqAD7Wi8EKfP9e8zdw==}
 
-  ultramatter@0.0.4:
-    resolution: {integrity: sha512-1f/hO3mR+/Hgue4eInOF/Qm/wzDqwhYha4DxM0hre9YIUyso3fE2XtrAU6B4njLqTC8CM49EZaYgsVSa+dXHGw==}
-
   uncrypto@0.1.3:
     resolution: {integrity: sha512-Ql87qFHB3s/De2ClA9e0gsnS6zXG27SkTiSJwjCc9MebbfapQfuPzumMIUMi38ezPZVNFcHI9sUIepeQfw8J8Q==}
 
@@ -5584,11 +5554,6 @@ snapshots:
 
   '@bprogress/core@1.1.18': {}
 
-  '@clack/core@0.3.4':
-    dependencies:
-      picocolors: 1.1.1
-      sisteransi: 1.0.5
-
   '@cloudflare/kv-asset-handler@0.4.0':
     dependencies:
       mime: 3.0.0
@@ -6014,29 +5979,6 @@ snapshots:
       '@solid-primitives/utils': 6.2.3(solid-js@1.9.9)
       solid-js: 1.9.9
 
-  '@kwsites/file-exists@1.1.1':
-    dependencies:
-      debug: 4.4.1
-    transitivePeerDependencies:
-      - supports-color
-
-  '@kwsites/promise-deferred@1.1.1': {}
-
-  '@lunariajs/core@0.1.1':
-    dependencies:
-      '@clack/core': 0.3.4
-      fast-glob: 3.3.3
-      get-port: 7.1.0
-      jiti: 1.21.6
-      micromatch: 4.0.8
-      path-to-regexp: 6.3.0
-      picocolors: 1.1.1
-      simple-git: 3.27.0
-      ultramatter: 0.0.4
-      zod: 3.25.76
-    transitivePeerDependencies:
-      - supports-color
-
   '@mapbox/node-pre-gyp@2.0.0':
     dependencies:
       consola: 3.4.2
@@ -8230,8 +8172,6 @@ snapshots:
 
   get-port-please@3.1.2: {}
 
-  get-port@7.1.0: {}
-
   get-proto@1.0.1:
     dependencies:
       dunder-proto: 1.0.1
@@ -10352,20 +10292,10 @@ snapshots:
 
   signal-exit@4.1.0: {}
 
-  simple-git@3.27.0:
-    dependencies:
-      '@kwsites/file-exists': 1.1.1
-      '@kwsites/promise-deferred': 1.1.1
-      debug: 4.4.1
-    transitivePeerDependencies:
-      - supports-color
-
   simple-swizzle@0.2.2:
     dependencies:
       is-arrayish: 0.3.2
 
-  sisteransi@1.0.5: {}
-
   sitemap@8.0.0:
     dependencies:
       '@types/node': 17.0.45
@@ -10702,8 +10632,6 @@ snapshots:
 
   ultrahtml@1.6.0: {}
 
-  ultramatter@0.0.4: {}
-
   uncrypto@0.1.3: {}
 
   unctx@2.4.1: