AI Ready Websites for Marketing Teams | Lesson 4: How to Build Websites With AI in Webflow
Watch on YouTubeAbout this video
Welcome to Lesson 4 of AI Ready Websites for Marketing Teams, a free course designed to help marketing teams understand how to use AI more effectively in their website workflow.
In this lesson, we’re taking everything we’ve built so far (your brand guidelines, messaging, ideal customer profile, funnels, and KPIs) and using those building blocks to actually build a page in Webflow with AI.
The key is that you can't just give an AI agent a blank Webflow project and expect it to build the right thing. The better your building blocks, components, and instructions are, the more consistent and useful your results will be.
In this lesson, you’ll learn:
- What an AI agent needs before it can effectively build in Webflow
- Why your AI model needs tool and MCP capabilities
- Why a component library is so important for AI-assisted web development
- How style guides, naming conventions, and components give AI better context
- What agent skill files are and how they can improve consistency
- How to use skill files with Webflow's agent instructions
- How to keep your AI instructions and building blocks up to date
- How to use Grokbot to build a Webflow page
The goal isn't to let AI make every decision for you. It's to give your agent the right building blocks and breadcrumbs so it can work within your existing system instead of guessing.
Next week, we'll look at SEO, AEO, and accessibility and how AI agents can help keep your website healthy and discoverable.
Resources
Chapters
- 00:00 Introduction
- 00:38 What You Need to Build With AI
- 03:51 Exercise: Building a Webflow Page With Grokbot
- 16:08 What’s Next: SEO, AEO & Accessibility
Full transcript
3,789 words
Welcome to lesson four. This is the AI ready websites for marketing teams course and it's built for small marketing teams or mid-size marketing teams that want to use AI more in their websites but aren't quite sure how to get started. This course focuses on using Grokbot and Webflow but a lot of these principles are applicable to a lot of other tools as well. This is lesson four in the course. We're building on some previous lessons so go back and watch especially lesson two if you haven't already.
It's important that you have your Grokbot set up or your LLM set up and your style guide for your brand. So last week we looked at marketing funnels and customer profiles and key performance indicators. This week we're actually going to be building in Webflow and have a real page to look at. Before we get into the exercise here's a couple things that you need. Number one is a large language model. Again, if you haven't gone through the course we set this up in lessons one and two.
I use Grokbot because I really like how it seems to just get things right on the first try. I can use it for my phone. It can connect to all the accounts that I need but there are other tools that can work well. Grokbot uses cursor on the back end because SpaceX bought cursor and then integrated it into their platform. There's the cursor agents that work well in the cloud but there are a couple of other options that work pretty well.
Many of my clients are beginning to use Claude desktop which is a very user-friendly way to go. Claude code is also extremely powerful and it's how I got started and I go back to it pretty often as well. And then there's always the chat GPT or codex offerings. They really have a great desktop app that can use your computer if you want to go view stuff on the front end and have it compare side by side. Each of these tools has different strengths and weaknesses.
Many of them are great in a lot of different situations. Depending on what you have just make sure you have an agent and make sure it has the ability to use tools or MCP. Without that things like co-pilot or Gemini in the browser are not going to be able to use tools the same way and they're not going to be able to build what we need in Webflow. Number two is a component library. I really do not recommend starting from just a Figma file and a blank Webflow project.
You're going to have a really hard time getting the right results. My favorite approach is to have the style guide and the building blocks that we talked about to actually assemble properly from a pre-built system and your agents are going to have a lot better time actually creating what you want without having to go try to fumble along and create custom classes that are not going to be very cohesive. So, that can be really frustrating and it's not a great experience, but it's also because the agent is trying to fill in its own blanks because it doesn't have enough building blocks or breadcrumbs or stepping stones to really know what you want it to do.
We're going to be starting from an already built system that's going to be a lot easier to work with. I prefer the client first or Relume style guide. I prefer the client first style guide and then the Relume component library. And they're two compatible systems. They work really well. There's been a lot of great work put into them and they're really good for agents. They are both great building blocks and stepping stones for any sort of AI tools.
The third optional requirement is an agent skill file. So, I'm actually still experimenting with this myself. I think this is something that's changing all the time, so it's hard to lock down an actual file that's always going to work for every situation. But, really a skill file is just a set of instructions and it can just be a text file or markdown file. It's instructions for your agent to properly use the tools or building blocks that it has to try to get the results that you're looking for.
So, it's a way that you don't have to continue to repeat yourself and try to just always run into the same issues. You can write it down in the skill file and hopefully some of those common issues won't come back up again. Some of the things I have in my skill file are common Webflow issues like using styles that don't show up properly in Webflow or framework specific instructions like how to work in Client First. I also recommend that you store your skill files actually in Webflow.
Webflow has a new feature called agent skills and you to write down the content that you want right in Webflow on the back end and then if any of your agents or MCP connections run into that, they're going to pick up that skill file and bring it into the context automatically and you don't have to worry about remembering to trigger it or passing it along to another person on your team. If they have access to Webflow, it's going to be found right in the right spot.
I recommend keeping it there, but just be aware that it won't be automatically updated. So, it's important to periodically review to make sure that it's not going out of date. All right, let's jump into the exercise. We're going to be building a page in Webflow with Grockit Bot based on some existing components. All right, welcome back. Once again, I have not done anything with the Grockit Bot between last week and this week. So, we've got an update here.
It says, "Introducing primary bot." This is a just a new update that they've allowed one bot to sort of be the head honcho. So, let's just choose an existing bot and we're going to use Chief of Staff. That's how we've been using it anyway. This bot will be more proactive and it knows now that it's in charge of everything. Some of the content here, I actually have told it to stop because I don't like when I do a call, it'll say, "That was a great call.
What do you want to do next?" And I'll say, "Just leave me alone." Let's look at these review. Here's some of the ideal customer profile things. It's talked about a couple of different things that I could comment on or ways that I could find new customers. So, this is cool. Some of these are, you know, pretty ideal customers for me. Once again, this is really something that I'm using myself as an example, but when you build this for your own website, it's going to have different content.
Don't expect it to look exactly like how mine looks. Uh let's see, KPI nerd. Again, all of this is placeholder data. Let me spend a minute or two on mute and I'm just going to try to hook up a couple of things and we'll see if we can get some better analytics here. And I want to make sure that my website is also connected. So, let me just do a couple of connection points. All right, I've got my analytics connected and I reviewed some of the other bots real quick.
Let's go ahead and create a builder type bot. All right, while the Webflow builder is working, let's talk about Webflow components. What we're going to do is use the Relume library and we're going to find a couple of new components for roughly what we we to use. And this is a great starting point because it keeps us from having to build stuff from scratch, and it keeps the agents from spending a lot of tokens recreating things that are already existing.
This is a paid product, but I really enjoy it. It's really served me well for many years. And they're keeping up with a lot of good AI technology, too. We can browse to find the content that we want. We'll just find a couple of sections that look good, and we can bring them into Webflow. I'm going to copy this section, and we're just going to paste right into Webflow. I have the Relume plugin installed, as well. It's going to sync the classes, and right away it's going to come in with all the styles that I've already defined, all the colors, and it's going to have this header 15 prefix, which is great.
And then what I'm going to do is I'm going to create a component, and I'll allow Webflow to create the different properties, because this is just a nice way to do it. And we'll just say header 15 component. And then what we have is this whole section is now a component. This is a really easy way to work in Webflow, because everything is modular, and again, like those building blocks that are going to work really well. And then we can just edit the particular pieces that we want to edit, and not have to worry about layout or other alignment stuff.
That's all been handled with the Relume component library. Okay, so we got a hero section. Let's do a feature section. I'm looking for a couple specific things. So, what we have here now is a page with some sections that are sort of pre-built, but also not quite complete. And what I'm going to do now is I'm going to work with Grok Bot and talk about each one of these sections. So, this is my preferred workflow is to go one section at a time and do what needs to be done to that particular section.
And that's another great reason to work in components, because then the AI is scoped really well to that particular component, and it doesn't get confused with the rest of the page or with other pieces even on that same page. So, let's work in this component. Let's talk to Rockbot. This is going to be called section header 15. So, I'm giving it a real quick brief about what I want it to do. Now, what I'm going to do is I'm going to pull in the Webflow skills that I've created and I'll link to these in the description as well.
I'm going to pull those in and give it to this builder and make sure that it knows where to go and what to find the specific instructions that I've created. Okay, and I'm going to tell this to our chief of staff, too. So, let's let this spin for a little bit. While we let that work, let's talk about the skills files. And this is a GitHub repo that I've created and I've made it public for what it's worth and I'm always updating it and seeing how I can make it better.
Here's the anatomy of the folder within the skills file. This is where the meat of all the content lives. I've created a couple of different tools here for auditing existing sites, for building specific sections, creating design systems, setting up new MCPs for different clients if you have multiple projects you're working for, and then building plans for how a Figma file could be converted into a Webflow site. sometimes I find it helpful to build a prototype in HTML instead of going right into Webflow.
You these skills are here, you can click into this and then actually read the information. And then I've also created some files for how Client First is supposed to work and I've dabbled into MASS a little. I really far prefer Client First. This is not super cohesive or complete, but I'm working again on improving these all the time. So, this is a great Client First skill. It matches what we see on the Client First style guide and like the Client First documentation.
And then finally, I have a list of common issues that I've run into in Webflow. Sometimes it'll do crazy things like it'll try to put an image inside of a paragraph where it doesn't belong or it'll use images instead of a bullet point. Uh sometimes it it just puts things in the wrong spot. As the MCP improves, I'm sure this will get better and better. For now, this file is going to be try to kept up-to-date with some of the issues that I've seen.
So, it says the Webflow connector is not connected. Let's try this again. I'm going to hide this screen cuz I have client work that's going to come up. All right, authorization complete. First of all, it makes itself a brief for what it's supposed to be doing, and then it's going to start to connect. We should be able to actually see this work as it happens as well. So, I'll keep this screen up. Uh once it connects, it's going to run, and it should be working in Webflow here.
All right, let's see. We've got the review. Uh this is fine. This is just the same content that was already there. This is great. Webflow builder now has updated instructions. You can also edit the instructions of the bot. I'm going to change where it lives. You used to be able to actually edit the bot instructions, but it looks like the chief of staff or primary bot is the one that's going to be giving the instructions. One of the things I like to do is is to either tell the bot that it's allowed or not allowed to publish to either staging or production.
And it's super useful to say, "Publish to staging, open on the front end, and review your work, or compare it to the Figma file, or send it to me, you know, send me a screenshot." You can do this stuff from your phone if you're really on the go. You can say, "Make this change, publish to staging, send me a screenshot on desktop, and then review it on your mobile phone of what it's going to look like on desktop." And then you say, "The color's wrong, the font's too big, etc., etc." Give it all your feedback, and it'll just go through the loop again.
I really like this tool. Again, this is one of the main reasons I prefer Grok bot because you don't have to worry about any of this setup, any of the setup for how that will work. Like, if you were trying to do this with code Codex or Claude code, you'd have to set up a virtual machine all on your own. You'd have to have a desktop always running or computer always on or server, and you'd have to give it all the browser skills and everything.
This just really seamlessly works really well, and usually it doesn't log me out all the time, but this is a secondary Grok bot account, so that could be part of it. I've really I've had a great experience with this whole tool. Another thing that I do is I kick off a plan like this, and I would go do something else. So, I would be working on another client or reviewing work from another agent, or I'd be on a phone call, or I'd be going to lunch.
All these things, they end up taking 5 to 10 minutes sometimes for the runs. So far, it's not fast enough that you can just sit here and watch it work for the most part. For this tutorial, we're just going to do this one section, but the process is going to work for everything. Probably what I'll do in this short video, just to keep it from being an hour long, I will probably build the first hero section, and then we can talk about what's happened, and then I'll continue with the build off the camera, and we'll come back in the next lesson if we want to review.
So, I'm actually going to send a message to see if it's stuck. Yeah, and so I did give it quite a bit in one prompt, especially reviewing like going out to Unsplash, finding an image, reviewing all these skills. And this is the first time that I'm building in Webflow here, so it makes sense that there's a number of things that it has to do first. I do wish that it would tell me specifically what it's doing. The Cursor app will give you a a couple more specifics of where the agent is in the process, what it's doing in the background.
In the interest of trying to keep this simple, I believe they've just sort of streamlined what this text says. I have noticed that it'll hang sometimes. There's probably one in 15 where it'll get stuck because I've given it such a large task, or sometimes I'll have multiple bots messaging back and forth, and something will get dropped. They are constantly improving this tool. It has gotten a lot better. Sometimes you might need to send it a little message to see what's going on.
All right, right away we can see that this hero section is dark, and it's been renamed, which is nice. It already has also used the correct button styles, so is alternate. I didn't have to change that at all. The original button style, it was just button. When you want to have it on a dark mode, we need a combo class called alternate. That was already created in the style guide, and the bot successfully found it and applied it to make this dark mode.
So, that's really nice. I believe I have a dark mode, but I didn't include that in the instructions, so it wouldn't have known that that was necessary. It's already done most of what's going on, what I've asked it to do, and it's correctly renamed things. It's got buttons properly, and it should be finding the image as well. The real next step in this process is to say to one of the writer bots, I want to build a page specifically for finance SaaS platforms.
Please help me. Let's do it right now. Okay, great. And there's Unsplash image as well. Now, this design pretty much does make sense. We'll keep that there. One of the things that's really useful when I work with my clients is that we have a way more robust library of content and sections. That's another thing for larger teams that this tutorial isn't going to capture all the way cuz my design system is quite simple. I have a pretty standard site and I don't need a ton of different variations on content.
Again, this is why it's worth putting in that work to get these building blocks for your brand because once we have five or six options for a hero section and four or five footers and sec- and just other sections that are available, then we're really going to have a ton of flexibility. We could start a process here that says, "Write the page and then build it in Webflow." Maybe we'd create a bot that's either page builder or campaign manager, maybe what I would call this bot.
It would say, "Talk to the Donald Miller, the writing bot, and then use the Webflow builder building bot and create all those things in one fell swoop." That's just another way you can stack all this stuff. Uh, here we go. Hero problem strip guide proof what you get plan fit check. There we go. This is a more in-depth process. If there's time someday and I'll probably build a longer course where I actually do all of this on camera, but it would take about an hour if I did this all right now.
In the interest of time, I'm going to leave this here. This is a real brief overview of how I build these sections. Usually, I start from Relume and then when I need to make tweaks, I can go into the section. Okay, let's review this real quick. Named it. Buttons and images show up. Okay, so it was disconnected cuz I started fiddling with it. As it was working. Cool, it renamed That's really great. I'm really happy about that because otherwise they would all be called header 15 still.
So, it's really nice to have the code itself clean. No dark mode variables, that's correct. One thing we might do based on this is say, "Create me a dark mode for my variables." Buttons, yep, use existing classes. I noticed that as well and I told it to set the links but not the text. So, that could be something I do. It picked an image. Then it's saying some of the section properties that are created here are not properly connected.
This is again, you can do this entire workflow from this bot here. Instead of having to manually code everything, you can really just talk back and forth to your bot and tune up the section. My recommendation is always to go section by section, get the base section from somewhere else or just be very careful when you're building it. If you do want to try to assemble it from scratch, get a section completely right and make it into a Webflow component like this.
And then when you're working, you can say, "Use the section hero split dark component." instead of having to say uh copy this Figma file or make me a random hero section. I'm going to leave you with that. This is going to be a real quick overview. Again, in real life, I would be doing this probably probably would take me an hour to finish it all. In the end, we'd have a great page that would be perfectly tuned up for SaaS platforms.
So, I'll probably have that run in the background and we can come back to it on our next video. Next week, we're going to talk about AEO and SEO, how your website can get found and stay healthy. We'll also cover some QA and accessibility issues. Thank you again for watching and we'll see you next week.