Method

Depth first, route promises later.

Dordogne.app begins with cultural and source-bounded context. The product should not imply finished route planning until stay-base, car-led sequencing, cave access, market rhythm, and river-day logic are written and tested.

Rules

  • Do not duplicate Loire Valley chateau-and-river positioning.
  • Use official sources for current facts.
  • Keep wider distribution behind source, route, and product-readiness checks.

What Dordogne owns

Caves, prehistoric memory, Sarlat, Périgueux, Vézère, Dordogne river days, bastides, stone villages, truffle, walnut, Bergerac wine, and car-led stay-base realism.

What stays out for now

Live schedules, ticket availability, exact public transport claims, and indexable itinerary promises before the route-planning layer is complete.

Next build standard

The next wave should add practical pages for bases, first itinerary, without-a-car limits, caves/castles, markets/food, and Dordogne versus Loire Valley comparisons.