ICON INDEXA

Icon Indexa compatibility with REEID Translate

Icon Indexa compatibility with REEID Translate is being evaluated from available plugin evidence. Bundles 4,500+ self-hosted SVG icons inside WordPress (no third-party CDN fetching). No specific visitor-facing translation surface is currently confirmed.

Visit Icon Indexa ↗

AWAITING VERIFICATION

What the available evidence establishes for Icon Indexa.

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
Icon Indexa is documented in the Media 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 Icon Indexa 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

  • Bundles 4,500+ self-hosted SVG icons inside WordPress (no third-party CDN fetching).
  • Provides instant full-text icon search using a local SQLite FTS5 index (search by icon name or tags).
  • Offers a Gutenberg icon block for inserting icons into the editor with controls including link, rotation (360°), horizontal/vertical flip, alignment, color, gradient, background, border, padding, margin, and hover effects.
  • Supports inline SVG output so icons scale cleanly and inherit color (unless the SVG has hard-coded color/fill values).
  • Includes library/style filtering to narrow results by icon set and variant (e.g., Ant Design Icons and Boxicons).
  • Allows adding custom icons by pasting SVG code directly or selecting an SVG from the WordPress Media Library, with sanitization of pasted/imported SVGs and restrictions on link URL protocols.
  • Builds a local SQLite database automatically on first run from bundled icon data and stores it in the uploads directory; requires the PHP SQLite (PDO) extension.

CONTENT BOUNDARY

Icon Indexa 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

Icon Indexa and REEID Translate FAQ.

What does Icon Indexa do according to the available plugin evidence?

Icon Indexa 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 Icon Indexa?

No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.

What would establish translation scope for Icon Indexa?

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 Icon Indexa in a multilingual WordPress workflow.

REEID documents Icon Indexa 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.

Shopping Cart
Scroll to Top