The Arabic web deserves first-class

Arabic is not a translation task: it is an engineering and authoring discipline that starts at the first sketch.

Something quietly strange happens on most bilingual websites. The Arabic version is a mirror of the English one: flipped, translated, and slightly broken. A search box that lands on the wrong side. Numbers that jump direction mid-sentence. Errors no native reader would forgive. The site works, technically. It just was not written for you.

We build in the other direction. On this very site, Arabic and English are two equal trees with independently authored copy, not a translated skin over an English source. The Arabic is not derived; it is written. Its sentences carry their own rhythm and their own way of arriving at the point, which is why nothing here reads like a translation.

The craft is unglamorous and cumulative. Logical CSS properties instead of left and right, so direction is a declaration rather than a refactor. Arabic-Indic numerals in Arabic copy, consistently, dates included. Layouts composed for right-to-left rather than mirrored into it. Typography that respects the script's joining rules. None of this shows up as a feature; all of it shows up as ease.

There is a strategic reading, too. As answer engines and assistants begin to cite their sources, the Arabic side of that index is remarkably thin: content that is authored, structured, and quotable is scarce relative to the readership it serves. The field is not empty because it is small; it is empty because it is hard. That gap is where a bilingual-first group compounds quietly.

This is why Arabic is a service line for us, not a courtesy. When we build a platform for a client, the Arabic experience is built, tested, and read aloud, not converted in the final week. The region's first language deserves the same engineering budget as everyone else's second.

Hold any site that claims bilingualism to the standard we invite for ours: switch the language and read. If the Arabic feels like a translation, it is one.

Related Practice: Web Platforms