Integrate builder content

Builder integrations must preserve the builder's serialized structure while exposing only public text. POM Translate already supports HTML and shortcode-oriented extraction; a custom builder should extend those public parser seams rather than copying its complete payload into a registered string.

Use pom_translate_parser_translatable_shortcode_attributes for known textual shortcode attributes. Use pom_translate_parser_should_extract_shortcode_attribute when extraction depends on the tag, attribute, or value. The pom_translate_parser_shortcode_attribute_seen action can observe encountered attributes for a maintained adapter.

For HTML-like builder output, extend the container, inline, translatable-attribute, or skip-tag filters. Keep layout settings, IDs, responsive values, classes, animation configuration, and query definitions untouched.

If a builder stores JSON or serialized metadata, register only supported metadata keys and implement schema-aware extraction. POM Translate does not guarantee that arbitrary proprietary builder payloads can be translated generically.

Save a representative layout after enabling the integration, then verify headings, buttons, links, nested modules, reusable blocks, and responsive output in each locale. Change the layout order and confirm translated strings remain attached to the intended elements.