QiblaCore
A Hajj and Umrah travel platform, architected as three apps and shipped one at a time, starting with the one that had to exist first.
The problem
A pilgrimage travel agency needed a real digital presence before it needed a booking system: something that could earn trust and convert enquiries while the more complex portal and backoffice work was scoped properly.
Approach
I scaffolded a Turborepo monorepo for all three apps (marketing site, pilgrim portal, staff backoffice) up front, sharing a design-token package and UI kit, then shipped the marketing site first: fully static, content modeled as typed, Zod-validated data rather than a CMS. The enquiry form composes an email client-side instead of posting to a server, deliberately, to avoid storing personal data the agency doesn't need to hold.
What it does
- A shared token and component system built to carry across all three apps from day one
- A six-part travel journal with generated Open Graph images and full structured data, not a bolted-on blog
- A measured performance call: benchmarked Webpack against Turbopack and shipped the smaller, faster bundle
- Domain models and UI primitives for the pilgrim portal and backoffice, designed and documented ahead of the build
Where it stands
The marketing site is live on Cloudflare Workers. The client portal and staff backoffice are architected, not yet built: I shipped the piece that needed to exist first and left the rest ready to build on.