When you run a transfer service that publishes fixed prices across 633 static pages in 8 languages, pricing changes are not a database update β they are a build.
The Problem
Our site navetteforyou.com serves Marrakech airport transfers and day trips. Every route has a price in MAD (Moroccan Dirhams) that appears on multiple pages across 8 language variants. Change one price, and it propagates to dozens of pages.
We needed:
A single source of truth for all prices
Automatic propagation to every language/page combo
A validation gate that catches any price anomaly before deploy
No price under our 600 MAD floor appearing anywhere
The Architecture
// src/content/pricing.ts β single source of truth export const ROUTES = { 'marrakech-airport' : { mad : 300 , category : 'airport' } , 'marrakech-essaouira' : { mad : 1800 , category : 'day-trip' } , 'marrakech-fes' : { mad : 3500 , category : 'intercity' } , // ...β¦