<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[NavetteForYou]]></title><description><![CDATA[Private airport transfers and day trips across Morocco. Operated by Serenity Morocco Tours. We write about travel logistics, Marrakech navigation, and building ]]></description><link>https://navetteforyou.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 14:57:21 GMT</lastBuildDate><atom:link href="https://navetteforyou.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Building a Multi-Language Static Booking Site: Our Tech Stack for Marrakech Transport]]></title><description><![CDATA[When we set out to build navetteforyou.com — a booking platform for private car transfers in Marrakech — we faced a challenge that most tutorials don't…]]></description><link>https://navetteforyou.hashnode.dev/building-a-multi-language-static-booking-site-our-tech-stack-for-marrakech-transport</link><guid isPermaLink="true">https://navetteforyou.hashnode.dev/building-a-multi-language-static-booking-site-our-tech-stack-for-marrakech-transport</guid><category><![CDATA[webdev]]></category><category><![CDATA[JavaScript]]></category><category><![CDATA[React]]></category><category><![CDATA[SEO]]></category><dc:creator><![CDATA[NavetteForYou]]></dc:creator><pubDate>Mon, 16 Nov 2026 18:42:37 GMT</pubDate><content:encoded><![CDATA[<p>When we set out to build <a href="https://www.navetteforyou.com">navetteforyou.com</a> — a booking platform for private car transfers in Marrakech — we faced a challenge that most tutorials don't cover: building a production-grade static site that works across 8 languages, generates hundreds of pages from a price engine, and loads in under a second on a 3G connection in rural Morocco.</p>
<p>Here's the technical breakdown of what we built and why we made the choices we did.</p>
<h2>The Problem: 8 Languages, 633 Pages, Zero CMS</h2>
<p>Our target audience includes travelers from across Europe, North Africa, and the Americas. That meant supporting English, French, German, Spanish, Portuguese, Italian, Dutch, and Arabic — with RTL layout support.</p>
<p>A traditional CMS would mean managing translations through a dashboard, dealing with API latency, and accepting slower page loads. We wanted something that felt instant, worked offline-first, and gave us full control over SEO and Schema.org structured data.</p>
<h2>TanStack Router: File-Based Routing Across Languages</h2>
<p>We chose <a href="https://tanstack.com/router">TanStack Router</a> for its file-based routing that maps cleanly to our language structure. Each language gets its own route tree:</p>
<pre><code>/en/marrakech-airport-transfer
/fr/transfert-aeroport-marrakech
/de/flughafentransfer-marrakesch
/ar/نقل-مطار-مراكش
</code></pre>
<p>Each route is a fully localized page with translated content, localized meta tags, and hreflang annotations. TanStack Router's type-safe approach catches broken links at build time — not in production.</p>
<h2>React 19 with Static Site Generation</h2>
<p>React 19's server components let us pre-render every page at build time. No runtime JavaScript needed for the initial paint. The result: a static HTML file for each of our 633 pages, served directly from a CDN.</p>
<p>The pages include:</p>
<ul>
<li>Airport transfers (Marrakech Menara to city)</li>
<li>In-town rides (Medina, Gueliz, Hivernage)</li>
<li>Day trips (Essaouira, Ourika Valley, Ouzoud Falls, Imlil)</li>
<li>Multi-city transfers (Casablanca, Fez, Ouarzazate)</li>
</ul>
<p>Each page is generated with localized content, correct pricing tier, and full Schema.org markup.</p>
<h2>The Price Engine: Static Pages with Dynamic Pricing Logic</h2>
<p>Our price engine generates every route-language-currency combination at build time. For pricing, we use a "get a quote" model — visitors tap a WhatsApp deep link to <a href="https://wa.me/212701664704">request their personalized quote</a> based on their specific needs: vehicle type, number of passengers, luggage, time of day, and whether they need a return trip.</p>
<p>This approach means:</p>
<ul>
<li>No stale prices cached in a CMS</li>
<li>No API calls at runtime</li>
<li>Every page has the right CTA for that specific route</li>
</ul>
<h2>Entity Graph: Schema.org JSON-LD That Actually Works</h2>
<p>One thing we invested heavily in was our entity graph — a connected web of Schema.org JSON-LD that links our Organization, Service, and Offer entities into a coherent knowledge structure.</p>
<pre><code class="language-json">{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "Marrakech Airport Transfer",
  "provider": {
    "@type": "Organization",
    "name": "Serenity Morocco Tours",
    "url": "https://www.navetteforyou.com"
  },
  "areaServed": {
    "@type": "City",
    "name": "Marrakech"
  }
}
</code></pre>
<p>Each page carries its own JSON-LD block, and the entities reference each other through <code>@id</code> URIs. This isn't just SEO theater — it helps Google, Bing, and AI assistants like ChatGPT and Perplexity understand the relationships between our services, locations, and business entity.</p>
<h2>Core Web Vitals: Sub-1s Loads</h2>
<p>Static generation gives us a head start, but we pushed further:</p>
<ul>
<li><strong>LCP under 800ms</strong>: No hero images above the fold. Text-first design with system fonts.</li>
<li><strong>CLS of 0</strong>: All layout dimensions are known at build time. No content shifts.</li>
<li><strong>INP under 50ms</strong>: Minimal client-side JavaScript. WhatsApp deep links are plain <code>&lt;a&gt;</code> tags — no JavaScript click handlers.</li>
</ul>
<p>The result: every page scores 95+ on PageSpeed Insights, on both mobile and desktop.</p>
<h2>WhatsApp Deep Links: The Conversion Layer</h2>
<p>In Morocco, WhatsApp is the primary business communication channel. Instead of building a complex booking form with payment integration, we use WhatsApp deep links that pre-fill the message with the route details:</p>
<pre><code>https://wa.me/212701664704?text=Hello,%20I%20need%20a%20transfer%20from%20Marrakech%20Airport
</code></pre>
<p>The visitor taps one button, WhatsApp opens with the message ready, and the conversation begins. No forms, no accounts, no friction.</p>
<h2>What We Learned</h2>
<ol>
<li><p><strong>Static generation scales languages better than a CMS.</strong> Each language is just another build target. No translation API, no runtime overhead.</p>
</li>
<li><p><strong>Schema.org entity graphs compound over time.</strong> As search engines and AI assistants crawl our structured data, the connections between entities build authority that a flat page can't match.</p>
</li>
<li><p><strong>WhatsApp deep links outperform contact forms</strong> in markets where WhatsApp is the dominant communication channel. The conversion path is shorter and feels more natural to the user.</p>
</li>
<li><p><strong>Core Web Vitals are easier when you start static.</strong> Most performance problems come from runtime JavaScript and third-party scripts. Remove those, and you're already in the green.</p>
</li>
</ol>
<h2>Try It</h2>
<p>Visit <a href="https://www.navetteforyou.com">navetteforyou.com</a> to see the site in action. Need a transfer in Marrakech? <a href="https://wa.me/212701664704">Get a quote on WhatsApp</a>.</p>
<hr />
<p><em>NavetteForYou is operated by Serenity Morocco Tours — private transfers across Morocco.</em></p>
]]></content:encoded></item></channel></rss>