YAML CUSTOM FIELDS
YAML Custom Fields compatibility with REEID Translate
YAML Custom Fields compatibility with REEID Translate is being evaluated from available plugin evidence. Define YAML schemas for page templates and template partials, including an admin UI for managing schemas and data No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for YAML Custom Fields.
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
YAML Custom Fields 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 YAML Custom Fields 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
- Define YAML schemas for page templates and template partials, including an admin UI for managing schemas and data
- Supports an ACF-like PHP template function approach (e.g., ycf_get_field, ycf_get_image, ycf_get_term, ycf_get_post_type, ycf_get_data_object) with auto-merge behavior
- Three-level data hierarchy: per-page data (post meta), per-template global data shared across posts using the same template, and site-wide global data for partials (e.g., headers/footers)
- Per-field global/local toggle to independently choose whether each field uses template global data or page-specific data
- Provides data objects for managing structured, reusable data types (e.g., universities/companies) and includes data validation for reviewing imported content
- Includes consolidated Export/Import functionality covering settings, page data, and data objects
- Administrator-only access for security and a clean uninstall that removes all database records
CONTENT BOUNDARY
YAML Custom Fields 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
YAML Custom Fields and REEID Translate FAQ.
What does YAML Custom Fields do according to the available plugin evidence?
YAML Custom Fields 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 YAML Custom Fields?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for YAML Custom Fields?
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 YAML Custom Fields in a multilingual WordPress workflow.
REEID documents YAML Custom Fields 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.