diff --git a/www/content/patterns/active-search.md b/www/content/patterns/active-search.md
new file mode 100644
index 00000000..1e056299
--- /dev/null
+++ b/www/content/patterns/active-search.md
@@ -0,0 +1,193 @@
++++
+title = "Active Search"
+template = "demo.html"
++++
+
+This pattern demonstrates active search functionality that queries as the user types.
+
+We start with a search input and an empty table:
+
+```html
+
+ Search Contacts
+
+ Searching...
+
+
+
+
+
+
+
+
First Name
+
Last Name
+
Email
+
+
+
+
+
+```
+
+The input issues a `POST` to `/search` on the [`input`](https://developer.mozilla.org/en-US/docs/Web/API/HTMLElement/input_event) event and sets the body of the table to be the resulting content.
+
+We add the `delay:500ms` modifier to the trigger to delay sending the query until the user stops typing. Additionally,
+we add the `changed` modifier to the trigger to ensure we don't send new queries when the user doesn't change the
+value of the input (e.g. they hit an arrow key, or pasted the same value).
+
+We can use multiple triggers by separating them with a comma, this way we add 2 more triggers:
+- `keyup[key=='Enter']` triggers once enter is pressed. We use [event filters](/attributes/hx-trigger#standard-event-filters) here to check for [the key property in the KeyboardEvent object](https://developer.mozilla.org/en-US/docs/Web/API/KeyboardEvent/key).
+- `load` in order to show all results initially on load.
+
+Finally, we show an indicator when the search is in flight with the `hx-indicator` attribute.
+
+{{ demoenv() }}
+
+
diff --git a/www/content/talk/_index.md b/www/content/talk/_index.md
new file mode 100644
index 00000000..fdf429d2
--- /dev/null
+++ b/www/content/talk/_index.md
@@ -0,0 +1,3 @@
++++
+redirect_to = "/help/"
++++
diff --git a/www/docs/DOC_UPDATE_ANALYSIS.md b/www/docs/DOC_UPDATE_ANALYSIS.md
new file mode 100644
index 00000000..8a503188
--- /dev/null
+++ b/www/docs/DOC_UPDATE_ANALYSIS.md
@@ -0,0 +1,921 @@
+# HTMX 4 Documentation Update Analysis
+
+**Generated:** 2025-10-26
+**Purpose:** Comprehensive analysis of documentation updates needed for HTMX 4 migration from HTMX 2.0
+
+---
+
+## Executive Summary
+
+### Major Architectural Changes
+
+1. **Complete Internal Rewrite**: HTMX 4 uses a class-based architecture (`class Htmx`) vs HTMX 2.0's functional/object approach
+2. **Event Naming Changes**: Event names have been restructured with more consistent naming patterns
+3. **Simplified Core Attributes**: Several attributes have been consolidated or renamed
+4. **Request Context Model**: New unified request context (`ctx`) object replacing separate configurations
+5. **Removed Features**: Several HTMX 2.0 features have been removed or deprecated
+
+### Documentation Impact
+
+- **Critical Updates Required**: ~60% of documentation needs revision
+- **New Sections Needed**: ~15% new content required
+- **Deprecated Content**: ~10% needs removal
+- **Minor Updates**: ~15% requires minor clarification
+
+---
+
+## Section-by-Section Analysis
+
+### 1. Introduction Section (#introduction)
+
+**Priority:** LOW
+**Status:** Minimal changes needed
+
+**Required Changes:**
+- Update version number references from 2.0.x to 4.0
+- No conceptual changes needed - the core philosophy remains the same
+
+**Action Items:**
+- [ ] Update example code if any syntax changes apply
+- [ ] Verify all conceptual examples still work
+
+---
+
+### 2. Installing Section (#installing)
+
+**Priority:** CRITICAL
+**Status:** Major updates required
+
+**Required Changes:**
+```html
+
+