More stuff

Author: mstijak

homedocs/TODO.md

@@ -1,6 +1,6 @@
-[ ] Fix search (make whole item clickable)
+[x] Fix search (make whole item clickable)
 [x] Add SEO data
-[ ] Add Google Analytics
+[x] Add Google Analytics
 [x] Preserve @jsxImportSource in llms.txt
 [x] try export default {} instead of export () => {}
 [x] document controller inline form
@@ -16,4 +16,4 @@
 [x] On this page nav
 [ ] Tab borders
 [ ] LinkButton styling
-[ ] Add OG image
+[x] Add OG image

homedocs/src/data/navigation.js

@@ -177,6 +177,46 @@ export const navigation = [
     title: "Concepts",
     slug: "concepts",
     groups: [
+      {
+        title: "Data Views",
+        items: [
+          {
+            title: "Overview",
+            slug: "data-views",
+            llms: "small",
+            description: "Components that iterate and transform data",
+          },
+          {
+            title: "Repeater",
+            slug: "repeater",
+            llms: "small",
+            description: "Render a template for each item in an array",
+          },
+          {
+            title: "Sandbox",
+            slug: "sandbox",
+            llms: "small",
+            description: "Isolate store changes for cancel/save workflows",
+          },
+          {
+            title: "PrivateStore",
+            slug: "private-store",
+            llms: "small",
+            description: "Create isolated store instances for components",
+          },
+          {
+            title: "DataProxy",
+            slug: "data-proxy",
+            llms: "small",
+            description: "Transform data between parent and child stores",
+          },
+          {
+            title: "Rescope",
+            slug: "rescope",
+            description: "Remap store paths for nested components",
+          },
+        ],
+      },
       {
         title: "Selections",
         items: [
@@ -238,46 +278,6 @@ export const navigation = [
           },
         ],
       },
-      {
-        title: "Data Views",
-        items: [
-          {
-            title: "Overview",
-            slug: "data-views",
-            llms: "small",
-            description: "Components that iterate and transform data",
-          },
-          {
-            title: "Repeater",
-            slug: "repeater",
-            llms: "small",
-            description: "Render a template for each item in an array",
-          },
-          {
-            title: "Sandbox",
-            slug: "sandbox",
-            llms: "small",
-            description: "Isolate store changes for cancel/save workflows",
-          },
-          {
-            title: "PrivateStore",
-            slug: "private-store",
-            llms: "small",
-            description: "Create isolated store instances for components",
-          },
-          {
-            title: "DataProxy",
-            slug: "data-proxy",
-            llms: "small",
-            description: "Transform data between parent and child stores",
-          },
-          {
-            title: "Rescope",
-            slug: "rescope",
-            description: "Remap store paths for nested components",
-          },
-        ],
-      },
       {
         title: "Drag & Drop",
         items: [

homedocs/src/pages/docs/concepts/data-views.mdx

@@ -10,36 +10,36 @@ import OnThisPage from "../../../components/OnThisPage.astro";
 
 <OnThisPage />
 
-All application data in CxJS is stored inside a central [Store](/docs/core/store). While convenient for global state, accessing deeply nested paths or working with collections can become cumbersome. Data View components wrap parts of the widget tree and provide a modified view of the Store data, making it easier to work with specific areas of the data model.
+All application data in CxJS is stored inside a central [Store](/docs/intro/store). While convenient for global state, accessing deeply nested paths or working with collections can become cumbersome. Data View components wrap parts of the widget tree and provide a modified view of the Store data, making it easier to work with specific areas of the data model.
 
 ## Comparison
 
-| Component                                | Purpose                                           | Use case                              |
-| ---------------------------------------- | ------------------------------------------------- | ------------------------------------- |
-| [Repeater](/docs/data/repeater)          | Renders children for each record in a collection  | Lists, tables, any repeated content   |
-| [Rescope](/docs/data/rescope)            | Selects a common prefix for shorter binding paths | Deeply nested data structures         |
-| [Sandbox](/docs/data/sandbox)            | Multiplexes data based on a dynamic key           | Tabs, routes with isolated page data  |
-| [PrivateStore](/docs/data/private-store) | Creates an isolated store for a subtree           | Reusable components with local state  |
-| [DataProxy](/docs/data/data-proxy)       | Creates aliases with custom getter/setter logic   | Computed values, data transformations |
-| [Route](/docs/core/route)                | Renders children when URL matches a pattern       | Page routing, exposes `$route` params |
+| Component                              | Purpose                                           | Use case                              |
+| -------------------------------------- | ------------------------------------------------- | ------------------------------------- |
+| [Repeater](./repeater)                 | Renders children for each record in a collection  | Lists, tables, any repeated content   |
+| [Rescope](./rescope)                   | Selects a common prefix for shorter binding paths | Deeply nested data structures         |
+| [Sandbox](./sandbox)                   | Multiplexes data based on a dynamic key           | Tabs, routes with isolated page data  |
+| [PrivateStore](./private-store)        | Creates an isolated store for a subtree           | Reusable components with local state  |
+| [DataProxy](./data-proxy)              | Creates aliases with custom getter/setter logic   | Computed values, data transformations |
+| [Route](./route)                       | Renders children when URL matches a pattern       | Page routing, exposes `$route` params |
 
 ## How Data Views Work
 
 Each Data View component exposes the same interface as the Store to its children, but can introduce additional properties. For example, Repeater adds `$record` and `$index` for each item in the collection, Route exposes `$route` with matched URL parameters, while Sandbox might expose `$page` for route-specific data. These additional properties are only accessible within the scope of that Data View, allowing child widgets to bind to them just like any other Store data.
 
 ## How to Choose
 
-Use [Repeater](/docs/data/repeater) when you need to render a list of items from an array.
+Use [Repeater](./repeater) when you need to render a list of items from an array.
 
-Use [Rescope](/docs/data/rescope) when working with deeply nested data and you want shorter binding paths.
+Use [Rescope](./rescope) when working with deeply nested data and you want shorter binding paths.
 
-Use [Sandbox](/docs/data/sandbox) when you need to switch between different data contexts based on a key (e.g., tabs, route parameters).
+Use [Sandbox](./sandbox) when you need to switch between different data contexts based on a key (e.g., tabs, route parameters).
 
-Use [PrivateStore](/docs/data/private-store) (also known as Restate) when you need completely isolated state that doesn't affect the global store.
+Use [PrivateStore](./private-store) (also known as Restate) when you need completely isolated state that doesn't affect the global store.
 
-Use [DataProxy](/docs/data/data-proxy) when you need to transform data or create computed aliases with custom getter/setter logic.
+Use [DataProxy](./data-proxy) when you need to transform data or create computed aliases with custom getter/setter logic.
 
-Use [Route](/docs/core/route) when you need to conditionally render content based on URL and access matched route parameters.
+Use [Route](./route) when you need to conditionally render content based on URL and access matched route parameters.
 
 ## Store Mutation
 

homedocs/src/pages/docs/concepts/selections.mdx

@@ -16,14 +16,14 @@ Selections enable users to select one or more items from widgets like Grid, List
 
 | Model                                                   | Storage                            | Best for                        |
 | ------------------------------------------------------- | ---------------------------------- | ------------------------------- |
-| [KeySelection](key-selection)           | Key value(s) in separate variable  | Selection survives data updates |
-| [SimpleSelection](simple-selection)     | Entire object in separate variable | Simple single select            |
-| [PropertySelection](property-selection) | Boolean flag on each record        | Checkbox lists, toggles         |
+| [KeySelection](./key-selection)           | Key value(s) in separate variable  | Selection survives data updates |
+| [SimpleSelection](./simple-selection)     | Entire object in separate variable | Simple single select            |
+| [PropertySelection](./property-selection) | Boolean flag on each record        | Checkbox lists, toggles         |
 
 ## How to Choose
 
-Use [KeySelection](key-selection) when selection needs to survive data refreshes. Keys remain stable while object references change after updates.
+Use [KeySelection](./key-selection) when selection needs to survive data refreshes. Keys remain stable while object references change after updates.
 
-Use [SimpleSelection](simple-selection) for simple single-select scenarios where you need immediate access to the selected object.
+Use [SimpleSelection](./simple-selection) for simple single-select scenarios where you need immediate access to the selected object.
 
-Use [PropertySelection](property-selection) for checkbox-based UIs where each record tracks its own selection state.
+Use [PropertySelection](./property-selection) for checkbox-based UIs where each record tracks its own selection state.

homedocs/src/pages/docs/concepts/simple-selection.mdx

@@ -24,7 +24,7 @@ SimpleSelection is the most basic selection model. It stores the entire selected
 - When you need immediate access to the full selected object
 - Quick prototyping or simple lists
 
-Note that selection is lost if the selected object changes in the data source, since the reference will no longer match. For more robust selection, consider [KeySelection](/core/key-selection).
+Note that selection is lost if the selected object changes in the data source, since the reference will no longer match. For more robust selection, consider [KeySelection](./key-selection).
 
 ## Example