Runtime, modules, and events

Layout and modules

Templates place modules in top, left, bottom, contextual, selection, or portal zones. A module can be enabled without appearing permanently in a menu.

Storefront permissions should expose customer actions only. Administration templates can expose product construction, elements, parameters, assembly, state, and diagnostic tools.

1. 1

   Create a reusable template.

2. 2

   Assign it as the administration default.

3. 3

   Override it per product only when necessary.

State and events

Treat exported state as the product source of truth. Listen for product, view, selection, price, validation, and export events instead of reading internal renderer objects.

History, view changes, and imports restore canonical state; host code should not mutate Fabric or Babylon objects directly.

1. 1

   Persist only serializable state.

2. 2

   Debounce remote saves.

3. 3

   Include runtime and schema versions with diagnostics.

Host adapters

Uploads, persistence, pricing, licensing, and HD exports are host-owned services. Adapters keep the JavaScript runtime independent from WordPress, Shopify, or a custom commerce stack.

1. 1

   Return durable public media URLs.

2. 2

   Validate file type and size server-side.

3. 3

   Never expose private service credentials in the browser.