Overview

Took two new Resources Hub components from Figma to production in WordPress using AI tools, with no engineering support. It was part of the Employment Hero 2.0 work to surface content by relevance.

Context

The hub was moving away from one long blog feed. The designs were ready, but engineering was committed elsewhere, and the hub runs on WordPress, not the product stack.

Insights

AI tools change who gets to ship. A designer can validate a hypothesis in working code before asking engineering to commit to it, and ship independently when engineering's attention is elsewhere.

Resources Hub design exploration: component specs and layer properties in Figma Dev Mode Resources Hub design exploration: component specs and layer properties in Figma Dev Mode, dark mode

Problem

Two interactive components still had to go live. They needed to match the design system exactly and work within WordPress's constraints, not just look right in Figma. Without them, the redesign would ship missing its most useful parts.

Solution

Ran a three-step workflow: pulled exact specs from Figma Dev Mode, prototyped the interactions in v0 and Figma Make, then used Claude to combine the specs, prototype code and WordPress constraints into vanilla JS and HTML. Reviewed every pass against the design system and refined it until it matched.

AI worked best as a translator between tools, closing the gap between design intent and shipped product.

Visit site ↗