Why would any website designer/developer still use WP if there's Webflow? I truly don't understand it. Because a client wants/needs WP? Except for very specific backend integrations, I truly see no reason to advise clients to go with WP. It’s such a mess behind the front door…
Edo v. your point is valid but clients still want websites in WP. we can't neglect that, its a clients personal choice.
If they would like to host the files themselves. They do not want an external provider to be the ‘boss’ of the files. If the webflow infrastructure fails (like a couple months ago) and their WP files are on a server in their basement, the website would still run. This is not possible with Webflow. Also; if Webflow decides to raise the hosting cost and triple it. In this case hosting your own WP stays the same price.
I'm hosting Webflow sites on Netlify using Udesly and Jamstack conversion. Great solution and way cheaper than Webflow’s own hosting. Works even with CMS. So clients can host Webflow sites with this approach on their own servers as well.
These videos explain the process I’m using: https://youtu.be/vzmc4eC5xpc?si=nkbBjf02xuxAtwkB https://youtu.be/V8a0LtxNuE4?si=6J3HcX52FAfRfTb2
That is interresting, I am interrested Edo thank you.
Super cool conversation here! I think that it might be shocking how much market share WP still has and I think there's a demand for open source and freedom that will likely always exist no matter how good Webflow is. But I also think that not all clients know exactly what they need and its up to us to dig into their needs and recommend the best path for them and that may not always be Webflow. Webflow used to have a sales one pager that you could hand to clients but now its just this page: https://webflow.com/vs/wordpress
This is a pretty concise comparison between WP and Webflow: https://youtu.be/Avc7xBoByxc?si=w-kKi0fOBVmKvHrq
Really interesting decoupling convo, question arise when using Edo v.’s workflow:
How do clients edit their own websites?
Do CMS conversions carry over as static web pages?
In concept this is pretty ideal for internal teams managing their own code, but for clients who need lots of handholding, feels less than idea, especially if they want to hire staff to do the website "editing" in the end / manage CMS (with a GUI)...
I'd suggest for startups or those starting out, just put all the weight on webflow, then as they grow, CONSIDER moving the website / migrating it to something more robust...

