I’m a developer based in San Diego. I’m a Forward Deployed Engineer at Article, a creative agency in Toronto, and I run Digital Anchor, a small web studio serving businesses in San Diego and Santa Barbara, grown almost entirely by word of mouth.

Before that I was CTO of a Southern California agency with more than 500 clients. My clients have ranged from solo practitioners and nonprofits to government services and multi-site platforms running hundreds of websites. That range taught me that every organization has the same problem underneath: too much repetitive work, too many tools that don’t talk to each other, and not enough time.

What drives the work

Making websites easier to live with. Launching a site is the easy part. The hard part is the years after: the update requests, the maintenance, the handoffs. A lot of what I build is about shrinking the distance between “can you change this?” and “done.”

Putting AI to work, not on display. I’m interested in AI that quietly does useful things: connecting WordPress to agents, automating the busywork, and giving people tools they’d never have had the budget to build.

Owning your infrastructure. I like knowing what everything costs and where it lives. I build on Cloudflare, self-host where it makes sense, and help clients avoid getting locked into platforms that don’t serve them.

Using the right tool. Most of my work is WordPress and Bricks Builder, but I’m just as comfortable with Astro, headless setups, n8n, APIs, and whatever else the job needs.

At Article, that looks like building modern WordPress stacks, AI-powered reporting, and systems that help a creative team ship faster. At Digital Anchor, it looks like migrations, rebuilds, site care, and automation for local businesses, plus large-scale work like reworking the mapping for a real estate platform serving hundreds of sites.

What I do for clients

• WordPress and Dynamic Data. Custom themes, blocks, and dynamic sites built on ACF, custom post types, and the REST API.
• AI and automation. Agents, MCP, n8n, and API integrations that take repetitive work off people’s plates.
• Modern stacks. Astro, headless, and Cloudflare when WordPress isn’t the right answer.
• Site care. Hosting, maintenance, security, and performance.
• Design and motion. GSAP, interactive storytelling, and design systems.

Teaching and community

I share most of what I learn in public. My YouTube channel has 50+ videos on Dynamic Data, WordPress, and the growing overlap between WordPress and AI, watched by tens of thousands of builders. I write about agents, automation, and infrastructure on this blog and on social media, contribute to the WordPress open source ecosystem, and co-organize the San Diego WordPress Meetup. I recently co-organized an AI builders workshop in Santa Barbara too. I do my best work around other people, so community has never felt like a side project.

From archives to APIs

Before I built websites, I studied history and Latin American studies, through my BA and into graduate work. It’s less of a detour than it sounds. Historians spend their time asking how information moves: who records it, who gets access, and how a new technology changes who gets to speak. The printing press did that five hundred years ago. The web did it again, and AI is doing it now. (It still delights me that the WordPress editor is named Gutenberg.)

That training shows up in how I work. I dig into primary sources before trusting a summary, I document everything, and I try to understand the people and context behind a project before touching the code. Studying Latin America also gave me a lasting appetite for travel, languages, and places with deep layers of history. When I’m not working, I’m usually planning the next trip, eating well, or digging through my music collection, heavy on ska and rocksteady.