fix: broken doc links (#4)

* fix: dead links
* removed examples dir

Author: desertthunder

ROADMAP.md

@@ -18,12 +18,12 @@
 | v0.3.0  |   ✓   | [Global State](#global-state)                                                    |
 | v0.4.0  |   ✓   | [Animation & Transitions](#animation--transitions)                               |
 | v0.5.0  |       | [History API Routing Plugin](#history-api-routing-plugin)                        |
+|         |       | [Navigation & History Management](#navigation--history-management)               |
 |         |   ✓   | [Refactor](#evaluator--binder-hardening)                                         |
-|         |       | [Persistence & Offline](#persistence--offline)                                   |
-|         |       | [Background Requests & Reactive Polling](#background-requests--reactive-polling) |
-| v0.6.0  |       | [Navigation & History Management](#navigation--history-management)               |
+| v0.6.0  |       | [Background Requests & Reactive Polling](#background-requests--reactive-polling) |
 | v0.7.0  |       | [Streaming & Patch Engine](#streaming--patch-engine)                             |
 | v0.8.0  |       | PWA Capabilities                                                                 |
+|         |       | [Persistence & Offline](#persistence--offline)                                   |
 | v0.9.0  |       | [Inspector & Developer Tools](#inspector--developer-tools)                       |
 | v1.0.0  |       | [Stable Release](#stable-release)                                                |
 
@@ -72,9 +72,6 @@ _NOTE_: `data-x-*` is now `data-volt-*`
 **Goal:** Use JavaScript Proxies to improve reactivity ergonomics and automatic dependency tracking.
 **Outcome:** More intuitive API with automatic dependency tracking and optional deep reactivity for objects/arrays.
 **Summary:** Proxy-driven automatic dependency tracking, deep reactive() objects, reactive arrays, lazy signal creation, and debugging utilities improve reactivity ergonomics and performance.
-**Notes:**
-    - Separate reactive() function for objects/arrays to gives users choice
-    - Keep .get()/.set() - explicitness is valuable for understanding reactivity (include in docs)
 
 ### Reactive Attributes & Event Modifiers
 
@@ -189,7 +186,7 @@ _NOTE_: `data-x-*` is now `data-volt-*`
     - Full API reference with examples
     - Create generator in `@voltx/cli` package
     - Finalized plugin registry and CLI (`volt plugins list/init`)
-    - Versioned documentation (stormlightlabs.github.io/volt)
+    - Versioned documentation (<https://stormlightlabs.github.io/volt>)
     - Announcement post and release notes
     - Community contribution guide & governance doc
 
@@ -199,6 +196,8 @@ _NOTE_: `data-x-*` is now `data-volt-*`
 
 All expression evaluation now flows through a cached `new Function` compiler guarded by a hardened scope proxy, with the binder slimmed into a directive registry so plugins self-register while tests verify the sandboxed error surfaces.
 
+### Naming
+
 ## Examples
 
 Many of these are ideas, not planned to be implemented
@@ -235,7 +234,7 @@ These will live in an example repo.
 
 - Authentication Flows - Login, signup, password reset, email verification (Go, Python, Rust, Node)
 - File Upload with Progress - Chunked uploads, progress bars, validation (Go, Python, Rust, Node)
-- Search with Server-Side Filtering - Debounced search, paginated results (Go, Python,Rust,  Node)
+- Search with Server-Side Filtering - Debounced search, paginated results (Go, Python, Rust,  Node)
 
 ### Desktop Apps
 

docs/installation.md

@@ -139,7 +139,7 @@ For SSR applications, use the `hydrate()` function instead of `charge()` to pres
 </script>
 ```
 
-See the [Server-Side Rendering & Lifecycle](./lifecycle) documentation for complete SSR patterns and hydration strategies.
+See the [Server-Side Rendering & Lifecycle](./usage/lifecycle) documentation for complete SSR patterns and hydration strategies.
 
 ## Plugin Setup
 
@@ -178,6 +178,6 @@ VoltX.js requires modern browsers with support for:
 ## Next Up
 
 - Read the [Framework Overview](./overview) to understand core concepts
-- Learn about [State Management](./state) with signals and computed values
-- Explore available [Bindings](./bindings) for DOM manipulation
-- Check out [Expression Evaluation](./expressions) for template syntax
+- Learn about [State Management](./usage/state) with signals and computed values
+- Explore available [Bindings](./usage/bindings) for DOM manipulation
+- Check out [Expression Evaluation](./usage/expressions) for template syntax

docs/usage/counter.md

@@ -282,7 +282,7 @@ This counter demonstrates core VoltX.js concepts:
 
 ## Further Reading
 
-- [State Management](../state) for advanced signal patterns
-- [Bindings](../bindings) for complete binding reference
-- [Expressions](../expressions) for template syntax details
-- [Lifecycle](../lifecycle) for SSR and hydration
+- [State Management](./state) for advanced signal patterns
+- [Bindings](./bindings) for complete binding reference
+- [Expressions](./expressions) for template syntax details
+- [Lifecycle](./lifecycle) for SSR and hydration

docs/usage/state.md

@@ -37,7 +37,7 @@ Common uses include:
 - Logging or analytics
 - Coordinating multiple signals
 
-For asynchronous operations, use `asyncEffect()` (see [asyncEffect](./usage/async-effect)) which handles cleanup of pending operations when dependencies change or the effect is disposed.
+For asynchronous operations, use `asyncEffect()` (see [asyncEffect](./async-effect.md)) which handles cleanup of pending operations when dependencies change or the effect is disposed.
 
 ## Declarative State