Designing the HackerU Site So i18n Wasn't a Rewrite

Most internationalization pain isn't linguistic — it's structural, and it lands on engineering. I design with that in mind even when the brief is single-market. HackerU's site is Hebrew-first, which means right-to-left is the native reading direction, not an afterthought bolted on later. For a CTO, the relevant point is what that forces upstream in the design system: directional layouts, mirrored navigation, and components that flip cleanly rather than breaking when content direction changes. When I build the modular system, I treat spacing, alignment, and iconography as direction-aware tokens instead of hard-coded left/right values. That discipline matters because the course page carries dense, structured content — syllabus blocks, the salary table, study-hours and format details — and dense layouts are exactly where RTL or future localization quietly fractures. Designing those modules to handle variable text length and mirrored flow means the cost of adding a locale later is configuration, not reconstruction. The principle I'd hand to any R&D leader: i18n readiness is mostly a design-system decision made early. If your components assume direction and string length, internationalization stops being a migration and becomes a setting.