ECS 4.0 — a full rewrite, built around modules.

ECS 4.0 is the version where Ele Custom Skin becomes a proper modular toolkit for Elementor. Instead of one growing feature surface, every capability now lives as a module that can be enabled only when a project needs it.

What changed

The core idea is simple: ECS should help you build more flexible Elementor sites without loading or exposing tools you are not using. In WordPress admin, each module can be toggled from ECS → Modules. Disabled modules do not load front-end JavaScript or CSS.

The module set

ECS 4.0 is organized around thirteen modules:

• Dark Mode Colours adds light and dark color values to Elementor Site Settings and generates CSS variables automatically.
• Container Layout extends Elementor containers with Flex, Grid, Slider, and Custom Layout modes.
• Loop Custom Layout arranges Loop Grid items inside ECS Custom Layout templates through placeholder widgets.
• Menu Responsive makes Elementor Nav Menu controls responsive per breakpoint, including dropdown behavior.
• Editorial Text adds a text widget with responsive inline image placement.
• Style Templates saves widget style presets and applies them across matching widget types.
• JSON PowerEdit lets you edit widget settings JSON directly from the Elementor panel.
• Responsive Container Layout changes container layout mode per breakpoint.
• Dynamic Repeater populates repeater widgets from posts, terms, ACF repeaters, or raw JSON.
• Color Schemes manages named global palettes.
• Font Schemes manages named typography systems.
• Alternative Site Logos swaps logos by condition.
• Custom Look & Feel bundles palette, typography, logo, and CSS into one conditional look.

Why module activation matters

On client sites, the biggest cost of a plugin is often not performance. It is cognitive load. Editors see controls they do not understand, developers inherit settings they did not create, and support becomes harder than it should be.

With ECS 4.0, a site can start narrow. Enable Dark Mode Colours for theme switching, Container Layout for layout work, or Dynamic Repeater for data-driven widgets. Leave everything else off until the project actually needs it.

Requirements

The documented baseline is WordPress 6.2, Elementor 3.18, and PHP 8.0. Elementor Pro is needed for workflows that depend on Pro widgets such as Loop Grid. ACF Pro is only needed when Dynamic Repeater uses an ACF Repeater source.

How to roll it out

1. Install or update ECS.
2. Open ECS → Modules.
3. Enable only the modules needed for the current project.
4. Test affected templates in Elementor and on the front end.
5. Document active modules before handing the site to the content team.

The useful part of ECS 4.0 is not just that it adds more features. It makes those features easier to reason about, which is what keeps large Elementor builds maintainable.