Eric Alli

How Agencies Are Migrating Client Portfolios from Elementor to Beaver Builder Without Breaking Production Sites After my recent post comparing build speeds between Elementor and Beaver Builder generated significant discussion, the most common question was: "How do we actually make this switch?" I've just published a comprehensive guide based on helping multiple WordPress agencies transition their entire client portfolios. Key insights from the article: Why the "rip and replace" approach fails (and what works instead) The 3-phase migration strategy that protects client relationships Detailed staging protocols and testing checklists When migration makes sense vs. when rebuilding is smarter Client communication frameworks that maintain trust The reality: Most agencies overestimate the technical risk and underestimate the operational planning required. The guide includes: Pre-migration assessment checklist Phase-by-phase implementation roadmap Testing protocols for each stage Client communication templates Post-migration optimization strategies This isn't theoretical - it's the documented process from agencies who've successfully made this transition. Full guide: https://lnkd.in/e8j7d7gZ For agency owners and WordPress developers managing client portfolios: What's your biggest concern about making a builder migration? #WordPress #WebDevelopment #BeaverBuilder #AgencyOperations

2

I’ve been playing with AI design tools for a while—initially as a way to move faster from intent to interface, and lately as something more. What caught my attention this past week wasn’t a new feature, but a pairing: Lovable running on Supabase. That detail shifted the frame for me. I care deeply about the front end—what our customers actually touch that improves their lives—and how my design teams can help define it faster, with greater clarity. But when tools like Lovable start partnering with infrastructure like Supabase, AI prompt design is no longer just about accelerating prototyping. It’s about collapsing entire layers of traditional ops and redefining where engineering effort gets applied. Supabase gives Lovable a real backend—live data, auth, persistence—without the drag of building scaffolding from scratch. Suddenly, you're not just seeing screens. You’re interacting with product-like behavior on day one. As a design org, that makes us force multipliers in a way that used to take a sprint cycle to even approximate. But the deeper shift is this: AI-native tools are no longer operating in isolation. They're forming ecosystems. Lovable on Supabase isn’t just a clever tech decision—it’s a systems alignment. And that alignment reshapes the economics of internal investment. You start thinking less about handoff and fidelity loss, and more about which tools can actually compose into one another in real time. That’s a very different kind of stack planning. It’s easy to say this is just where the tooling is headed. But to me, it feels more like a return to something I’ve missed. In the Web 2.0 era, people talked about this stuff—openly, publicly, and often imperfectly. We wrote about what it meant for tools to be modular, or for the web to behave like a platform instead of a destination. We imagined lightweight, expressive infrastructure that supported creativity instead of slowing it down. And we made decisions—sometimes naïve, sometimes visionary—based on what felt possible in that moment. This feels like one of those moments. We’re watching the scaffolding of product creation become intelligible across functions. The tools are increasingly fluent with each other. And instead of fighting for fidelity between design and build, we’re moving toward something far more fluid: a product surface that responds to intent, supported by infrastructure that doesn’t need a dedicated team to stand up. Call it Web 2.5 if you want. I’m less interested in the label than the posture. And right now, the posture feels open again—like the best tools are quietly building toward something bigger than themselves.

7

4 Comments

She's right that the old design process is dead, but I think she's underselling how fast it happened. Jenny says her September talk already feels outdated. That tracks. The gap between idea and shipped code is measured in minutes now, not sprints, and the tooling is only accelerating. The part about "seven agents constantly running" hits close to home. That's the workflow and when you're moving that fast, the bottleneck isn't design or engineering anymore. It's deciding what actually matters. Taste/signal is key. Jenny nails it: someone still has to be accountable for the decision. The three hiring archetypes are worth paying attention to. Especially the "craft new grad" one. People without baked-in process assumptions are adapting faster than senior folks who spent 10 years learning a workflow that just got obsoleted. Blank slate is an actual advantage right now. One thing I'd push back on: she says Claude isn't hireable as a designer yet. That's true if you're comparing to her deep specialist archetype. But for the execution layer she described, pairing with an engineer and polishing the last mile, it's closer than people think and if you're a designer/engineer its already here.

4

Starting simple with Canvas App filters 👩‍💻 I just published a walkthrough on how to create a gallery in Canvas Apps that can filter across different column types—text, dates, lookups, and multi-selects. This post is meant to be a simple starting point: how to handle blank filters, use the right property for each control type, and tie everything together into one clean formula. I’ll be sharing follow-up posts that dive into more complex filtering patterns, but if you’ve ever struggled with the basics of getting multiple filters to work together in PowerFX, this one’s for you. 👉 Read the full post here: https://lnkd.in/gXYH7sfS #PowerApps #PowerPlatform #PowerFX #Dataverse #CanvasApps

11

You can now try Gemini 3 Pro in Figma Make! What stands out to me from early testing is how useful Gemini is at exploring visual directions + ideas that designers can then shape with their craft. As AI models get better, Figma gets better and designers can go further. I share more thoughts in the attached video, but a few quick highlights below... Gemini 3 is excellent at 0->1 generation I've never seen a model do one shots like this so consistently! It's honestly very addictive... using it in Figma Make reminds me of play Civ 5 😅 Just one more prompt... ! A wide variety of styles and aesthetics With detailed prompting, you can consider different visual directions very quickly. This creates more understanding of the option space you're working in, giving you more time to deeply explore the path you want to take. It is a highly steerable model Of course we also tested Gemini 3's ability to work with Figma design files in Make. The model translates designs with precision + offers impressive interactions. Working with Design Systems I also wanted to see how Gemini 3 could work with Design Systems in Figma, in particular with Make kits and npm packages. Again, the results were impressive. It's great for exploring options and refining details while staying on brand. New possibilities I'm especially excited to see the creative possibilities skilled, high-craft designers will explore with models like Gemini 3 + Figma Make. Additionally, these types of tools help non-designers express ideas at higher fidelity — bringing new perspectives to the design process. If you want to try Gemini 3 in Figma Make, go to "Settings" in the upper right and click "Experimental models." Then toggle it on. Have fun and please let me know if you create something cool!

2,829

83 Comments

The design-to-code handoff is one of the most expensive gaps in enterprise software development. Weeks of engineering time spent interpreting Figma files, reconciling spacing math, and rebuilding what designers already specified. On March 30, join Aditya Karra, Blitzy's Founding Designer, and Ben Bergerson, Senior AI Solutions Consultant, for a walk thru of Blitzy native Figma-to-production capability. No prototypes. No Refine PR. Production-ready code. - Every design token read before a single line of code is written - Responsive output across five viewports from one desktop frame - A new feature integrated into an existing codebase, brand-aligned, checked directly into the repo Designers and product teams can now move at the speed of design. Come see what that looks like in practice. Register with the link in the comments. March 30 | 12pm ET | Free with live Q&A #Blitzy #Webinar #Figma #Platform40 #FrontendDevelopment #EnterpriseAI #ProductVelocity

29

1 Comment

The classic design process is evolving and fast. For African tech innovators, this is a wake-up call: the way we build products, design interfaces, and solve problems is changing globally. Leveraging AI, thinking beyond traditional processes, and embracing new design archetypes could be the key to creating world-class products from Africa. 🌍✨ Tech is no longer about following established playbooks, it’s about adapting, experimenting, and innovating faster than ever. #AfricanTech #Innovation #Design #AI #ProductBuilding #FutureOfWork

1

📱 Responsive Navigation Menu Built a mobile-first navbar that gracefully collapses into a hamburger menu 🍔 using CSS Grid and Media Queries. Accessibility and adaptability at its best ✅ Code N Career Inc 🧠 Learning: Responsiveness isn’t a feature — it’s a necessity. #ResponsiveDesign #CSSGrid #WebDevelopment #UIUX #TechInternship

42

2 Comments

Quick summary of our live stream: "Send Data from Drupal to n8n and Make via Webhooks" In this stream, we cover: - Sending form submission data from Webform using webhooks. - Triggering webhook requests with the ECA module. - Accepting and processing incoming webhooks in n8n and Make. - Building basic workflows in n8n and scenarios in Make to handle incoming data. Links below ⬇️ #drupal #webhooks #n8n ~~~ ♻️ Please repost and follow. 📧 Join our newsletter; link in the first comment.

33

1 Comment

I maxed out my Supabase and Vercel free tiers. Instead of upgrading to a Pro plan, I built my own version of that. From scratch. 🤓 If you've ever bought a hosting package, you've probably seen that browser-based control panel where you set up your domain, create email accounts, manage databases. That's usually cPanel. With Claude Code I put together a full self-hosted control panel running on my own Hetzner server. 23 modules, one interface: ▸ Domains, DNS, SSL automated ▸ Database management with a built-in query editor ▸ Deployment pipeline (git pull, build, live) ▸ Live monitoring, logs, backups, scheduled tasks ▸ A full terminal running directly in the browser ▸ Multi-user access with role-based permissions ▸ Authentication with two-factor login (2FA) What made it actually work wasn't just the AI though. I set up shared files that multiple agents can read and write to, so they always know what's been done and what's next. The documentation gets updated in Notion automatically by Claude Code after every session. Same for the backlog: every feature listed in technical terms, plus a plain-English explanation 😅 so I always know exactly what was built and what's still missing. Not just "AI wrote my code" but a system where agents collaborate, document, and hand off context like a real team. And the thing I appreciate most: I now have one server that can run as many projects as I want. No per-project pricing, no usage limits, no platform deciding what I can or can't do. One fixed monthly cost, everything under my own control. Hitting that free tier limit might have been the best thing that happened to me. The foundation is set, the infrastructure is in place. From here I can just focus on building. Next up is still a native iOS app, so that one isn't going anywhere. 😉

2

How to use Claude Code better for designers: ⚡ I went to an event about using Claude Code and wrote down these tips. Get Claude to interview you about your project: A 10 min interview with Claude is better than starting from scratch. Ask Claude to interview you so it gets all the context before you begin. Using Plan Mode: Use Plan Mode to plan out your projects before starting. Most of engineering is logic, not syntax — Plan Mode forces you to think through the flow before building. Figma MCP: Use the Figma MCP to let Claude “inspect” your design files directly. It reads your Auto Layouts and design tokens to generate production-ready code that actually matches your mocks. It’s not a “one-click deploy,” but it eliminates the design-to-code translation error. Superpower Plugin: Use the Superpower plugin to brainstorm architectural approaches — great for when you’re stuck and want to explore a few different directions before committing. CLAUDE.md file: Use the CLAUDE.md file to set up your project — it acts as your source of truth. Claude will read this at the start of every conversation. Desktop App: A lot of people don’t know they can use the desktop app with Claude Code. Use it if you want to see previews of your design while using the terminal. #Claude #Claudecode #vibecoding #vibedesigning

713

23 Comments

Anthropic recently shipped Legal Skills for Claude Desktop's Cowork, which triggered a market selloff. We ran its contract review feature against our own custom, legally engineered pipeline. The SaaS contract, playbook, and model (Opus 4.6) were all the same. The results were not: - Findings: 222 vs. 18 (12.3x delta) - Track changes applied to DOCX: 52 vs. 0 - Quantitative risk score: 93/100 vs. "CRITICAL" (a label, not a number) - Market benchmarks with percentiles: 12 vs. 0 - Comparable contracts analyzed: 4 vs. 0 - Deliverables produced: 7 vs. 1 The pipeline also produced a send-ready negotiation email, a strategy report with 10 priorities each with target/fallback/walk-away positions, 8 anticipated pushback scenarios with prepared counters, 15 talking points citing market data, and analytics with risk scoring, playbook alignment, and market percentile benchmarks for every major term. That said, Claude Desktop's output, while narrow, did correctly identify the 8 most dangerous provisions from the Provider's perspective: liability cap carve-outs, MFN pricing, escrow, uncapped indemnification. For a 5-minute investment, that's genuinely impressive. But even here, the depth gap was critical and obvious. Only the pipeline connected Section 13.3(f), which carves out insurance-covered losses from the cap, to the insurance requirements in Section 16. The practical effect: Provider's own insurance policy limits become the real liability cap, not the negotiated number in Section 13. You negotiate a $1M cap. You carry $10M in cyber insurance. Your actual exposure is $10M. A single pass reads Section 13 and Section 16 independently. Sixteen specialists cross-referencing each other catch the interaction. The same pattern repeats throughout. A 5-day outage simultaneously triggers SLA credits, DR termination, escrow source code release, and unlimited liability — a cascade across four sections. Three separate payment withholding mechanisms plus an express prohibition on service suspension effectively eliminates revenue protection. These mechanisms are not an accident. They're a coordinated conspiracy woven into the contract. And only AI specialists, working in parallel and synthesized together, are built to find it. This is our fifth controlled experiment. The pattern holds across drafting, triage, legal research, redlining, and now contract review. The model is not the product. The architecture around the model is the product. If you want to see what that looks like for your legal work: Taylor Legal Engineering, LLC. Full interactive report with methodology, pipeline architecture, and all comparison data: https://lnkd.in/eyiaXcdd #LegalTech #LegalEngineering #AI #ClaudeDesktop #ContractReview #LegalAI #LegalOps #MultiAgentAI #SaaS

25

4 Comments

This is super interesting and especially relevant right now. AI is reshaping product design, development, and engineering at an unprecedented pace. Many of the assumptions and practices we relied on are being disrupted, and we need to adapt quickly.

11

How do you get the benefits of a full redesign for your #Drupal site without spending the money for a full redesign? Look at it like this: Your website is like the car you bought yourself 3-4 years ago. Sure, you might *want* a new car, but you don’t want to *pay* for a new car. You want that thing to last for 10 years while staying fresh and helpful and without breaking down every month. You need: - Regular oil changes and maintenance - Patches for flat tires - Touch-ups on the paint - Full car detail and maybe a ceramic coat to make it feel like new again You don’t necessarily need: - The newest model - New upholstery - A complete repaint We recently worked on a #Drupal design at Bright Plum, Inc. - A white-glove, certified Drupal support shop refresh that: - Found a design language that matched their vision - Reimagined their existing content within that framework - Focused costs on the features they actually needed - Delivered a clean, professional look that gave them confidence The client got a #Drupal site that feels new without the six-figure price tag of starting from scratch.

4

In the AI era, how may teams are efficiently creating low quality experiences and without coherence of connected systems? Love this framing:”Focusing on Quality: Efficiency is a solved problem. Now we use the system to bake in high-level craft and education.” #DesignSystems #Design #AI

🌵Latest work for Anima, the biomimicry studio, a venture studio dedicated to nature-inspired innovation. They bring together an experienced team with deep expertise in biomimicry, AI, design, business, and finance to help founders take their ventures from 0 to 1. We partnered with their team to build a unique 3D universe, inspired by organic life and blended with laboratory and AI experimentation. We then designed an immersive website that highlights the art direction while preserving the same atmosphere and vision. Explore their universe → anima.ai Huge congrats to everyone involve Anima team : Sandra REY Alex de las Heras Branding : Clara Hevia Aranguren 3D : Beaucoup x Aurélien Thomas Website : Beaucoup

168

24 Comments

Just got a preview of MagicPath's new Figma integration… 2026 is about to close the entire loop on design and code. From the code quality to the pixel placement - this is the snappiest loop I’ve ever used. Not exaggerating. I think Pietro Schirano just figured it out.

157

11 Comments

Jenny Wen (design lead for Claude) on Lenny Rachitsky podcast: Her main point: The old design process is dead. Engineers move too fast. Fully agree....we have experience this first hand internally. Every tool that enabled this speed was built for engineers. Some very technical PMs and designer are trying to adjust (aka hang-on) but the bottleneck has moved....and we've been cooking up just the solution get the entire team up to speed.

12

1 Comment