How damonsomu/better-adsmanager works
Project Type and Purpose
• This is a WordPress plugin (“better-adsmanager.php”) that provides ad management features (AdSense, DFP, image ads, AMP support).
• It uses the “Better Framework” (under includes/libs/better-framework) to generate admin panels, Gutenberg blocks, page-builder integrations, shortcodes, widgets, etc.
File Structure
Top-level components:
• Plugin root: better-adsmanager.php (bootstrap), functions.php
• Assets: css/, js/, templates/
• Includes/:
– dynamics/ (dynamic CSS injection)
– fia/ (rules engine configuration)
– options/ (settings panels and fields)
– shortcodes/ (PHP classes for ad shortcodes)
– widgets/ (widget classes)
– libs/better-framework/ (core framework modules)
Main Components
A. WordPress Core
B. Plugin Bootstrap
– better-adsmanager.php (registers hooks, enqueues assets)
– functions.php
C. Better Framework Library
– Admin-Page & Admin-Panel
– Field Generator (all form fields)
– Gutenberg Adapters & Blocks
– Page-Builder Integrations (Elementor, VC, KC)
– Shortcodes Manager
– Widgets Manager
– Taxonomy & Metabox Generators
– Content Injector & Utilities
D. Plugin-Specific Modules
– Dynamics (editor_css.php): dynamic style injection
– FIA (rule engine + JSON config)
– Options (settings pages + panel-fields)
– Shortcodes (class-better-ads-shortcode.php)
– Widgets (class-better-ads-widget.php)
E. Assets
– CSS (bam.css, admin styles)
– JS (bam.js, bam-admin.js, adsense-lazy.js)
– Templates (normal-adsense.php, normal-dfp.php, AMP variants)
F. External Services
– Google AdSense API / script
– DFP / Google Ad Manager
– (Optionally any other ad network)
Relationships & Data Flows
1. WordPress loads plugin bootstrap → registers hooks (init, admin_menu, enqueue_scripts).
2. Admin request:
• Hooks → Better Framework Admin-Page/Panel modules → renders settings UI
• Options saved → WordPress DB (wp_options / postmeta)
3. Content editor (TinyMCE / Gutenberg):
• Editor shortcodes & Gutenberg adapters → display ad blocks in editor
• Field-generator → populates control panels in editor UI
4. Frontend request:
• Hooks → front-end CSS/JS enqueued
• Shortcode / widget → query stored settings from DB
• Templates → render appropriate ad markup (AdSense/DFP calls)
• External scripts loaded to fetch/serve ads
5. Page-Builder integration:
• BF Page-Builder Adapters → map plugin fields to VC/Elementor modules
• Generates shortcodes/widgets under the hood
Architectural Patterns & Design Principles
• Modular plugin design (separate folder per feature)
• Dependency injection via Better Framework init files
• Single point of entry (plugin bootstrap)
• Use of WordPress hooks (actions & filters) as events
• MVC-like separation (settings UI vs. rendering logic vs. templates)
• Extensibility layers (page builder & Gutenberg adapters)
Diagramming Recommendations
– Blue rectangles for WordPress Core & DB
– Orange for Plugin-Specific modules (Dynamics, FIA, Options, Shortcodes, Widgets)
– WordPress → Plugin Bootstrap
– Plugin Bootstrap → Framework Modules → DB (read/write)
– Frontend → Templates → External Ad Services
– Admin UI layer
– Editor integration layer
– Frontend rendering layer
• Clear component labels (e.g., “BF Field Generator”, “AdSense Template”)