Beond

Beond flies premium routes to the Maldives, and the site has to do two quite different jobs at once. It is a booking engine: search flights, manage an existing booking, check in, look up flight status. It is also the brand's shop window, where an expensive proposition gets sold with photography and copy.

Those pull in opposite directions. A booking engine is an application with state, validation and live availability. A brand site is editorial content that marketing needs to change without a release.

The front end is Next.js. Editorial content lives in Contentful, so destination pages, the holidays offering and campaign content are all edited by the marketing team rather than deployed by a developer.

Booking runs against the airline's own APIs. The search widget on the homepage is the entry point to that, with the other journeys (manage booking, check-in, flight status) sitting alongside it as tabs rather than being buried in a menu, because those are the tasks returning passengers actually arrive to do.

Multilingual support is handled at the content layer, so adding a market is a content exercise rather than a rebuild.

• Next.js frontend with server rendering for the marketing pages
• Contentful as the content layer, marketing owns editorial
• Booking, manage, check-in and flight status against the airline's APIs
• Multilingual content model for market expansion

The marketing team publishes destination and campaign content without developer involvement, while the booking journeys run against live airline systems on the same front end.