To offer the other side of this, at $dayjob we just got done getting out of Webflow and into hand-coded HTML. That stack comes with a number of severe headaches.
* The UI layer is complete and total garbage. It is unbelievably slow and clunky and it makes doing anything with it a chore.
* The UI is complicated enough that it would be easier to teach the non-technical folks to use markdown.
* Uncomfortable amounts of lock-in. You can export your entire site of course but retrieving your "CMS" records is not so straightforward.
* If you need to do anything interesting, the UI benefit is gone, because now you get to write code AND use their awful platform.
* Expensive, with a recent price hike with no increase in the functionality or quality.
The recompile and deploy steps can be automated in ways that don't require hitching yourself to this behemoth.
* The UI layer is complete and total garbage. It is unbelievably slow and clunky and it makes doing anything with it a chore.
* The UI is complicated enough that it would be easier to teach the non-technical folks to use markdown.
* Uncomfortable amounts of lock-in. You can export your entire site of course but retrieving your "CMS" records is not so straightforward.
* If you need to do anything interesting, the UI benefit is gone, because now you get to write code AND use their awful platform.
* Expensive, with a recent price hike with no increase in the functionality or quality.
The recompile and deploy steps can be automated in ways that don't require hitching yourself to this behemoth.