From ea8f1b3f956304fdd8618f30952040629bf0d9bb Mon Sep 17 00:00:00 2001 From: Jeff Emmett Date: Wed, 18 Feb 2026 12:41:24 -0700 Subject: [PATCH] Add offline-first section to rSpace landing page New feature card in hero grid and a dedicated section explaining local IndexedDB persistence, Automerge auto-merge, and incremental sync. Matches the existing visual style with pillars and identity cards. Co-Authored-By: Claude Opus 4.6 --- website/index.html | 53 ++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 51 insertions(+), 2 deletions(-) diff --git a/website/index.html b/website/index.html index 006f6f6..7278c64 100644 --- a/website/index.html +++ b/website/index.html @@ -125,7 +125,7 @@ .features { display: grid; - grid-template-columns: repeat(3, 1fr); + grid-template-columns: repeat(4, 1fr); gap: 1.5rem; margin-top: 4rem; } @@ -329,7 +329,7 @@ grid-template-columns: 1fr; } .features { - grid-template-columns: 1fr; + grid-template-columns: repeat(2, 1fr); } .section h2 { font-size: 1.5rem; @@ -380,6 +380,11 @@
Real-time Sync
Powered by Automerge CRDT
+
+
📡
+
Offline-First
+
Works without internet, merges on reconnect
+
🌐
Your Subdomain
@@ -442,6 +447,50 @@
+ +
+
+

Offline-First, Always Available

+

+ rSpace works without an internet connection. Edit your canvas on a plane, + in a field, or underground — your changes merge automatically when + you're back online. No sync buttons, no conflict dialogs. +

+ +
+
+
💾
+
Local Persistence
+
Your canvas is cached in the browser. Refresh the page — it loads instantly, even offline.
+
+
+
🔀
+
Auto-Merge
+
Automerge CRDTs resolve conflicts automatically. Multiple people can edit the same canvas offline and merge without data loss.
+
+
+
⚡
+
Incremental Sync
+
Only new changes are transferred on reconnect — not the whole document. Fast even on slow connections.
+
+
+ +
+

How it works

+

+ Every rSpace canvas is an Automerge CRDT document stored + locally in your browser's IndexedDB. When you open a canvas, it renders from the + local cache first — no waiting for the server. Edits you make are saved locally + and synced to the server via WebSocket when a connection is available. If you go offline, + the app keeps working: a Service Worker serves the app shell + from cache, and your changes accumulate in the local CRDT document. When connectivity + returns, Automerge's incremental sync protocol reconciles + your changes with everyone else's — conflict-free, automatically. No manual + merge, no "which version do you want to keep?" dialogs. +

+
+
+