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 😂

I’m a Webflow Awards finalist! Nominated for Educator of the Year. And honestly, a nomination like this only happens because people actually watch the tutorials, take the courses, ask questions, share my work, and keep me excited about teaching @Webflow. So: thank you!!! 🥹 And if you think I deserve the title, voting is open until August 8.

Looking forward to seeing what’s next, man. You’re one of the most inspiring people I’ve ever come across in this community. God bless your journey.

CodeTV's latest Web Dev Challenge is live. Watch 3 teams race the clock to build the most creative landing page possible. Think you could've done better with the same stack? You've got until July 31st. Build with @astrodotbuild + @greensock, deploy to Webflow Cloud. Three winners get a Webflow keyboard, GSAP swag, and a keyframers patch. Join our hackathon wfl.io/3SFZD1P

GOD WOULD NOT PLANT A DREAM IN A MAN INCAPABLE OF REACHING IT.

Focus beats intelligence. Consistency beats intensity. Action beats intention.

The portfolio I never launched. Almost two years ago, I designed and developed the portfolio shown in this video. It never went live. For a long time, I saw unfinished projects as wasted effort. Now I see them differently. Many of the projects that shaped how I design, build, and think today never received a single public update. This portfolio happened to be one of them. It never launched. But parts of it are probably still present in almost everything I build today.

The design led me to code before I even realized it. I've been a little quieter lately, mostly focused on client work at LenkerLabs, studying, mentoring Webflow students, and building. One of those experiments turned into the project below. It started as a solution to a problem I was facing myself, but after talking to people across different industries, I realized it could be useful to far more people than I initially imagined. A few years ago, I thought the hardest part was having good ideas. Today, it feels like the hardest part is deciding which one to build first. Still not ready to share all the details, but I'm genuinely excited about where this is going.

If there’s one person who’s pushed the boundaries of what’s possible with Webflow Interactions, it’s @victorwork_ ⚡️ Victor's responsible for creating some of the most beautiful sites on the internet, and even took home the win in our Interactions with @greensock community challenge 🏆 His work has inspired an entire generation of builders, and now he’s breaking down his process in a FREE interactions course, supported by the Webflow Collective Fund. If you want to create experiences that feel polished, dynamic, and unforgettable, learn from one of the best in the game. Check out the course → wfl.io/4nDaVyW

Is @webflow becoming an AI-first building environment? After testing Webflow MCP with Claude, I started to see a different level of capability. In this video, the sections you see were created entirely by AI from screenshot references. What stands out isn’t just the speed, but how the structure follows Client-First logic with a level of organization that usually takes time to build manually. One thing I learned from Alka, my tech lead: if AI can handle structure, naming, and layout with this level of consistency, then the role shifts away from assembling and toward defining systems, constraints, and direction. The build becomes a reflection of how well you think, not how fast you execute. If Webflow is moving in this direction, it may stop being just a visual development tool and start becoming a system where the quality of your input determines the quality of the output.

Becoming a @webflow Developer opened a career path I hadn’t fully imagined before. Yesterday I joined a live session with the Horizontes community (from Brazil 🇧🇷), led by @BrunoCorazza , where we talked about becoming a Webflow Developer and building an international career. Hearing the questions from people in the community made me remember when I was at the beginning of this path, trying to understand what was actually possible. What I’ve learned over time is that sometimes a tool can be the starting point for something much bigger. You begin by learning how to build websites, and little by little you realize that the skills you’re developing can connect you to opportunities far beyond where you started. For many people, Webflow can be more than just a tool to learn. It can be the doorway to a completely different professional path, especially if you’re willing to keep exploring where it might take you.

Most design problems start appearing once a project needs to change. In my @webflow projects, one practice that consistently protects the structure is the heavy use of variables. Instead of hardcoding spacing, typography, or color values across dozens of elements, I define them once and let the system reference them everywhere else. What looks like a small setup decision at the beginning quickly becomes structural support as the project grows. Variables shift the mindset from styling pages to defining rules. When spacing scales, color adjustments, or typographic refinements inevitably happen, the change happens at the system level instead of through scattered manual fixes. The build stays coherent because the logic behind it remains centralized. Design tends to look static on the surface, but in practice it’s always evolving. And the projects that age well are usually the ones where the flexibility was designed into the foundation from the start.

Day 04 — 100 Days of Editorial Design – Project: Works Gallery Layout – Focus: Grid discipline, visual rhythm & typographic scale Powered by: @fastflowdesign

Day 03 — 100 Days of Editorial Design – Project: Paint & Coatings Company Hero Section – Focus: Visual softness, brand tone & typographic restraint Powered by: @fastflowdesign

Day 02 — 100 Days of Editorial Design – Project: Portfolio Hero Section – Focus: Scale, contrast & typographic dominance Powered by: @fastflowdesign