TRIPLANDOO
Triplandoo compatibility with REEID Translate
Triplandoo compatibility with REEID Translate is being evaluated from available plugin evidence. Provides a `[triplandoo_booking]` shortcode to embed hosted Triplandoo booking pages in WordPress. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Triplandoo.
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
Triplandoo is documented in the Other category with 7 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 Triplandoo 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
- Provides a `[triplandoo_booking]` shortcode to embed hosted Triplandoo booking pages in WordPress.
- Registers a server-rendered `Triplandoo Booking` block for the block editor to embed the booking iframe.
- Integrates with Elementor by providing an Elementor widget, which is only registered when Elementor is active.
- Requires a Triplandoo booking iframe URL to render the embedded booking page; the plugin acts as an interface to the hosted booking service.
- Renders only HTTPS iframe URLs from `triplandoo.com` or its subdomains (non-Triplandoo iframe URLs are not allowed).
- Supports optional embed parameters including height, color/accent, language, heading, subheading, and support phone, which are passed to the embedded booking page.
- Does not collect or store visitor booking data in WordPress; the embedded booking page is loaded from Triplandoo and site owners should reference Triplandoo in their privacy policy where required.
CONTENT BOUNDARY
Triplandoo 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
Triplandoo and REEID Translate FAQ.
What does Triplandoo do according to the available plugin evidence?
Triplandoo has 7 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 Triplandoo?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Triplandoo?
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 Triplandoo in a multilingual WordPress workflow.
REEID documents Triplandoo 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.