Skip to main content
Studio implements RTL direction support. It derives direction from the selected locale through HeroUI’s isRTL, sets lang and dir on its own interface/portal root, and provides the locale to HeroUI’s I18nProvider. It does not require changing the direction of the entire host application.

Mount an Arabic instance

The example supplies a partial Arabic dictionary. The layout’s direction is RTL, but missing labels remain English. Register a full catalog using custom translations for a localized interface. Hebrew and other RTL locales use the same locale-driven mechanism. StudioOptions does not currently expose a separate direction override.

Direction-aware behavior in the implementation

Host components and mixed content

The host owns Filament/FLEX Fields direction outside the Studio root. Configure the host’s locale/direction independently. Third-party preview engines, chart axes, code blocks and text inside the uploaded file can have their own direction. Selecting Arabic does not mirror image pixels or rewrite a PDF. Filenames, email addresses, IDs and URLs often mix scripts. In host-authored UI, isolate them with semantic bidi elements rather than inserting invisible control characters into stored names:

Support boundary and review

RTL direction support and a complete RTL-language translation are different. EN/PL are the shipped dictionaries. Catalog-backed localization has known surface limitations. The current implementation is not a certification of every editor/codec/provider surface for Arabic or Hebrew. When shipping a custom RTL locale, review search/popovers, deep folder navigation, selection and preview actions, focus order, keyboard arrows, dialogs, captions, numeric inputs and embedded host fields in both themes and at mobile width. Keep your own translated labels in that review; unusually long translations can expose layout issues that English does not.