Headless WordPress · Next.js

Happylife Tourism.

Arabic travel browsing with a headless WordPress backend.

Next.jsReactWordPressVercelArabic / RTL
HeadlessContent architecture
Arabic / RTLInterface direction
Next.jsFrontend
Happylife Tourism
Happylife Tourism homepage
Happylife Tourism — homepage preview

01 / Context

The project and my contribution

Happylife Tourism needed a custom travel website while retaining WordPress for content management. Visitors browse destinations, offers and itineraries through an Arabic, right-to-left interface.

My contribution

At WOT Agency, I architected and launched the headless WordPress website, connecting the content backend to a custom frontend deployed on Vercel.

02 / Functionality

Key Features

01

Destination-led discovery

Destination and trip-category routes organize packages around places, family travel, honeymoons, and cruises.

02

Structured trip presentation

Cards present trip duration, package names, and starting prices, with links into individual trip pages.

03

Arabic-first interface

Right-to-left navigation, Arabic content, and mobile menu behavior form part of the frontend presentation.

04

Search and contact paths

A visible trip-search interface and dedicated contact navigation support the journey from browsing to an inquiry.

03 / Implementation

Technical decisions

  1. 01WordPress content
  2. 02Next.js frontend
  3. 03Destination & trip pages
  4. 04Visitor inquiry
Simplified architecture

Separate content from presentation

WordPress remains the content backend while React/Next.js handles the visitor-facing interface. This gives the frontend its own component and layout structure.

Give content a route

Destinations, categories, and trips have separate URLs rather than existing only as temporary interface states.

Make travel content discoverable

Headings, navigation and trip content are available in the page HTML, alongside canonical URLs and structured data.

04 / Delivery

Result

The live website brings destinations, travel categories and individual trip pages into a consistent Arabic browsing experience, with content managed through WordPress.

05 / Evidence

Scope & Review

My contribution is documented in my CV. The public homepage, destination navigation and HTML were reviewed on September 28, 2026. Checkout and private administration were outside that review; traffic, booking and performance improvements have not been measured here.

↑