LAPDI CHAPTERS
LAPDI Chapters compatibility with REEID Translate
LAPDI Chapters compatibility with REEID Translate is being evaluated from available plugin evidence. Manages real organization chapters with structured addresses and directory statuses from a WordPress dashboard. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for LAPDI Chapters.
Official documentation did not establish a visitor-facing content item within the supported scope for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
LAPDI Chapters is documented in the Forms 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 LAPDI Chapters 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
- Manages real organization chapters with structured addresses and directory statuses from a WordPress dashboard.
- Publishes an accessible, responsive, server-rendered chapter finder using the [lapdi_chapter_finder] shortcode.
- Supports distinct visitor actions for Active chapters: Join This Chapter, Visit Chapter Website, and Contact Chapter.
- Provides configurable empty-state actions such as Start a Chapter and Contact Us.
- Exposes public read-only chapter data via the /wp-json/lapdi-chapters/v1/chapters REST API endpoint.
- Allows configuration of chapter leader titles, photos, and framing options for display in lists and finders.
CONTENT BOUNDARY
LAPDI Chapters 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
- No visitor-facing translation surface was established for this integration.
COMMON QUESTIONS
LAPDI Chapters and REEID Translate FAQ.
What does LAPDI Chapters do according to the available plugin evidence?
LAPDI Chapters 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 LAPDI Chapters?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for LAPDI Chapters?
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 LAPDI Chapters in a multilingual WordPress workflow.
REEID documents LAPDI Chapters 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.