Quick Answer
Use a built-in Divi module when its fields and behavior fit the content. Consider a Module Group when arranging separate existing modules solves a specific layout constraint. Grouping creates an assembled layout; it does not automatically reproduce every feature of the module it resembles or create a new functional extension.
Name the limitation before rebuilding
The May 23, 2025 publisher tutorial demonstrated compositions resembling blurbs, pricing tables and testimonials. Its “build your own modules” phrasing refers to arranging existing parts in a group.
Identify the actual constraint: an image position, an unusual text arrangement or a content field the built-in layout does not expose conveniently. If the existing module already meets the request, rebuilding it introduces more elements to edit and inspect without a clear benefit.
Compare the maintenance tradeoff
Scroll horizontally to see all columns.
| Question | Built-in module | Assembled group |
|---|---|---|
| How is content edited? | Through the module’s supplied fields. | Through several child modules that need clear labels. |
| What controls the arrangement? | The supported module layout options. | The group and its children’s supported layout controls. |
| What behavior must be verified? | The configured module’s actual output. | Each assembled action, content relationship and any separately configured behavior. |
The official Group reference describes a container for modules and nested rows. Choose the smallest structure that solves the defined problem.
Build one representative comparison
On a working copy, preserve the original and assemble one alternative using approved content. Label the child modules so another editor can identify the title, description and action. Compare long and short text, missing optional information and narrow-screen stacking.
A price-shaped text layout does not calculate prices or implement a purchase flow. A testimonial-shaped arrangement does not supply permission or evidence for the quotation. Verify the required behavior and content separately.
Choose from the actual result
Compare editing effort, saved output, responsive behavior and keyboard access. Keep the built-in module if the composition adds complexity without solving the stated constraint. Record the reason when the group is the better fit.
For reusable card construction and dynamic data, our card Module Group guide covers those tasks. For shared styling roles, see the small design framework. Our WordPress website design service can help evaluate a specific layout requirement.
Key Takeaways
- Identify a concrete limitation before rebuilding.
- Account for the extra child elements and editing work.
- Verify behavior separately from a matching appearance.
Frequently Asked Questions
Does a Module Group create a new plugin module type?
The composition described here arranges existing modules inside a container. New extension functionality is separate development.
Should I recreate every built-in module?
No. Rebuild only when the additional control solves a real requirement and the maintenance tradeoff is acceptable.
Does a grouped price display create an order process?
No. Verify calculations, product data, actions and commerce behavior separately.

