WHAT THE FILE
What The File translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what What The File does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Adds a toolbar option that shows the file and template parts used for the page being viewed.
- Lets you click the file name to open it in the WordPress theme editor.
- Supports BuddyPress themes.
- Supports Roots Theme based themes.
- Shows the currently used template file in the toolbar hover state.
- Can display template parts used to render the current page.
Distinctive features
Shows theme file and template-part information directly in the toolbar. Includes a click-through path from the file name to the WordPress theme editor. Documented support is available for BuddyPress themes and Roots Theme based themes.
Dynamic content
Runtime behavior is established for the page currently being viewed: the toolbar can show the file, template parts, and current template file for that page. Broader dynamic content handling is not established.
SEO and metadata
No SEO or metadata behavior is established in the supplied evidence.
URLs and navigation
The plugin is tied to the page currently being viewed and exposes a clickable file name that opens the WordPress theme editor. No broader URL navigation behavior is established.
Forms and commerce
No forms or commerce behavior is established in the supplied evidence.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what What The File does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- Evidence is limited to toolbar-based file and template information on the page being viewed. Compatibility is explicitly documented for BuddyPress themes and Roots Theme based themes, but no broader theme coverage is established. The available evidence does not show any frontend layout changes beyond displaying file and template information.
COMMON QUESTIONS
What The File and REEID Translate FAQ.
Does the current evidence establish translation scope for What The File?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.