My portfolio is live! I designed and developed a landing page in @webflow, animated with @greensock, and structured using @finsweet's Client-First to showcase my work. It's a simple, clean space that reflects both my design and development style. Since many of the best projects I’ve worked on are under NDA or done "white-label" in collaboration with other professionals and agencies, the links to current projects will be updated soon. The portfolio will continue to evolve as I add more projects, the goal is to keep it real and highlight work I’m truly proud of. Excited for what’s ahead as I keep refining my craft and delivering more value through my designs. [🔗 Link in the first comment]

I came away from WebflowConf 2026 feeling more optimistic about where @webflow is heading. That doesn't mean I don't understand the skepticism. AI is changing the way we build at an incredible pace. New tools are showing up constantly, interfaces can be generated in seconds, and the distance between an idea and a working product is getting shorter. Naturally, that changes expectations, including the expectations people have of Webflow. But after watching this year's announcements, I found myself thinking that maybe looking at Webflow only through the lens of its direct competitors misses part of the bigger picture. I've been experimenting with this myself. Recently, I built an AI workflow connecting the Figma MCP and the Webflow MCP through Claude. What interested me most wasn't simply how much faster AI could help me move from one step to another. It was the possibility of reducing the friction between those steps. Instead of treating design, content, development and production as completely separate environments, AI can start working across them with more context. And I think that is where things get really interesting. The announcements around Source, Campaigns, AEO, MCP and AI agents suggest that Webflow is exploring that broader shift as well. Not just adding AI to existing workflows, but questioning how those workflows might evolve in the first place. Of course, there is still a lot to figure out. The competition is moving fast. Some tools will be better at specific parts of the process. And not every new feature or direction will necessarily be the right answer for every team. But I don't think the right way to look at this moment is to ask which tool can generate something the fastest. As AI makes building easier, the questions around context, collaboration, quality, brand and business outcomes become even more important. From what I saw at WebflowConf, I feel like Webflow and its team are thinking seriously about that. And considering how much of this space is still being defined, I think there is still a lot more to explore. Webflow has spent years talking about the importance of community, and that community has played a meaningful role in getting the platform to where it is today. As the company moves into its next chapter, I hope that relationship continues to be treated as more than part of the story we tell about the past. Technology will evolve. Tools will change. But communities are built over time. Webflow has always understood the value of that. I hope it continues to lead with it.

I just published Figma → Claude → @Webflow: an AI implementation playbook, a practical, step-by-step look at how I’m using Claude Code + MCP to turn Figma designs into Webflow builds. I’m also sharing the Claude Skill I built for the workflow, so you can take it, inspect it, adapt it, and make it your own. This started with a LinkedIn post that got a lot more attention than I expected. Quite a few people asked me to share the actual process, so I decided to document it properly. The article walks through the workflow, what I learned along the way, and why simply connecting AI to Figma and Webflow is not enough. The playbook and Skill are free. More importantly, I hope this encourages more people in the Webflow community to share their own workflows, experiments, and lessons. The more knowledge we share, the better the community gets. Article + Skill → mattvidal.works/blog/figma-t…

I can finally say this with complete confidence: the @figma → @claudeai → @webflow MCP workflow is working beautifully. With the Client-First skill I built, I needed just one prompt to get the entire page implemented with virtually no errors. And it’s worth mentioning that even CMS-driven pages become insanely faster and more pixel-perfect with this approach. This is honestly next-level. Amazing work, Webflow team!! I’m really excited to see what’s coming over the next few days 😂