Five languages as standard on every build
English, Arabic, German, Turkish and French — with right-to-left handled properly rather than mirrored as an afterthought.
Every site we deliver now ships multilingual by default, in five languages, with the language layer built in from the first commit rather than retrofitted when a client asks.
Why it is not an add-on
Retrofitting translation into a finished site is expensive and it shows. Layouts break at the point where German compounds run long, right-to-left text is mirrored crudely, and the URLs end up as query strings that search engines treat as one page in the wrong language.
Building it in from the start costs almost nothing and avoids all three. Each language gets a real URL, a correct hreflang set and its own metadata, so a page can be found in the language it is written in.
Arabic is not a mirrored layout
Right-to-left is where shortcuts show up fastest. Direction is only part of it: type needs a face designed for the script, letter spacing that works for Latin display fonts is wrong for Arabic, and any icon that implies direction has to flip while a logo must not.
We treat it as a first-class layout rather than a CSS transform applied to a layout built for English.
What clients get
Content is edited per language in the dashboard, on the record itself, so nothing is stranded in a separate translation file. An untranslated field falls back rather than rendering blank, which means a page is never broken because one field was missed — and adding a sixth language later is configuration, not a rebuild.
