LEAFLET MAP
Leaflet Map compatibility with REEID Translate
Leaflet Map compatibility with REEID Translate is being evaluated from available plugin evidence. Creates interactive maps via the `[leaflet-map]` shortcode, with map tiles sourced by default from OpenStreetMap or MapQuest. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Leaflet Map.
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
Leaflet Map is documented in the Navigation 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 Leaflet Map 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
- Creates interactive maps via the `[leaflet-map]` shortcode, with map tiles sourced by default from OpenStreetMap or MapQuest.
- Supports geocoding by address as well as direct latitude/longitude placement with zoom control.
- Allows multiple markers per map, including marker popups and fit-to-bounds behavior across markers/shapes.
- Supports additional vector and overlay content through shortcodes for lines, circles, polygons, GeoJSON, KML, GPX, WMS, and image/video overlays.
- Can render a plain image as a zoomable/pannable Leaflet-based image map via `[leaflet-image]`.
- Supports marker and shape customization through shortcode attributes, including styling, visibility, draggable markers, and SVG marker icons.
- Can load GeoJSON from a URL and bind popup content from shortcode text or feature properties.
- Provides a setting/filter for the Nominatim contact email used in geocoding requests.
CONTENT BOUNDARY
Leaflet Map 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
Leaflet Map and REEID Translate FAQ.
What does Leaflet Map do according to the available plugin evidence?
Leaflet Map 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 Leaflet Map?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Leaflet Map?
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 Leaflet Map in a multilingual WordPress workflow.
REEID documents Leaflet Map 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.