Just completed this Webflow website project for Mind Your Business Radio
The goal was to turn a growing library of business interviews, guest stories, and media content into a clean, easy-to-explore experience.
I focused on strong episode discovery, clear guest presentation, responsive layouts, podcast and video integration, and a structure that makes it easy for listeners to find valuable conversations while giving potential guests and partners a clear way to connect.
I’d love to hear your thoughts, does the website feel like a platform you’d actually enjoy browsing and listening through?
One of my favorite projects this year: a full migration of ecopiatech.com from a legacy PHP CMS to Webflow.
Ecopia builds AI-generated 3D maps, and their site had a lot going on. Smooth scroll, parallax, character reveals, a fullscreen menu with an animated tile grid, timeline carousels, before/after sliders. The brief was simple: rebuild it 1:1.
So instead of eyeballing it, I went into the live site's CSS and measured everything. Easing curves, delays, durations, even the "random" text reveal turned out to be a 6-step delay cycle per word. Then I rebuilt it in Webflow so it feels exactly like the original, but now the team can update everything on their own.
On the content side:
220+ blog posts, news and case studies moved into Webflow CMS
Before/after sliders, videos and map embeds inside rich text, handled with simple shortcodes the editors can use
250 redirects mapped and verified so no old URL breaks
HubSpot forms restyled to match the brand, plus tracking set up for launch
The fun part of projects like this is the details nobody notices when they're done right.
Take a look: https://www.ecopiatech.com/
Our Peak3 website build covered 17 page templates and six CMS collections. At that scale, the questions about publishing deserve as much attention as the finished pages.
A blog post, a whitepaper and a careers entry need different information. Making them editable is only part of the design problem. The person adding the next entry also needs to understand what is missing and what happens when they publish it.
Here’s a hypothetical review I’d run before a CMS handoff: create a whitepaper entry, add the title and cover, then leave out the download file.
Does the editor flag the missing file? Can someone preview what the visitor will see? If the entry can still be published, does it create a download button that leads nowhere?
I’d use that test to decide which fields must be required and which incomplete states need an explanation.