Understand the POM Translate integration model
POM Translate keeps one WordPress object and stores extracted source strings, translations, localized slugs, and content skeletons separately. Integrations should participate at the supported extraction, context, rendering, and invalidation boundaries.
Lifecycle
- Eligible content is saved.
- The parser extracts source values and structural placeholders.
- Editors or machine translation provide locale-specific values.
- POM Translate resolves the request language.
- Read-time filters rebuild the object for that locale.
- Missing translations fall back to source values.
Frontend rendering should not create translation jobs or persist new source rows.
Guides
- Save-time extraction
- Read-time translation
- Language context
- REST and AJAX
- Background processes
- Email generation
- Structured content
- Builder content
- Cache invalidation
- Compatibility contract
- Do and do not
Use a helper when a direct multilingual value is needed. Use a filter when extending a supported decision or output. Register source material early enough for extraction; do not reverse-engineer storage rows.