A bilingual platform bridging two business cultures

Starting point

Bridge platforms have a hard job: each audience expects the site to feel local. If you build one site and machine-translate the other, both sides know — and both sides leave.

Translation is the obvious trap — and the boring one. The harder problem is editorial: each market expects a different voice, a different sense of authority, a different relationship between writer and reader.

Decisions

1. Two language tracks, hand-written. Not duplicates — each version edited for its audience.
2. Editorial sections for trade, culture, and business news, with a clear separation between voice and reporting.
3. Calm typographic system that works across Latin and the secondary script without looking dressed up.
4. Performance non-negotiable — both audiences sit on networks where every second of load time costs readers.

Execution

A CMS the editorial team can run themselves, with bilingual fields modelled into every content type. Performance kept tight enough that the site loads quickly on weak networks.

The result reads as native to each audience, not as a mirror of the other. That's the only honest measure of success for a bridge platform.

“Bridge platforms only earn trust when both audiences feel the site was made for them, not translated to them.”
— Elvin Sharifov

Result

• One platform, two audiences, neither treated as a translation of the other.
• Editorial team can publish in both languages without us in the loop.
• The site reads as authoritative on both ends — that was the whole point.
• Performance budget met on both audiences' typical networks — the site doesn't penalise either side.