Four locales, one shared page system
Language changes routes, metadata, reading direction, and the space each interface label needs. Those constraints belong in the architecture from the start.
Translating strings is only one part of a multilingual site. Each language also affects page addresses, canonical and hreflang metadata, text direction, and the length of labels inside shared components. Leaving those decisions until after launch spreads fixes across routes and templates.
This site serves en, ru, ar, and zh-cn through shared route and content structures. Locale-aware metadata builds canonical URLs and language alternatives from the same source. The document receives the appropriate language and direction, while typed content keeps every page on a common component model.
Architecture does not replace editorial review. Each locale still needs copy written for its readers and checks for long labels, language switching, and right-to-left layout. It gives that work a stable foundation instead of turning every new language into a separate rebuild.