David M.

Edo v. when you mentioned this "hosting Webflow sites on Netlify using Udesly and Jamstack conversion." I'd love to see in more detail what updating the CMS/blog content looks like in a real world workflow, of course when you have time : ) Appreciate any feedback.

This goes back to how much internal talent or self talent a client has. Do they have basic editing ability? Are they familiar or learn things like Canva / Google Docs very easily, or do they hate it? Do they have staff that's really good at this stuff, even semi-technical? Edo v. can you create a serial list (numbered bullets) of your process? I looked into it, and where it broke down for me is the heavy CMS usage (so keeping things Webflow natively would be simpler). Are you doing headless work and keeping the CMS content in a content delivery service?

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...

Really interesting decoupling convo, question arise when using Edo v.’s workflow:

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)...

Thanks Matt, greatly appreciated.

Yep, used to do all sorts of sites (never liked Drupal), and a handful of WordPress custom sits (as a designer/agency founder), love how Webflow abstracts away and protect the code, so you just "instruct it" on how to look / operate on different screens. It's neat! I don't miss WP or plugin conflicts, etc.