
ACF FLEXIBLE LAYOUT PREVIEW
ACF Flexible Layout Preview compatibility with REEID Translate
ACF Flexible Layout Preview compatibility with REEID Translate is being evaluated from available plugin evidence. Adds visual preview images and a visual layout picker to ACF Flexible Content fields in the WordPress admin No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for ACF Flexible Layout Preview.
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
ACF Flexible Layout Preview is documented in the Other category with 7 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 ACF Flexible Layout Preview 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
- Adds visual preview images and a visual layout picker to ACF Flexible Content fields in the WordPress admin
- Automatically discovers Flexible Content layouts from ACF field groups and provides a centralized dashboard/page for managing layout preview images
- Supports uploading, replacing, removing, and setting a default preview image for Flexible Content layouts (including custom layouts)
- Stores uploaded preview images under /wp-content/uploads/acf-layout-previews/
- Provides admin UI options such as popup/grid column settings and light/dark admin themes for the preview experience
- Includes a dedicated “Layout Preview management” page and a documentation tab with setup instructions
- Requires Advanced Custom Fields Pro (advanced-custom-fields-pro) to function, since Flexible Content fields are only available in ACF Pro
CONTENT BOUNDARY
ACF Flexible Layout Preview 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
ACF Flexible Layout Preview and REEID Translate FAQ.
What does ACF Flexible Layout Preview do according to the available plugin evidence?
ACF Flexible Layout Preview has 7 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 ACF Flexible Layout Preview?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for ACF Flexible Layout Preview?
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 ACF Flexible Layout Preview in a multilingual WordPress workflow.
REEID documents ACF Flexible Layout Preview 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.