Ripley’s Entertainment · In-house
Ripley’s Multisite-to-Single-Site Overhaul
Supported Ripley’s WordPress multisite, then helped overhaul it by bringing multiple websites into a single site while maintaining day-to-day operations.
Project imagery
From WordPress multisite to one website.
Reported outcomes
- 30+ legacy websites modernized six-month consolidation project
- +25% online conversions within one month after launch
- 1.03M peak monthly visits consolidated Ripley’s website
01 / Context
The work in context.
Led development work across a WordPress multisite, then contributed to a six-month overhaul that brought multiple websites into a single site. The work modernized 30+ legacy websites while daily operations continued. The wider group included developers, QA, and design and content partners from other departments.
02 / Challenge
The problem to solve.
Keep the existing WordPress multisite running while preparing to consolidate multiple websites into one site. Updating PHP versions risked breaking dependencies across the multisite environment before the planned overhaul.
03 / Approach
How I approached it.
- Use analytics reports to prioritize sites with the most traffic and highest conversions.
- Defer the PHP upgrade, with senior-team agreement, until the overhaul could address multisite dependency risks.
- Assign high-priority tickets to match developers’ capabilities while giving them room to grow, and step in to unblock work.
04 / Implementation
What I delivered.
- Modernized 30+ legacy websites within six months as part of the multisite-to-single-site overhaul.
- Prioritized urgent fixes for color contrast, screen-reader usability, and text accessibility.
- Contributed to the consolidated site using Svelte, TypeScript, Cloudflare, and GitHub.
- Managed a core group of 1–4 developers and worked with QA and cross-department design and content partners.
- Used interim plugins and guidelines to keep content work moving and the existing sites running securely while the PHP upgrade was deferred.
05 / Constraints & tradeoffs
What shaped the work.
- The existing WordPress multisite had PHP dependencies that could break if versions were updated before the planned overhaul.
- Consolidating multiple websites into one site ran alongside ongoing multisite operations and cross-department collaboration.
06 / Outcome
What changed.
Company analytics shared with stakeholders reported a 25% increase in online conversions within one month after the six-month multisite-to-single-site overhaul. The consolidated Ripley’s website, where I contributed as a senior developer, reached a peak of 1.03 million visits in a month. From observation, ticket open time shortened by an estimated two to three days, and the team processed an estimated five to ten more tickets per week.
The conversion figure comes from private company analytics shared with stakeholders. The ticket-flow changes are approximate observations, not tracked measurements.
- WordPress multisite
- PHP
- Svelte
- TypeScript
- Cloudflare
- GitHub
07 / Reflection
What I take forward.
Moving from WordPress multisite to one consolidated site meant supporting the existing environment while sequencing platform changes around the overhaul.