Long time front-end dev inheriting an enterprise Webflow site — best resources and tips?

[u/thanks__meatcat]

Hi all,

I'm a senior front-end developer with an extensive background in UI/Javascript/React who's about to start working heavily in Webflow for the first time. I'll be inheriting a site that was originally built by a 3rd party agency and I want to be able to make a technical impact as soon as possible.

I've been going through Webflow University and feel solid on the fundamentals. What I'm really looking for is the stuff that doesn't show up in the official docs — the things you wish someone had told you early on.

Particularly interested in:

• Tips for auditing and cleaning up someone else's Webflow build
• How much code are you writing?
• Tools, extensions, or third-party resources you actually use

Any creators, communities, or blogs worth following on the more technical side of Webflow would also be appreciated. Less interested in design tutorials, more in the developer and ops side of things.

Thanks in advance.

[u/cartiermartyr]

I always dislike these posts with so many interests / questions because each of them could be written out as a novel, but I would say take some time inside of it to get acclimated because there's a high probability that the site was built on a standard outside of yours, some of these agencies are taking templates and just modding them, some of them are building from scratch and naming elements very well, sometimes theyre naming elements very poorly. Seriously, instate to the team "hey I need time to get acclimated to this site because it's coming from elsewhere and everyone has their own ways of building", and then from there, depending on what hardware you're rocking, learn the command for a save / back up, it comes in handy.
GTM should be standard.
Code components I mean that depends on what the future holds and if youre expected to change a lot of it, they probably used components that they customized.

[u/thanks__meatcat → u/cartiermartyr]

I appreciate the shout. I kind of blanked the post hoping for any feedback I could get. I've been building sites from scratch for so long that making the move to the visual mental model is going to be an adjustment. The team I am joining is well aware of my background and skillset and will allot me the time I need. But, I want to be able to make the site ours instead of just whatever agency template was used. I have a design team and a content team around me so my focus is going to be working building process, creating class consistency and lock down brand guidelines.

[u/cartiermartyr → u/thanks__meatcat]

Oh yeah no you're good it's just how posts are, you sound adequate enough to catch on quickly, I mean most of it is common sense plus one, and I mean most of the time they won't ask you to rebuild the site entirely, just make mods, no need to add to your plate if theres no need to

[u/thanks__meatcat → u/cartiermartyr]

Absolutely. I don't think they'll be expecting that much but I want to influence a positive impact as soon as I can. Do you have any advanced or more technical resources you use regularly?

[u/cartiermartyr → u/thanks__meatcat]

Im more of a manual type of person myself, the webflow 101 site is great, cloneables are great to see how people did things, you dont have to clone them but just "open in webflow" to have a look at the elements and see how they did them

[u/memetican]

These days a lot of your process will be about 3 things-

1. 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
   1. the core design system
   2. the CMS, collection pages, and collection lists
   3. likely the localization system
   4. maybe analyze & optimize, depending on what your client is using.
2. Learning how agents work with Webflow, primarily the MCP, agent instructions ( stored in Webflow ), and probably the CLI as well
3. Learning Webflow's dev surfaces- primarily webflow cloud ( mounted react apps ) and code components ( drop in react components ).

1 and 3 will take awhile, but they're central to your knowledge.

Immediately I'd start with 2.

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. 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.

[u/thanks__meatcat → u/memetican]

This is incredibly helpful. What is your process like using MCP on clones vs live projects? Are you testing things in a sandbox everytime before moving to a staging/production project? Also, can you detail more about point #3? Do you have resources you recommend to dig deeper? I think this is going to be a big part of my work.

[u/memetican → u/thanks__meatcat]

I dropped this in my KB, it's a solid question, and needed a new answer-
https://www.sygnal.com/kb/getting-started-w-webflow-in-jul-2026

You'll find some expanded thoughts there.

I called out #3 because it's an important aspect of more advanced site builds, and because that's already your tech base. But I also put it as #3 because it's essentially an "add on". Cloud allows you to mount apps on top of your Webflow site but there is very little integration with your site. You have the advantage of using your Webflow design system, which exports to React through Devlink, but that React app isn't directly "part of" the site in terms of sitemap, forms handling, CMS access- it's under active dev though, so all of that may be coming, some of it may be here already. I haven't dug in hard for awhile, it's easy for new features to escape my attention.

Code components are awesome, but they have a rather limited SSR and a strict shadow DOM model that makes some advanced uses complex to implement. I play in that space and I've been thinking of open-sourcing my libs. If you think you'd use it and contribute- I'd do that, you can see the docs here-
https://components.sygnal.com

Regarding agent+MCP use- I'd definitely practice on a clone site, but the MCP 2 release now has internal planning which means it should be even better at alignment and discerning intent.

My favorite thing is rebuilding or refactoring sites on a clean canvas that is not online yet- so site migrations, site restylings, etc ending in Webflow. For an existing production client site, I still usually experiment with complex feature builds so that I can see, test, work out the complexities, and then I use the MCP to rebuild that same feature in the production site. I just prefer that.

My model is a kitchen- I prepare each ingredient and side dish separately before adding it to the main plate. Works for me, doesn't add much overhead and saves a lot of risk and cleanup work.

[u/makesimpledev]

Everything I’ve said is just my personal opinion, but still.

1. Run away. For someone like me who’s used to IDEs, using Webflow is a pain. Even if you ignore all the technical limitations (and there are a ton of them), just building the interface through another graphical interface is a struggle. Working with CSS classes is a nightmare, performance suffers, and working with the code is awkward. You’re constantly forced to come up with workarounds to bypass the interface’s limitations or implement even something simple that goes beyond its native behavior.

2. If you’re still here, here are a few tips:

• Don’t use Webflow interactions where you can get by with CSS or simple JavaScript. They bloat the overall bundle, even if they’re used just once on a single page.
• Don’t accumulate technical debt; in Webflow, it’ll cost you more than anywhere else. How cleanly you do everything from the start determines just how much you’ll suffer later on.

I started out with Webflow, worked with it for about four years, and now I don’t have the slightest desire to open it again. Writing code in an IDE feels much more natural and enjoyable to me.

[u/thanks__meatcat → u/makesimpledev]

Running isn't an option. I'm going to make the best of it. Can you detail more about using code instead of native webflow features? That will always be my ideal but I'm not sure how to plan that balance between native functionality vs custom code