Documentation Category
Multilingual Sites
Configure language providers, translated content, menus and booking routes without losing the active guest language.
Articles
Understand locale and language-navigation providers
Core separates locale resolution from navigation. Resolving the locale for an email, admin request or booking does not by itself provide a list of…
Configure a multilingual provider for Hotel Booking
Core provides compatibility adapters for WPML and Polylang and a native WordPress fallback. Themes consume Core's normalized language contract; they should not call vendor…
Translate interface strings and hotel content separately
Translation files, multilingual Page/menu configuration and supported hotel-entity translations solve different problems. Installing a .mo file does not translate room descriptions or create another…
Assign menus and custom links for each language
Aurelia renders the menu selected by WordPress and the multilingual provider. Translating a Page or enabling the language switcher does not automatically translate every…
Preserve language across booking routes
Core owns localized booking destinations and the validated hb_language context. A theme should use supplied URLs/forms rather than guessing a route from the current…
Understand booking, email and invoice languages
The current visitor language, a saved booking language and the WordPress administrator's language are different contexts. Changing today's site language does not translate every…
Consume the public language-navigation API
Current Core exposes language navigation through kimorapro_hb()->languages(). The small public facade returns normalized language data and safe switch URLs; the theme owns placement, labels,…
