<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: TRIPLE</title>
    <description>The latest articles on DEV Community by TRIPLE (@triplestore).</description>
    <link>https://dev.to/triplestore</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4248732%2Fe1370d24-3c77-43ea-addf-da4865804e1f.png</url>
      <title>DEV Community: TRIPLE</title>
      <link>https://dev.to/triplestore</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/triplestore"/>
    <language>en</language>
    <item>
      <title>How we built a bilingual (EN/AR) e-commerce store for an Egyptian streetwear brand</title>
      <dc:creator>TRIPLE</dc:creator>
      <pubDate>Tue, 17 Nov 2026 02:51:53 +0000</pubDate>
      <link>https://dev.to/triplestore/how-we-built-a-bilingual-enar-e-commerce-store-for-an-egyptian-streetwear-brand-1kj2</link>
      <guid>https://dev.to/triplestore/how-we-built-a-bilingual-enar-e-commerce-store-for-an-egyptian-streetwear-brand-1kj2</guid>
      <description>&lt;p&gt;If you sell clothes in Egypt, your shop is an Instagram page and your checkout is a DM. That's how TRIPLE, a men's streetwear brand I work with, was running: every order was a chat thread, every size question a voice note, and half the "orders" never showed up to pay.&lt;/p&gt;

&lt;p&gt;A few months ago we decided to fix that with a real store. The catch: it had to feel native in two languages at once. Egyptian shoppers browse and search in Arabic, the brand's lookbook culture is English, and neither audience should feel like an afterthought.&lt;/p&gt;

&lt;p&gt;This is what we shipped and what I learned building it. The store is live at &lt;a href="https://triplestore.vercel.app" rel="noopener noreferrer"&gt;triplestore.vercel.app&lt;/a&gt; if you want to click around while reading.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we shipped
&lt;/h2&gt;

&lt;p&gt;A full e-commerce store for a streetwear catalog: ~50 products across categories like sweatshirts, tees and jeans, a cart, cash-on-delivery ordering with a deposit step, an order-tracking page for customers, printable receipts, and an admin dashboard the brand runs themselves - products, prices, coupons, stock, size charts, even the SEO copy, all editable without touching code.&lt;/p&gt;

&lt;p&gt;And the part this post is about: every single page exists twice. English at &lt;code&gt;/&lt;/code&gt;, Arabic at &lt;code&gt;/ar&lt;/code&gt;. Not a translation plugin, not a language cookie that swaps strings - two real, linkable, indexable versions of the whole store.&lt;/p&gt;

&lt;h2&gt;
  
  
  The stack
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;TanStack Start (React, SSR)&lt;/strong&gt; - server-rendered pages, because a store that Google can't read doesn't exist, and most Egyptian buyers are on mid-range phones on mobile data.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Supabase (Postgres + storage)&lt;/strong&gt; - products, orders, inventory and images. Row-level security means the storefront reads through policies and the admin writes through policies; there's no separate API layer to secure twice.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Vercel&lt;/strong&gt; - hosting and previews.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Nothing exotic. The interesting decisions are in the bilingual and payments work, so let's go there.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fky7i28lqlo9oqrjy4h8q.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fky7i28lqlo9oqrjy4h8q.jpg" alt="TRIPLE store home page in English" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Two versions of every page, not a translation toggle
&lt;/h2&gt;

&lt;p&gt;The decision I'm happiest about: Arabic is not a string swap on the same URL. Every page exists at &lt;code&gt;/...&lt;/code&gt; in English and &lt;code&gt;/ar/...&lt;/code&gt; in Arabic, and both are first-class routes.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;/shop              -&amp;gt; English catalog
/ar/shop           -&amp;gt; Arabic catalog (RTL)
/product/essential-tee
/ar/product/essential-tee
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Three reasons. First, SEO: Google indexes Arabic search queries against Arabic pages. An Egyptian shopper types "هوديز رجالي" (men's hoodies), not "hoodies" - and a language cookie gives you nothing to index against that. Second, sharing: when the brand posts a product link in an Arabic caption, the link itself is Arabic. Third, honest rendering: &lt;code&gt;&amp;lt;html dir="rtl" lang="ar"&amp;gt;&lt;/code&gt; on the Arabic routes, which makes the browser do the right thing with text direction, punctuation and form fields instead of you fighting it in CSS.&lt;/p&gt;

&lt;p&gt;The sitemap carries both versions with proper alternates, 63 pages in each language:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight xml"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;url&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;loc&amp;gt;&lt;/span&gt;https://triplestore.vercel.app/shop&lt;span class="nt"&gt;&amp;lt;/loc&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;xhtml:link&lt;/span&gt; &lt;span class="na"&gt;rel&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"alternate"&lt;/span&gt; &lt;span class="na"&gt;hreflang&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"en"&lt;/span&gt;
              &lt;span class="na"&gt;href&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"https://triplestore.vercel.app/shop"&lt;/span&gt;&lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;xhtml:link&lt;/span&gt; &lt;span class="na"&gt;rel&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"alternate"&lt;/span&gt; &lt;span class="na"&gt;hreflang&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"ar"&lt;/span&gt;
              &lt;span class="na"&gt;href&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"https://triplestore.vercel.app/ar/shop"&lt;/span&gt;&lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;xhtml:link&lt;/span&gt; &lt;span class="na"&gt;rel&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"alternate"&lt;/span&gt; &lt;span class="na"&gt;hreflang&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"x-default"&lt;/span&gt;
              &lt;span class="na"&gt;href&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"https://triplestore.vercel.app/shop"&lt;/span&gt;&lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/url&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Each page also cross-links its twin with &lt;code&gt;&amp;lt;link rel="alternate" hreflang&amp;gt;&lt;/code&gt; in the head, and &lt;code&gt;canonical&lt;/code&gt; points at itself, never at the other language. The two versions are siblings, not copies.&lt;/p&gt;

&lt;h2&gt;
  
  
  RTL is a design task, not a CSS property
&lt;/h2&gt;

&lt;p&gt;Setting &lt;code&gt;dir="rtl"&lt;/code&gt; gets you 80% of the way. The remaining 20% is where bilingual sites usually look broken, and it's all manual:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Use logical properties everywhere.&lt;/strong&gt; &lt;code&gt;margin-inline-start&lt;/code&gt; instead of &lt;code&gt;margin-left&lt;/code&gt;, &lt;code&gt;inset-inline-end&lt;/code&gt; instead of &lt;code&gt;right&lt;/code&gt;. If the codebase does this from day one, most of the layout mirrors itself for free.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Directional icons must flip, semantic icons must not.&lt;/strong&gt; A back arrow points right in RTL. A WhatsApp glyph or a size chart does not. We ended up with a small &lt;code&gt;FlipInRtl&lt;/code&gt; wrapper component so the decision is explicit at every call site.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Numbers stay Western.&lt;/strong&gt; Egyptian shoppers read prices as &lt;code&gt;650 ج.م&lt;/code&gt; - Western digits, Arabic currency label, Arabic amount formatting around it. Full Arabic-Indic digits (٦٥٠) would look more "translated" and less familiar.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fonts carry the brand in both scripts.&lt;/strong&gt; The store uses Anton for Latin display type and Alexandria for Arabic copy. Arabic display fonts are a much smaller pool than Latin ones; pick early, because the whole visual identity shifts with that choice.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Test the forms, not just the hero.&lt;/strong&gt; A checkout form mixing an Arabic name, an Egyptian phone number and an English email address is where direction bugs actually hurt - placeholder alignment, input direction, validation messages.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The Arabic home page, fully RTL with mirrored navigation:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F99vxnouzhjlhybexk32t.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F99vxnouzhjlhybexk32t.jpg" alt="TRIPLE store home page in Arabic, full RTL layout" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Payments: build for how Egypt actually pays
&lt;/h2&gt;

&lt;p&gt;Card penetration is low and cash on delivery is the default expectation, but pure COD has a brutal failure mode: fake orders. Someone orders three hoodies to a made-up address, the courier rides out, nobody's home, and the brand eats the shipping both ways.&lt;/p&gt;

&lt;p&gt;So COD orders require a small deposit - 100 EGP by Vodafone Cash, the mobile wallet basically every Egyptian phone has. The checkout generates the order in an &lt;code&gt;awaiting deposit confirmation&lt;/code&gt; state, the buyer transfers 100 EGP and uploads a screenshot of the transfer, and the order only enters the fulfillment queue when the brand confirms the deposit from the dashboard. The deposit comes off the final price on delivery.&lt;/p&gt;

&lt;p&gt;A product page in Arabic - price in EGP, sizes, quantity, stock state:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1fwayouucajue02gdg5l.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1fwayouucajue02gdg5l.jpg" alt="Product page in Arabic: price in EGP, sizes, quantity" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Is it friction? Yes, deliberately. The bet is that a buyer who won't pay 100 EGP (~$2) up front was never picking up the package. The brand's answer so far: the fake-order problem simply stopped.&lt;/p&gt;

&lt;p&gt;Everything else about the order flow is built for the same reality: customers can check their order status on a public "my orders" page without an account (orders tie to phone numbers, not logins), receipts print cleanly for the courier bag, and the whole thing works on a mid-range Android over mobile data.&lt;/p&gt;

&lt;h2&gt;
  
  
  The unglamorous parts that mattered
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;SEO is generated, not written.&lt;/strong&gt; Product titles, descriptions, structured data and sitemap entries are generated from the product data, with the live price in the JSON-LD. When the brand edits a price in the dashboard, the SEO layer updates with it - nobody maintains 126 pages of meta by hand.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Inventory is strict.&lt;/strong&gt; Stock decrements per size, sold-out items stay visible and indexable marked as sold out rather than 404ing, and the admin warns (without blocking) when a product is missing a description, Arabic name, category or stock count.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The admin is the product.&lt;/strong&gt; The people running this store are not developers, so size charts, shipping fees per governorate, coupons and even the brand copy are dashboard settings. Anything hard-coded is a support message waiting to happen.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What I'd do differently
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Start RTL on day zero.&lt;/strong&gt; We built English-first and retrofitted. Logical properties and the icon wrapper would have been nearly free early; they were a week of diff later.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Translate the microcopy with the brand, not for it.&lt;/strong&gt; Egyptian Arabic has its own shopping vocabulary, and a literal translation of "checkout" or "sold out" reads wrong. The final pass was the brand's owner reading every string out loud.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Deposits are a product decision wearing a payments costume.&lt;/strong&gt; It changed who orders, not just how they pay.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The store is live at &lt;a href="https://triplestore.vercel.app" rel="noopener noreferrer"&gt;triplestore.vercel.app&lt;/a&gt; (try &lt;code&gt;/ar&lt;/code&gt; for the Arabic version). Happy to answer questions about the bilingual setup, the deposit flow, or TanStack Start + Supabase for e-commerce in the comments.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>react</category>
      <category>typescript</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
