MAP BLOCK FOR YANDEX
Map Block for Yandex compatibility with REEID Translate
Map Block for Yandex compatibility with REEID Translate is being evaluated from available plugin evidence. Renders Yandex Maps as a native WordPress block (Gutenberg) powered by Yandex Maps JavaScript API v3, with live inspector-driven updates in the editor preview. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Map Block for Yandex.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Map Block for Yandex is documented in the Media category with 8 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Map Block for Yandex compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Renders Yandex Maps as a native WordPress block (Gutenberg) powered by Yandex Maps JavaScript API v3, with live inspector-driven updates in the editor preview.
- Supports multiple independent map blocks per post/page, with each block isolated in a Web Component using Shadow DOM and owning an independently disposable map instance.
- Provides configurable map viewport and appearance settings (e.g., center, zoom, camera, tilt/azimuth, map mode, and automatic/light/dark theme) and selected map behaviors/controls (e.g., zoom, geolocation, fullscreen).
- Implements structured markers per block, including adding/duplicating/reordering/removing markers and configuring marker coordinates, labels/descriptions, links, colors/icons/images, sizes, and stacking order.
- Supports optional client-side marker clustering and applies bounded Yandex vector-map customization rules.
- Controls loading behavior for compatibility/performance: lazy-load near the viewport or click-to-activate mode; can disable or customize a loading overlay/spinner/preloader and map reveal.
- Handles failure/accessibility states: when the Yandex SDK/key is missing or fails, the block displays an accessible error and a fallback link instead of a blank map; editor preview is intentionally non-interactive (gesture-locked).
- Restricts marker content to text and safe HTTP(S) URLs (no executable code stored in block attributes) and limits inline markers to 1,000 per block (and an approximately 1 MiB rendered configuration).
CONTENT BOUNDARY
Map Block for Yandex capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Map Block for Yandex and REEID Translate FAQ.
What does Map Block for Yandex do according to the available plugin evidence?
Map Block for Yandex has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Map Block for Yandex?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Map Block for Yandex?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Map Block for Yandex in a multilingual WordPress workflow.
REEID documents Map Block for Yandex functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.