MKWEBTECH CONVERSION BLOCKS
MKWebTech Conversion Blocks translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what MKWebTech Conversion Blocks does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Conditional frontend asset loading based on block usage (no global frontend bundle).
- Frontend interactivity implemented with dependency-free JavaScript (explicitly no jQuery dependency).
- Provides multiple conversion-oriented Gutenberg blocks (countdown timer, notification/announcement bars, promo banners, coupon/offer box, floating CTA) intended to render on the frontend when used.
- WooCommerce-aware targeting for where blocks display (e.g., shop, product, product category archives, cart/checkout, specific product/category IDs, sale/stock states, and additional site/front-page/post/page/content-ID/URL-path matching).
- Notification/announcement bar behaviors include sticky vs static placement, dismissibility, scheduling (start/end window in site timezone), and optional auto-hide.
Distinctive features
Conditional frontend asset loading based on block usage (no global frontend bundle). Frontend interactivity implemented with dependency-free JavaScript (explicitly no jQuery dependency). Provides multiple conversion-oriented Gutenberg blocks (countdown timer, notification/announcement bars, promo banners, coupon/offer box, floating CTA) intended to render on the frontend when used. WooCommerce-aware targeting for where blocks display (e.g., shop, product, product category archives, cart/checkout, specific product/category IDs, sale/stock states, and additional site/front-page/post/page/content-ID/URL-path matching). Notification/announcement bar behaviors include sticky vs static placement, dismissibility, scheduling (start/end window in site timezone), and optional auto-hide. Countdown timer behaviors include fixed-date, evergreen, and recurring daily/weekly countdowns, plus configurable expiry handling (e.g., leave at zero, hide, show a message, or redirect).
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
Keep plugin capabilities separate from translation scope.
Current evidence documents what MKWebTech Conversion Blocks does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
MKWebTech Conversion Blocks and REEID Translate FAQ.
Does the current evidence establish translation scope for MKWebTech Conversion Blocks?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.