There are a lot of resources for the Webflow CMS out there. There are templates, component libraries, single components, pre-build pages that are not a template, custom code snippets and third-party integrations. All kind of stuff. So what do we have to complain about?
A lot of Webflow resources seem like they're made to provide design inspiration or take workload in the field of designing and crafting your website. Which is awesome – we all need a little inspiration sometimes when building websites and software interfaces. It's great that there are so many good designers sharing their (often clonable) work providing templates and components that help us craft a sweet-looking result.
But for ourselves, we didn't feel like this is the field we most desperately needed help.
The obvious answer might be: both. And it's true. All of us are designing websites and therefore the user experience of a digital product, service, Online-Shop or whatever the goal of your site may be. In the Webflow designer we all build HTML and CSS code in a faster and easier way using the Webflow interface instead of a plain text code editor. The tool provides us with a CMS that is client-friendly, easy to set up and maintains itself while not being too expensive.
And yes: all of us for sure already implemented some pieces of custom code to work around the feature limitations of Webflow. Code that we found somewhere Online while searching for solutions to our problems that seemed to work – at least more or less.
So Webflow is made for designers, that understand and maybe have a certain ability to work with code. But are we JavaScript Developers? Are we Webflow developers senior front-end developers who would be able to build whole interfaces with frameworks like React, Angular, vue, ...? For me and everyone I know using Webflow on a professional level the answer would be: no.
There are so many different headless CMS solutions that allow you to add a nice working CMS to pre-written code, update features and basically everything you'd be looking for if you'd be a front-end hacker who wants to build a website. It would be faster, cheaper and have fewer limitations that block the development process.
Webflow users are designers, that understand front-end code and how websites are built, launched, and maintained. They are no developers in need of design advice.
So the conclusion of this to us was: we as Webflow users don't need help with the design. We need help with the code! We need solutions for things we can design in a design tool, but can't build in Webflow because it's not possible within the native system.
Our goal is to provide solutions for Webflow users that search for specific components to add more functionality to their sites. We want to provide you with these components, tutorials, and ideas on how to use them.
So that you'll never ever again have to worry about implementing some weird solution that doesn't work and breaks on a client's website. Everything we provide is like Webflow itself: closed source, maintained and therefore doesn't break. Every component is easy to implement and free to style – build by Webflow designers for Webflow designers.
That's something we always wanted to find ourselves while building Webflow websites as a web agency for 4 years. Now we decided to build it ourselves.
As of now, the feedback on this approach is overwhelmingly positive. If you want to follow us to see what components are on our roadmap or get updated with the latest launches check our road map.
Until then we wish you a happy building and success for your projects.
Your No Code Flow Team
