SPECIFIC CONTENT FOR MOBILE
Specific Content For Mobile – Customize the mobile version without redirections translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what Specific Content For Mobile – Customize the mobile version without redirections does, but does not yet establish specific visitor-facing content values that REEID should translate.
Visit Specific Content For Mobile – Customize the mobile version without redirections ↗
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
- Creates separate, mobile-specific page/post content rather than redirecting mobile users to a different URL.
- Provides an admin workflow to create or remove a mobile version for individual Pages and Posts (e.g., via a “Create mobile version” action/icon).
- On mobile devices, loads the created mobile version for the corresponding page/post while keeping the public URL the same as the desktop URL.
- When logged in, the plugin exposes an additional mobile-version URL variant (e.g., `…/page-example-mobile/`), while logged-out users only see the original public URL (e.g., `…/page-example/`).
- Synchronizes post/page metadata between desktop and mobile versions by default, with an option to allow mobile versions to have their own metadata.
- Checks theme support for the blog posts page mobile version; if the theme does not declare support, the mobile blog page may fall back to the desktop content.
- Supports developer customization via mobile template overrides placed in `wp-content/scfm/` or `wp-content/themes//scfm/` (with mobile-specific template lookup order).
- Exposes developer integration via a filter named `eos_scfm_meta_integration_array` to add metadata synchronization options for external plugins.
Distinctive features
Creates separate, mobile-specific page/post content rather than redirecting mobile users to a different URL. Provides an admin workflow to create or remove a mobile version for individual Pages and Posts (e.g., via a “Create mobile version” action/icon). On mobile devices, loads the created mobile version for the corresponding page/post while keeping the public URL the same as the desktop URL. When logged in, the plugin exposes an additional mobile-version URL variant (e.g., `…/page-example-mobile/`), while logged-out users only see the original public URL (e.g., `…/page-example/`). Synchronizes post/page metadata between desktop and mobile versions by default, with an option to allow mobile versions to have their own metadata. Checks theme support for the blog posts page mobile version; if the theme does not declare support, the mobile blog page may fall back to the desktop content. Supports developer customization via mobile template overrides placed in `wp-content/scfm/` or `wp-content/themes//scfm/` (with mobile-specific template lookup order). Exposes developer integration via a filter named `eos_scfm_meta_integration_array` to add metadata synchronization options for external plugins.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what Specific Content For Mobile – Customize the mobile version without redirections 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
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Specific Content For Mobile – Customize the mobile version without redirections and REEID Translate FAQ.
Does the current evidence establish translation scope for Specific Content For Mobile – Customize the mobile version without redirections?
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.