eWizard.js documentation

Appearance

September 2026 ​

Cross-channel content and components ​

ModCon 2.0 introduces a template-agnostic architecture to eWizard.js, enabling modular content creation and its seamless sharing across emails, e-Detailers, and other templates.

With ModCon 2.0, matching masterTemplateCode values allow different templates to exchange components and reuse modular content. A new grid-based structure preserves layout during autofill, supports block-to-module conversion, and enables seamless republishing to Veeva Vault to update modules with changes there.

The cross-channel content approach represents a powerful shift toward modular, reusable content architecture that adapts to modern pharmaceutical marketing needs.

Dynamic templates and localization ​

The eWizard.js framework now supports dynamic templates, enabling a single, context-aware template to replace multiple platform-specific variants by adapting in real time using template metadata.

Key features

  • Dynamic localization: Generates dynamic localizations and handles real-time content translation using the DynamicI18n module.

  • Conditional style rendering: Filters dynamic values via the DynamicFilter module to apply context-specific styles and layouts automatically.

  • Metadata-driven adaptation: Leverages unified template metadata across localization and rendering modules to control display logic dynamically.

The eWizard.js framework now features the Banner animation plugin introducing data-driven, timeline-based GSAP animations for banner component.

Key features

  • Data-driven GSAP integration: Registers animation definitions from JSON configurations as named GSAP effects, which can be called directly from animation timelines.

  • Merged animation schemas: Automatically merges standard framework animations with custom, template-level definitions (common/resources/animations.json).

  • Component-level control: Uses an <animation> block within each banner component to define its animation state, timing, and active effects upon template initialization.

Multi-tone blocks ​

Email templates with two or more color schemes now support multi-tone blocks. By default, all components in an email template inherit the template-wide color scheme. With multi-tone blocks, you can override this behavior at the individual block level. Each block can now maintain its own distinct scheme, and child components will automatically adapt to the block's scheme rather than defaulting to the template-level setting.

Starting with eWizard.js framework version 5.55.0, you can export banners for Google Studio and prepare them for upload to this target system.

The export generates a self-contained directory for each banner size with all required HTML, CSS, JavaScript, backup image, fonts, and theme assets. The builder also configures Google Studio compatibility features, including automatic Enabler initialization, polite loading, exit handling, and banner size metadata.

To help meet Google Studio size requirements, the build process optimizes media assets and excludes unused resources and modules. You must manually add at least one exit to the banner to allow click-through tracking.

Documentation updates ​

  • The new look and feel of the eWizard.js documentation due to the migration to VitePress.

  • Dynamic block list: Described the block filtering principles in emails.

  • Tutorials: Comprehensive update of the e-Detailer and email tutorials.

  • Component setup: Expanded the list of the sealed properties.