i18n Starts in the Layout, Not the String Table

For R&D leaders, i18n often gets framed as a string-extraction task. Designing for an Israeli insurer reframed it for me: the hardest part of internationalization is structural, and it shows up long before you swap a single word. Menora's interfaces are Hebrew-first, which means right-to-left as the default reading direction — and RTL is not a mirror trick you apply at the end. In dense, field-heavy flows like the agent zone, mirroring touches everything: where labels sit relative to inputs, how multi-axis filters read, how tabular data aligns, which way affordances point. If layout decisions assume left-to-right, you inherit a backlog of directional bugs that no translation layer fixes. My recommendation to engineering leaders is to treat direction and layout neutrality as a first-class concern in the component system, the same way you'd treat date or number formatting. Bake bidirectional behavior into the primitives, not the patches. When the underlying components respect direction natively, adding or maintaining a locale becomes configuration rather than rework. The teams that internationalize cheaply are the ones who designed the skeleton to flex from the start.