If you only need a static website then it's a great solution.
But it is NOT hard to start running into barriers. In my experience it's essentially impossible to use it as a frontend design tool with say a node.js backend. There's no templating support, very restricted export (their CMS costs extra per site, and isn't part of the export), etc.
If your website has a login button then I'd be impressed if you designed the whole thing in webflow.
Exact reason why we migrated a webflow site to Next.js/GraphQL/Contentful/Hasura stack.
Webflow is an awesome design tool, but the exported code is very messy to work with. If are a designer or plan to stay on webflow for simpler static sites, it wouldn't matter though.
However, It does create a technical debt if you happen to scale up and your needs grow.
* eliminates the need for front-end development on static sites
I have been using it since its beta days for my blog and some mockups and am not sure I agree. It is one of the finest 'web design tool' that I have ever used. But one that will create a technical debt for the 'real front end developers' in the future.
But it is NOT hard to start running into barriers. In my experience it's essentially impossible to use it as a frontend design tool with say a node.js backend. There's no templating support, very restricted export (their CMS costs extra per site, and isn't part of the export), etc.
If your website has a login button then I'd be impressed if you designed the whole thing in webflow.