Zero-downtime migrations, lessons from production incidents, dashboardless products, two upcoming meetups and more: Here’s what we covered in our latest Wix Engineering newsletter (October, 2026) Our AI Agent’s Design Looked Complete. 3 Runtime Checks Proved It Wrong / Yoav Abrahami Unnecessary APIs, over-engineered types, and an update flow that would leave stale data on screen. Written mostly by the agent itself (!), this account of designing for Wix’s Jay framework shows h

Introduction The component abstraction was designed to solve a human cognitive limit: a developer cannot hold an entire UI hierarchy in their head, so we learned to encapsulate UI once and reference it across files. But as AI agents increasingly write and maintain frontend code, that trade-off inverted. Agents struggle with multi-file indirection and slot composition seams, but thrive on local context they can see and verify in a single file. Components are the abstraction fo

Introduction Traditional dashboards force users to hunt through menus and learn complex interfaces before they can complete a simple task. We wanted to reverse that relationship. A merchant should be able to say: “Give customers 10% cashback on orders over $50.” From there, the app brings the relevant controls to the merchant, updates a live preview, and guides them toward publishing the configuration. Instead of navigating the product to find the right interface, the merchan

A user opens a support ticket. Their subscription cancellation stopped working. Somewhere inside a system with thousands of services and millions of users, something broke. Before we built Wix Orchestrator, here's what happened next: the ticket joined a queue. Days later, a support engineer picked it up, tried to reproduce the issue, contacted the customer to gather more context, and opened a Jira ticket routed to R&D. We triaged it, prioritized it against everything else on

No one wakes up excited to do a code migration. Deprecated libraries, method version upgrades, infra changes - they happen constantly, they affect dozens of teams, and they always arrive at the worst possible moment. A small technical change somehow becomes months of coordination. Slack threads. Priority negotiation. Manual tracking. Reminders. Many google sheets. For years, I managed cross-team projects at Wix, and migrations were always the hardest part. Not because they'r

The industry has a new obsession: AI skills. The logic seems bulletproof: if you want an AI agent to use your platform, you shouldn’t just give it raw documentation. You should give it a "skill", a curated, condensed, and optimized guide. This will allow the agent to perform tasks on your platform better than if they have to trawl through your docs. Skills are intuitive and trendy, but do they really provide agents with an edge over just using the docs and, if so, in what cas

Intro: The Limits of Prompt Engineering In modern AI agent development, many teams, including ours at Wix , start with an intense focus on prompt engineering , carefully crafting instructions for the LLM. We iterated endlessly on system messages and instruction sets to solve a core problem: our AI scheduling assistant was struggling with vague requests, such as "Schedule a meeting with Jake." This simple sentence triggers a surprisingly complex challenge. The system must iden