PIKIT BOOKING WIDGET
Pikit Booking Widget compatibility with REEID Translate
Pikit Booking Widget compatibility with REEID Translate is being reviewed using official plugin documentation. Embeds the official Pikit booking widget by enqueuing a front-end script from `https://book.pikit.io` (specifically `book.pikit.io/install/widget.js`) when the embed is enabled No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Pikit Booking Widget does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Pikit Booking Widget is documented in the Other category with 8 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Pikit Booking Widget compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Embeds the official Pikit booking widget by enqueuing a front-end script from `https://book.pikit.io` (specifically `book.pikit.io/install/widget.js`) when the embed is enabled
- Provides a branded Pikit admin settings page that includes setup/onboarding steps and an installation-code workflow
- Supports placing a booking trigger via a Gutenberg block named *Pikit Button* (with core Button styling controls such as colors, typography, border, padding, and width)
- Supports a *Pikit Button* integration for Elementor (Elementor widget) and WPBakery (WPBakery element), with native button controls when those page builders are active
- Offers a shortcode `[pikit_book_button]` to render the booking button on any page builder/theme
- Supports configurable shortcode attributes including `text`, `style` (`button` or `link`), `class` (CSS classes), and `align` (`left`, `center`, `right`)
- Includes an embed scope option for front page or site-wide embed scope and provides SEO-friendly or fast-load embed modes
- Works with Pikit dashboard **Verify Connection** to confirm the widget is live on the site
TRANSLATION BOUNDARY
Pikit Booking Widget capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
Pikit Booking Widget and REEID Translate FAQ.
What does Pikit Booking Widget do?
Pikit Booking Widget has 8 documented features listed in its official documentation. See the Plugin Information section for details.
Does Pikit Booking Widget have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Pikit Booking Widget?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Pikit Booking Widget in a multilingual WordPress workflow.
REEID documents Pikit Booking Widget functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.