Status: In Progress | Last Updated: May 28, 2026 | Stakeholders: James, Brian

The Problem We're Solving

Our current workflow — Figma designs → manual Bricks Builder translation → WordPress config → integrations → launch — is slow. The bottleneck is the manual, piecemeal translation of design into a CMS-driven site. The goal is to compress this into something closer to: Figma designs → AI agent builds it → client can edit → launch.

The most recent reference build is carrot.io, built entirely in WordPress + Bricks Builder from Figma designs.

Three Pillars Every Option Must Address

Every path we evaluate comes down to how it handles these three things:

1. Design-to-Code Pipeline — How do designs become working code?
2. Component System — How reusable and AI-consumable is the architecture?
3. Client Editing Experience — Can clients manage content without breaking things?

Path 1: Astro + Storyblok + Claude Code

Strongest candidate for our use case right now.

How It Works

• Astro — Static-first framework, outputs fast lightweight sites
• Storyblok — Visual headless CMS with real-time visual editor (feels like a page builder)
• Claude Code — Handles actual component development from Figma designs

Workflow

1. Design components in Figma (heroes, feature grids, pricing tables, CTA blocks, form sections)