Hebrew-First, Built to Bend

Designing an internal hub for a leading Israeli law firm means Hebrew is the native experience, not a translation target — which puts i18n concerns front and center for anyone thinking about the build. The most consequential decision is bidirectionality: a community hub that mixes warm social content with formal firm notices has to handle RTL layout as a first-class citizen, not a mirrored afterthought. Cards, feeds, iconography, and reading order all have to feel native, and English product and legal terms inevitably appear inline, so the layout must absorb mixed-direction text without breaking rhythm. For an engineering leader, my design intent translates into structural requirements: logical rather than physical layout properties, components that flip cleanly, and typography chosen to carry Hebrew with the same gravitas it gives Latin script. I designed the system so the visual language — the corporate-serious-yet-socially-warm balance — survives direction-flipping intact, because tone shouldn't degrade when text mirrors. I won't claim we shipped a dozen locales; the firm's real need was a Hebrew-first product that respects mixed-language reality. But building it that way means the foundation bends rather than breaks if scope ever grows. That's the i18n posture I'd defend to any CTO: localize the structure, not just the strings.