VOXYCURE FRAMEWORK

Voxycure Framework compatibility with REEID Translate

Voxycure Framework compatibility with REEID Translate is being reviewed using official plugin documentation. Code-first developer framework for registering custom Gutenberg blocks, fields, content types, taxonomies, reusable components, and option pages via PHP registrations. No specific text shown to visitors is currently confirmed for translation.

Visit Voxycure Framework ↗

AWAITING VERIFICATION

What Voxycure Framework 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
Voxycure Framework 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 Voxycure Framework 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

  • 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.

TRANSLATION BOUNDARY

Voxycure Framework 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

Voxycure Framework and REEID Translate FAQ.

What does Voxycure Framework do?

Voxycure Framework has 8 documented features listed in its official documentation. See the Plugin Information section for details.

Does Voxycure Framework 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 Voxycure Framework?

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 Voxycure Framework in a multilingual WordPress workflow.

REEID documents Voxycure Framework 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.

Shopping Cart
Scroll to Top