michael · michael · May 31, 2026 · May 31, 2026 · May 31, 2026 · May 31, 2026
diff --git a/ARCHITECTURE.md b/ARCHITECTURE.md
diff --git a/COMMON_CONTENT_MODEL.md b/COMMON_CONTENT_MODEL.md
diff --git a/IMPLEMENTATION_PLAN.md b/IMPLEMENTATION_PLAN.md
diff --git a/README.md b/README.md
@@ -1,10 +1,8 @@
-# Editable Website v2
+# Editable
 
-The next generation of Editable Website — a complete rewrite designed to make Svelte developers happy.
+Editable brings live on-page editing to Svelte. Site owners edit directly in the layout; developers keep full control with ordinary Svelte components.
 
-> **NOTE:** v2 is a complete rewrite using [Svedit](https://github.com/michael/svedit). It's under active development — feel free to explore locally, but hold off on production deployments for now.
-
-## Who is Editable Website for?
+## Who is Editable for?
 
 For anyone who enjoys creating websites using Svelte and wants to allow their clients to make edits directly in the layout as they browse their site.
 
@@ -59,14 +57,21 @@ Next, you probably want to adjust the colors and fonts in [app.css](./src/app.cs
 :root {
 	--background: oklch(0.98 0 0);
 	--foreground: oklch(0 0 0);
+	--muted: oklch(1 0 0);
+	--border: oklch(0.88 0 0);
+	--muted-foreground: oklch(0.55 0 0);
 	--accent: oklch(0.21 0.034 264);
 	--accent-foreground: oklch(0.98 0 0);
 }
 
 @theme {
 	--font-sans: 'Inter', ui-sans-serif, system-ui, sans-serif;
 	--font-serif: 'Libertinos Serif Display', ui-serif, Georgia, serif;
-	--font-mono: ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, 'Liberation Mono', 'Courier New', monospace;
+	--font-mono:
+		ui-monospace, SFMono-Regular, Menlo, Monaco, Consolas, 'Liberation Mono', 'Courier New',
+		monospace;
+	--shadow-sm: 0 2px 4px -1px oklch(0 0 0 / 0.12), 0 1px 2px -1px oklch(0 0 0 / 0.12);
+	--shadow-xl: 0 20px 25px -5px oklch(0 0 0 / 0.12), 0 8px 10px -6px oklch(0 0 0 / 0.12);
 }
 ```
 
@@ -76,7 +81,7 @@ However, likely you'll want to customize more than that. E.g. edit [Button.svelt
 
 ## Manual
 
-For detailed documentation on building with Editable Website see [MANUAL.md](./MANUAL.md).
+For detailed documentation on building with Editable see [MANUAL.md](./MANUAL.md).
 
 ## Deploy
 
@@ -91,6 +96,8 @@ fly secrets set -a my-editable-website \
   ADMIN_PASSWORD='change-me'
 ```
 
+Optionally set `ASSET_GRACE_PERIOD_DAYS` (default 7): unreferenced asset files are kept on disk this many days after losing their last reference. This is also the safe window for rolling back a database backup against the live assets folder without ending up with dead image references.
+
 ```
 fly deploy -a my-editable-website --primary-region fra --vm-size shared-cpu-1x --vm-memory 256 --volume-initial-size 1
 ```
@@ -117,23 +124,23 @@ All content lives in a single `data/` directory — an SQLite database (`db.sqli
 
 ### How about AI?
 
-Editable Website is a foundational, AI-agnostic tool. That said, it makes perfect sense to utilize AI workflows to help building your custom site. Think prompts like "Create a hero block type with title + description and optional CTA buttons" and "Implement Hero.svelte with 5 distinct layout variations".
+Editable is a foundational, AI-agnostic tool. That said, it makes perfect sense to utilize AI workflows to help building your custom site. Think prompts like "Create a hero block type with title + description and optional CTA buttons" and "Implement Hero.svelte with 5 distinct layout variations".
 
 ### Plugins?
 
-Editable Website is modular and you can and should reuse code across projects. However, I purposely don't want to establish a community maintained plugin repository. I want to encourage you to own all your code, for the benefit of simplicity, safety, and control. Share code snippets, not plugins.
+Editable is modular and you can and should reuse code across projects. However, I purposely don't want to establish a community maintained plugin repository. I want to encourage you to own all your code, for the benefit of simplicity, safety, and control. Share code snippets, not plugins.
 
 ### Hosting?
 
-Editable Website runs on any VPS. All you need is Node.js and SQLite. The repository includes a `Dockerfile` and `fly.toml` for one-command deployment to [Fly.io](https://fly.io) — see [Deploying to Fly.io](#deploying-to-flyio) above. The same Dockerfile works with any platform that supports Docker.
+Editable runs on any VPS. All you need is Node.js and SQLite. The repository includes a `Dockerfile` and `fly.toml` for one-command deployment to [Fly.io](https://fly.io) — see [Deploying to Fly.io](#deploying-to-flyio) above. The same Dockerfile works with any platform that supports Docker.
 
 ### Static builds?
 
-There's no point for static builds with Editable Website. The whole idea is that users edit content live, without having to wait for a rebuild to finish. SQLite is fast. Very fast. Web-optimized images are generated client-side before upload: resizing happens in the browser via canvas and `toBlob()`, and WebP encoding is done with `@jsquash/webp`. It still makes sense to enable a proxy for images, so they can be delivered from a CDN.
+There's no point for static builds with Editable. The whole idea is that users edit content live, without having to wait for a rebuild to finish. SQLite is fast. Very fast. Web-optimized images are generated client-side before upload: resizing happens in the browser via canvas and `toBlob()`, and WebP encoding is done with `@jsquash/webp`. It still makes sense to enable a proxy for images, so they can be delivered from a CDN.
 
 ### License?
 
-Editable Website will at least be source-available. There will likely be an affordable one-time registration fee (per domain) for personal use, and a fair fee for commercial projects. I'm still working on the details. If you’re open to discussion, join the [technical preview](https://docs.google.com/forms/d/e/1FAIpQLSfkL9e9X3Lcn6oBDIG-gU4yrfSenh8fndupbIX7zkyxX3X9ZQ/viewform).
+Editable will at least be source-available. There will likely be an affordable one-time registration fee (per domain) for personal use, and a fair fee for commercial projects. I'm still working on the details. If you’re open to discussion, join the [technical preview](https://docs.google.com/forms/d/e/1FAIpQLSfkL9e9X3Lcn6oBDIG-gU4yrfSenh8fndupbIX7zkyxX3X9ZQ/viewform).
 
 ## Looking for v1?
 

diff --git a/add_section.js b/add_section.js
@@ -0,0 +1,28 @@
+import fs from 'fs';
+
+let content = fs.readFileSync('src/lib/demo_doc.js', 'utf-8');
+
+const section1Str = `		section_1: {
+			id: 'section_1',
+			type: 'section'
+		},`;
+
+content = content.replace('page_1: {', section1Str + '\n\t\tpage_1: {');
+
+const page1BodyEndStr = `					'footer_1'
+				],
+				annotations: []`;
+
+const page1BodyEndStrRepl = `					'footer_1'
+				],
+				annotations: [
+					{
+						start_offset: 0,
+						end_offset: 3,
+						node_id: 'section_1'
+					}
+				]`;
+
+content = content.replace(page1BodyEndStr, page1BodyEndStrRepl);
+
+fs.writeFileSync('src/lib/demo_doc.js', content);
diff --git a/convert.js b/convert.js
@@ -0,0 +1,14 @@
+import fs from 'fs';
+
+let content = fs.readFileSync('src/lib/demo_doc.js', 'utf-8');
+
+const array_properties = ['buttons', 'content', 'body', 'gallery_items', 'items', 'blocks', 'nav_items', 'footer_items'];
+
+for (const prop of array_properties) {
+    const regex = new RegExp(`\\b${prop}:\\s*\\[([^\\]]*)\\]`, 'g');
+    content = content.replace(regex, (match, inner) => {
+        return `${prop}: {\n\t\tnodes: [${inner}],\n\t\tannotations: []\n\t}`;
+    });
+}
+
+fs.writeFileSync('src/lib/demo_doc.js', content);