MAQSY: FAQ MANAGER AND AI CHAT
Maqsy: FAQ Manager and AI Chat compatibility with REEID Translate
Maqsy: FAQ Manager and AI Chat compatibility with REEID Translate is being evaluated from available plugin evidence. Frequently Asked Questions are managed via a private custom post type (`maqsy`) with an ordered list of question/answer pairs. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Maqsy: FAQ Manager and AI Chat.
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
Maqsy: FAQ Manager and AI Chat is documented in the Other 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 Maqsy: FAQ Manager and AI Chat 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
- Frequently Asked Questions are managed via a private custom post type (`maqsy`) with an ordered list of question/answer pairs.
- FAQs can be displayed on pages or posts using the `[maqsy]` shortcode or a dedicated Gutenberg block.
- Two accessible display templates are available: Simple (definition list) and Accordion (WAI-ARIA disclosure pattern).
- The plugin automatically generates `schema.org/FAQPage` JSON-LD structured data for singular views to support search engine understanding.
- An optional AI chat widget allows visitors to query published FAQ content, disabled by default until configured.
- The AI chat feature supports OpenAI-compatible APIs (including OpenRouter and self-hosted endpoints) via configurable base URLs and API keys.
CONTENT BOUNDARY
Maqsy: FAQ Manager and AI Chat 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
Maqsy: FAQ Manager and AI Chat and REEID Translate FAQ.
What does Maqsy: FAQ Manager and AI Chat do according to the available plugin evidence?
Maqsy: FAQ Manager and AI Chat 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 Maqsy: FAQ Manager and AI Chat?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Maqsy: FAQ Manager and AI Chat?
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 Maqsy: FAQ Manager and AI Chat in a multilingual WordPress workflow.
REEID documents Maqsy: FAQ Manager and AI Chat 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.