AM LOTTIEPLAYER
AM LottiePlayer | REEID Translate Compatibility
REEID processes supported titles, captions, alt text, descriptions and other visitor-facing media metadata while AM LottiePlayer remains responsible for files, galleries and media processing.
AWAITING VERIFICATION
Translate media metadata. Preserve media assets.
Text attached to supported media can become multilingual without modifying binary files, upload behaviour or media processing configuration.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
CONTENT BOUNDARY
Translatable content remains separate from plugin-specific functional configuration.
MEDIA-SAFE
Images, video, audio and file-processing behaviour remain separate from translatable metadata.
PRACTICAL WORKFLOW
Translation workflow
01 · Prepare the source media
Upload and organize media using the normal AM LottiePlayer workflow.
02 · Identify translatable metadata
Target supported titles, captions, alt text, descriptions and visitor-facing labels.
03 · Translate media text
Process supported metadata while leaving the underlying media asset unchanged.
04 · Review multilingual presentation
Check captions, accessibility text, galleries and frontend media presentation.
SUPPORTED CONTENT
Translation scope
Visitor-facing text
Replace this draft item with the exact evidence-backed content coverage.
Interface content
Document supported labels, titles or interface strings where applicable.
Product-specific content
Add confirmed product-specific support before publication.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Provides two Gutenberg blocks: a player block and a cover block with text overlay.
- Supports embedding Lottie animations via a shortcode `[am-lottieplayer]` with documented parameters (e.g., `src`, `autoplay`, `controls`, `loop`, `objectfit`, `speed`, `direction`, and interaction triggers like `onclick`/`onmouseover`/`onmouseout`).
- Accepts Lottie animation files in either JSON or dotLottie formats, including uploading to the WordPress Media Library and drag-and-drop upload.
- Allows specifying a Lottie animation source from a URL (via shortcode parameter `src`) and inserting animations from URL in the block/widget contexts described in the readme.
- Offers rendering/scaling-related configuration via block/widget settings (Gutenberg block settings are stated to expose options such as scaling, speed, size, background color, and interactions).
- Loads plugin scripts only on pages where the player is used (per readme).
- Integrates with multiple page builders/constructors: Divi Builder (module), Elementor (widget), Bricks (element), Flatsome UX Builder (integration), and has partial support for WPBakery (menu/settings access described).
Distinctive features
Provides two Gutenberg blocks: a player block and a cover block with text overlay. Supports embedding Lottie animations via a shortcode `[am-lottieplayer]` with documented parameters (e.g., `src`, `autoplay`, `controls`, `loop`, `objectfit`, `speed`, `direction`, and interaction triggers like `onclick`/`onmouseover`/`onmouseout`). Accepts Lottie animation files in either JSON or dotLottie formats, including uploading to the WordPress Media Library and drag-and-drop upload. Allows specifying a Lottie animation source from a URL (via shortcode parameter `src`) and inserting animations from URL in the block/widget contexts described in the readme. Offers rendering/scaling-related configuration via block/widget settings (Gutenberg block settings are stated to expose options such as scaling, speed, size, background color, and interactions). Loads plugin scripts only on pages where the player is used (per readme). Integrates with multiple page builders/constructors: Divi Builder (module), Elementor (widget), Bricks (element), Flatsome UX Builder (integration), and has partial support for WPBakery (menu/settings access described).
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Translate media metadata without modifying media files.
REEID handles supported textual metadata while AM LottiePlayer remains responsible for media files, galleries, processing and storage behaviour.
Binary assets, transformations and dynamically generated media may require separate handling.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
AM LottiePlayer and REEID Translate FAQ.
Does REEID Translate work with AM LottiePlayer?
REEID Translate Pro processes the supported visitor-facing fields documented for this integration while AM LottiePlayer retains control of its own functionality.
Does REEID duplicate or modify media files?
Not as part of ordinary text translation. Media assets and processing remain controlled by AM LottiePlayer.
Can captions and alt text be translated?
Supported textual media metadata such as captions and alt text can be processed when exposed through supported fields.
RELATED GUIDES
Continue through the compatibility library.
MEDIA INTEGRATION
Translate AM LottiePlayer media metadata without rebuilding your media library.
Localize supported captions, titles and descriptions while preserving the original assets.
Supported content and limitations are defined by the integration record.