# Ardennes

Indexable Belgian Ardennes short-break planner for source-backed route decisions.

## Core routes
- [Ardennes Short Break Planner](https://ardennes.app/): A decision-led start page for matching river valleys, castle towns, forest bases, rail access, memory layers, and one-night trip shape.
- [Brussels to the Ardennes](https://ardennes.app/brussels-to-ardennes/): A conservative arrival guide for readers deciding between a Brussels rail day, a car-based weekend, and a simpler city break.
- [One-Night Ardennes Itinerary](https://ardennes.app/one-night-itinerary/): A practical sequencing page for arrival, base choice, one anchor visit, dinner rhythm, and a calm second morning.
- [Where to Stay in the Belgian Ardennes](https://ardennes.app/where-to-stay/): A stay-base decision guide for river towns, castle villages, memory bases, forest bases, rail-friendly edges, and deeper Ardennes weekends.
- [Ardennes Train and Car Logistics](https://ardennes.app/train-car-logistics/): A logistics guide for checking train feasibility, deciding when a car matters, and keeping base transfers realistic.
- [Villages, Castles, Rivers, and Memory](https://ardennes.app/villages-castles-hikes-rivers/): A nature, heritage, food, and memory decision guide for avoiding overloaded routes and choosing one strong Ardennes lane.

## Narrative pillars
- Forest: The Ardennes should feel wooded, wet, and old rather than alpine: Arduenna Silva, Hautes Fagnes, fog, beech, spruce, winter, and slower movement.
- Rivers: The Semois, Ourthe, Lesse, Meuse, Ambleve, and Our shape the real trip logic through valleys, bends, caves, canoe routes, towns, and borders.
- Castles: Bouillon, La Roche-en-Ardenne, Dinant, Vianden, Sedan, and smaller fortress towns explain the Ardennes as a frontier landscape.
- Memory: Bastogne, the Battle of the Bulge, and wider wartime memory need sober context, not adventure branding or casual attraction-list language.
- Food: Jambon d'Ardenne, trout, game, mushrooms, cheeses, abbey and local beers, and winter cooking should support place identity.

## Editorial judgements
- Start with the constraint, not the postcard (https://ardennes.app/): The Ardennes only works as a recommendation after the page knows the reader's time, arrival mode, tolerance for moving after dinner, and appetite for forest, river, castle, memory, or food.
- The return journey decides the day trip (https://ardennes.app/brussels-to-ardennes/): From Brussels, rail-led plans should stay focused and close to a realistic station arrival; deeper bases need overnight margin or a car.
- One night needs one anchor (https://ardennes.app/one-night-itinerary/): A good overnight should choose the base first, protect the evening, and use the second morning for one castle, river, cave, hike, or village pair.
- The stay base is the product (https://ardennes.app/where-to-stay/): Where to stay decides the valley, evening, and second morning; hotel lists should come after the base type is clear.
- Transport honesty beats optimism (https://ardennes.app/train-car-logistics/): Train-first planning is for focused routes; car-first planning is for valley patterns, village pairs, viewpoints, and deeper nature bases.
- Let one texture lead (https://ardennes.app/villages-castles-hikes-rivers/): The strongest Ardennes page chooses a primary texture - village, castle, river, cave, hike, memory, or food - and uses the rest as support.

## Editorial depth
- The region promise is calm, not coverage (https://ardennes.app/): The Ardennes start page should decide whether the reader wants one slower Belgian geography of forest, rivers, castles, food, and memory, not prove that every valley can fit into one break.
- Arrival margin decides the Brussels route (https://ardennes.app/brussels-to-ardennes/): The Brussels-to-Ardennes page should begin with return margin because transport pressure decides whether the plan is a day, overnight, or no.
- The overnight is a sequence, not a haul (https://ardennes.app/one-night-itinerary/): The one-night itinerary should protect the evening and second morning because those are the parts that make the trip feel different from a long day.
- The base is the editorial choice (https://ardennes.app/where-to-stay/): Where-to-stay content should make the base perform a job before any hotel-style recommendation appears.
- Logistics are the editorial filter (https://ardennes.app/train-car-logistics/): The train and car page should treat transport as a content decision, not a practical footnote after the route has already been sold.
- Texture selection gives the trip identity (https://ardennes.app/villages-castles-hikes-rivers/): Villages, castles, hikes, rivers, caves, food, and memory should be treated as competing trip identities, not mandatory checklist categories.

## Machine surfaces
- https://ardennes.app/discoverability.json
- https://ardennes.app/schema.json
- https://ardennes.app/network-registry.json