CM TOOLTIP GLOSSARY
CM Tooltip Glossary translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what CM Tooltip Glossary 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
- Automatically links glossary terms in posts and pages to glossary definitions.
- Generates a glossary index page with alphabetically organized terms.
- Creates dedicated pages for individual glossary terms.
- Displays hover tooltips for glossary terms.
- Supports excluding specific content from parsing with a shortcode.
- Supports controlling where tooltips appear across pages, posts, and the homepage.
- Includes a setup wizard for initial configuration.
- Supports performance optimizations and caching for large glossaries.
Distinctive features
Glossary-focused linking, hover tooltips, an alphabetized glossary index page, and dedicated term pages are the main user-facing differentiators supported by the evidence.
Dynamic content
The evidence supports automatic glossary-term linking in posts and pages, plus hover tooltips for glossary terms. It also supports excluding specific content from parsing with a shortcode and controlling where tooltips appear across pages, posts, and the homepage. Other runtime content behavior is not established.
SEO and metadata
Official evidence supports glossary-related internal linking and glossary/term pages. It does not establish additional SEO metadata, schema, or indexing behavior beyond those glossary page and term page outputs.
URLs and navigation
The evidence supports navigation to a glossary index page and to dedicated pages for individual glossary terms. No broader URL or 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 CM Tooltip Glossary 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
- Official evidence does not establish additional SEO-specific metadata, schema, indexing, or translation behavior beyond the documented glossary links, glossary pages, and term pages. Content parsing can be limited with a shortcode, and tooltip display can be controlled across pages, posts, and the homepage.
COMMON QUESTIONS
CM Tooltip Glossary and REEID Translate FAQ.
Does the current evidence establish translation scope for CM Tooltip Glossary?
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.