
A newsroom that can't stop publishing
Hunterbrook first asked us to take over and stabilize WordPress. After digging in, we recommended a different path: the problems were the kind that keep coming back on WordPress, and Webflow suited how the team works. That meant moving a live newsroom to a new platform without changing its design or losing its search equity, with every footnote, chart, document embed, and map-driven story carried over intact while the team kept publishing on deadline.
Stabilize first, then move everything
We split the work into two tracks. First, we fixed the WordPress site so Hunterbrook could keep publishing reliably during the transition. In parallel, we planned and built the new platform: a clear URL structure, purpose-built CMS collections, a 301 redirect for every existing URL, and a Webflow build that reproduces Hunterbrook's design faithfully across desktop, tablet, and mobile. The new site launched in mid-June 2026, roughly eight weeks after the project kicked off.
A distinctive identity, rebuilt as a system
Hunterbrook already had a look readers recognize: the stacked HNTR BRK wordmark, condensed Barlow headlines, Merriweather for long-form reading, and Newsprint Black set against Hunterbrook Blue, with red for breaking news and data. Because this was a migration, our job was to keep every detail exactly as readers knew it. We rebuilt the palette and responsive type scale as Webflow variables and shared styles, so new stories, pages, and features stay on brand without anyone rebuilding them.
Keep the newsroom publishing during the move
With an article scheduled to go out that Friday, the first priority was making WordPress dependable again. In the project's first week we repaired broken post scheduling, corrected a database that mixed HTTP and HTTPS addresses, and cleared out debug tools and inactive plugins. That gave the newsroom a stable place to publish while the new platform was built alongside it, without interfering with day-to-day work.
Every story, rebuilt by hand
Hunterbrook's articles are built from custom content blocks that change from story to story, so the archive could not be moved with an automated import. Our team migrated it article by article into purpose-built Webflow collections for Investigations, Breaking News, Authors, and Team, checking images and alt text, Datawrapper charts, DocumentCloud documents, and footnotes along the way. Bylines, author bios, and the team roster are now managed directly in the CMS.
Built for evidence-heavy storytelling
Hunterbrook's reporting leans on evidence: satellite imagery, maps, financial filings, and dense sourcing. We built custom features in Webflow to carry that over, including interactive footnotes, a scroll-driven video template for map-based investigations, expandable rich-text sections, smooth article transitions, and featured stories that editors control from the CMS. After launch, we added load-more buttons so readers can keep moving through the archive.
Move the site without losing its place in search
A newsroom's archive is its authority, so search preservation was planned from the start. We organized stories into Investigations and Breaking News folders, mapped every existing URL to its new home with a 301 redirect, kept the hntrbrk.com address readers already knew, and rebuilt the site's RSS feed. Post-launch crawls took the site to an Ahrefs health score of 100 within two weeks of going live.
A hidden traffic problem, caught early
Two weeks after launch, Webflow's usage dashboard showed roughly 1 TB of bandwidth served in under 16 days, against a 50 GB monthly plan. The traffic was not new. WordPress had simply never metered it. Webflow automatically upgrades sites that go over their limit two months in a row, so the clock was running. We put Cloudflare in front of Webflow to serve cached pages and optimized images, and the last fixes went live on July 16, two days before the billing cycle rolled over.
A partner after launch, not just for it
We carried Hunterbrook's cookie consent over to Webflow with Google Consent Mode v2, so analytics stay in a restricted, cookieless mode until a reader opts in, and reconnected Google Analytics, Tag Manager, and Search Console to the new site. Since launch, Hunterbrook has kept working with us on a maintenance plan covering new features, consent updates, navigation changes, and new domains as the newsroom grows.
Same newsroom, a fraction of the load
Readers see the same Hunterbrook they always have. Behind it, a WordPress site that kept needing repairs became a Webflow platform the newsroom can publish on with confidence. And the bandwidth spike that surfaced after launch was brought under control within a month, from roughly 1 TB in under 16 days to under half a gigabyte a day by late July, before Webflow's automatic upgrade could kick in.




















