CEDRIC RECIPE EXPLORER
Cedric Recipe Explorer compatibility with REEID Translate
Cedric Recipe Explorer compatibility with REEID Translate is being evaluated from available plugin evidence. Recipe discovery/search by ingredient, dish, or craving via Spoonacular-powered backend. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Cedric Recipe Explorer.
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
Cedric Recipe Explorer 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 Cedric Recipe Explorer 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
- Recipe discovery/search by ingredient, dish, or craving via Spoonacular-powered backend.
- Instant autocomplete for recipe search results (Spoonacular-backed).
- Recipe presentation including recipe cards with ingredients/method details and a per-recipe nutrition profile (Spoonacular-backed).
- Random recipe selection/display capability.
- Multilingual cleanup and translation of recipe content is supported when an OpenAI API key is configured; plugin remains usable without OpenAI.
- Output language selector supports French, English, Spanish, Italian, German, and Dutch (for the plugin’s output).
- Content can be embedded either via a shortcode (`[cedrrex_recipes]`) or a dedicated Gutenberg block.
- Multiple front-end display variants are offered (Auto, Editorial, Compact).
CONTENT BOUNDARY
Cedric Recipe Explorer 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
Cedric Recipe Explorer and REEID Translate FAQ.
What does Cedric Recipe Explorer do according to the available plugin evidence?
Cedric Recipe Explorer 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 Cedric Recipe Explorer?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Cedric Recipe Explorer?
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 Cedric Recipe Explorer in a multilingual WordPress workflow.
REEID documents Cedric Recipe Explorer 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.