Plan a Reusable Preset System in Divi 5

By Interactive OnlinePublished Updated Editorial draft

Quick Answer

Use Divi 5 presets to save design decisions at the level where they belong. Element Presets apply to a matching element type; Option Group Presets reuse a group of settings; a default defines the baseline for new matching elements. Stacking combines presets, while nesting connects reusable settings inside another preset. Plan a small system with clear responsibilities before creating many variations.

A site becomes difficult to edit when five nearly identical buttons have five unrelated sets of colors, spacing and borders. A preset system should explain which choices are shared and which are deliberate exceptions.

Choose the right level for a decision

An Element Preset packages styling for a particular kind of module or layout element. An Option Group Preset packages settings such as a border or spacing group and can be used by elements supporting that group.

The December 26, 2025 publisher overview describes this model and default presets. Current Element Preset documentation explains reuse and stacking. Check the installed builder’s supported settings when following an older example.

A planning map for reusable Divi styles
Decision Useful home
Shared brand color or spacing value A named design variable, referenced where needed
Reusable border treatment An Option Group Preset for the relevant group
Standard service-card composition An Element Preset that draws on shared groups
Baseline for new matching elements A deliberately chosen default preset

Build one component before a full library

Choose a repeated element, such as a service card. List its common typography, spacing, border and image treatment. Create shared groups only where reuse would be useful, then connect them in the element preset.

Use names that describe purpose, such as Card Border or Section Spacing. A name like Blue Version 7 does not explain whether changing it should affect buttons, cards or an entire section.

Apply the result to a new element and an existing one. Compare the rendered pages, including responsive settings and interaction states. Existing local values may explain a difference; inspect the source of a property before adding another override.

Give variations a bounded responsibility

A compact card variation might change spacing while leaving typography and border choices with the base. Stacking can express that small difference. If two layers define the same property, inspect their order and the resulting value.

Nesting lets an element depend on shared groups. Editing one of those groups can therefore affect several element presets and the modules using them.

Document the impact of a shared edit

Before changing a widely used preset, identify representative uses, preserve the working configuration and test on a development copy. Check a dense page, a sparse page and a contrasting background rather than reviewing one isolated module.

Record the preset’s purpose and exceptions for future editors. Our ongoing development service can help maintain that shared system as new page types are added.

Key Takeaways

  • Put values, option groups and element designs at suitable levels.
  • Establish one tested component before expanding the library.
  • Keep stacked variations narrow and inspect conflicts.
  • Review dependent uses before editing shared presets.

Frequently Asked Questions

Is a preset the same as a design variable?

A variable stores a reusable value. A preset stores a collection of settings and can reference variables where supported.

Should every component have many preset layers?

Use layers when they express real reuse or variation. Extra layers without a clear responsibility can make the final styling harder to understand.

Can editing a nested group affect other components?

Yes. Check the components that depend on that group before changing it and verify their rendered output afterward.

Archives