I’m not convinced that managed solutions are the solution. I say this as a professional web developer with a range of clients. Webflow tends to fall apart with complexity. It creates the illusion of simplicity. For example, a designer will update a component, not understanding the underlying CSS classes, and end up breaking every other components relying on that class. Even worse, trying to do anything sufficiently complex, like embedding a third party form, becomes a mess of copy pasted JS embeds. And forget global components, the edge cases make them virtually unusable.<p>On the other end of the spectrum are headless solutions with your pick of framework, let’s say Contentful + Next.js. While far less flexible for a non-developer, the outcome is a rock solid, repeatable, maintainable template. You can democratize editing much more reliably. Although, yes, you need a dev for every customization.<p>Different solutions for different scales I suppose. I’d love to see the marriage of these two approaches. Something that gives the greatest experience to both editors and developers. I’m trying to tackle this problem in my free time, but it is a massive problem. The more I work on it, the more I recognize why it hasn’t been solved. And admittedly, WP has done a decent job of solving it with its massive ecosystem. There is a need for innovation, but it’s a shame to see the baby being tossed out with the bathwater.