Princess Lodges

The problem

Princess Lodges relied on a legacy booking engine that was built on end‑of‑life software and tightly coupled to their existing WordPress site. This setup made it difficult to maintain, risky to update, and slow to adapt to new business requirements. Non-technical staff were hesitant to touch the system, and any change to the booking flow required significant developer effort and careful manual workarounds.

From a guest perspective, the booking experience felt dated and inconsistent with the rest of the site. From a technical and business perspective, the fragmented stack increased operational overhead, introduced reliability concerns, and limited the team’s ability to experiment with new features or optimize conversions. The organization needed a modern, maintainable solution that preserved the existing WordPress property while eliminating technical debt in the booking pipeline.

Solution

I rebuilt the booking engine using a modern PHP application framework and integrated it with the existing WordPress site on the backend. The goal was to provide a booking experience that felt fully native to the current property while simplifying the underlying technology stack. I focused on creating a clean separation of concerns: WordPress continued to manage content and marketing pages, while the new application handled booking logic, availability, and pricing.

On the full-stack side, I designed and implemented the server-side application, routing, and business logic, and exposed a structured interface for WordPress to communicate with the booking engine. I also refined the front-end booking flow so it aligned visually and behaviorally with the existing site, ensuring that guests experienced a seamless transition between content and booking. By consolidating the stack around a single, modern PHP ecosystem, I enabled a more consistent developer experience across applications and laid the foundation for faster iteration on new features.

Challenges

One challenge was integrating the new application cleanly with an established WordPress property without disrupting existing content workflows. I addressed this by designing a clear contract between the booking engine and WordPress, relying on backend integration patterns that allowed WordPress to remain the “face” of the site while delegating all booking operations to the new system behind the scenes.

Another challenge involved migrating business rules and edge cases from the legacy engine, which had accumulated years of ad‑hoc logic. I worked closely with stakeholders to document current behavior, then refactored that logic into explicit, testable components in the new framework. This reduced hidden complexity while preserving the rules that were important to the business.

A third challenge was ensuring that the new system could be supported and extended efficiently by future developers. To solve this, I standardized the stack, introduced consistent patterns across applications, and added documentation and basic automated testing around critical booking paths. This helped shrink the mental overhead for developers working across both the WordPress layer and the booking engine.

Outcomes

Helped create a more consistent developer experience across the booking engine and WordPress, contributing to faster delivery of new booking features.

Improved the reliability and maintainability of the booking flow by replacing end-of-life legacy code with a modern, testable application framework.

Reduced operational risk and overhead associated with updates and content changes, enabling the team to iterate on the booking experience with greater confidence.