FUBAR
-
When evaluating Elementor’s claim that it provides a theme builder, it’s important to keep in mind that Elementor has evolved from a single page builder, where devs could easily modify both content, structure and style in a single editor.
But in trying to extend Elementor to a true theme builder, the authors completely ignored the very important concept of separation of concerns. As a result, they used a template-based architecture, which co-mingles content, structure and style.
The site settings, where you’d expect only style properties to be maintained, is only navigable from within a template, page or post – there’s a reason why all other frameworks (e.g. Bootstrap) isolate style properties from page structures.
If you modify site settings from within a page, Elementor places those settings in a default single page in its theme builder – and you’d never guess that the single page is where settings are hidden, unless you try to delete that page…
Further, except for colors, site settings are neither complete nor scalable, unless you want to write your own SCSS/CSS. But even then, Elementor does not expose its class structures, so you have to manually assign custom classes to each element on each page.
Finally, because of the co-mingling of content and style, global widgets and even templates have limited usability – you can’t create a global widget and assign text (or other content) to each instance of that widget.
Does all this sound confusing? It should – Elementor is a really confusing product to use.
You don’t put wings on a car if you want to fly from New York to LA – you build an airplane. Elementor’s theme builder on top of their page builder is like putting wings on a car.
The “new” Elementor is kludgy, unintuitive and difficult to maintain.
- The topic ‘FUBAR’ is closed to new replies.