We utilized Webflow to work fast and stay within a tight budget. This platform also gave us the opportunity to make the site more custom - moving away from a strictly “flat” design. Using the no-code approach, we had the flexibility to add more personality while keeping a consistent user experience.
In the initial phases of a web build, there are few different routes we can take. We’re faced with decisions like what CMS to chose, what templates we may work from, how custom-fit features need to be, and more. Typically, we start to make decisions based on our constraints such as budget or timeline.
Utilizing the triple constraint triangle, we can always select two out of the three points to help inform our decisions. In our initial conversations with Thresher, we quickly discovered their team needed a marketing site to convey the important points of their brand and offerings while keeping the project timeline short and the level of investment low. In this case, less of the focus was on a large scope, and more involved time and cost.
Because this was a new approach to building a website, we needed to make sure we covered all our bases when it came to executing to the same standards as any of our other CMS projects. Our design team built the site from scratch on Webflow, allowing more bandwidth for the development team to focus on other custom development needs that Thresher had prioritized in parallel.
Not only was the design collaborative but the front-end development side of the project was too. Even though Webflow is a no-code site builder, the way the interface is set up, it is still possible to QA and troubleshoot development issues. Webflow University and Webflow’s customer support was a great help in solving problems that arose during the build, but the most successful part of the project occurred during 1:1 time between one of our designers and front-end developers screen sharing the interface of Webflow. They were able to solve problems almost immediately, together, instead of siloing their workspaces and getting it done individually.
This was a great learning experience for all parties on the Savas team; project management, design, and development. We learned the value of bringing in a developer to help our design team think through constraints and act as a coach without needing to write a line of code.
During the project retrospective, one talking point identified the unique challenge of designers thinking like developers and developers designers. This was an eye-opening conversation and allowed us to think about how we can use that to our advantage in future projects, even if we don't use Webflow.
Working with a team like Thresher, they challenged us to constrain our design to make the handoff and post-project maintenance as seamless as possible. Webflow has a fantastic experience for editors and collaborators to make copy and image updates to the site. For Thresher, we collectively agreed that "locking" most of the design would provide less stress to the Thresher team, so they are only focused on a few parts of the site to maintain.
Webflow gives designers, developers, and content creators a deep well of information — including how-to videos on Webflow University — to support the undertaking of leveraging the platform. It's a tool we're adding to our arsenal when considering solutions for our clients moving forward. In the end, Webflow provided an excellent option for a client who wanted a custom-designed, easy to maintain, simple site when their budget didn't offer the flexibility to leverage other comprehensive off-the-shelf CMS solutions.