
CARDS LAYOUT
Cards Layout – showcase content in responsive card grids compatibility with REEID Translate
Cards Layout – showcase content in responsive card grids compatibility with REEID Translate is being reviewed using official plugin documentation. Build responsive card layouts in Gutenberg using feature cards, hero cards, achievement cards, and grids with full styling control. No specific text shown to visitors is currently confirmed for translation.
Visit Cards Layout – showcase content in responsive card grids ↗
AWAITING VERIFICATION
What Cards Layout – showcase content in responsive card grids does
Official documentation did not establish a visitor-facing content item within the supported scope for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Cards Layout – showcase content in responsive card grids is documented in the Page Builder category with 6 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Cards Layout – showcase content in responsive card grids compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Build responsive card layouts in Gutenberg using feature cards, hero cards, achievement cards, and grids with full styling control.
- Provide a “Default Card” with image, title, description, and button controls.
- Provide a “Hero Feature Card” with advanced image focal point controls and overlay gradients.
- Provide an “Achievement Card” with a large central metric and a customizable spinning SVG badge animation.
- Provide a “Responsive Grid Engine” with native control over column counts (Desktop, Tablet, Mobile) and gap spacing.
- Provide “Advanced Global Styling” controls for typography (fonts, sizes, weights) and multi-state box shadows, borders, padding, and alignments.
TRANSLATION BOUNDARY
Cards Layout – showcase content in responsive card grids capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- No visitor-facing translation surface was established for this integration.
FREQUENTLY ASKED QUESTIONS
Cards Layout – showcase content in responsive card grids and REEID Translate FAQ.
What does Cards Layout – showcase content in responsive card grids do?
Cards Layout – showcase content in responsive card grids has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does Cards Layout – showcase content in responsive card grids have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Cards Layout – showcase content in responsive card grids?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Cards Layout – showcase content in responsive card grids in a multilingual WordPress workflow.
REEID documents Cards Layout – showcase content in responsive card grids functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.