SPINTAX
Spintax compatibility with REEID Translate
Spintax compatibility with REEID Translate is being evaluated from available plugin evidence. Template-based content generation using spintax markup with enumerations, permutations, variables, conditionals, plural agreement, and nested templates/includes. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Spintax.
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
Spintax is documented in the Other category with 6 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 Spintax 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
- Template-based content generation using spintax markup with enumerations, permutations, variables, conditionals, plural agreement, and nested templates/includes.
- Inline rendering via shortcode and a PHP render function, with optional WooCommerce single-product context that exposes product-related variables (e.g., product name/SKU/categories/attributes) when on a product page.
- Pre-generation bindings that write rendered output into ACF fields and/or post-meta keys on triggers such as post save, cron schedules, “Bulk Apply”, and WP-CLI apply/test/export/import workflows.
- WooCommerce product-field bindings that can write generated copy into only the product description and short description fields (with manual-edit preservation behavior described).
- Caching of rendered output using the WordPress Object Cache API, with optional cron-based cache refresh per template/binding.
- Validation and admin tooling: syntax/bracket matching, circular reference detection, admin UI for templates/bindings/logs, and WP-CLI subcommands for managing bindings.
CONTENT BOUNDARY
Spintax 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
Spintax and REEID Translate FAQ.
What does Spintax do according to the available plugin evidence?
Spintax has 6 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 Spintax?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Spintax?
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 Spintax in a multilingual WordPress workflow.
REEID documents Spintax 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.