The appeal of Client-First is undeniable when embarking on a Webflow build. However, it's crucial to consider its potential drawbacks. Two key aspects of this framework could significantly impact your project's scalability and manageability. This article aims to critically examine Client-First, providing essential insights to inform your decision for your next endeavor.
First of all. Deep respect to the Finsweet team. They are the major Webflow community contributor. They have a proven track record delivering top quality products to boost our Webflow builds. With this history, there is no surprise on the huge adaption of their framework for Webflow, Client-First.
There are three main factors that make Client-First some sort of “standard” when building in Webflow.
This three things have made Client-First adoption huge in the Webflow space. To the point that has become the default choice. Where people blindly use it without questioning if it is the right framework for a specific project or the mental model of the person using it.
There are two foundational points that heavily impact on the Client-First “mindset” and shouldn’t be taken lightly.
While these two might sound good as simple stated, there are underlying problems that we can run into.
As simple as that. When you have more of something, there is more effort invested on managing them.
When creating new classes is the predominant approach, the likelihood of having redundant classes and styles increases. This directly impacts the scalability and maintainability of the project. Needing to go through different classes updating values.
Relying heavily on custom classes opens the door to CSS properties with values close to each other. As the project grows, the solidity of the initial design system dilutes.
Too many classes can led to an overwhelming feeling of having lost the control of the project
The way client requests are handled can determine whether the project becomes an unmanageable challenge. In front of a random client request we should have a solid system defined by design that informs the creation and update of UI components.
By allowing for random requests, we are letting a brand’s visual identity evolve in uncontrolled ways. This might not have a huge impact on small shops that don’t put much effort on their brand. But, as we work with more established companies, it could really impact on how a solid brand is perceived.
Client first is a super-well documented framework. It is a good starting specially if you don’t have a framework in place. You can build very fast with all the resources around it_ Client-First starting templates and the Relume Library which is built upon the naming conventions and strategies behind this framework.
But once delivered, and with more attention on bigger projects, the strategies and mindset behind Client-First are not the best approach to keep scaling a site in a controlled and logical way. That being said, you can create some constraints around the out-of-the-box version of Client-First to overcome the mentioned problems.
Whatever framework you choose, after you get comfortable with it, it is a good ideo to question what does and doesn’t work for you. From there, create you own version.
Happy Webflow building!