The problem
Kuwait is well covered in English and badly served in Arabic. What exists is either a news wire rewritten, or a personal blog, or a listicle assembled by someone who has never been to the place they are ranking. Nobody was building a daily Arabic publication about ordinary life — what opened, what changed, what a ministry decision actually means for you this week — to a standard that holds up.
What it is
KWT.ONE is a daily Arabic publication about living in Kuwait, positioned between the present and the past: what is happening now, and the history underneath it. It runs ten categories, from what is on this weekend to a dated on-this-day almanac, and publishes on a fixed rhythm through the day rather than in bursts.
Why it was hard
- Arabic typography and right-to-left layout done properly, not a mirrored English theme. Custom theme, no page builder, one typeface family chosen for screen reading rather than for looking Arabic.
- Editorial volume without editorial collapse. A publication that ships several pieces a day needs the research standard written down and enforced, or it silently becomes a wire rewriter.
- Advertising had to live outside the theme entirely, so placements can be changed from the dashboard without a developer and without redeploying anything.
- Discovery had to be designed in from the first day: structured data, a sitemap that actually validates, and content shaped to be quotable by an assistant rather than only rankable by a crawler.
What it demonstrates
It is the whole argument of this practice in one artefact: the strategy, the theme, the publishing system, the ad platform and the newsletter are one design rather than five purchases stitched together. That is the same reasoning I bring to a client build — decide the structure once, and the things that are expensive to reverse stay cheap.
Where it is now
Live and publishing daily at kwt.one, with its own WhatsApp and Telegram channels and a newsletter on a dedicated sending domain.