Appearance
Standard Operating Procedures
Step-by-step procedures for setting up a Divi development environment and building Divi Extensions and modules.
Setup
| Procedure | What you'll do |
|---|---|
| Divi Development Environment | Install Docker, NodeJS, Yarn, and gettext; pull the official Divi development Docker image; bring up a local WordPress with Divi installed. |
Extension build path
| Procedure | What you'll do |
|---|---|
| Create A Divi Extension | Scaffold a new Divi Extension plugin using create-divi-extension, install dependencies, and run the build watcher. |
| Create A Divi Builder Module | Define a module's PHP class, JSX React component, settings, and CSS — then register it inside the extension. |
| Create A Custom Field For A Module | Add a brand-new module setting field type that doesn't ship with Divi out of the box. |
What "SOP" means here
An SOP is a procedure you can follow top-to-bottom to get a known good result. The pages in this section are oriented around an outcome ("I want a working Divi Extension") rather than a single concept. The conceptual reference for individual settings, hooks, and field types lives under Modules, Hooks, and Code Reference.
Where to start
If you've never built a Divi Extension before, follow these in order: