INGOTFORGE CARDS FOR ACF
IngotForge Cards for ACF compatibility with REEID Translate
IngotForge Cards for ACF compatibility with REEID Translate is being evaluated from available plugin evidence. Provides a shortcode `[ingotforge_cards]` to render posts/ACF data as responsive cards in grid, list, or Swiper-based slider layouts. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for IngotForge Cards for ACF.
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
IngotForge Cards for ACF 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 IngotForge Cards for ACF 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
- Provides a shortcode `[ingotforge_cards]` to render posts/ACF data as responsive cards in grid, list, or Swiper-based slider layouts.
- Supports AJAX pagination for grid and list layouts, including a documented WordPress AJAX endpoint usage for pagination.
- Integrates with Advanced Custom Fields (ACF/ACF PRO) by reading multiple ACF field types (e.g., text/textarea/date/taxonomy/post object/relationship/file and scalar return types) via `get_field()` and `get_field_object()`.
- Implements filtering capabilities based on post type/taxonomy/meta and supports date filtering including `{today}`; also includes Events Calendar-specific date/cost/venue and upcoming/past event support.
- Loads Swiper assets conditionally: Swiper CSS/JS are bundled locally and only loaded when at least one slider instance is rendered (with additional pre-detection for common shortcode placements).
- Offers visibility controls to show/hide card elements such as image, title, excerpt, ACF fields, taxonomy fields, dates, and document buttons; also supports image-only cards and disabling image/title links via `link_to`.
- Exposes developer integration hooks/extension points including filters for normalized shortcode args, query args, per-card HTML, and asset requirements, plus actions/events for AJAX pagination completion and slider initialization; also provides `window.IngotForgeCards.loadPage(…)` and `window.IngotForgeCards.initSliders(…)` for controlled integrations.
CONTENT BOUNDARY
IngotForge Cards for ACF 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
IngotForge Cards for ACF and REEID Translate FAQ.
What does IngotForge Cards for ACF do according to the available plugin evidence?
IngotForge Cards for ACF 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 IngotForge Cards for ACF?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for IngotForge Cards for ACF?
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 IngotForge Cards for ACF in a multilingual WordPress workflow.
REEID documents IngotForge Cards for ACF 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.