When we set out to build navetteforyou.com — a private car transfer booking site for Marrakech — we had an unusual constraint: the site needed to work in 8 languages, load instantly on Moroccan mobile networks, and cost almost nothing to host.

The CMS Trap

The obvious move was WordPress or Strapi. Multilingual plugins exist. Templates exist. You can be live in a week.

But we had watched competitors do exactly this, and the result was always the same: bloated pages, 3+ second load times on 3G, broken hreflang tags, and translation plugins that generated URLs like /fr/?lang=fr instead of clean /fr/transfers/marrakech-to-essaouira.

For a site where 60% of visitors come from Google on a mobile device, often on a hotel Wi-Fi or a prepaid SIM, page speed is not a nice-to-have. It is the product.

What We Built Instead

The stack:

  • TanStack Router with static site generation (SSG)
  • TypeScript end to end, including all content
  • Content as code — every route, guide, FAQ, and translation lives in typed .ts files, not a database
  • Vite for builds, with aggressive code splitting per locale
  • Vercel for hosting and edge delivery

Every page is pre-rendered at build time. There is no server. There is no database query on page load. The HTML arrives complete, with all structured data (JSON-LD) baked in.

Content as Code

This is the part that surprises people. All 8 language versions of every page are generated from a single source of truth: TypeScript content files that look like this:

export const transfers = { "marrakech-to-essaouira": { from: "marrakech", to: "essaouira", distance: "175 km", duration: "2h30", } } 

Translation keys reference a dictionary per locale. The build generates /en/transfers/marrakech-to-essaouira, /fr/transferts/marrakech-vers-essaouira, /de/transfers/marrakesch-nach-essaouira, and so on — each with correct hreflang alternates, canonical URLs, and locale-specific structured data.

No translation plugin. No CMS API call. No runtime overhead.

The Results

  • Lighthouse Performance: 98–100 across all pages
  • First Contentful Paint: under 0.8s on a throttled 3G connection
  • 8 languages, 200+ pages — all statically generated
  • Zero hosting cost spikes — static files on a CDN do not scale with traffic
  • Perfect hreflang — because the build generates it, not a plugin

What We Lost

Honestly? Almost nothing. The tradeoff is that content changes require a code commit and a build. For a site with stable routes and infrequent copy changes, that is a feature, not a bug. Every content change goes through TypeScript type checking, which catches broken translation keys, missing locales, and malformed URLs before they reach production.

Would I Recommend This for Every Travel Site?

No. If your content changes hourly (a blog, a deals aggregator, a marketplace), you need a CMS. But for a service site with a fixed set of offerings in multiple languages — transfers, tours, activities — static generation with content-as-code is faster to build, faster to load, and far cheaper to run.

The site is navetteforyou.com — a Marrakech private transfer service operated by Serenity Morocco Tours. Built with TanStack Router, TypeScript, and Vite. Deployed on Vercel.