[robertlf]

While I'm new to Webflow, I get a feeling that some people try to push it too far. It seems to me that it's mostly a no-code tool meant for basic "brochure" sites with some modest CMS capabilities built in. And for many, many businesses, that's sufficient. It provides additional design flexibility for those who understand HTML and CSS. If you're making a site that's so complex that you need version control, you should probably be using a web application framework. But, in a pinch, you can always export your code and do VC on that. Just my $.02.

[tobr]

Those are basically the types of projects I’ve been involved with, but with high standards for the design quality, and sticking to a brand manual. A project like that still has the kind of complexity where version control would be extremely useful. Like just having a place to see what changes have been made, by whom, merging the things we want to deploy, reverting other things - it’s just a matter of time before you run into problems without it. See also Elof’s comment in the thread which explains basically the same problems.