Matthew: Welcome to the Restock Podcast by No Code Supply Co. where we highlight the people, the things they build, useful tools, visual inspiration, and conversations to fill ourselves and ourselves. I'm Matthew. Corey Moen: And I'm Corey. What's up y'all? Matthew: Well, everybody, thanks for tuning in. We've got a special episode, I guess. We're gonna talk about Webflow conf and some of the announcements there. Corey Moen: Okay. Matthew: And for those that may not know, I do work at Webflow, so I do wanna state that up front. mostly we're just gonna be checking out Corey's reaction to everything. Corey Moen: As an ex-Weblowboy. Matthew: Right. Corey Moen: But I think irregardless, right? We both have used that tool for a long time and just generally built websites for a long time and seen so many different ways that people build out there in teams and for clients and all that stuff. So I just think there's so much of what was announced that Is relevant to all of that. You know, even even just like is relevant of the times, regardless of web flow. It's really fascinating to see how products like Webflow are taking their own perspective and take on how to put all of these new ways of working together alongside agents and, you know, all these other toolings and instructions and skills and MCP and et cetera. yeah, it's it's a lot to wrangle and make sense of where to, you know, spend the time. But Matthew: Yeah. Corey Moen: yeah. It's interesting. Matthew: And I'll bring it up later, but some of this stuff is things you and I have envisioned and talked about for years. So it's it's Corey Moen: yes. Matthew: it's it's pretty exciting that you know it's becoming reality. we're getting there. So Corey Moen: Mm-hmm. Mm-hmm. Matthew: let's just kind of I first I want to touch on there was a there were two keynotes because there were so much announced. And one that's probably near and dear to our hearts was the second one, which is the builder's keynote. And a lot of this is stuff that's shipping immediately or very soon or slowly rolling out already. And so I thought let's just kind of go through this builder's keynote real quick, before we kind of get to the main topic, which I'm sure people are waiting for, which is the new platform called Source. Corey Moen: Mm. Matthew: All right, visual editing for AI code components, code components, Very nice feature. but now you can actually edit those designs by, you know, visual editing the way you're kind of used to in Webflow. So fine like here. Yeah. Nice little Corey Moen: Heck yeah. Yeah, it's Matthew: quality of life thing. Corey Moen: for sure. And I mean it's it's definitely something that also makes this feel a lot more useful or less tedious, right? Like in in any of this, including source that we'll get to is just like the the premise is that you know, maybe the majority of work is moving to asking an agent to do it just like with this, but still having that like individual polish edit. thing is so useful. Matthew: Yeah. Those fine tuning kind of that last mile. You can often do it faster manually, yeah. Corey Moen: Yeah. And the thing I totally the thing I missed in this one was when you make styling changes, can you still bind to variables and stuff in the project? I wonder. I wasn't sure if that or if it's mostly just like styled specifically to that component. Matthew: The styles are still within the AI code component. So these are Corey Moen: Right. Matthew: these are React islands in your Corey Moen: Mm. Matthew: Webflow site. So they're isolated in that sense. So when you Corey Moen: Mm-hmm. Matthew: initially build them up, they will reference your design system from the site. But then after that, Corey Moen: Okay, interesting. Matthew: if you want to adjust things, you're gonna be basically doing it within that island, that AI Corey Moen: Red. Matthew: code component itself. And so this just makes that iteration process easier. Or if you made some updates to your design system and you need to kind of come back to the component. Data it makes that easier. Corey Moen: For sure. Also, I see we got community hang in here. Ollie, maybe joined in. Matthew: Right. Corey Moen: We we should have prefaced too that we put it out in the no code supply code Slack. if anybody wanted to join and talk about reactions and thoughts, it was Matthew: Yeah. Corey Moen: open for them. So Ollie, what's up? Whenever you get a Matthew: Yeah. Corey Moen: chance, no worries as audio and video and as all all that's getting hooked up. Matthew: This is actually a pretty impactful one here. This is components Corey Moen: Heck yes. Matthew: in CMS, but it's actually more than that. It's components in rich text. now Corey Moen: Mm-hmm, mm-hmm. Matthew: most often you're probably going to be using this in the CMS because that's where you're a little bit more restricted for your content editors and stuff. But now they can safely apply components right there. A few restrictions, Corey Moen: Totally. Matthew: they can't be components with CMS or slots. at this time. They kinda need to be static components so we don't kind of end up in these weird situations where you get loops of data and content. But yeah. Corey Moen: Yeah, this is, I mean, this is huge though. Even the simplest example of like, I want to put a button in a blog post body that goes to something, right? Like used to be a big pain of like, throw it in an embed or something. Like Ollie, I'm sure maybe you've seen that even with client work and some of that. Ollie: Yeah, absolutely. I was just speaking to some folks about how you could kind of use the rich text element like anywhere on a CMS page to kind of drop a component in. So it's Matthew: Yeah. Ollie: not necessarily like, hey, inline CTA or anything like that. You could go kind of full ham with this. So yeah, it's cool. Corey Moen: Heck yeah. Dude, love it. Also, do you want to do a quick intro for who you are and what you do? Cory Runnells: Mm-hmm. Matthew: Ollie, yeah. Go ahead. You want to intro yourself? Corey Moen: Ollie, yeah. And then Corey, who is also here. What's up, Corey? Ollie: yeah, hey folks, it's Ollie McMillan, independent dev masked enthusiast. And yeah, Corey Moen: Ho ho Ollie: there you go. fan of the podcast Matthew: Mm-hmm. Ollie: as well, so Corey Moen: Love. Thanks for Matthew: Yes. Corey Moen: coming, dude. Corey, what's up? I haven't seen you in so long. The goat. Cory Runnells: I know how's it how's it going? I didn't exp I didn't expect my face to be seen as like I'll just drop in and peek from behind the curtain, but Hey everybody. Corey Moen: no. Dude, good to Matthew: Welcome. Corey Moen: see you. Matthew: Breakpoint canvas. So we that canvas was introduced recently. Yeah, Ollie: Yeah, hot stuff. Matthew: now you can actually see more things on the canvas than just the single view. So now you get all those side by side. Ollie: Mm. Matthew: Sh check Corey Moen: This Matthew: that responsiveness out. Corey Moen: I I'm on the fence in this one. I think Matthew: Mm. Corey Moen: I think I'm too stuck in my ways of just like I don't I've never really liked that from even like like Framer and tools like that. I'm like, I don't like Matthew: Frame or inf. Corey Moen: I don't I don't really care about that. I would rather just see it as I normally see it in the browser and resize, but Matthew: Mm-hmm. Corey Moen: I totally get the point of like having a quick way to quickly scan a page and make sure that nothing's like overflowing or clearly broken in one go instead of having to like click through and scroll around, but I don't know. Matthew: Yeah. Cory Runnells: that last thought was just my why I like it, just I want to have that quick reference, like to see if like man, I forgot to go change the flex layout of these columns or something and Ollie: Hm. Matthew: Yeah. Cory Runnells: instead of having to toggle back and forth. Matthew: I do think Corey Moen: Totally. Matthew: that is where it can shine is when you're checking, especially like in grid and flexbox, how things are actually working at the different breakpoints. So you can make sure that layouts aren't breaking anywhere and you can do it, you know, see how the cascading controls are are working. And then also for things that are conditional based on the breakpoints, you can actually make sure that those things are happening as you've defined them or expect them to. Ollie: Actually a big fan of like canvas mode because I find I'm constantly flicking between a a designer's Figma file and Webflow and to kind of have like the same behaviour, I find really useful. but it is more for like a kind of bird's eye view like content dump first and Matthew: Mm-hmm. Ollie: then I'm like going into the kind of full mode as it were. 'Cause you get you get some really Corey Moen: Mm-hmm. Ollie: weird viewport height behaviours when you're in canvas mode because it's like I don't know what the viewport height is. So Corey Moen: Yeah. Ollie: yeah. It's fun. Corey Moen: Interesting. Matthew: I also think it's good for for those who may not really understand how CSS inheritance works and Corey Moen: Yeah. Matthew: how breakpoints work, you can actually visualize it a lot easier Corey Moen: See it Matthew: as you're learning. Corey Moen: for sure. We got another new person. Derek, what's up? If anybody watched last episode. Matthew: Hey Derek. Derek from last week's pod. Derek: Yo. Boys. Corey Moen: Need need no introduction. Also, Corey, I didn't give you the chance to intro if you want to who you are, what you do. Derek: Low man himself. Corey Moen: Ha ha Cory Runnells: Yeah. Xflow man. No, yeah, I'm Corey. I I work at Webflow now. I'm I'm on the solutions architect team. So this has Corey Moen: Woo! Cory Runnells: been a this has been a fun week just getting to experience I didn't get to go to conf, but just getting to experience the other side of things. So it's it's been fun. Corey Moen: Totally. Cory Runnells: I was I was just gonna say about the the breakpoint canvas here, like what does it look like for those sites that have like four Four additional breakpoints added, like is it just pure chaos? Matthew: It's a lot to pan and scan. I mean, they're they're all there. Cory Runnells: Yeah. Matthew: Yeah. So you could have what, up to seven breakpoints side by side if you've added all the larger ones. Cory Runnells: I I also when they made this announcement, I in my head I was like, Are people cheering because they finally think they're getting like breakpoint controls? As in we can change the values of what the breakpoints didn't Matthew: Custom breakpoints. Mm-hmm. Cory Runnells: did any of you think that and hope that's what it was or Matthew: personally, no. Like dump dump breakpoints, container queries are where it's at. Breakpoints are old hat. Derek: Yes, yes. Matthew: Like stop using them over relying on them. Derek: Yes. I think anytime I open up a well flow project and it still has like the custom breakpoints, I was like, This is gonna be a nightmare. Matthew: I remember when there was a phase of development, people were doing custom builds and they would do breakpoints like for each like device that was popular Corey Moen: yeah. Matthew: at the time. my gosh, that's just so much to maintain the overhead of that. And now you just got a mess. That's worthless. Ollie: Everyone's had Derek: Yeah, what Ollie: that sad experience. Derek: point is your site not responsive then? Ollie: Yeah. Matthew: Yeah, it's like you might as well just define every every Derek: Like it's just serving up device queries. Matthew: pixel width, right? Just keep stepping up pixel by pixel and Corey Moen: the thing with container queries, I would say though, is they're like A, are they fully is there full browser support depth? And B in Matthew: believe so yeah. Corey Moen: Webflow specifically, there's still no way to actually work with them, really. Matthew: Not in web flow, the classic web flow you know and love today that we're looking at. We'll get to the future in a minute. 'Cause Corey Moen: Is that is that the name now? Classic Webflow and Webflow source? Matthew: It i Derek: What what flow classic? Matthew: it is it is officially Webflow You Know and Love today. That's the official name for for Webflow today and Cory Runnells: Yeah, it's a mouthful. Corey Moen: I love it. Just like classic interactions. I remember I remember at the time Matthew: Ha ha. Corey Moen: when IX3 was coming out and there was all this back and forth internally on naming. Matthew: There is no IX three, it's interactions with GSAP. See, you're you're getting me wrong still. Ollie: Ha ha Corey Moen: I still call IX3 because why would we Ollie: Yeah. Corey Moen: not version? I don't know. It's yeah. Matthew: Because it's be well, it's who's naming it? Is it engineering and versioning or is it marketing and you know? Okay. Corey Moen: hundred percent fair. Derek: yeah. What I love about this, just full transparency, guys, I love that like we're peeling back that layer. Like witnessing this and hearing from you guys, it's just there's so much, right? Like I've I've said my comments on X, like you can read them, you don't need to read them. They're my thoughts. But they are, you know, they're unfiltered. They're also uneducated of like what actually is happening behind the scenes and what you Matthew and you, Corey, and you, Corey, have all like witnessed and are going through, right? And like me and Ollie, what's up, Ollie? Like me and Ollie are just like, you know, we're just making assumptions and thoughts as we go and we're only we only know what we know. Matthew: You've never worked in the kitchen, you've only been patrons eating the dishes we Derek: Yeah. Matthew: serve. Derek: Yeah, we're at the dining table wondering where our dish is. Exactly. Ollie: Yeah. I like that. Matthew: You're at the chef's table today, so buckle up. No, I'm just kidding. Ollie: Yeah. Derek: We're getting sushi served. Let's go. Matthew: All Ollie: Nice. Matthew: right. next one, popovers. So this is a kind of part initial piece of a larger piece of work, which is to bring more modern HTML elements into Webflow. And so this one is popovers. lot more flexibility than kind of the current drop downs and it's also more accessible HTML and all that goes along with it. So any Corey Moen: I mean, Matthew: thoughts? Corey Moen: I think this is great. I think anything, anytime the platform is embracing the actual latest capabilities of HTML and CSS is a win. So I my assumption without knowing is to is to your point, popovers is one, but hopefully other things are coming, like dialogue, and I'm drawing a blank on what the like accordion Ollie: Details to marine. Matthew: Detail. Corey Moen: yeah, detail summary, some of those are all coming. yeah, right there it says modal yeah. Matthew: Let's see right here. Yep. So it was mentioned in the builder's keynote. So sliders, tabs, accordions, and more. So Corey Moen: Nice. Matthew: sounds like some updates and some new things to look for. Cory Runnells: I think yeah, I think it's just nice to have more native things with kind of accessibility baked in because I still think there's plenty of people using the product that don't think about accessibility. So if you think about how we've had to build modals in the past, like what's a percentage of people building them actually making them accessible? That's probably pretty low, Corey Moen: Yeah, low for sure. Cory Runnells: right? Corey Moen: Yeah. This is the nuance though, where like then you start to get into the territory of like if you're building with mostly agents on top of source or it, you know, using source, then like agents, at least some of the latest models have already gotten really good. Like you don't even have to ask. They will build things so that they're accessible, usually by default. yeah, always do that. Focus styles, Derek: They they always do the reduced motion. Like they always do reduced motion. Yep. Matthew: By default. By default is Corey Moen: keyboard for sure. so it's like at what point does the platform have to try to accommodate that? Or if you move more agentic in your development, one way or another, it is just accommodating that for you, you know? Matthew: Yeah. It's it's about accommodating people at different levels, right? Because Corey Moen: Mm-hmm. Matthew: you could do this in Webflow with custom elements yourself or even with embeds before. Yeah, it's just it becomes easier, it becomes more accessible to people who don't know how to build things accessibly or with the correct semantics. You know, now it's baked in for them to easily do what is designed and not have to go through all that process. Derek: It also keeps it v actually visual, which is the whole purpose of the designer. Matthew: So yeah, exciting stuff, new elements. That's haven't had new elements in quite a while. So this is this is a big one here, if you ask me. This is one of the biggest ones, most impactful ones. Default components for slots. So no more dragging a component and it just has an empty slot when you put on the canvas or when the marketer Derek: yeah. Matthew: puts it on the canvas and you have to, and Ollie, I know you do this, right? Where you name the component or the slot, like insert such and such component here, right? Don't you do patterns like that for your? Yeah. Ollie: Yeah, as much as as a valiant effort it is, Derek: Well hey, the mass framework now has that built in. Plug plug. Corey Moen: Well, the other Ollie: Yeah. Matthew: It does. Yeah, there's Corey Moen: the other way around. Mass they just released before comp the scopes, right? So like you can limit what components this will be the defaults, right? Like so a r anytime you add a row, it Matthew: This is like the final piece of day. Corey Moen: should always have a column in it, for example. Yeah, yeah. Mm-hmm. Derek: Gotcha, gotcha. Ollie: Something to add to that though is that I foolishly was like, amazing. What I'll do then is I'll create a page main component with a slot and scope sections to it. So then that way the client always starts with a section. And then I've quickly discovered, I need a page slot to then put this in. And then the client was like adding sections outside of this page main component that I made. I was like, no So I I quickly requested that we added like could we add slot restrictions to page slots as well? I I don't know. Or whether Corey Moen: Right, right. Ollie: like you just kinda ditched page slots and create components with slots. I don't know. I'm not sure but yeah, I was like went down a a rabbit hole there and then got punched in the face. Corey Moen: This is generally great to see though. I'm excited about this. Between this and the restrictions, the combination is the is the the the real value, I think, in just like Matthew: Absolutely. Corey Moen: not only making sure people don't use the wrong things in the wrong place, also just to like save you time, right? Like if there's only one option to pick, you know, or it's already there, you're just saving your time at every single step. So why not? Matthew: Yeah. So what has already shipped that this is adding to? So this is kind of three pieces that make a more full picture. So you have component visibility controls. So that's saying that marketers can even see this component because like it may be a row or a column, you know, something that's more of a primitive component that devs use that marketers don't need. So you have that control to hide that from them, them seeing it at all. And then you have the slot restrictions, which is what you're talking about, where you can say, This slot can only accept these components. And then now the third piece of this to land is default components so that the slots aren't empty to begin with. So even though, like in this example, the button may be the default component that's inside that slot, the marketer could add an additional button or potentially any other component that you've allowed for them to put in there. So they're not. restricted to what the default is. That's just a starting point for them. All right, let's go to the next one. Agentic translation. So I've seen some misunderstanding about this one. So what this is, this is automatic translation or continuous translation. So whenever you update a page, the locales will get updated automatically. We've had machine translation for years in Webflow for locales. This just makes it automatic. So you don't have to manually go into each locale and, you know, like right click, chan translate this page or translate this piece of content. That's just gonna Corey Moen: Mm-hmm. Matthew: automatically happen in the background if you have this enabled. Corey Moen: Is there, I forget, is there a way to steer the translate the the agentic translation? Like, like you can I I wanna say, wait, it says right here in the localized tone informality, localized custom code. and properties control available. Yeah, so like basically, you know, is there a way to inject glossary terms and style guides? natively that the agent is referencing when processing the translations and yeah, I think you just said yes. I know that glossary existed before. I didn't know it's style guide. Yeah. Matthew: Yeah, the glossary has existed, actually brings up a good question I don't have the answer to, and that is with the agentic instructions, which is another new feature we'll get to. If that Corey Moen: Mm-hmm. right. Matthew: works with locales as well. if you're working through the MCP, it should you should be able to have it do that. But if the I'm not sure Corey Moen: For sure. Matthew: if the automatic translation refers to those instructions or not. It's a good question. Corey Moen: I will say I'm I know that, you know, not every site, especially smaller sites, are localizing. And I'm by no means an expert in this, but the more I've been involved in the last year or year and a half, my goodness, I am so here for this. I think it is 2026 and it's pretty mind-bending to me. Some of the traditional localization processes that exist out there where we're doing like We update a page and then manually, you know, the a vendor, you know, it exports everything, processes it, translates it, re-imports it, reviews it, like the lifecycle is gnarly. and I get it for like really, really high importance pages and high traffic pages on a typical big site, but like for the vast majority of content, it just seems like overkill. And like, why would most people, most teams not opt for something like this? especially if it's still within a steer bill control, right? Again, you are it's not just doing everything out of the box. It is doing it with some way that you can constantly refine the terms that it's using correctly or not, you know, the style that it's using and all that. Like, and then it's just especially the that the option, the continuous option, like, my goodness. So then you don't have to worry about if some, you know, marketer goes in and changes a sentence on a page and Matthew: Yeah. Corey Moen: then that bleeds English into 20 locales. And you don't even know about it. Matthew: Or the opposite where it's like we updated the primary and then the locales stay out of date, like so yeah. Corey Moen: yes. Yes. Yes. So so like what's really, you know, the value then if like all the secondary locales aren't even up to date or, you know, is half the size of a site because you've only localized half of it. It's like to me, that's just why would I not just leave it so that anybody in other countries can just use Google Translate built into Chrome or many other browsers to just translate on the fly? I don't know. Spicy take. I'm just here for this feature. I think this is a great move. yeah. Matthew: Well, I think because as a brand you get that control to say, never translate these words. These are like our brand words or you know, words within our product or a company, you know, that Corey Moen: Mm-hmm. Mm-hmm. Matthew: should never be translated. Or if you translate it, you know, here's the word you should use for the translation. You just get that control. Whereas if you're just letting your visitors do their own translations on the fly, you're just not gonna have control over that. And also when talk about AEO and serving content up to to the LLMs, like having it pre-translated, you know, you're gonna reach, I think, it further into those markets. Style props for components. This is one that was announced by the community's own Timothy Ricks on stage. nothing to show for this one yet, but just pointing that right now we have data props. we're soon gonna have style props. So more than just variants, you can actually give your marketers specific style controls. So if you want them to be able to switch between two different, you know, colors or different things, like they they can have those kinds of controls at the component Corey Moen: This Matthew: level. Corey Moen: this this was one I'll have I guess I'll have to see what it looks like because I I my brain weights goes straight to well what couldn't does this need its own type or couldn't this just be like we can have more than one variant as long as there aren't styles that collide between one variant and another or Matthew: It it's when you want to give more granular control than a variant. A variant is like Corey Moen: Mm. Matthew: a group of applied styles, if you will, and p potentially even Corey Moen: Hmm. Interesting. Matthew: layout and DOM changes. Wh whereas Corey Moen: Interesting. And Matthew: this is specific dials or controls for specific style properties. Corey Moen: Okay, okay, because I was gonna say that you can also already do like a style attribute and they can modify that string, but obviously that's not very client-friendly. So to your point, it's a UI. Matthew: Right. So just think of yeah, taking whatever you would have done there with a style attribute and having a visual control for it instead. Corey Moen: Love that. Love that. Ollie: I was saying I caught Tim off the announcement and he was like, Yeah, Matthew: go for it. Yeah. Ollie: goodbye style props. So he's very Corey Moen: Ha ha. Matthew: Okay. Ollie: happy that this is kind of in the pipeline. Matthew: well lots of performance updates. So if you're working on a big site, lots of components. Corey, I know you felt this one. very welcomed. Performance is a feature, updates. get to enjoy those every day. Corey Moen: Yeah, especially with all the component features and all that. I feel like, you know, the this as more of that came out, big projects got slower and slower. But even in the last, I don't know, month or so, there's I've yeah, personally seen a lot of turnaround and improvement in this in big projects I've worked on. yeah, I'm it just it's also one of those things that it's like if this is this is like bare requirements, y'all. Matthew: Mm-hmm. Corey Moen: There are so many other tools and platforms out there that are built on newer stacks and they are snappy. Like it is wild how performant software has gotten these days. And more and more of those that are that fast. And and and examples might be things like Notion or whatever that like are still can be really data heavy, but still very performant. It's like the more that grows, the more this becomes more important for Webflow and anybody making software, in my opinion. So I think this is just cool that they called it out and are still focusing Matthew: Yeah. Corey Moen: on it. Matthew: Yep. All right. Let's get to the big big ticket items here. So this these are items that were mentioned in the main keynote. we're gonna save source for the end. this one's this one's for marketers campaigns. So this is a standalone product, so you can build individual campaigns. So Even if the main kind of dot com website is not on Webflow, brands, companies can use campaigns to do to do one-off stuff, one-off work. And it's more of that marketer kind of editor view of Webflow. So it's still kind of the core webflow classic, but in the marketer view with a little bit of extras, they have access to analytics. Component props and kind of the brand system. So the brand is actually extracted as part of the flow. And then you go and you actually build a campaign brief, and then everything is generated from there. So nice little product for marketers. But for most of us who are watching this as builders, it's not going be something we're going to use, but it enables marketers to be able to build safely with the components and the styles. Corey Moen: I think the one thing I would note on this one that I didn't I don't know if this is the intention or not, but one of the other updates here is releases. And this is the combination of these, is where my brain goes, but I have yet to see I think teams actually do this in other platforms like Sanity. but you know, when you think about big launches that happened at companies and using a feature like releases, and I think where campaigns is going. to be able to not just ship one or new multiple new pages on your site at the same time, but also ship social posts, emails, you know, et cetera, et cetera, et cetera, all from a single button, basically, like is where mind my brain goes with the like potential behind something like campaigns and releases and like that whole ecosystem living in one centralized control. yeah. Matthew: Yeah, absolutely. And part of what campaigns has access to is the new assets product. So Corey Moen: Mm. Matthew: it's the second of the new products, which will won't just be available in campaigns, but that's kind of the first place you'll see it appear. And so that's where you can have all of your approved assets, but then marketers can actually turn those into, like you said, social social images or or media. So it works with with images, it works with video. And you're able to use AI to edit and generate content as well. So this was the Videoso acquisition that happened last year. And so this is that technology being applied in what? Corey Moen: Do you know if this will come with URL control? AKA can I finally have an asset on the same domain as my website in Webflow? Ollie: that'd be cool. Matthew: I I actually don't don't have Corey Moen: Ha. Matthew: the answer for that one. Ollie: Yeah. Matthew: I wish I did. yeah, yeah. Corey Moen: Slip in the request. I I think that that is my my broad thing too is like I think a dam is great, but if it's just another way to view and edit images and videos, like to me that's that's like leapfrogging the real underlying value of like governance and and like full control over how the world consumes the assets via a URL. Or some of that, you know what I mean? So hopefully we'll see some of that coming. Matthew: we'll learn more about assets as it as the release gets closer. Corey Moen: For sure. Matthew: some updates to AEO. So new content creation, so new agents that that yeah, that generate briefs and help you write new content. So actually I have seen this. so it'll actually make recommendations to you, which is what we're seeing here. So create content for website. content for freelancers, it's suggesting it and you can say, yep, go ahead and generate a brief based on the analysis it did for your existing content, competitors, the market that your company is in. It will make those suggestions. And then you say, yep, write me up that brief. And then once you have the brief, then you it can actually go through the process of generating that content. So this is a new recommendation engine inside AEO insights. Corey Moen: Love it. I think the thing in the blog post that was interesting is it it sounds like part of the way that it's doing these suggestions is it's actually polling or doing something to get data from ChatGPT, Claude, Gemini, and Perplexity to Matthew: Uh-huh. Corey Moen: know how your brand is actually showing up there, which I thought was actually quite interesting and not necessarily like completely novel, but very much you know, a helpful, useful tool that you would have to go elsewhere for. Matthew: See where you're cited, where you're not cited, and and figure out how you can improve Corey Moen: Mm-hmm. Matthew: your content. MCP two point one. So two point was actually not that long ago, but I think the big one here is interactions with GSAP, not IX3, Corey Moen: Mm-hmm. Matthew: but interactions with GSAP. yeah. Through through the MCP. So It's pretty exciting. So you can have have your AI generate GSAP and then edit like fine-tuned control edits directly in the designer using the timeline. Corey Moen: Hmm. Super cool. I I would assume hopefully too this also goes with binding interactions to elements. So you could be like, hey, find every instance of this component in the project and go edit it and, you know, or apply an interaction. Maybe a component's a bad example. But you know what I mean? Like being able to also set those globally as like a bulk operation would be super cool. Matthew: Yep. CBD, we'll we'll find out. Like I Corey Moen: T V D if that's actually possible. Matthew: actually haven't tested it out, so we'll find out. and then also better CMS querying and Webflow Cloud. Nice, nice. So you don't have to just use the CLI for Webflow Cloud. And then releases, you kind of mentioned this. This is think of it as site branching, because that's what it is. It branches your entire site, and then you're able to make updates to various things. So that could be components, it could be content, CMS pages, it could be design systems. So you're making all of these independent changes and wrapping them up in a release. Whereas, you know, currently today you can do single page publish, single item publish, but when you're anything else, you're just pushing the whole site all at once, right? So this allows you to have separate areas of work because you could have multiple releases or multiple site breaches happening at the same time and be working on. different isolated piece of work without kind of overriding each other or pushing pushing Corey Moen: Heck yeah. Matthew: somebody else's work out early, right? That's that's dangerous. Ollie: There's a there's a very specific scenario that I'm excited to like try this with and that's during a rebrand. so because I Matthew: Mm. Yeah. It's a great great use for it, yeah. Ollie: am I right in saying that this kind of a release branch will allow you to update variable values because cool. Because that was something that I think was a limitation with page branching. so we would just have to like freeze the site anyway. So this is gonna really be like an unlock for the the marketing teams who say, Don't worry, nothing urgent's gonna be needed for the next two weeks and then literally two days later, we need to put this thing Matthew: Yeah. K Corey Moen: Sorry. Matthew: who can actually freeze publishing for two weeks to like implement Corey Moen: Dude. Matthew: a brand redesign or something. Yeah, exactly. Or if or yeah, speaking about Corey Moen: Hundred percent. Ollie: Yeah. The classic It's Urgent. Matthew: campaign campaign that might touch like lots of items, things around the site, you know, maybe it's adding new like brand theme, you know, so and maybe it's adding changing components as well as new content and pages, you know, this allows you to wrap those up as well. So Corey Moen: The it's it's funny the spectrum too, because on one end, Ollie, like you said, you could literally essentially have a release for an entire for the entire site getting redesigned that you're then merging back all at once or publishing all at once. On the other end of the spectrum is I just want to stage a single blog post. Please. Like I just want to and go into a CF single CMS item and publish it only to staging. That is not possible outside of the API today. Matthew: Well that well, okay. I mean you see it here in the screenshot. There is staging. So yeah. I mean, you could use releases for that. It's a bit overkill maybe to branch the entire site to stage one. Yeah. Corey Moen: Totally. That's what I'm saying. Like today, the only way you could Right. You could you could have a release for just one blog post and it would and you can have multiple releases at once. So you could have multiple blog posts staged or branched, Matthew: Yeah. Yep. Corey Moen: if you will, and then published, right, to a private link. Whereas today, the only way to do it is either to like cue and publish the project just to staging, but then if somebody else comes along and pushes the whole thing live, then there goes your blog post. You know, like there's no way to do it. feasibly today. And the point is that I think it's really interesting how a feature like this solves for something as simple as as that all the way up to the like huge spectrum site overhaul type of idea. Matthew: Yeah. And I think there are plenty of companies that I mean you have to be aware of kind of content leaks. And if Corey Moen: Mm-hmm. Matthew: your staging domains, links are Corey Moen: totally. Matthew: not protected, you may be working at a company that you just it's not an option. Like if if your staging is not password protected or behind SSO or a secure domain, like you just can't use staging that way. So yeah. Corey Moen: Totally. And I I think the the last thing I'd say even to that is that definitely, you know, bigger companies or companies in the limelight or whatever have more of this pressure. But you could also think of it in the way that as more and more of the major the traffic on the internet is becoming agents, that it is constantly crawling. And if if if two, three years from now it's like 80% of the internet. Like that exposes more and more companies that before they might have just been okay publishing something knowing that like nobody right, no one will find it. Yes. Matthew: Yeah, 'cause no one's gonna find it. It's it's a it's a random hash URL, whatever, you know. Corey Moen: Where the internet is just filling with more and more scrapers, you know, generally. And so like less and less companies are going to just be able to get by by, you know, just hoping no one finds something while it's being tested. so yeah, I just yeah. Governance stuff I feel like is more important than ever before, no matter the size. So super interesting. Matthew: age instructions generation. Age instructions have existed. Now you can have the AI assistant generate those based on the existing site, and then you can edit those drafts and then push them live, which makes them available via the MCP. Corey Moen: Hmm. Was in the screenshot too, it looks like you can bind real things from the site like variables. Was that there before? Sick. Matthew: Yep. Variables, CMS collections, pages, like all that kind of stuff. So if you see the toolbar at the top, to the right of the format is that like circle with the dot and line coming out of it. That's the binding drop down. So you just click there and then add it to the page. Corey Moen: Mm. Mm-hmm. Super cool. Super cool. Matthew: Yeah. So you can see in this example, they're referencing the specific variables from the design system. Corey Moen: Ice. Matthew: Agent presence is just bringing agents into the multiplayer real time engine so you can see where they are on the site, you know, what page they are, especially now with MCP two point that it's headless, so you don't need the bridge app. So you can actually s visualize where those agents are if you're actually working, you or your coworkers are in the site at the same time. And it's just fun to watch the agent build too. Just see it work. You can just Corey Moen: Yeah. We Matthew: sit back and keep drinking your coffee like like I am. Corey Moen: An an Easter egg feature request is a short keyboard shortcut for a hand slap. The you know, the like it the cursor turns into a hand and you can just like agent get out of here. I'm editing this. Yeah. Matthew: To stop the agent from doing what it's doing? That's my branch. Get out. Okay. Okay. Corey Moen: For real though, like there's I think in general working with AI, I've had times where it's like starting down a path and then you know you're in chat or whatever you're just like, no, stop, stop. Like, same Matthew: Sure. yeah. Corey Moen: thing here. It's like be fascinating to see it doing something and you're like, No, don't do that. Matthew: Right. To be able to to stop it from here. I mean otherwise you gotta go back to your agent. Yeah. Corey Moen: Yeah, yeah. I'm sure on there is actually a way to do this. Yeah, yeah. But so funny. Matthew: Are we ready to get to the main to the main topic? And that is Webflow has announced a new platform that sits alongside today's Webflow classic, if you will, the Webflow you know and use, hopefully love today. That will still continue to exist and it is still a great fit for a lot of companies. For those companies that want to Adopt more of an agentic first workflow and work from a shared code base, this opens up a whole new world. essentially you can you can open up, let's say, an Astro or an X.js project on local files on your machine and just start start working with that site or that app And then we've talked about things like releases, assets, campaigns, all that kind of stuff will be brought here as well. so you can use Webflow's, you know, services, you know, products, you know, or you can use it with your own stack and mix and match. and it just it creates one place where you can bring your whole marketing stack, into a shared workspace where you can customize the views. that you have or as a team you have or different roles within the organization have. You have that same kind of governance controls and r releases controls that we're talking about. All of that in one place. It's customizable and you have your agents in here working together, whether it's Webflow agents, custom agents, pretty excited yeah Corey, if we remember back to 2023, we went to SF and we were part of a Tiger team that this is when AI was really just getting going and Webflow was at a turning point. And we got to be part of a small team that got to envision what the future of Webflow might look like. And one of the things that we really envisioned was this malleable professional workspace that you could mold to whatever your workflows were. where your teams were and you the interface can be whatever you make it, right? and then yeah, we're we're finally here. You know, the the Corey Moen: Yeah. Matthew: the agents, the AI has finally got to the point and web flow's gotten to the point, like we're ready, ready to do this for real. So we've got this source by web flow. Thoughts, impressions, questions, I opened up the floor. Ollie: I think when we were watching it like in the keynote, I th I could sense a lot of people were having like a culture shock, like, what what am I looking it like when IOS Matthew: Ha ha. Ollie: seven came out and people were like it wasn't necessarily cause it was bad, it was just cause it was com very different, you know, like a Matthew: Yeah. Ollie: a a solid departure from what's come before. and the way I've like tried to contextualize it for my dumb, dumb brain is by just calling it like cursor for marketing teams. It's a very crass definition, maybe, but like. Yeah. Matthew: I don't think it's that crass. I think it's it's a pretty good comparison. Corey Moen: I think that's good. Ollie: Yeah, it's just because it's you know it's all about basically allowing the marketing teams to interface with the code base directly, but with all the sort of sort of contextual like abstraction that's needed specifically for their job to to do that safely and effectively. So That's how I kind of am positioning it or when someone asks me to describe it, I will say it's really cool and then I'll say it's cursive for marketers. So Matthew: Mm. Ollie: yeah, it's it's cool. I'm interested to see how it's gonna look when it actually ships as well, between like what was announced and when it's ready. So yeah, very cool. Matthew: I understand a lot of people think it is for marketers, but it's actually for devs and designers as well. I think marketers are just currently underserved when it comes to these types of workflows or this type of Corey Moen: Mm-hmm. Matthew: act app to to work inside. so that's more kind of groundbreaking. But then it's also that kind of all three of those main personas, kind of the builders, which are the devs and the designers, and the practitioners, which are your marketers, your content editors. all being able to work inside the same workspace, but have it completely customized to what they need access to and how they work. so yeah, you're able to work directly with the code if you're a developer, you know, you can also prompt changes to the code, you know, if you have access to that, or you maybe you just have view only and you're just editing The possibilities, this is where it's kind of mind boggling is because the possibilities are kind of endless and open, but it it allows companies and agencies to create to create views and workflows just for them or then to be able to share even more broadly within the community and the marketplace. Corey Moen: one way that I've started to think about this is like at a very high level, Webflow Classic, Webflow Classic in the past, did this incredible job of creating using the same fundamental concepts and strategies and names and elements of traditional development in a visual way, right? Like divs are divs, and blah blah blah. I've said all this so many times. This is almost like a the modern era, the agentic era conception of that. A good example to me in this is Matthew: Mm-hmm. Corey Moen: agents. Like Derek is now not on here anymore, but Derek was on our last episode and was talking about how he has like multiple subagents in most of his main projects he works on. So like Harvest is like this Bible notes app he's been building for, I don't know, probably over a year now. And he has all these subagents. A lot of people don't understand. what that is. Like it's actually just a you Matthew: Mm-hmm. Mm-hmm. Corey Moen: know file that you're pointing at and giving it rules and guidance. But here this makes that visual. Like you go in, say I want a new agent, give it some instructions. Like now those same concepts you can use that our developers are using with the Gentech development outside of any of this tooling, you can use that in again a visual way that gives you controls that's a lot easier to understand and steer and get onboarded with than just figuring it out in raw code. so I think that's the part that is is interesting to me. And just like even in the realm of the it kind of like was shown briefly in the keynote and then right off is is there a screen in here or maybe it's on the yeah, we're on the landing page. The style panel, the webflow style Matthew: What Yeah, what do you mean? yeah. Corey Moen: panel lives on in sort. Matthew: yeah. Corey Moen: Like you you can you can inline edit and do little tweak style things. Yeah, I don't know if they're showing it anywhere on the page. Matthew: yeah, I'll play the video. Maybe we can get something in here. Corey Moen: For sure. there you go. Yep. Matthew: yeah, the visual direct manipulation that you're used to in Webflow is still here. It's just now Corey Moen: Yes, yes. Like Matthew: we're working directly on the code. There's no with the advances over the past ten years and the past couple years with AI, like we don't need the abstraction layer that Webflow Classic always provided. Corey Moen: Like a a way to even think about it and take this with a grain of salt, because this is just the current state I am in with building things or whatever, is I think there's a lot Matthew: Mm-hmm. there you go. Commission. Corey Moen: of people that are still in this state with agents of 80% of the work there's right there. Yeah, baby. Matthew: Yeah. Still there. Corey Moen: There's a lot of people that are still doing like 80% of the work with man manually, and then they'll use agents for 20%. Like the, you know, update this CMS or bind this thing or build this component. I think. some of the latest is is flipping that. I I am the other way. A agents are doing 80% of the work for me, but that 20%, maybe even 10%, I do still get pretty damn annoyed to have to like not, you know, tell an agent to like, nah, change this margin to that. And then that font size should be using that class. And like those little polish and dare I say craft and taste tweaks. you know that you make on for the last mile of a page or or a section of a site, I think still is so nice to do visually. And and this enables that, right? Like you can still have that styling tweak and polish, quick edit something directly on the page, text-wise, you don't have to ask the agent and wait for it to respond to edit something as simple as text. Like I think that's the nuance and balance that this does hit pretty well. where you can do most things, just have the agent build out sections and all that kind of stuff, but have those other tools like subagents, skills, workflows, all of that that can help yourself, but also your teammates or client be very easily steered where they're just like, make, you know, lazily, especially the less technical clients and such, make me an FAQ section with these FAQs. They're not going to specify Matthew: Mm-hmm. Corey Moen: like use these components and this container width. And you know, like they're not gonna do that. Like you need to set up the tooling so they can just ask an agent to do it and it will do it reliably and consistently every time. And so it's like about far more now than just like building pages and sections and using component strategies and all that, like to the to the tune of you, I mean, I don't know, y'all. I'm I'm having more and more qualms of like, do we even need frameworks like mast and some of that anymore? Like, I you know, e even the other thing that you just showed there in the video, is some of the views. It comes with like brand as a base view. Like, how Cory Runnells: Yeah. Corey Moen: long have we asked for a native style guide in Webflow? right? Like, like we we have these style guide pages built in just because of frameworks and things, but like a lot of those fundamentals, no matter your framework, are Evergreen, you need colors defined, you need fonts defined, you need voice and tone defined. So like I think that was also a really smart move they went with this was that. Matthew: Well, and it's it's building that. I mean, if you come in with an existing site or app, it's building that brand view based on what already exists. It's not it's Corey Moen: Totally. Matthew: not making it up or suggesting things. It's like here's what you already have and just presenting that to you in a way you can digest. Corey Moen: Totally. And when you think about this also in the in the realm of like future tense, you know, we've seen React and and now Astro and some of these latest frameworks that you can build your sites with while using source, but who knows what it's gonna look like in five years, you know. the point is that this is code agnostic now, and so you can have a little more confidence in knowing no matter how we approach building our site. This is, you know, the the higher level layer of of coordinating and managing it all that I think is definitely a little more apt to being, you know, standing the test of time, if you will. and then the last thing I'll say before I off, sorry, getting all the rants out, is Matthew: Yeah. And okay, go. Go go for it. Close it out. Get in. Corey Moen: I still think the easily missed but most valuable thing in this is views. The Matthew: Mm-hmm. Corey Moen: the thing that I think especially is interesting is Thinking about analytics and reporting and planning as like pretty major tenants of especially, let's be real, probably bigger sites, marketing teams, in-house teams, that kind of thing. But those three things used to be like go do a dashboard and Google Analytics or somewhere. And I think because of agents now, having context of data and analytics and your entire site's content and all that, we're now moving into this era of like. you know, personalize or on the fly reporting, like, hey, I want to know how this page is doing and what collections are we showing on this page again? And are we running into tests? And you can just ask an agent and it could spin up a view of those different things that you care about in that moment visually. Matthew: And it's looking at data that's not necessarily in source. You know, let's say Corey Moen: Totally. Matthew: you have Google Analytics, you have, you know, whatever sources, it's actually Corey Moen: Yes, yes. Mm-hmm. Matthew: pulling those together and creating those views for you. So you get the holistic place picture in one place. Corey Moen: Totally, totally. So I I just think there's it's so many different workflows around the sphere of marketing and websites that are all being disrupted at the same time. And I do think Webflow has done generally a really good job with this first approach of source that like really does seem like it has a lot of legs to grow and is is is you know capturing all those different things that are changing. but again, as you said, Ollie, we'll see. We're all fingers crossed, excited to get our hands on it. but yeah, I yeah, it'll be it'll be interesting. Matthew: Thanks, Corey. Cory Runnells: going back to Corey Moen talking about he's excited that the visual editor experience is still gonna be there in source. that kind of the the deeper things like our the power users or the builders are looking for. Matthew: I think people will be pleasantly surprised that even though it can be presented as like an agentic first way to work, like you don't have to work that way. And all the best pieces that you know in Webflow are are going to carry over. There's a there's a years and years of knowledge there on on how how we can best, display Cory Runnells: Yeah. Matthew: like UI for for for controls to give you both the granularity you need, but also the guardrails, so that you can do things safely. Cory Runnells: my dream wish list item would be or maybe I could hey agent spin up a view that just gives me the classic designer experience. Matthew: Well that's the thing. You can because you're working directly on the code, you can actually have the agent spin up any kind of control panels or like you said, like they showed in the demo, it'll actually insert UI controls directly in the chat if it's just like a one-off thing that you're doing. And you know, maybe you're working with if you're trying to create variants of something, I where you can see the node graph view. You can actually say, like, I want this is showing like image generation, but you can do this with components or anything or even a page and say, Hey, show me some different variations of how we could lay this section out, or you know, do some more creative animation here and let me try it out. So you have this kind of surface where you can work on things temporarily and then commit it directly to the code once you've landed on. And it's it's flexible out of the box. So you whatever your Martex stack is, you know, whatever your framework it is that you're building your code upon, whatever your CMS. you're using, you know, whatever you're using for analytics, all that kind stuff, you'll be able to mix and match all those things and it gives source that flexibility to change and grow as your marketing team does. Cory Runnells: It's all very, very exciting and it's gonna be fun to see to to see where we end up. Matthew: Yeah, it's a it's a new world and I guess we should kind of close this out by saying sign up for the research preview. And it is real. We've we've both used it as it exists. So it will be in everyone's hands as fast as we can safely do so. Everyone go sign up and help us build the future.