BLOCK CATALOG
Block Catalog compatibility with REEID Translate
Block Catalog compatibility with REEID Translate is being evaluated from available plugin evidence. Indexes Gutenberg blocks used across the site and stores results in a WordPress taxonomy (requires initial indexing). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Block Catalog.
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
Block Catalog is documented in the Other category with 8 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 Block Catalog 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
- Indexes Gutenberg blocks used across the site and stores results in a WordPress taxonomy (requires initial indexing).
- Provides an admin UI entry under WP-Admin > Tools > Block Catalog to run indexing and view indexed block usage.
- Supports WP CLI command `wp block-catalog index` to index content from the command line.
- Keeps the indexed block usage data automatically in sync after initial indexing and subsequent content updates.
- Displays blocks present in a post when navigating to the Block Editor post type (post listing can show blocks per post).
- Adds filtering to show posts that use a specific block via a dropdown in the post listing.
- Detects reusable blocks and can list posts that use Reusable Blocks.
- Uses a filter hook (e.g., `block_catalog_block_title`) and custom WordPress filters to extend behavior, including overriding displayed block titles when block metadata is missing.
CONTENT BOUNDARY
Block Catalog 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
Block Catalog and REEID Translate FAQ.
What does Block Catalog do according to the available plugin evidence?
Block Catalog has 8 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 Block Catalog?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Block Catalog?
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 Block Catalog in a multilingual WordPress workflow.
REEID documents Block Catalog 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.