What to put behind a lightweight website editing snippet

Keep the runtime focused

A good editing snippet should load published content changes, apply them safely, and stay out of the way of the application.

It should not become a second frontend framework.

Support explicit and inferred mappings

Explicit keys are best for production stability. Inferred mappings help teams start quickly before they add instrumentation.

The editor should explain that difference without forcing users to understand implementation details.

Handle modern pages

SPAs mutate the DOM after load, so the runtime should reapply published edits after route changes and relevant DOM updates.