Are you jumping into a big Webflow project, and trying to figure out to approach it? Here are some tips that might help.
Webflow is not so much of a tool as it is an operating system for building sites. There are a lot of tools in there, but understanding the system itself is just as important for navigating and constructing your workflows.
But if you're diving in today, as a non-Webflow user, on a large Webflow site, the landscape has changed enough that the approach deserves a rethink.
Important;
I recommend you read the full page before starting your plan, because there's a big difference between;
- A site where you're the only designer/editor vs. one with a team of active users
- A standalone site v. a site with complex integrations
- A simple box-layout-structure v. very heavy interactions and GSAP use
- An element-based site v. a heavily component-first site build
Your 3 Skill Pillars
These days a lot of your process will be about 3 things-
- Learning Webflow as a platform to understand navigation, design system implementation, how the publishing system renders HTML/JS/CSS, you need that mental model to be solid for you to be effective. Critically, this includes
- Learning how agents work with Webflow, primarily the MCP, agent instructions ( stored in Webflow ), and probably the CLI as well
- Learning Webflow's dev surfaces- primarily webflow cloud ( mounted react apps ) and code components ( drop in react components ).
The Approach Path
1 and 3 will take awhile, but they're central to your knowledge.
Immediately I'd start with 2, the MCP
Clone the site. Connect Claude/Gemini/whatever to the Webflow MCP on that test clone, and start learning what it can do.
Build a page, design a feature, tear apart the style system variables, classes, build components, add variants, props, do data-binding, etc. Learn now to create and use agent instructions.
I recommend you name the clone something obvious like TEST CLONE #1, so you can't confuse it, and when you auth the MCP, scope the permissions to only that one test site.
Part of the learning is learning how to connect and control the MCP/agent's access scope. I wouldn't recommend you auth the entire workspace, because it becomes possible [though still unlikely] for you or the agent to get confused and affect the wrong site.
This will get you to the point of understanding some important control surfaces, since we're in a transition where agents are becoming central to the site build and maintenance workflows.
Learning Webflow's system and designer
While you're working with the MCP, also have Webflow open so that you can see the changes, understand what happened to your variables, where those components were created, how the CMS schema was modified, what bindings look like...
And just as importantly you need to learn what the MCP cannot do, which is a rapidly moving target.
Understanding Your Client's Setup
In between and during this work, you want to do is establish a clear inventory of which features your client is using.
Core;
- CMS - what tables, what content, what collection pages and lists and how are they used in the site
Subsystems;
- Localization
- ECommerce
- Analyze ( analytics )
- Optimize ( A/B )
Enterprise sites;
- What enterprise features is the client using?
- Page branching?
External Integrations
Are there other key integrations here?
- Whalesync or other system syncs of CMS data
- Forms handling to Hubspot integrations etc
How the Team Works
You also need to understand how the company uses Webflow;
- Editors and marketers using those interfaces?
- Larger design team at play?
- What are the publishing / update cycles at play?
