CLASSIC MENU IN NAVIGATION BLOCK

Classic Menu in Navigation Block compatibility with REEID Translate

Classic Menu in Navigation Block compatibility with REEID Translate is being evaluated from available plugin evidence. Renders classic WordPress menus within the native Navigation block in Full Site Editing (FSE) themes No specific visitor-facing translation surface is currently confirmed.

Visit Classic Menu in Navigation Block ↗

AWAITING VERIFICATION

What the available evidence establishes for Classic Menu in Navigation Block.

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
Classic Menu in Navigation Block is documented in the Navigation category with 6 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 Classic Menu in Navigation Block 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

  • Renders classic WordPress menus within the native Navigation block in Full Site Editing (FSE) themes
  • Re-enables the Appearance → Menus admin screen and registers menu locations for block-based themes
  • Provides a caching mechanism for converted classic menus with an option to disable it for dynamic content
  • Integrates with multilingual plugins by allowing navigation to revert to classic menu structures
  • Preserves standard Navigation block features such as accessibility, customization, and responsiveness
  • Adds configuration settings to the WordPress Customizer under Appearance → Customize → Menus

CONTENT BOUNDARY

Classic Menu in Navigation Block 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

Classic Menu in Navigation Block and REEID Translate FAQ.

What does Classic Menu in Navigation Block do according to the available plugin evidence?

Classic Menu in Navigation Block has 6 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 Classic Menu in Navigation Block?

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

What would establish translation scope for Classic Menu in Navigation Block?

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 Classic Menu in Navigation Block in a multilingual WordPress workflow.

REEID documents Classic Menu in Navigation Block 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