Paris first
City base, museums, arrival, and Disneyland pressure
Travelers whose first fixed decision is Paris lodging, museum tickets, arrival day, or Disneyland Paris.
Handoff: Paris GuideMethod
Route first, publish only where the hub adds value.
The hub should answer network-level decisions: Paris or Loire Valley, city plus region, Provence or Dordogne, and which standalone product owns the next step. It should not fill space with generic France copy.
Editorial contract
- Do not duplicate Paris Guide city-guide content.
- Do not launch as a thin country landing page.
- Keep planned domains behind product-readiness and source-boundary checks.
I
Decision-first writing
Every article idea must name the decision it resolves.
Loire first
Chateaux, bases, wine, cycling, and car-free reality
Travelers adding a slower region after Paris or building a France trip around chateaux and river towns.
Handoff: Loire ValleyVillage France
Dordogne-style villages, markets, caves, and river days
Travelers who want a car-led stay base and slower village rhythm rather than a city-and-chateau route.
Handoff: DordogneProvence base
Aix, markets, food, and Provence day-trip access
Travelers choosing a Provence city base before committing to villages, Marseille, coast, or lavender-season routes.
Handoff: Aix-en-ProvenceII
Editorial boundaries
The country hub edits by ownership, not by appetite.
The hub should not rewrite Paris Guide. It should make clear when Paris is the whole trip, when it is an arrival base, and when the traveler should leave the city-guide layer for a regional product.
The editorial question is whether the traveler wants a slower river-region rhythm, a base outside Paris, and realistic transport tradeoffs before they choose specific chateaux, towns, or wine days.
Dordogne should avoid postcard inventory and keep explaining villages, markets, caves, river days, and driving shape as one coherent trip decision.
Aix-en-Provence should help choose a city base, market rhythm, food focus, and day-trip reach before it claims wider Provence coverage.
- 4 boundaries
III
Brief standard
A France node does not publish until its brief is specific.
Live
Paris Guide
- Reader question
- Is Paris the whole trip, the arrival base, or the first handoff?
- Editorial job
- Frame Paris as a decision point inside the France network: arrival pressure, city-base depth, museum planning, Disneyland demand, and the moment a traveler should move from Paris Guide into a regional product.
- Must include
- Clear distinction between Paris-only planning, Paris-plus-region planning, and Paris as a gateway into Loire, Dordogne, Provence, or later France nodes.
- Must avoid
- Rewriting Paris Guide, creating duplicate museum pages, or treating Paris as mandatory context for every France traveler.
- Handoff
- Send city-level decisions to Paris Guide; keep only routing, sequencing, and network-fit decisions on Premier France.
Live
Loire Valley
- Reader question
- Do I want a slower chateaux-and-river region after Paris?
- Editorial job
- Explain Loire as a pace and base decision before destination detail: chateaux density, towns, wine days, cycling appeal, rail limits, and when a car changes the shape of the trip.
- Must include
- A plain comparison between using Paris as an anchor, sleeping in the Loire, and choosing a compact route that does not overpromise car-free reach.
- Must avoid
- Publishing a decorative chateaux list without transport reality, stay-base logic, or a clear reason to choose Loire over another region.
- Handoff
- Send itinerary, base, chateaux, village, wine, and transport depth to the Loire Valley product.
Live
Dordogne
- Reader question
- Am I choosing village France, and am I ready for a car-led trip?
- Editorial job
- Route Dordogne as a focused regional product for travelers who need villages, markets, caves, river days, meal rhythm, and driving shape framed as one practical stay-base decision.
- Must include
- A car-led assumption, slower village cadence, stay-base tradeoffs, and explicit boundaries around what still needs official-source verification.
- Must avoid
- Using Dordogne as a vague countryside mood board, publishing village inventory before base logic, or implying live guide coverage before the product exists.
- Handoff
- Send villages, routes, stays, and source-backed local planning to Dordogne while Premier France keeps only the comparison frame.
Live
Aix-en-Provence
- Reader question
- Is Aix the right Provence base before I widen the trip?
- Editorial job
- Use Aix-en-Provence to clarify base fit: city rhythm, markets and food, access to nearby Provence days, and the point where Marseille, coast, villages, or seasonal routes need separate ownership.
- Must include
- A sober base-choice frame that separates Aix city stay, Provence day-trip access, and wider-region ambition.
- Must avoid
- Romance-first Provence copy, lavender shorthand, or broad Provence claims before Aix has a real product surface.
- Handoff
- Send base guidance, day-trip logic, and Provence boundaries to Aix-en-Provence while Premier France keeps the country-level choice.
IV
Quality gates
A planned France node is allowed to remain planned.
Substance before wider distribution
A France surface stays narrow or planned until it has enough original routing value, canonical ownership, and operational checks to justify broader discovery.
One owner per decision
Premier France routes country-level choices. Paris Guide, Loire Valley, Dordogne, and Aix-en-Provence own their destination depth when those products are live.
No duplicate guide pages
The hub may compare, sequence, and hand off. It should not become a thin duplicate of city guides, regional guides, or generic France travel articles.
Machine-visible posture
Every launch claim must match schema, robots, sitemap, registry, LLM notes, and the visible publication status shown to readers.
V
Machine contract
The method has to survive outside the page.
The same routing model feeds the page, structured data, sitemap, registry file, `llms.txt`, and rollout checks. If one layer changes, the others must keep the same publication posture.
Wider distribution waits until canonical routing, content substance, source boundaries, and deployment checks all agree.