Getting started

Choose the delivery

Use the package exports for an application build, or the browser bundle for a script-based integration. Load the shared stylesheet before creating the designer.

Production hosts should serve the generated files from their own versioned assets. Do not reference a source workspace or a development server.

1. 1

   Choose package or browser delivery.

2. 2

   Load the core stylesheet and runtime.

3. 3

   Load Fabric or Babylon only when the product needs that renderer.

Create the instance

Mount AsukaDesigner in a stable container with an explicit width and responsive height. Pass the initial product state, locale, permissions, upload adapter, and commercial API endpoint from the host.

The active view decides whether the 2D or 3D renderer is loaded; the host does not need a manual start-in-2D or start-in-3D switch.

1. 1

   Wait for the ready event.

2. 2

   Load or import the product state.

3. 3

   Subscribe to state and pricing changes.

Validate production behavior

Test desktop, tablet, and mobile sizes, keyboard navigation, uploads, history, view changes, and cart serialization. Verify that lazy 3D chunks are reachable from the final domain.

1. 1

   Exercise a complete product-to-order journey.

2. 2

   Record the runtime version with diagnostics.

3. 3

   Pin and roll back bundles as one release.