AI can build a Webflow page in minutes. Keeping it on-brand is the hard part.

Pages drift for four reasons:

- No variables, so the AI guesses colors and sizes - Loose class names, so it keeps making new classes - No section library, so every page is a new layout - No written rules for the AI to follow

If you don't have a solid foundation, whatever you do, you'll end up with a lot of clutter.

Wrote an article about it: https://www.wicked-genius.com/articles/webflow-ai

Variables and strict class naming are exactly what keep Webflow builds clean, AI or not. Giving the AI a section library and written rules sounds like the only way to stop the drift.

Webflow horror story. It was Halloween a couple of days ago, so here's a story about a small UI issue that published a whole new website without any approval. If you've worked in Webflow, you know you can publish to staging and production. When you work on new pages, you uncheck production in the Designer and expect it to be off everywhere. In the site settings, that checkbox didn't show the same state as in the Designer. I was invited to build a few pages for an existing website. After a full day of work, adding new pages and doing mobile breakpoints, I needed to tweak something in the site settings. I did it and wanted to publish right away and send the link to the client. I clicked publish, and then publish again. While it was publishing, I saw the production checkbox was checked. That was a true Halloween moment. Cold rush down the spine. I couldn't revert, because that meant redoing everything I'd done that day. The oldest backup was 3 days old. I reached out to the client immediately. As an apology, I offered a performance optimization: cleaning up old classes and interactions, optimizing custom code, and every other improvement I could make. Moral of the story: don't rush. Check where you publish.