01Status
Built end-to-end for AOG Developments. Not launched.
02Context
A boutique wellness hotel with serviced suites inside one of AOG Developments' coastal projects. I built a bilingual lead-capture site for it, completed in May 2026 but never launched.
03Problem
AOG needed a campaign page that could take ad traffic in Arabic or English and turn visitors into leads with a clear interest, instead of generic contact messages.
04My role (and what I didn’t do)
I designed and built both versions alone: an English hotel page and an Arabic-first campaign page with an English toggle. I did not connect the forms to a CRM or set up a WhatsApp number.
05Constraints
Static files only, with no backend or framework. Mobile-first, because campaign traffic comes from phones, and every section had to stay readable if JavaScript was slow or off.
06Architecture / workflow
- Visitor lands
- Chooses Arabic or English
- Picks an interest
- Form is validated
- Tracking event fires (no CRM connected)
07What I built
Two static versions in plain HTML, CSS and JavaScript. One toggle switches Arabic and English, flips the text direction and remembers the visitor's choice. Two lead forms with required-field validation and an interest picker: viewing, payment plan, serviced suite, or brochure. Every key action, such as a form submit, a validation error, a language switch or a gallery open, sends a tracking event to the dataLayer, ready for Google Tag Manager. Also gallery and floor-plan dialogs, a sticky mobile call-to-action, lazy-loaded WebP images, and reduced-motion support.
08Evidence
QA notes record checks at seven screen sizes, from 360px phones to 1920px desktops, plus accessibility and motion checks. The source and QA screenshots are kept privately, because the brand and imagery belong to AOG Developments.
09Verified outcome
10Limitations
11Next step
Connect the form to a CRM or an n8n webhook, add a verified WhatsApp number, and launch it with a measured campaign.