Develop integrations for POM Translate

POM Translate exposes procedural helpers and WordPress hooks for integrations that need multilingual values, localized URLs, registered strings, parser extensions, or request-aware language context.

Build integrations in a custom plugin. Do not write directly to POM Translate tables or instantiate internal storage, parser, routing, or queue classes.

Choose an integration path

• Concepts and compatibility explains extraction, rendering, context, caching, and structured content.
• Public helpers documents callable functions and their fallbacks.
• Registration covers strings, metadata, and shortcode attributes.
• Public hooks lists supported filters and actions with arguments.
• Machine translation boundary explains the supported extension points and the limits of custom provider integrations.

Compatibility rules

Check function_exists() before calling an optional helper, preserve source text and placeholders, escape only at final output, and restore any temporary locale in a finally block. Treat public filters and helpers as the supported extension surface; public PHP method visibility alone does not make an internal class a compatibility API.

Test base and target locales while logged out, plus relevant REST, AJAX, cron, email, multisite, and cache paths. A translated browser page is not sufficient proof that a background or API integration preserves language context.