WPML and Polylang
Highend ships WPML configuration out of the box and a WPML-specific language switcher; Polylang works at a basic level only.
Highend has first-class support for WPML and only basic, untailored compatibility with Polylang. If you're choosing between the two for a Highend site, that's worth knowing up front.
This page is about translating your content (pages, posts, custom post types, and Highend Options strings) with a multilingual plugin. To translate the theme's own interface strings (labels, buttons) into a new language, see Translate the theme instead.
WPML
Highend ships a wpml-config.xml file, which WPML reads automatically once it's active, so there's nothing to configure by hand.
- Translatable content types: Team, Clients, FAQ, Pricing Tables, Testimonials, Portfolio, and Gallery are all registered as translatable, along with their category taxonomies.
- Copied, not translated: the custom-field groups that drive gallery images, pricing settings, contact page settings, blog and portfolio layout settings, and portfolio slider images are set to copy across translations rather than being translated field-by-field, since they're layout data, not text.
- Theme option strings: around two dozen short Highend Options strings (footer text, the quick-contact box copy, location info blocks, 404 page text, and a few others) are registered as admin texts, so WPML's String Translation module picks them up automatically for per-language values under WPMLString Translation. Most Highend Options fields (layout, color, and other non-text settings) aren't part of this list, since they're not the kind of thing you'd translate per language.
Language switcher
Turning on Right Widget: WPML Languages in HighendHighend OptionsLayout SettingsHeader Layout adds a flag-and-language dropdown to the header's top bar. It's built directly from WPML's own language list (icl_get_languages()), so it only appears once WPML is active.
Polylang
Highend has no Polylang-specific integration: no wpml-config.xml-equivalent configuration, and no built-in language switcher for it. Polylang still works at the ordinary WordPress level (its own translatable post type and taxonomy settings apply regardless of theme), but you'll need to configure translatable content types yourself, and add Polylang's own language-switcher widget or menu item rather than relying on Highend's header toggle above.