From the Nerd News Archive: our road retold in the voice of the moment. A story written today.
I moved my whole practice to Webflow, and I want to write down why while the reasons are still fresh, because leaving WordPress felt less like switching tools and more like leaving a hometown.
WordPress was good to me. It powers something like forty percent of the web for a reason, and the Divi builder let me ship real client sites years before I could have coded them by hand. Nothing that follows is a grudge. It is just an honest ledger of why I packed.
What actually triggered it
Two things, and neither one was a shiny feature. The first was maintenance fatigue. Every WordPress site I ran was a little stack of obligations: core updates, theme updates, a dozen plugin updates, PHP version bumps at the host, backups before touching any of it. Multiply that by every client site and my calendar grew a recurring appointment I started calling update night. Update night is not design. It is not marketing. It is paying rent on complexity I never wanted.
The second was design control. Builders like Divi are shortcuts, and shortcuts have ceilings. I kept hitting moments where the design in my head required fighting the builder instead of using it, layering custom CSS over generated markup and hoping the next update did not undo me. When you spend more time working around a tool than working in it, the tool has told you something.
Underneath both was a slower realization about how I choose platforms at all: match the tool to the goal and the budget. A template when speed is everything. A builder when the budget is small and the needs are standard. Something with more control when design is the product. My own work had outgrown its bracket, and I had been ignoring it.
What was scary
Leaving an ecosystem is the scary part, and anyone who tells you otherwise has not done it. WordPress has a plugin for everything; Webflow has a features list, and if a thing is not on that list, there is no plugin aisle to save you. That is a real constraint, and I stared at it for a long time before jumping. The fears, listed honestly:
- No plugin ecosystem: if the platform does not do it, you adapt, embed custom code, or do without
- Subscription hosting: the site lives on Webflow's infrastructure, priced per site per month
- Export limits: you can export code, but the CMS and the hosting features do not come with you
- Relearning: my hands knew WordPress, and the Designer had to earn that same muscle memory
What got me over the line was realizing the Designer is not just another builder. It is a visual layer over real HTML and CSS: classes, the box model, flexbox, grid. Learning it made me a better designer of actual web pages, not a better operator of somebody's shortcode system. That knowledge travels.
What was instantly better
The first month felt like putting down a bag I had forgotten I was carrying. One tool. Design, CMS, forms, hosting, SSL, backups, staging, all in the same place, all maintained by the same company, none of it my problem at two in the morning. No update night. I checked twice, out of habit, that there was nothing to update. There was nothing to update.
The CMS deserves its own sentence: Collections turned repeating content, projects and testimonials and service pages, into structured data with designed templates, and handing a client the Editor stopped being an invitation to break the layout. Interactions gave me scroll and hover animation without hunting for yet another plugin.
Where this leaves me
The industry backdrop right now is everyone talking about ChatGPT, and I have poked at it like everybody else, drafting copy and asking it questions. Interesting, occasionally eerie. But it has nothing to do with how I build sites; the craft conversation for me is entirely about owning design without owning maintenance.
I do not assume Webflow is the last platform I will ever use. Platforms are brackets, and businesses move brackets as they grow, mine included. But for the work in front of me, the trade is obvious: I gave up an infinite plugin aisle and got back my nights, my design control, and a stack where keeping the lights on is one vendor's job instead of mine. So far that trade wins every single week.
