HEADLESS
Headless compatibility with REEID Translate
Headless compatibility with REEID Translate is being evaluated from available plugin evidence. Extends the WordPress REST API with extra fields and prepared block content when the ?headless=true query parameter is present. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Headless.
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
Headless 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 Headless 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
- Extends the WordPress REST API with extra fields and prepared block content when the ?headless=true query parameter is present.
- Provides custom REST routes for retrieving site menus and settings under /headless/v1/.
- Enables frontend previews by redirecting preview links to a configured base URL instead of the WordPress theme.
- Supports cache revalidation requests sent to the frontend's /api/revalidate endpoint using a shared secret token.
- Allows configuration via wp-config.php constants for the frontend base URL, secret token, and optional API key headers.
- Includes security filters to restrict access to protected meta keys and enforce public post types in REST queries.
CONTENT BOUNDARY
Headless 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
Headless and REEID Translate FAQ.
What does Headless do according to the available plugin evidence?
Headless 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 Headless?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Headless?
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 Headless in a multilingual WordPress workflow.
REEID documents Headless 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.