NEX DIRECTORY
Nex Directory compatibility with REEID Translate
Nex Directory compatibility with REEID Translate is being evaluated from available plugin evidence. Frontend submissions workflow with draft auto-save, owner editing, and moderation (including moderation queue actions like approve/reject/reviewer notes). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Nex Directory.
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
Nex Directory 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 Nex Directory 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
- Frontend submissions workflow with draft auto-save, owner editing, and moderation (including moderation queue actions like approve/reject/reviewer notes).
- Directory/event browsing UI supporting multiple views (list, grid, map, and calendar) plus search and filtering by distance, category, tag, and listing fields.
- Event-specific attendee tools including RSVP, capacity, waitlist, and waitlist-status, along with public site calendar and organizer calendar subscriptions (iCalendar feeds).
- Import/export capabilities including CSV and JSON imports with preview mapping.
- Developer-facing integration surface including shortcodes, Elementor widgets for included shortcodes, and REST endpoints for approved integrations.
- Member/organizer dashboard and workflow features including dashboards for listings/messages/saved items/settings, notifications for messages/claims/moderation/RSVPs/waitlist changes, and claim-listing workflow for ownership requests.
- Optional integrations and external services are conditional on configuration or user action (e.g., reCAPTCHA only after site owner configures it; Google Maps/geocoding only when selected; Google Calendar sends listing details when “Google Calendar” is clicked; map/tile/geocoding providers used only when selected).
- Optional Nex Directory Chrome extension setup screen for the official Nex Directory Scanner, with the extension download link opened only after an administrator clicks it; extension is optional and not required for core plugin functionality.
CONTENT BOUNDARY
Nex Directory 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
Nex Directory and REEID Translate FAQ.
What does Nex Directory do according to the available plugin evidence?
Nex Directory 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 Nex Directory?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Nex Directory?
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 Nex Directory in a multilingual WordPress workflow.
REEID documents Nex Directory 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.