How Webflow makes life easier
Now that I’m experienced running a marketing website in Webflow, I’m convinced there’s no better setup, both for me as a marketer and for our design and development teams.
From the designer’s perspective
So you don’t need a developer to focus on your marketing site. And you have full control. And even if your designers can code, I’m still convinced it’s worth building the site in Webflow, for all the benefits I’ll sketch out below about the CMS.
From the marketer’s perspective
Once your site is built, the marketing team can do basically all the content updates in the Editor, which brings the power of the CMS to the non-designers in the room. This means you can run a completely custom blog, or quickly spin out landing pages based on a templated design, or build a bespoke resource center from scratch — or, really, anything your content strategy demands.
And because you can build the structure of your content however you’d like, the playing field is so much wider when you compare the Webflow CMS to something like WordPress.
Let’s take an example: when we launch new features, we release a lot of content, which usually includes an update. The great thing about that whole system is that the update pages were custom built to the design we needed, and I can do that entire creation and publication cycle on my own, without bugging designers to add a new page or asking developers to deploy a codebase.
And remember all that code I learned to make copy edits? Not even close to a thing anymore. Now I can just click and tweak copy right on the page.
But marketing sites aren’t just “set it and forget it.” They evolve. They get redesigned. Which means heavy ongoing collaboration between design and marketing.
But the thing about Webflow is, now that you’ve given your design team the power of development, work on the marketing sites can go as fast as you’re able to collaborate with design.
That makes a designer and a marketer an extremely powerful combo with Webflow, as you can “fire on all cylinders” and work with basically no restrictions on communicating your company’s “pitch” and improving your site.
From the developer’s perspective
As I’ve said elsewhere, the most obvious benefit to Webflow is that you don’t need a developer’s time to set up or maintain the site. And all the integrations you need can be quickly and easily set up with Zapier, or in native Webflow integrations, like MailChimp and Google Analytics.
So that means your developer gets to focus on building whatever else they need to build. In our case, as a software company, that means our product. But if you’re not in software, then no developer needed, problem solved.
TL;DR: Division of labor is good
I’m obviously biased, but I know that wherever I end up next, I’ll be pushing pretty hard for the website to live in Webflow. In the end, it lets everyone focus on what they do best: designers design, marketers handle content, and developers build software applications.
How has your transition to Webflow gone? Let us know in the comments!