Divi5 Builder

divi5-builder Claude skill

Build and edit **Divi 5** WordPress pages programmatically, over the WordPress REST API — from a compact JSON spec, using **native Divi modules** so pages stay fully editable in the Divi Visual Builder afterwards. No paid AI addon, no browser automation: just Node.js + the WP REST API.

It ships as a [Claude Code](https://docs.anthropic.com/claude-code) **skill**, but the two scripts (`scripts/wp.js`, `scripts/divi.js`) are plain Node and work standalone in any pipeline.

Other than the skill, it requires an MU plugin installed on your site and a "web-creds" file that you populate on your own machine with login info/password. And your site must use Divi 5 [will not work with Divi 4 sites].

⚠️ **Independent, community project — not affiliated with, endorsed by, or supported by Elegant Themes / Divi or Divi Plugins.** Divi 5 is evolving fast; the block format was reverse-engineered from real sites and verified live, but it can change between releases. Use on staging first. No warranty.

Why

Divi 5 stores pages as **WordPress block markup** (`` with a nested-JSON attributes object), not Divi 4 shortcodes. That means a page can be built by writing the right block markup into a post's `content` via REST. This tool gives you:

• scripts/divi.js — a spec → block-markup compiler. You author a small JSON page spec; it emits correct, builder-editable Divi 5 blocks (sections, rows, columns, and ~26 module types), with no inline CSS — everything via module settings + global colour/preset variables.
• scripts/wp.js — a secure WP REST client (pages, media, "Divi mode" meta, canvases, block inspection).
• assets/divi5-builder-rest.php — a tiny must-use plugin that bridges the few gaps the REST API leaves (see below).

Requirements

• A WordPress site running Divi 5 (5.x). Divi 4 sites use [et_pb_*] shortcodes and are not supported — wp.js divi-check will tel