How varioush/elementor works
Project type and purpose
• This is a monolithic, full-stack WordPress plugin (“Elementor Page Builder”) that provides a live, drag-and-drop frontend editor.
• It consists of a PHP backend that hooks into WordPress (admin screens, AJAX endpoints, database), a JavaScript frontend editor built on Backbone/Marionette, and a build pipeline for assets (Grunt/SCSS → CSS, ES5/JS module bundling).
File structure
• Top-level:
• elementor.php (plugin bootstrap & init)
• composer.json / package.json / Gruntfile.js (dependency & build configs)
• includes/ (PHP modules: admin, api, controls, widgets, templates, settings, frontend, compatibility, etc.)
• assets/dev/ & assets/css, assets/js (source SCSS/JS → compiled CSS/JS)
• tests/ (PHPUnit tests, bootstrap)
• Pattern: MVC in the JavaScript editor (models, collections, views, layouts, behaviors); modular PHP with separation by feature (controls, widgets, settings, API).
README insights
• Confirms WP plugin registering hooks, provides live edit via AJAX and iframe avoidance.
• Describes Template Library with local & remote sources (includes/template-library/).
• Relies on WordPress hooks & AJAX, no external microservices except remote template source.
Main components
a. WordPress Core
• Hook registration (actions, filters)
• Admin menu & editor entry point
• AJAX handler (wp-ajax)
• Database (wp_postmeta)
b. PHP Backend (Elementor Plugin)
• Bootstrap (elementor.php → includes/plugin.php)
• Admin module (includes/admin.php → control panel UI)
• API module (includes/api.php → REST/AJAX endpoints)
• Controls manager & controls (includes/controls-manager.php + /includes/controls/*.php)
• Elements & widgets managers (includes/elements-manager.php, /includes/widgets/*.php)
• Template-library manager (includes/template-library/…)
• Settings & system-info (includes/settings/)
• Compatibility & upgrades (includes/compatibility.php, includes/upgrades.php)
c. Frontend JavaScript Editor
• Backbone.Marionette application (assets/dev/js/editor/)
– Models (models/)
– Collections (components/template-library/collections/)
– Views & layouts (views/, layouts/panel/)
– Behaviors & utilities (behaviors/, utils/)
• CSS/SCSS for editor panel (assets/dev/scss/editor/, editor/panel/)
d. Frontend Page Renderer
• JS Handlers (assets/dev/js/frontend/handlers/*.js)
• Utilities (assets/dev/js/frontend/utils.js)
• Compiled CSS for frontend widgets (assets/css/frontend.css)
e. Build Pipeline & Dependencies
• Grunt tasks (Gruntfile.js) for compilation, minification
• package.json & composer.json for JS/PHP dependencies
• assets/lib/ third-party libraries loaded in appropriate contexts
f. External Services
• Remote Template Library API (source: includes/template-library/sources/remote.php)
• WordPress REST/AJAX endpoints
Relationships & interactions
• WordPress loads Elementor on init → registers admin menu and AJAX hooks → enqueues editor JS/CSS.
• User clicks “Edit with Elementor” → editor panel loads in iframe-less live view → Backbone app boots → models fetch data via AJAX to PHP API.
• User actions (drag, drop, config) → JS sends AJAX requests → PHP updates postmeta → returns JSON → JS re-renders.
• Template Library: Backbone models fetch from local (DB) and remote sources via API modules.
• On “Publish/Save” → PHP finalizes post content, persists configuration.
• Frontend page load → enqueues compiled frontend JS & CSS → handlers activate dynamic widget behaviors.
Architectural patterns & design principles
• Modular PHP by feature (SRP).
• MVC/MV* pattern on JS side (Backbone + Marionette).
• Build separation: dev source vs. compiled assets.
• WordPress plugin standards (hooks, filters, REST/AJAX).
• Extensibility: interfaces (includes/interfaces/), sources for templates, group controls.