Hanover Communications

The Challenge

Hanover Communications is a global PR and reputation consultancy — the people big organisations call when they need to get ahead of a story, not just react to one. Their own site was running on WordPress, which meant everything from a client case study to a podcast episode to a job vacancy was, underneath, the same flat "post" — distinguished by a category tag if you were lucky, held together with plugins if you weren't.

That's fine for a blog. It's not fine for a PR agency publishing nine different kinds of content — insight articles, client case studies, job vacancies, podcast episodes, and Rewire, their own editorial magazine — all of which need their own fields, their own filtering by sector, location and service line, and their own place in the site, not just another entry in one undifferentiated list.

Our Approach

We rebuilt the site on Statamic, a flat-file CMS running on Laravel, and moved the content across with a WordPress import tool rather than asking Hanover's team to rekey years of posts by hand.

The real work was the restructuring: nine distinct content types — insights, case studies, podcast episodes, magazine articles, team profiles, job vacancies and more — each with its own blueprint defining exactly what fields it needs, plus five taxonomies (sector, location, service line, magazine issue, role type) so a case study and a job vacancy can both be tagged "Energy" and actually mean the same thing. Every piece of content lives as version-controlled Markdown, git-committed automatically as Hanover's team publishes.

On top of that: a custom integration pulls live vacancies straight from Greenhouse instead of someone copy-pasting job ads, a queued job generates social share images automatically so nobody's opening Photoshop before a launch, and a custom accessibility widget in the CMS flags any image missing alt text before it goes live.

The Results

The site launched in December 2022 and Hanover's content team is still publishing into it today — over 500 pieces of content across insights, case studies, team bios, podcast episodes and job vacancies, entirely self-served, each one correctly structured rather than another WordPress post pretending to be something else. No dev ticket required to run a campaign, announce a new hire, or publish the next issue of Rewire.