Russell Anderson

I build the systems that make a help center work, and for the last few years I have built the AI that runs on top of them. Nearly a decade at Wix carried me from the support phones to senior editor and my team’s AI lead, and the through-line has not changed: Absorb unfamiliar software quickly, then make it plain enough that anyone can act on it. I am an artist by degree and an engineer by mindset, which is why I care as much about how content is structured for retrieval as about how it reads.

On the content side, I grew the Wix Answers help center from roughly 100 articles to more than 500 over three years. I was the sole knowledge base writer for Wix CMS for three to four years, one of the platform’s most technically complex areas, and I have been the sole owner of Wix Vibe documentation since it launched in August 2025. Back in 2021 I rebuilt Wix’s main support contact page around a language model, mapping real user utterances to the intent behind them so the page could route people itself. Years on the phones and in tickets are what made that possible, since the words a user reaches for and the problem they actually have are often different things.

Since 2026 my focus has been the layer underneath the articles, the structure that decides whether the right answer comes back at all. I build agents as Claude skills whenever a recurring need surfaces, shipped through code review into a shared company repo. One compresses 50+ pages of style guidance into a single skill and was the most-used skill in my team’s August usage poll. Another is a canonical lookup table of 169 UI icons so agents stop guessing images. A third converts Markdown drafts into our internal knowledge base backoffice, scoped deliberately to drafts and never to auto-publish.

Other recent work: I migrated first-steps content for 48 products in three days after diagnosing that our project board was silently stripping hyperlinks out of the steps our agents read. I verified 166 categories of a platform migration by having Claude drive my browser through checks I first ran by hand, and the findings changed the migration sign-off. I took second place at Wix’s first company-wide AI hackathon. I run workshops and recurring open office hours that moved a globally distributed writing team toward daily AI use, and I persuaded our Claude admins to change Enterprise account defaults so writers who are not developers could actually use the tooling.

I work with AI as a co-pilot: I decompose business requirements into tasks a model can implement, then validate that the results hold up. I am looking to own a knowledge system as the whole job rather than as a fraction of one.