Editorial Commerce Pattern

This pattern treats commerce as editorial: the story around a product carries as much weight as the transaction. It is designed for brands that sell in both Arabic and English and refuse to let the Arabic experience feel like a translation.

Most commerce templates bolt Arabic on as a mirrored afterthought, breaking typography and reading order. And aggressive personalization often erodes trust. The challenge is a bilingual store that reads beautifully in both directions and personalizes without feeling invasive.

• Arabic is art-directed independently — layout, type, and reading order are designed, not mirrored.
• Product storytelling and merchandising share one content model across both languages.
• Checkout boundaries are explicit so payment concerns never leak into the browsing experience.
• Personalization is opt-in and legible, never silent behavioral tracking.

• Bilingual, RTL-first storefront composition
• Editorial product storytelling and merchandising
• Cart and checkout boundary with a payment provider
• Opt-in, transparent personalization
• Content model shared across languages

• Next.js
• TypeScript
• Commerce APIs
• RTL

A shared content model keeps both languages in parity. RTL is handled through native CSS logical properties rather than per-component overrides.

This is a capability pattern demonstrating a bilingual commerce approach. It is not a named client store, and no sales or conversion figures are claimed.

• An Arabic experience that feels designed, not translated
• Product stories that build trust before the transaction
• Personalization customers can see and control