Stagecoach
I built the Stagecoach Canada website and the custom API integrations for Stagecoach’s international websites, alongside integration work for the UK platform. My work connects the public website with the systems that hold school, venue and course information, helping families find the right classes and take the next step.
The Canadian site sits within Stagecoach’s wider brand and website platform. It uses WordPress, ACF and Timber/Twig, with custom PHP and JavaScript around the data-heavy parts of the experience. That includes bringing imported course information into editable website structures and presenting it consistently across local school pages and search results.
Finding the right school
Search is a central part of this project. Families need to find a school near them, but a school name on its own is not enough to make a decision. The results bring together the venue, distance, age groups, days and class times, so someone can compare the practical details before opening a school page.
My integration work connects the external school, venue and course data with the public website. Keeping those relationships intact matters: the right class needs to appear against the right venue and lead to the right school. The Toronto search shown here illustrates how several venues can belong to the same school while offering different timetables.
A microsite for each school
The national website leads into individual school microsites. Each one needs to feel like part of Stagecoach while giving families the local information they came for: an introduction to the school, its classes and camps, the team, contact details and an enquiry route.
I built the Canadian website within a shared WordPress multisite platform, using ACF and Timber/Twig alongside custom PHP and JavaScript. Shared templates provide consistency, while school-specific content and imported data give each microsite its own useful detail. The Toronto East page is one example of that national-to-local journey.
The detail behind a timetable
A course listing has several layers. The age group, venue, class time, term dates, price and availability all need to stay connected. On the microsite, venue sections let families open the relevant location and see the classes available there, including the distinction between a booking option and a fully booked session.
This is why I treat the work as a data integration rather than simply placing an API response on a page. I work with the relationships between franchises, schools, venues, courses and dates, carrying that context through to search results and school pages. Changes in the source systems need to reach the correct part of the website.
Keeping the school context through an enquiry
I also built connections between the website forms, the chosen school and external enquiry services. Dynamically populated choices and franchise routing help carry the visitor’s selection into the next step, rather than asking them to explain which school they meant all over again.
My work covers the Canadian site and custom API integrations across international and UK platforms. It is ongoing development across connected websites and systems, with the public search experience, local microsites and enquiry journeys depending on the same underlying information.
Technologies
WordPress multisite, PHP, ACF, Timber/Twig, JavaScript, Alpine.js, Tailwind CSS, Gravity Forms, external system API integrations, JSON feeds, Webpack.