Douro Valley
Choose the Douro for landscape-led days and deliberate movement.
Travelers prioritizing river scenery, wine-country pacing, viewpoint logistics, and a multi-night inland base.
Editorial method
Decision first. Source current facts. Keep scope visible.
The hub exists only where country-level comparison adds value. Detailed local planning belongs to the relevant product.
Editorial rules
- Three owned products only.
- Time-sensitive claims cite an official source with a check date.
- No live conditions inferred from evergreen copy.
I
Decision-led writing
Every surface names the choice it resolves.
Ericeira
Choose Ericeira for a lived-in coastal base with Lisbon in reach.
Travelers who want ocean rhythm, a compact town, surf culture, and flexible access to the capital region.
Benagil
Choose Benagil when a specific Algarve coast experience shapes the route.
Travelers planning around coastal conditions, access windows, boat or paddle choices, and nearby Algarve bases.
II
Product briefs
The handoff boundary is part of the content.
Product
Douro Valley
- Reader question
- Does an inland river journey fit the time and transport available?
- Editorial job
- Explain the Douro as a choice about pace, transfers, viewpoints, river movement, and multi-night bases before presenting deeper local detail.
- Must include
- Travel-time realism, base logic, seasonal variables, and a clear handoff to the dedicated product.
- Must avoid
- Comprehensive-country language, guaranteed transport claims, and decorative lists that ignore how the valley is actually reached.
- Handoff
- Premier Portugal owns the comparison; Douro Valley owns future local itineraries, operator checks, and base-level detail.
Product
Ericeira
- Reader question
- Is an Atlantic town base the right everyday shape for this trip?
- Editorial job
- Clarify compact-town rhythm, Lisbon-region access, ocean conditions, car-light potential, and who benefits from staying rather than day-tripping.
- Must include
- Town-base trade-offs, realistic access framing, seasonal rhythm, and a clear handoff to the dedicated product.
- Must avoid
- Reducing the destination to surf, promising universal car-free ease, or presenting the hub as a complete local guide.
- Handoff
- Premier Portugal owns the comparison; Ericeira owns future neighborhood, activity, access, and stay-level detail.
Product
Benagil
- Reader question
- Should one sensitive coastal experience determine the Algarve route?
- Editorial job
- Frame Benagil through conditions, permitted access, mobility, nearby bases, and alternatives so the route remains useful if plans change.
- Must include
- Current-source checks, access constraints, weather sensitivity, and a clear handoff to the dedicated product.
- Must avoid
- Guaranteed cave entry, unsafe operational advice, or broad Algarve coverage that the product does not yet provide.
- Handoff
- Premier Portugal owns the comparison; Benagil owns future condition-aware access, nearby-base, and local coast detail.
III
Source hierarchy
Volatile facts remain attached to current primary sources.
Orient.
Use stable geography and route logic to frame the decision.
Verify.
Check transport, maritime, access, safety, and operating facts at the point of publication.
Date and bound.
Show review dates and state what the copy cannot guarantee.
IV
Release gates
Technical readiness does not equal editorial launch.
Sources before claims
Time-sensitive access, transport, and safety claims cite an official or first-party source and carry a check date.
Only owned scope
Country-level framing must state that the current network contains three owned products and is not a directory of all Portugal destinations.
One layer per decision
The hub compares route shapes; each destination product owns its deeper local planning work without duplicate filler.
Consistent reader promise
Visible labels, machine documents, metadata, and network status must all describe the same owned, three-product scope.