VOXYCURE FRAMEWORK
Voxycure Framework compatibility with REEID Translate
Voxycure Framework compatibility with REEID Translate is being evaluated from available plugin evidence. Code-first developer framework for registering custom Gutenberg blocks, fields, content types, taxonomies, reusable components, and option pages via PHP registrations. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Voxycure Framework.
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
Voxycure Framework is documented in the Other 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 Voxycure Framework 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
- Code-first developer framework for registering custom Gutenberg blocks, fields, content types, taxonomies, reusable components, and option pages via PHP registrations.
- Registers definitions through the `voxycure/register` action, where the callback receives a `$registry` object automatically.
- Native editor integration: built blocks/fields/post types/taxonomies appear in WordPress’ native editor screens created by the PHP registrations (no admin builder menu for creating definitions).
- Reusable Components feature uses native private WordPress posts as the storage mechanism; component content is not sent to Voxycure and has no public URLs.
- Block attribute persistence: block values are saved by WordPress as block attributes in post content; document fields use registered post meta; option pages use `wp_options` (no custom database tables required for definitions).
- WooCommerce integration for product fields: product field groups can target `post_types => ['product']` with `editor => 'woocommerce'`, rendering supported controls in WooCommerce Product data tabs and saving through the WooCommerce product object.
- Output caching support for dynamic block output: individual block registrations can set `cache_ttl` to enable caching (disabled by default; enabled when value > 0).
- Privacy/telemetry behavior: Voxycure Framework does not send activation/deactivation/update/site/usage/administrator data to Voxycure or a tracking service; activation schedules a one-time local rewrite-rule refresh.
Distinctive features
Code-first developer framework for registering custom Gutenberg blocks, fields, content types, taxonomies, reusable components, and option pages via PHP registrations. Registers definitions through the `voxycure/register` action, where the callback receives a `$registry` object automatically. Native editor integration: built blocks/fields/post types/taxonomies appear in WordPress’ native editor screens created by the PHP registrations (no admin builder menu for creating definitions). Reusable Components feature uses native private WordPress posts as the storage mechanism; component content is not sent to Voxycure and has no public URLs. Block attribute persistence: block values are saved by WordPress as block attributes in post content; document fields use registered post meta; option pages use `wp_options` (no custom database tables required for definitions). WooCommerce integration for product fields: product field groups can target `post_types => ['product']` with `editor => 'woocommerce'`, rendering supported controls in WooCommerce Product data tabs and saving through the WooCommerce product object. Output caching support for dynamic block output: individual block registrations can set `cache_ttl` to enable caching (disabled by default; enabled when value > 0). Privacy/telemetry behavior: Voxycure Framework does not send activation/deactivation/update/site/usage/administrator data to Voxycure or a tracking service; activation schedules a one-time local rewrite-rule refresh. Option page load/save uses requests initiated by an authorized administrator to the plugin’s local WordPress REST endpoint.
CONTENT BOUNDARY
Voxycure Framework 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
Voxycure Framework and REEID Translate FAQ.
What does Voxycure Framework do according to the available plugin evidence?
Voxycure Framework 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 Voxycure Framework?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Voxycure Framework?
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 Voxycure Framework in a multilingual WordPress workflow.
REEID documents Voxycure Framework 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.