EDITORIAL STANDARDS

Sources & editorial methodology

The platform separates verified information from editorial interpretation.

01

Editorial Riviera regions

The twelve Riviera chapters are journey-planning regions created to make the coast legible. They do not claim to reproduce municipal, county or tourism-board boundaries. Each guide states this distinction explicitly.

View map
02

Destination and heritage facts

Transport, cultural heritage, park access and destination facts should be checked against official destination-management organisations, public authorities, protected-area institutions and operators before publication or seasonal updates.

Croatia.hr ↗
03

Opatija Riviera

Promenade, destination and historical context is cross-checked against official Opatija and Croatian tourism information. Seasonal recommendations remain editorial judgements rather than guarantees.

Official source ↗
04

Crikvenica Riviera

The Riviera structure and principal coastal places are aligned with official local destination information. Travel-time and suitability language should be revalidated whenever transport services change.

Official source ↗
05

Šibenik and connected landscapes

City, archipelago and nearby protected-landscape information is checked against the official destination organisation and relevant park authorities. The platform avoids implying that every attraction belongs to one administrative Riviera.

Official source ↗
06

Transport and car-free claims

“Excellent”, “good”, “partial” and “limited” are editorial suitability ratings, not a promise of service. Timetables, seasonal ferries, road conditions and accessibility must always be confirmed with the operator before travel.

Travel by sea ↗
07

Commercial disclosure

Tourism boards and selected businesses may support chapters, journeys or map visibility. Sponsored participation must be labelled and cannot automatically displace stronger editorial recommendations.

Contact
08

Photography

Launch photography is supplied through Pexels and paired with locally generated fallback imagery for resilience. Production deployment should replace or confirm every image with documented usage rights and precise place identification.

Photo credits