Skip to main content

Drupal · November 10, 2026

How I built Content Builder

Why a Layout Builder field took years of design and weeks of building, and how I split the work with AI.

The idea came first

For years I wanted a field that edits like Layout Builder on the page but stores content like Paragraphs: flexible sections and columns, configured per field, with guardrails for editors. I started and abandoned several versions because the hard part was the architecture, not the code.

The design is mine

Content Builder builds on Layout Builder and the Field API instead of replacing them. It reuses Layout Builder’s sections, layouts, and blocks, adds section types that admins configure, and gives editors a WordPress-like experience with permissions and safeguards, without needing to know Drupal.

AI did the typing; I did the engineering

I used Claude Code to implement the design. Every change went through automated tests on three Drupal versions, static analysis, and my own review.

Review is where it counts

After 1.0, I found that adding a Content Builder field crashed on Drupal 11.2 and later. Drupal 11.2 had changed the add-field page to render the field’s widget before the field exists. I traced the error and directed the fix in 1.0.1.

About: Content Builder

  • AI
  • Claude Code
  • Drupal
  • Field API
  • Layout Builder
  • Paragraphs